Continue background job after encountering error message type A

[lmoc]

Hi Gurus,

I hope someone may help me regarding our requirement. We have a customized program that stops running upon encountering an error message with message type A. Due to the volume of data being processed by the program, we hope to have this message sort of skipped when encountered and let the program proceed with the execution especially when it is running in the background. Can this be done? If yes, how?

Thank you so much everyone! 🙂

[matt]

What do you mean "a customized program"? One you've written yourself?

[lmoc]

Yes, that is correct

[Sandra_Rossi]

Type A -> abort job (see ABAP documentation).

Try to not trigger one of type A.

Try to implement a status for the data (to be processed/processed) or to update a process date/time column in order to implement a restart logic (process only what is left).

[Carlos_Idiaquez]

Hi LM O,

As Sandra discribe, when you run your customized program you do this:

1. Collect information (a table)

2. Loop the final table (Line by line) and execute a process (Call function)

3. The function returns a message, success or error. Right now, the program stops if there is any error. You need to change the logic of the program. If the result of the call function is an error, continue with the next line of the table.

4. Bonus: You need a log report for the errors the program find. Each time the call function send and error, you can pass the IMPORT PARAMETERS of the FUNCTION to a table. With your new table, you can try to execute manually your function (TCODE or SE37) and analyze the message to understand what you need to avoid the error message. (It can be procedure error, master data or customizing).

[lmoc]

Thank Carlos. We'll look into this suggestion. By the way, the abort message we were getting is as per screenshot below, if relevant at all.

[Carlos_Idiaquez]

I found this SAP POST with the same situation:

https://answers.sap.com/questions/9224187/transaction-canceled-bs-703-error-log.html

You can try the approach of the post. I hope this help with your incidence.

[raymond_giuseppi]

If you got this error message BS 703, the history of some orders status is inconsistent

• Consider SAP note 300077 - Status management: Update termination BS703 and run the attached correction reports RBSVREP_JEST_JCDS (not RBSVREP_JSTO_JCDO) in order to fix the status management problem.
• You should also add some status check in your program and handle lock and wait.