After an event is identified by one of the event-detection mechanisms, it is triggered by one of the adapter-delivered event triggers. Event triggers can cause events to be processed immediately or in the future.
The function modules that
trigger events are described in the
following list.
- /CWLD/ADD_TO_QUEUE_AEP
This function module triggers events to the current event table for immediate processing.
- /CWLD/ADD_TO_QUEUE_IN_FUT_AEP
This function module triggers events to the future event table to be processed at a later time.
Note: Both functions are for real-time
triggering.
Current® event table
If the event is triggered in real-time, /CWLD/ADD_TO_QUEUE_AEP commits
the event to the current event table (/CWLD/EVT_CUR_AEP).
Specifically, it adds a row of data for the object name, verb, and
key that represents the event.
Figure 1. The function module adds a row of data to
the current event table
Future event table
If an event needs to
be processed at a future date, the processing described in the following
list.Figure 2
- A custom ABAP handler calls /CWLD/ADD_TO_QUEUE_IN_FUT_AEP with the event.
- The /CWLD/ADD_TO_QUEUE_IN_FUT_AEP module commits the event to the future event table (/CWLD/EVT_FUT_AEP). Specifically, it adds a row of data for the object name, verb, and key that represents the event. In addition, it adds a Date row
- The adapter-delivered batch program /CWLD/SUBMIT_FUTURE_EVENTS reads the future event table.
- If scheduled to do so, the batch program retrieves events from the future event table.
- After it retrieves an event, the batch program calls /CWLD/ADD_TO_QUEUE_AEP.
- The /CWLD/ADD_TO_QUEUE_AEP module triggers the event to the current event table.
Figure 2. How
an event is added to the future event table, retrieved from the table,
and added to the current event table
/CWLD/ADD_TO_QUEUE_IN_FUT_AEP uses the system date as the current date when it populates the Date row of the future event table.