Hi,
I have a program executed in background, which produces a bunch of consecutive documents for a set of Bulk Shipments -> TD Loading and TD Delivery Confirmation. To create those documents I use function modules 'OIGI_LOADING_CREATE' and 'OIGI_DEL_CONF_CREATE' - both from Industry-Solution Oil-and_Gas (IS-Oil).
In some cases these FM-s produces error messages (E-type) which cancel execution of the program and broke my flow-logic.
Below are few messages recorded in a job log for my task:
18.08.2005 15:56:41 Job started
18.08.2005 15:56:41 Step 001 started (program /PTRL/TAS_POSTPONDED_SYNC, variant , user name IMUTAFCHIEV)
18.08.2005 15:56:58 Shipment 180753 saved
18.08.2005 15:57:06 The plant data of the material 177 is locked by the user BMINKOV
18.08.2005 15:57:06 The plant data of the material 177 is locked by the user BMINKOV
18.08.2005 15:57:06 The plant data of the material 177 is locked by the user BMINKOV
18.08.2005 15:57:06 Job cancelled after system exception ERROR_MESSAGE
Both function modules are not designed to handle any exceptions, and in owr environment (4.6c) there is no documented system exception 'ERROR_MESSAGE' which to be handled in CATCH-ENDCATCH block.
Is there a way to handle this exception and to track the list of error messages produced by some FM into an internal table, log, whatever, as it is done in the log of the background job. I need to find a way write these messages in my log-tables and to proceed further with my flow-logic.
FYI: my program executes an RFC call to a remote system and retrieve a list of documents which need to be synchronized with R/3. I loose information, if the R/3 broke my flow-logic.
Any help would be highly appresiated.
Many thanks in advance.
Ivaylo Mutafchiev