diff --git a/02_Structures.md b/02_Structures.md index d08d1c0..a4f2416 100644 --- a/02_Structures.md +++ b/02_Structures.md @@ -5,7 +5,7 @@ - [Structures](#structures) - [Introduction](#introduction) - [Globally Available Structures and Structured Types](#globally-available-structures-and-structured-types) - - [Creating Structures and Structured Types](#creating-structures-and-structured-types) + - [Creating Structures and Structured Types Locally](#creating-structures-and-structured-types-locally) - [Creating Structured Types](#creating-structured-types) - [Creating Structures](#creating-structures) - [Creating Structures Using Existing Structured Types](#creating-structures-using-existing-structured-types) @@ -56,7 +56,7 @@ Structures ... "Database table DATA struc_from_dbtab TYPE zdemo_abap_fli. "CDS view entity -DATA struc_from_cds_ve TYPE zdemo_abap_fli. +DATA struc_from_cds_ve TYPE zdemo_abap_fli_ve. "CDS abstract entity DATA struc_from_cds_abs TYPE zdemo_abap_abstract_ent. "CDS table function @@ -75,7 +75,7 @@ TYPES ty_struc_from_cds_ve TYPE zdemo_abap_fli. > - This cheat sheet focuses on locally defined structures and structured types. > - Classic [DDIC views](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenddic_view_glosry.htm) are not available in [ABAP Cloud](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenabap_cloud_glosry.htm). They can only be used as structured types in [classic ABAP](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenclassic_abap_glosry.htm). -## Creating Structures and Structured Types +## Creating Structures and Structured Types Locally The typical language elements for creating structures and structured types locally in an ABAP program are [`BEGIN OF ... END OF ...`](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abaptypes_struc.htm). They are used in combination with the [`TYPES`](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abaptypes.htm) keyword to create a structured type and the [`DATA`](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abapdata.htm) keyword to create a structure. diff --git a/04_ABAP_Object_Orientation.md b/04_ABAP_Object_Orientation.md index e3142f4..2833879 100644 --- a/04_ABAP_Object_Orientation.md +++ b/04_ABAP_Object_Orientation.md @@ -296,7 +296,7 @@ As the name implies, it is used to inherit from a visible [superclass](https://h -To define [abstract](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenabstract_glosry.htm) classes. These classes cannot be instantiated. These classes can contain both abstract methods and non-abstract methods. Abstract methods can only be implemented in [subclasses](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abensubclass_glosry.htm) by redefinition. See a simple implementation example [here](#excursion-example-interface). +To define [abstract](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenabstract_glosry.htm) classes. These classes cannot be instantiated. They can contain both abstract methods and non-abstract methods. Abstract methods can only be implemented in [subclasses](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abensubclass_glosry.htm) by redefinition. See a simple implementation example [here](#excursion-example-interface). diff --git a/08_EML_ABAP_for_RAP.md b/08_EML_ABAP_for_RAP.md index dca763d..b2e100f 100644 --- a/08_EML_ABAP_for_RAP.md +++ b/08_EML_ABAP_for_RAP.md @@ -2511,13 +2511,11 @@ ENDCLASS. ### Additions to ABAP EML Statements in ABAP Behavior Pools +There are a [special additions when using EML in behavior pools](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abeneml_in_abp.htm). + #### IN LOCAL MODE Addition -- There are a [special additions when using EML in behavior - pools](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abeneml_in_abp.htm). - One of them is [`IN LOCAL MODE`](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abapin_local_mode.htm). -- This addition can be used to exclude feature controls and - authorization checks. +- Using the [`IN LOCAL MODE`](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abapin_local_mode.htm) addition to ABAP EML `READ` and `MODIFY` statements can be used to suppress feature controls, authorization checks, and prechecks. - Consider the following use case: There is a field to display the booking status of a trip on a UI. In the BDEF, this field is specified as read-only. Hence, it cannot be modified by a user on diff --git a/22_Released_ABAP_Classes.md b/22_Released_ABAP_Classes.md index a254882..7f70f85 100644 --- a/22_Released_ABAP_Classes.md +++ b/22_Released_ABAP_Classes.md @@ -65,7 +65,7 @@ Access to SAP-provided repository objects is restricted to objects that have bee ![Released APIs](./files/released_APIs.png) -You can also programmatically get the released obects. You can use specific XCO classes or a CDS view, as shown in the example code snippet below. +You can also programmatically get the released objects. You can use specific XCO classes or a CDS view, as shown in the example code snippet below. ```abap SELECT ReleasedObjectType, ReleasedObjectName, ReleaseState @@ -346,7 +346,7 @@ The setup is similar across all examples: - One example requires creating a demo interface. -Expand the following collapsible section for descriptions and example code: +Expand the following collapsible sections for descriptions and example code:
🟢 Class runner and data object displayer