Get Example source ABAP code based on a different SAP table
SAP LUW, RAP This example demonstrates how SAP LUWs are bundled in the context of RAP. The RAP artifacts are as follows:
Data model: The CDS data model consists of the root entity DEMO_CDS_UPDATE.
RAP behavior definition: DEMO_CDS_UPDATE defined in RAP BDL.
Behavior implementation: For the above RAP behavior definitions, there is an ABAP behavior pool (ABP) available: BP_DEMO_CDS_UPDATE. The actual implementation takes place in the BP_DEMO_CDS_UPDATE============CCIMP. The implementation is not relevant for this example.
ABAP_SOURCE_CODE DEMO CL_DEMO_SAP_LUW_RAP
ABAP_DESCRIPTION The example is divided into segments by switching the work process. An implicit database commit is performed at the end of each segment. Here, the work process is switched using the statement WAIT UP TO. In real programs, a switch of this kind can have many different causes . The example covers several ABAP_EML MODIFY statements that create and update RAP BO instances. COMMIT WORK statements trigger the saving of those RAP BO instances on the database. This entails closing an SAP LUW and opening another.
