Triggering an Application Event After Successful IDoc Processing
Any number of events can be triggered within the inbound function module by calling the Workflow "create event" function module; doing this gives you full control of the event’s parameters.
If you simply want to have an event triggered for your application object with a single parameter RESULT in its container, you can let ALE do this for you. An example where this is used is the message type EDLNOT, process code EDLN.
To let ALE trigger the event you need to
Triggering your application object event using ALE and Specifying a Value in the RESULT Parameter.
Wf_Param |
Doc_Number |
Parameter RESULT in event container |
Continue_Objects1 |
1234 |
1 |
Continue_Objects2 |
1234 |
2 |
Continue_Objects3 |
1234 |
3 |
Continue_Objects4 |
1234 |
4 |
Continue_Objects5 |
1234 |
5 |
How to let ALE trigger one of your application object’s events, and how to affect the value of the parameter RESULT in its container. How to fill the export parameters when processing packets of IDocs, when all the IDocs were successfully processed and an application object event should be triggered for each successfully processed IDoc. IDoc numbers 4711 and 4712 created application objects 1234 and 1235. In both cases the RESULT parameter in the event container is set to 1.
Parameter |
Value | ||
In_Update_Task |
" " Update task not used | ||
Call_Transaction_Done |
" " | ||
Workflow_Result |
"3" | ||
Application_Variable |
" " (e.g. initial value) | ||
Idoc_Status |
The table must contain three records with fields containing: | ||
Docnum |
Status | ||
4711 |
53 | ||
4712 |
53 | ||
Optionally the fields Msgid etc. can be filled containing the application’s success message. | |||
Return_Variables |
The table must contain the following six entries: | ||
Wf_param |
Doc_Number | ||
Processed_IDOCs |
4711 | ||
Appl_Objects |
1234 | ||
Continue_Objects1 |
1234 | ||
Processed_IDOCs |
4712 | ||
Continue_Objects1 |
1235 | ||
Serialization_Info |
Empty if not using serialization |