Dear all,
I'm facing some inconveniences when scheduling a background job. Let me explain you briefly the picture I'm having right now.
We are preparing an Unicode conversion in our system.
We scheduled yesterday a job for UMG_ADD_DOWNTIME_STEPS report. But, sadly, the job has been cancelled.
Reason?.
Control Framework: Fatal error - GUI cannot be reached
Internal session terminated with a runtime error (see ST22)
If you get into ST22 TX, you can read the following:
Category ABAP Programming Error
Runtime Errors RAISE_EXCEPTION
ABAP Program UMG_ADD_DOWNTIME_STEP
Application Component BC-I18-UNI
Date and Time 08.04.2015 04:07:52
In the source code you have the termination point in line 62
of the (Include) program "CL_GUI_CUSTOM_CONTAINER=======CM001".
The program "CL_GUI_CUSTOM_CONTAINER=======CP" was started as a background job.
Job Name....... "UMG_ADD_DOWNTIME_STEP"
Job Number..... 18033600
CALL METHOD SET_VISIBLE
EXPORTING
VISIBLE = '1'
EXCEPTIONS
CNTL_SYSTEM_ERROR = 1
CNTL_ERROR = 2.
CASE SY-SUBRC.
WHEN 0.
WHEN 1.
RAISE CNTL_SYSTEM_ERROR.
WHEN 2.
RAISE CNTL_ERROR.
WHEN OTHERS.
RAISE CNTL_ERROR.
ENDCASE.
So, in a first glance, seems to be as if the system would try to launch that program in background and, therefore, could not get the GUI. .
You may say: OK. Let's not schedule a job for it!. BUT, it should be executed when no one is logged in the system. But, would it work?.I'm not really sure!.
At this point, I don't have a clue about which- or what - can be the proper solution for this topic.
if you SAP gurus, have had this situation earlier and have solved it, it'd be really nice of you!
Kind Regards.
Raúl