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 do this, you must:
Fill the field application event for your process code's inbound method.
Enter a value in the inbound function module's table Return_Variables- note that Wf_Param must be filled as outlined in the following table, and Doc_Number is the same as your application object ID.
Assign the Workflow_Result parameter a value not equal to zero. Customers can use alphanumeric values beginning with Y or Z. In the example below the value 3 is used.
Wf_Param |
Doc_Number |
Parameter RESULT in the Event Container |
Continue_Objects1 |
1234 |
1 |
Continue_Objects2 |
1234 |
2 |
Continue_Objects3 |
1234 |
3 |
Continue_Objects4 |
1234 |
4 |
Continue_Objects5 |
1234 |
5 |
Parameter |
Value |
In_Update_Task |
" " update task not used "X" update task used |
Call_Transaction_Done |
" " |
Workflow_Result |
"3" |
Application_Variable |
" " (initial value, for example) |
Idoc_Status |
The table must contain three records with fields containing: |
Docnum |
Status |
4711 |
53 |
4712 |
53 |
Optionally the fields Msgid, and so on, can contain 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 serialization is not used |
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.