Ansicht
Dokumentation
ABENDERIVED_TYPES_PID_ABEXA - DERIVED TYPES PID ABEXA
CPI1466 during Backup Fill RESBD Structure from EBP Component StructureThis documentation is copyright by SAP AG.
Using %pid
This example demonstrates the use of %pid with an
unmanaged RAP
BO in a late numbering scenario.
Data model
The CDS data model consists of the root entity DEMO_UMANAGED_ROOT_LATE_NUM.
Root entity:
Behavior definition
The CDS behavior definition DEMO_UMANAGED_ROOT_LATE_NUM is defined in CDS BDL as follows:
Behavior implementation
For the above CDS behavior definition, one ABP is created. The global class of the behavior pool is
BP_DEMO_UMANAGED_ROOT_LATE_NUM. The actual behavior implementation takes place in local classes that are defined and implemented in the
BP_DEMO_UMANAGED_ROOT_LATE_NUMCCIMP of the behavior
pool. See more details on the implementation in the example COMMIT ENTITIES BEGIN, END with CONVERT KEY OF.
Source Code
Description
Access with ABAP using EML
There is one modify request that creates several RAP BO instances. Here, the keys are left empty because a preliminary ID %pid is assigned in the course of the create method in the behavior pool.
With a COMMIT ENTITIES BEGIN ... END statement, which includes a CONVERT KEY OF statement, the instances are saved to the database table. The adjust_numbers method assigns the final keys to the instances. Using the CONVERT KEY OF statement, the key information for the instances is retrieved.
The output shows two tables for the mapping information. The first one includes the MAPPED EARLY mapping information that shows initial values for the key. The second one shows the MAPPED LATE mapping information including the final keys. Note that %tmp is not used and relevant in this scenario, hence, %tmp shows initial values. Another table shows the database table entries after the create operation.
General Data in Customer Master CPI1466 during Backup
This documentation is copyright by SAP AG.
Length: 3409 Date: 20240512 Time: 075411 sap01-206 ( 44 ms )
