CL_CRM_1O_EVENT - Business Transaction Event Handler

rdisp/max_wprun_time - Maximum work process run time   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Functionality

The event handler records entries according to registration, and when events are triggered it executes the registered callback functions either immediately, or after a delay.

Class Concept:

• A class instance exists for each of the subobjects in the CRM transaction which act as senders or recipients of events. These instances are created in the class constructor.

• Two data packages are derived from the registration information (CRMC_EVENT_CALL) for each instance. This only occurs once when loading the class.

• The GT_REGISTERED_EVENTS table is used when publishing events to quickly determine whether any recipients are registered for a specific event.

• If this is the case, the DO_ORDER_EVENT method is called for all registered instances = subojects.The instance called then checks with its second type of data package, called GT_REGISTERED_CALLBACKS, to see which callback modules are to be executed, or to be noted.

• The sets of business object types are implemented using binarynumbers of category EVT1O_BOR_GROUP. This means an efficient check can be made to see whether a specificset is a superset of another set, or since the event handler frequently requires it, whether at least one element of the set 'SET1' occurs in the set 'SET2' (that is, through the operation NOT ( SET2 Z SET1 ) ).

• The administration of old/new data occurs using the Ref To Data concept. In particular, the removal of data that is no longer required is left to the Garbage Collector.

• Although the implementation is directed towards the existing implementation of function group CRM_EVENT_OW, it is however fully independent of this.

• The OO-Events AFTER_CHANGE and so on, do exist, but are currently not used since performance testshave shown that is more beneficial to use the handler method DO_ORDER_EVENT to explicitly call the relevant instances.

• One advantage of using RAISE EVENT is that customers can insert their own handler methods simply and without the need for modification.

Example

Notes

Further information

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   General Data in Customer Master  
This documentation is copyright by SAP AG.


Length: 2472 Date: 20120526 Time: 103725     triton ( 136 ms )