b.santos/abap-cheat-sheets
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update

Browse Source
This commit is contained in:
danrega
2024-12-02 09:49:17 +01:00
parent 23d6c43d52
commit 91d7033370
15 changed files with 458 additions and 148 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
08_EML_ABAP_for_RAP.md
View File

@@ -159,7 +159,7 @@ The following points cover RAP-related terms such as *RAP business objects* and
- The [global
class](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenglobal_class_glosry.htm "Glossary Entry")
of a behavior pool does not implement the behavior itself. It is
(initially) empty apart from the declaration and implementation part skeletons. The behavior implementation is coded in local
empty on creation apart from the declaration and implementation part skeletons. The behavior implementation is coded in local
[RAP handler
classes](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenabp_handler_class_glosry.htm "Glossary Entry")
and a [RAP saver
@@ -1101,7 +1101,7 @@ derived_type = CORRESPONDING #( some_other_type CHANGING CONTROL ).
#### ABAP SQL Statements with BDEF Derived Types
The ABAP SQL statements `INSERT`, `UPDATE`, `MODIFY`, and `DELETE` offer the [`MAPPING FROM ENTITY`](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abapmapping_from_entity.htmaddition) addition to handle BDEF derived types.
The ABAP SQL statements `INSERT`, `UPDATE`, `MODIFY`, and `DELETE` offer the [`MAPPING FROM ENTITY`](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abapmapping_from_entity.htm) addition to handle BDEF derived types.
```abap
"--------------- INSERT ---------------