Ansicht
Dokumentation
CRM_PS_CRMC_EVT_PHAS - Define SSE Event Processing Phases
RFUMSV00 - Advance Return for Tax on Sales/Purchases BAL_S_LOG - Application Log: Log header dataThis documentation is copyright by SAP AG.
In this IMG activity, you define the settings for the two types of event processing phases TRFT and DELAYED that are provided for Social Services Eventing. In the Sequence field, you can specify the sequential call of the phases in relation to each other and thus the sequence of the subscriptions contained in an SSE event.
Additionally, you can add customer-defined event processing phases. A possible example is an event processing phase that executes a subscription as a background job at a stipulated time. You need to implement the relevant phase driver classes for customer-defined phases accordingly. The following phase driver classes are provided for the two event processing phases delivered by SAP:
| Event Processing Phase | Phase Driver Class |
|---|---|
| DELAYED (delayed execution) | CL_CRM_EVT_PHASE_DRV_V2 |
| TRFC (immediate execution) | CL_CRM_EVT_PHASE_DRV_TRFC |
The phase TRFC (sequence 100) is executed before the phase DELAYED (sequence 200) in the standard system.
To add customer-defined event processing phases, proceed as follows:
- Define your own class with the interface IF_CRM_EVT_EVENT_PHASE.
- Implement both class methods IF_CRM_EVT_EVENT_PHASE~PROCESS and IF_CRM_EVT_EVENT_PHASE~INIT.
- You must first decide in the instance method PROCESS whether the different event processing phases are to be registered for later processing or whether the control is to be passed to the BRF within the event processing. When the attribute EVENT_PHASE_STATE has the values NEW and SPACE, the event processing phase is registered. With all other values for this attribute, the control must be passed to the BRF with CALL CL_CRM_EVT_PROCESSOR=>PROCESS_EVENT_BRF.
- For the registration, make sure that:
- The event processing status WAITING is set after the update of the event phase and the destination of the event processing phase is provided.
- The event processing phase driver for the registration creates a separate LUW for the event phase statuses.
-
You can, for example, schedule this in the background using the function module CRM_EVT_DRV_TRFC. This
function module must call the function module CRM_EVT_DRV_EVENT_PROCESS in the same system by means of RFC in order to be scheduled in a separate
roll area. The function module CRM_EVT_DRV_EVENT_PROCESS makes sure that the event processing is continued.
Alternatively, you can implement a batch run that executes the processing of the event processing phases at regular times. In such cases, the batch run acts as the dispatcher. A corresponding call to execute the batch run could look as follows:
-
CALL FUNCTION CRM_EVT_DRV_EVENT_PROCESS
STARTING NEW TASK task DESTINATION IN GROUP
group|DEFAULT] PERFORMING subr|CALLING meth ON END
OF TASK].
- The errors that occur during registration are handled.
- You initiate the processing of the registered event processing phases by means of a COMMIT WORK.
General Data in Customer Master Fill RESBD Structure from EBP Component Structure
This documentation is copyright by SAP AG.
Length: 4012 Date: 20240523 Time: 180621 sap01-206 ( 68 ms )
