cancel
Showing results for 
Search instead for 
Did you mean: 

Handle System-Exception ERROR_MESSAGE

Former Member
0 Kudos

Hello everybody,

the problem I want to solve looks as follows:

I have an ABAP report that is runnng as Batch-job (imagine a frame within certain reports run).

The program runs, as customised, the whole day continuesly as a batch-job . At customised intervals it checks some conditions and "submits" other reports also in the same instance of the Batch-job and waits for them to "return".

Within the process/stack of a submitted, second report any messages are posted in certain application logs (BALLOG).

Every message that usually would come to the display is suppressed by FuBa "DIALOG_SET_NO_DIALOG" and "DIALOG_SET_WITH_DIALOG". This is necessary because else the Batch-job would crash as you know.

However, in the endless downs of SAP there is a location where an "E" message raises and the whole job crashes with "A" because of system exception "error_message".

The second job crashes and aborts the whole job without returning to the caller report.

This happens maybe once in a week or once a month, very unregular.

The location is not to be found!

Is is okay that the submitted, second report aborts.

But it is absolutely necessary that the first report still runs after the second one crashed and the batch job still must stay active.

How can I prevent that the wohle job aborts?

Any idea (simple/complicated) is welcome.

Thanx

Frank

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Below is the SAP's say about this .

Programs called with SUBMIT ... AND RETURN or CALL TRANSACTION cannot propagate exceptions to the caller, because exception objects are bound to the internal mode of a program.

I doubt you can catch the error message.

Former Member
0 Kudos

Hello,

thank you for your answer.

I already found this out, because after the abort the whole program flow broke and did not return to the caller program.

Therefore I search for an idea to realize the abort in the called program, and so to take the chance to "ignore" the abort and to "return" to the caller Program.

Former Member
0 Kudos

Would you like to share how you did it? It seems like I have the same problem.

Thanks.

Former Member
0 Kudos

Hi,

in fact I still investigate if I have solved the problem.

In my case the reason seems to be related to my "long" running job and the changes of the "Operation Mode" during the job-runtime.

Old runtime settings were 00:05 - 23:50...

Current operation modes 06:00 - 20:00 daytime

20:00 - 06:00 night processing

New runtime settings are 06:05 - 19:50 and

20:05 - 05:50

The goal was that the job is not active during the change of the operation mode.

Until today it works fine...

Check OSS 35615 & 93732 and other similar related hints.

Answers (0)