Get Example source ABAP code based on a different SAP table
ID RAISE-ENTITY-EVENT • RAISE ENTITY EVENT ABAP_STATEMENT_EML
RAISE ENTITY EVENT
ABAP_SYNTAX RAISE ENTITY EVENT bdef~evt FROM tab.
What does it do? Raises a RAP business event. The statement can only be used in ABAP behavior pools. Since RAP business events can only be raised on the root node level, bdef must be the source name of the RAP BO. In the case of an extension using an interface, it must be the source name of the BDEF interface. The event evt that is raised must be defined in a BDEF or BDEF extension. tab is an internal table typed with the BDEF derived type TYPE TABLE FOR EVENT. The statement triggers the calling of RAP event handler methods. The data that is passed in tab always includes a RAP BO instance key of the root entity (component group %key). If the event is defined with parameters, tab includes the component groups %key and %param.
Latest notes:
RAP business events may be raised in an ABAP behavior pool in various contexts. However, it is recommended that they are raised during the RAP saver methods. In managed RAP BOs, it is recommended that a RAP additional save is specified using the syntax addition with additional save and raise the RAP business event in this additional save implementation.
If your use case requires raising a RAP business event outside of the behavior pool, you can create a separate local class in the behavior pool's global class. In this local class, you may create a static method where the event raising is wrapped in the implementation part. NON_V5_HINTS ABAP_HINT_END
ABAP_FURTHER_INFO
RAP BDL - event
Development guide for the ABAP RESTful Application Programming Model, section about RAP Business Events.
ABAP_EXAMPLE_VX5 The following code snippet demonstrates the implementation of a save_modified method in which RAP business events are raised for RAP BO instances that are created and deleted. The event for created RAP BO instances is defined without parameters in the BDEF. The event for deleted instances is defined with parameters. Therefore, the %param component group is contained in the BDEF derived type . In both cases, the internal tables (which have the name of the BDEF) contained in the deep structures create (which is of type TYPE REQUEST FOR CHANGE) and delete (which is of type TYPE REQUEST FOR DELETE) as components are looped across using iteration expressions with FOR to make sure that events are raised for all relevant instances. ... CLASS lsc_some_bdef IMPLEMENTATION.
METHOD save_modified.
IF create-some_bdef IS NOT INITIAL. 'Event defined in BDEF: event created; RAISE ENTITY EVENT some_bdef~created FROM VALUE #( FOR <(><<)>cr<(>><)> IN created_tab ( %key = VALUE #( key_field = <(><<)>cr<(>><)>-key_field ) ) ). ENDIF.
IF delete-some_bdef IS NOT INITIAL. 'Event defined in BDEF: event deleted parameter some_abstract_entity; RAISE ENTITY EVENT some_bdef~deleted FROM VALUE #( FOR <(><<)>del<(>><)> IN delete-some_bdef ( %key = VALUE #( key_field = <(><<)>del<(>><)>-key_field ) %param = VALUE #( par_a = '01' par_b = 'Item deleted' ) ) ). ENDIF.
ENDMETHOD.
ENDCLASS. ABAP_EXAMPLE_END
ABAP_EXAMPLE_ABEXA The example Local Consumption of RAP Business Events demonstrates the use of RAISE ENTITY EVENT statements. ABAP_EXAMPLE_END
