).
...
@@ -358,6 +357,9 @@ ref5 = CAST #( ref6 ).
"Casting operator in older syntax
"ref5 ?= ref6.
+
+"Note: The cast operators can also but need not be specified for upcasts.
+ref4 = CAST #( ref3 ).
```
**Addressing data references**
diff --git a/07_String_Processing.md b/07_String_Processing.md
index 9d46faf..242f822 100644
--- a/07_String_Processing.md
+++ b/07_String_Processing.md
@@ -149,10 +149,9 @@ DATA char_len_one TYPE c.
## Assigning Values
-- When you declare character-like data objects, you can specify start values directly. For example, you can use
-the [assignment operator](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenassignment_operator_glosry.htm "Glossary Entry")
-`=`.
-- As mentioned above, you can declare character-like data objects inline using the operators `DATA` or, in newer ABAP releases, `FINAL`.
+- When you declare character-like data objects, you can specify start values directly with the `VALUE` addition, e.g. `DATA chars TYPE c LENGTH 3 VALUE 'abc'.`.
+- You can do value assignments to data objects using the the [assignment operator](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenassignment_operator_glosry.htm "Glossary Entry") `=`.
+- As mentioned above, you can declare character-like data objects inline using the operators `DATA` or `FINAL`.
- You can use the operators at many [write positions](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenwrite_position_glosry.htm "Glossary Entry").
- Unlike the `VALUE` addition of the declaration statements, inline declarations allow you to declare variables for the results of expressions or at other positions where character strings are returned.
- In the case below, a variable specified in parentheses preceded by `DATA` (or `FINAL`) on the left side of the assignment operator automatically derives a data type from the operand on the right. This helps to make your
@@ -161,6 +160,8 @@ programs leaner.
Syntax examples:
``` abap
"Data object declarations including default values with VALUE
+"Note the chained statement: DATA followed by a colon, listing the data object declarations,
+"separated by a comma.
DATA: flag TYPE c LENGTH 1 VALUE 'X',
str1 TYPE string VALUE `Hallo!`.
diff --git a/08_EML_ABAP_for_RAP.md b/08_EML_ABAP_for_RAP.md
index ff9d587..8bf1057 100644
--- a/08_EML_ABAP_for_RAP.md
+++ b/08_EML_ABAP_for_RAP.md
@@ -3,7 +3,7 @@
# ABAP for RAP: Entity Manipulation Language (ABAP EML)
- [ABAP for RAP: Entity Manipulation Language (ABAP EML)](#abap-for-rap-entity-manipulation-language-abap-eml)
- - [Excursion: EML in the Context of RAP](#excursion-eml-in-the-context-of-rap)
+ - [RAP Buzzwords](#rap-buzzwords)
- [ABAP Behavior Pools (ABP)](#abap-behavior-pools-abp)
- [RAP Handler Classes and Methods](#rap-handler-classes-and-methods)
- [RAP Saver Class and Saver Methods](#rap-saver-class-and-saver-methods)
@@ -21,11 +21,10 @@
- [More Information](#more-information)
- [Executable Examples](#executable-examples)
-## Excursion: EML in the Context of RAP
+## RAP Buzzwords
[ABAP Entity Manipulation Language](https://help.sap.com/doc/abapdocu_latest_index_htm/latest/en-US/index.htm?file=abenaeml_glosry.htm) (or EML for short) is a subset of ABAP that allows you to access the data of [RAP](https://help.sap.com/doc/abapdocu_latest_index_htm/latest/en-US/index.htm?file=abenarap_glosry.htm) business objects in an ABAP program.
-The following points are meant to touch on RAP-related buzzwords like
-*RAP business objects* and others for setting the context:
+The following points touch on RAP-related buzzwords such as *RAP business objects* and others for setting the context:
- RAP business objects (RAP BO)
- A RAP BO is based on a special, tree-like hierarchical structure
@@ -140,8 +139,8 @@ The following points are meant to touch on RAP-related buzzwords like
provided or self-implemented by developers in an ABAP behavior
implementation
- Unmanaged RAP BOs are, for example, relevant for brownfield
- scenarios, i. e. in scenarios in which business logic is already
- available and should be embedded in the RAP world.
+ scenarios, i. e. in scenarios in which transactional buffers and application logic is already
+ available and should be embedded in the RAP world. Note that it is possible to have a managed RAP BO with unamanged parts, e.g. unamanged save or additional save. Find more information [here](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenbdl_rap_bo.htm).
- ABAP behavior implementation in an ABAP behavior pool (ABP)
- An [ABAP behavior
pool](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenbehavior_pool_glosry.htm "Glossary Entry")
@@ -625,7 +624,7 @@ the additions
BY`](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abapmodify_entity_entities_op.htm),
[`UPDATE`](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abapmodify_entity_entities_op.htm),
and
-[`DELETE`](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abapmodify_entity_entities_op.htm)
+[`DELETE`](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abapmodify_entity_entities_op.htm))
and non-standard operations (actions) using the addition
[`EXECUTE`](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abapmodify_entity_entities_op.htm).
All EML statements for the mentioned operations begin with
diff --git a/14_ABAP_Unit_Tests.md b/14_ABAP_Unit_Tests.md
index 08c0c55..dd5a84d 100644
--- a/14_ABAP_Unit_Tests.md
+++ b/14_ABAP_Unit_Tests.md
@@ -79,21 +79,21 @@ CLASS ltc_test_class IMPLEMENTATION.
ENDCLASS.
```
-Notes:
-- `FOR TESTING` can be used for multiple purposes:
- - Creating a test class containing test methods
- - Creating a test double
- - Creating helper methods to support ABAP unit tests
- - Note the possible [syntax options](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abapclass_options.htm) before `FOR TESTING`
-- Optional addition `RISK LEVEL ...`:
- - `CRITICAL`: test changes system settings or customizing data (default)
- - `DANGEROUS`: test changes persistent data
- - `HARMLESS`: test does not change system settings or persistent data
-- Optional addition `DURATION ...`:
- - `SHORT`: execution time of only a few seconds is expected
- - `MEDIUM`: execution time of about one minute is expected
- - `LONG`: execution time of more than one minute is expected
-
+> **💡 Note**
+> - `FOR TESTING` can be used for multiple purposes:
+> - Creating a test class containing test methods
+> - Creating a test double
+> - Creating helper methods to support ABAP unit tests
+> - Note the possible [syntax options](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abapclass_options.htm) before `FOR TESTING`
+> - Optional addition `RISK LEVEL ...`:
+> - `CRITICAL`: test changes system settings or customizing data (default)
+> - `DANGEROUS`: test changes persistent data
+> - `HARMLESS`: test does not change system settings or persistent data
+> - Optional addition `DURATION ...`:
+> - `SHORT`: execution time of only a few seconds is expected
+> - `MEDIUM`: execution time of about one minute is expected
+> - `LONG`: execution time of more than one minute is expected
+> - To create a class in ADT, type "test" in the "Test Class" tab and choose `CTRL` and `SPACE` to display the templates suggestions. You can then choose "testClass – Test class (ABAP Unit)". The skeleton of a test class is automatically generated.
To test protected or private methods, you must declare [friendship](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenfriend_glosry.htm) with the class to be tested (class under test).
Example:
diff --git a/15_CDS_View_Entities.md b/15_CDS_View_Entities.md
index efd679f..66bce5b 100644
--- a/15_CDS_View_Entities.md
+++ b/15_CDS_View_Entities.md
@@ -16,6 +16,7 @@ Core data services (CDS) are an infrastructure for defining and consuming semant
- [Feature Matrix: Data Modeling with ABAP Core Data Services](https://blogs.sap.com/2022/10/24/feature-matrix-data-modeling-with-abap-core-data-services/)
- [ABAP CDS Cheat Sheet: Amounts and Quantities in ABAP CDS](https://blogs.sap.com/2022/07/07/abap-cds-cheat-sheet-amounts-and-quantities-in-abap-cds/)
- [Section *ABAP - Core Data Services (ABAP CDS)* in the ABAP Keyword Documentation](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abencds.htm)
+- [ABAP Data Models Guide](https://blogs.sap.com/2023/05/09/abap-data-models-guide/)
## Executable Example
[zcl_demo_abap_cds_ve](./src/zcl_demo_abap_cds_ve.clas.abap)
diff --git a/16_Data_Types_and_Objects.md b/16_Data_Types_and_Objects.md
index 354e9a1..40e4e55 100644
--- a/16_Data_Types_and_Objects.md
+++ b/16_Data_Types_and_Objects.md
@@ -31,7 +31,7 @@ Note that the topics covered here are also partly covered in other ABAP cheat sh
Data types
- Define technical properties of all data objects that have these data types, such as the maximum length of a [text field](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abentext_field_glosry.htm).
- Are descriptions only, with no data memory attached except for administrative information.
-- Can occur in A[ABAP programs](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenabap_program_glosry.htm) as [bound data types](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenbound_data_type_glosry.htm), that is, the type is a property of a data object, or as a [standalone data type](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenstand-alone_data_type_glosry.htm), that is, the data type is defined independently.
+- Can occur in [ABAP programs](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenabap_program_glosry.htm) as [bound data types](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenbound_data_type_glosry.htm), that is, the type is a property of a data object, or as a [standalone data type](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenstand-alone_data_type_glosry.htm), that is, the data type is defined independently.
- Can be defined locally in an ABAP program or globally in classes, interfaces and in the [ABAP Dictionary (DDIC)](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenabap_dictionary_glosry.htm).
> **💡 Note**
> - Note: Data types in the ABAP Dictionary are either created directly as [repository objects](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenrepository_object_glosry.htm) ([DDIC data elements](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abendata_element_glosry.htm)) or in a type pool (only in [Standard ABAP](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenstandard_abap_glosry.htm)). [Database table](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abendatabase_table_glosry.htm), [CDS entities](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abencds_entity_glosry.htm) and their components can also be used as data types in ABAP programs.
@@ -46,7 +46,7 @@ Data objects:
> **💡 Note**
-> There are several differentations that further distinguish and characterize data types and objects (see [here](#glossary-terms-in-a-nutshell)).
+> There are several differentations that further distinguish and characterize data types and objects. See [here](#glossary-terms-in-a-nutshell).
(back to top)
@@ -61,7 +61,7 @@ Data types can be divided into three groups:
For an overview, see the [ABAP Type Hierarchy](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abentype_hierarchy.htm) in the ABAP Keyword Documentation.
### Elementary Data Types
-- Elementary (or scalar) data types are based directly on a set of [built-in ABAP types](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenbuiltin_abap_type_glosry.htm)
+- Elementary (or scalar) data types are based directly on a set of [built-in ABAP types](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenbuiltin_abap_type_glosry.htm).
- Are not composed of of other data types.
- Are types for holding numeric values, text information, binary data and special types for date and time.
- Are further divided into elementary types of fixed and variable length.
@@ -82,7 +82,7 @@ For an overview, see the [ABAP Type Hierarchy](https://help.sap.com/doc/abapdocu
> - The numeric data types `b` and `s` cannot be specified directly in ABAP programs for short integers. Alternative [built-in DDIC types](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenbuiltin_ddic_type_glosry.htm) are available.
> - `decfloat16` and `decfloat34` for decimal floating point numbers can be regarded as more modern versions of `p` and `f`, combining their advantages.
> - Although they are character-like, `t` and `d` can be used for calculations.
-> - See the ABAP Keyword Documentation [here](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenbuilt_in_types.htm) for more information about the initial values of the data types, how long they can be, and so on.
+> - See the ABAP Keyword Documentation [here](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenbuilt_in_types.htm) for more information about the initial values of the data types, the standard length, and so on.
(back to top)
@@ -117,7 +117,7 @@ For an overview, see the [ABAP Type Hierarchy](https://help.sap.com/doc/abapdocu
### Declaring Data Types
Data types are defined in an ABAP program using the [`TYPES`](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abaptypes.htm) statement. Depending on the declaration context, the types can be accessed either locally or globally. As mentioned, data types can also be declared in the ABAP Dictionary. The focus here is on data type declarations in ABAP programs using `TYPES` statements.
-You can use built-in and user-defined data types can be used to create data types (and data objects).
+You can use built-in and user-defined data types to create data types (and data objects).
The following code snippet shows various syntax options for declaring data types:
@@ -146,7 +146,7 @@ TYPES: te_c5 TYPE c LENGTH 5,
te_str TYPE string.
"Byte-like types
-TYPES te_do_string TYPE x LENGTH 2.
+TYPES te_x_l2 TYPE x LENGTH 2.
TYPES te_xstr TYPE xstring.
"Types for date and time
@@ -260,7 +260,7 @@ TYPES ts_ddic_tab TYPE zdemo_abap_carr.
"Internal table type based on internal type that exists in a gloabl interface
TYPES tt_tab_type_from_itf TYPE zdemo_abap_get_data_itf=>carr_tab.
-"Internal table types with an elementary line type based globally available types
+"Internal table types with an elementary line type based on globally available types
"Elementary table type
TYPES tt_strtab TYPE string_table.
"Elementary line type; the type is available in a global interface
@@ -433,7 +433,7 @@ DATA struc_like_line LIKE LINE OF itab_ddic_tab.
> **💡 Note**
-> The above data objects are declared by assigning a dedicated name. These data objects can be addressed by taht name. This is not true for [anonymous data objects](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenanonymous_data_object_glosry.htm), which can only be addressed through reference variables. This is covered below.
+> The above data objects are declared by assigning a dedicated name. These data objects can be addressed by that name. This is not true for [anonymous data objects](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenanonymous_data_object_glosry.htm), which can only be addressed through reference variables. This is covered [below](#assigning-references-to-data-reference-variables).
Data reference variables:
@@ -444,7 +444,7 @@ DATA dref_int TYPE REF TO i.
DATA dref_str TYPE REF TO string.
DATA dref_ddic_tab TYPE REF TO zdemo_abap_carr.
"Using a generic type as static type
-DATA dref_8_dataa TYPE REF TO data.
+DATA dref_data TYPE REF TO data.
"Referring to an existing reference type
TYPES tr_int TYPE REF TO i.
@@ -574,8 +574,8 @@ An [inline declaration](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-
> **💡 Note**
> - In an assignment, if the data object is declared inline on the left side, there are many options for what can be placed on the right side as shown in the previous section. The date type of the variable is determined by the operand type. It must be possible to derive this type completely statically.
-> - For more information about the possible declaration positions, see [here](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abendeclaration_position_glosry.htm).
-> - You can use the [`FINAL`](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenfinal_inline.htm) declaration operator to create [immutable variables](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenimmutable_variable_glosry.htm), as shon below.
+> - For more information about the possible declaration positions, see [here](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abendeclaration_positions.htm).
+> - You can use the [`FINAL`](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenfinal_inline.htm) declaration operator to create [immutable variables](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenimmutable_variable_glosry.htm), as shown below.
> - [Programming guidelines for inline declarations (F1 for Standard ABAP)](https://help.sap.com/doc/abapdocu_latest_index_htm/latest/en-US/index.htm?file=abendeclaration_inline_guidl.htm)
@@ -663,13 +663,13 @@ SELECT * FROM zdemo_abap_carr INTO TABLE @DATA(itab_b3).
### Assigning References to Data Reference Variables
-- As with other data objects and types, there are special assignment rules for [data reference variable](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abendata_reference_variable_glosry.htm). See the ABAP Keyword Documentation.
+- As with other data objects and types, there are [special assignment rules](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenconversion_references.htm) for [data reference variable](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abendata_reference_variable_glosry.htm). See the ABAP Keyword Documentation.
- An initial reference variable contains the [null reference](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abennull_reference_glosry.htm), which does not point to any objects. This means that it has neither a data type nor a class as a [dynamic type](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abendynamic_type_glosry.htm).
-- The concepts of [upcast](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenup_cast_glosry.htm) and [downcast](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abendown_cast_glosry.htm) enter the picture here. For more information, see the ABAP Keyword Documentation and the following code snippet.
+- The concepts of [upcast](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenup_cast_glosry.htm) and [downcast](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abendown_cast_glosry.htm) enter the picture here. See the following code snippet.
```abap
"Declaring data reference variables with static types
-"At this stage, initial references variables contains null references.
+"At this stage, initial references variables contain null references.
DATA dref_1_i TYPE REF TO i.
DATA dref_2_str TYPE REF TO string.
"Generic type as static type
@@ -974,7 +974,8 @@ DATA: BEGIN OF struc_a,
"Complete: Non-generic data type
"Generic:
"- Data type that does not set all properties of a data object.
-"- Can only be used for the typing of formal parameters and field symbols.
+"- Can only be used for the typing of formal parameters and field symbols, except for
+" data reference variables using the generic type 'data'.
"Complete data type
DATA do_d_i TYPE i.
@@ -1052,7 +1053,6 @@ DATA do_j_i TYPE i VALUE 3.
DATA do_k_str TYPE string VALUE `hallo`.
"Dynamic types
-"Set a break point here and check the Variables tab in ADT how the value and the information changes.
dref_a_i = REF #( do_j_i ). "Only type i possible; the dynamic type is the same
"The dynamic type is more special than the static type (which is the generic type data in this case)
@@ -1074,7 +1074,7 @@ dref_b_data = REF #( dref_a_i ).
"- Structures that do not contain any deep components are flat structures. Structures that contain
" at least one deep component are deep structures.
-"Flat data object
+"Flat elementary data object
DATA do_l_i TYPE i.
"Flat structure
@@ -1083,7 +1083,7 @@ DATA: BEGIN OF struc_b_flat,
comp2 TYPE c LENGTH 3,
END OF struc_b_flat.
-"Deep data object
+"Deep elementary data object
DATA do_m_str TYPE string.
"Deep structure
@@ -1106,7 +1106,7 @@ DATA do_n_i TYPE i.
CONSTANTS con_b_str TYPE string VALUE `hi`.
"Unnamed data objects
-"Literal that is output. It is cannot be addressed via a dedicated name.
+"Literal that is output. It cannot be addressed via a dedicated name.
output->display( `I'm a literal...` ).
"Anonymous data object created using the NEW operator
@@ -1137,7 +1137,7 @@ The declaration context of data types (and objects) determines the validity and
- Declarations in the ABAP Dictionary, which is a special storage for the declarations of data types that are visible in all repository objects, provided that the [package](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenpackage_glosry.htm) check allows this.
- The data types of the ABAP Dictionary are not declared with the `TYPES` statement, but using ADT tools (and/or SAP GUI tools in systems where SAP GUI is available).
- The DDIC has many more [built-in types](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenbuiltin_ddic_type_glosry.htm) than ABAP. These types have other names. They cannot be used in ABAP programs.
- - The DDIC provides many options for defining types, including elementary data types (defined as data elements), reference types, complex types such as structured types and table types. Note that the name of a database table or a view can be used in type declarations to address the line type of these repository objects (for example, a structure: `DATA a TYPE some_db_table.).
+ - The DDIC provides many options for defining types, including elementary data types (defined as data elements), reference types, complex types such as structured types and table types. Note that the name of a database table or a view can be used in type declarations to address the line type of these repository objects (for example, a structure: `DATA a TYPE some_db_table.`).
- Note the following trap: Local declarations hide global declarations of the same name.
(back to top)
diff --git a/src/zcl_demo_abap_amdp.clas.abap b/src/zcl_demo_abap_amdp.clas.abap
index 3259e60..04b21c4 100644
--- a/src/zcl_demo_abap_amdp.clas.abap
+++ b/src/zcl_demo_abap_amdp.clas.abap
@@ -159,7 +159,7 @@ CLASS zcl_demo_abap_amdp IMPLEMENTATION.
DATA(output) = NEW zcl_demo_abap_display( out ).
- output->display( `Demo: ABAP AMDP` ).
+ output->display( `ABAP Cheat Sheet Example: ABAP AMDP` ).
output->display( `1. AMDP procedure` ).
diff --git a/src/zcl_demo_abap_cds_ve.clas.abap b/src/zcl_demo_abap_cds_ve.clas.abap
index 4c1bc78..98a2938 100644
--- a/src/zcl_demo_abap_cds_ve.clas.abap
+++ b/src/zcl_demo_abap_cds_ve.clas.abap
@@ -98,7 +98,7 @@ CLASS zcl_demo_abap_cds_ve IMPLEMENTATION.
DATA(output) = NEW zcl_demo_abap_display( out ).
- output->display( `ABAP cheat sheet: CDS view entities` ).
+ output->display( `ABAP Cheat Sheet Example: CDS view entities` ).
output->display( `1) Operands, expressions and built-in functions ` &&
`in a CDS view entity` ).
diff --git a/src/zcl_demo_abap_constructor_expr.clas.abap b/src/zcl_demo_abap_constructor_expr.clas.abap
index b027c18..32ee00f 100644
--- a/src/zcl_demo_abap_constructor_expr.clas.abap
+++ b/src/zcl_demo_abap_constructor_expr.clas.abap
@@ -111,7 +111,7 @@ CLASS zcl_demo_abap_constructor_expr IMPLEMENTATION.
DATA(output) = NEW zcl_demo_abap_display( out ).
- output->display( `ABAP cheat sheet: Constructor expressions` ).
+ output->display( `ABAP Cheat Sheet Example: Constructor expressions` ).
output->next_section( `VALUE` ).
output->display( `1) Structures: Populating a flat structure` ).
@@ -341,9 +341,9 @@ CLASS zcl_demo_abap_constructor_expr IMPLEMENTATION.
END OF substruc,
END OF deep_struc_ty.
- DATA(deep_struc) = VALUE deep_struc_ty( num = 1 char1 = 'aaa'
-
- substruc = VALUE #( int = 123 str = `hallo` ) ).
+ DATA(deep_struc) = VALUE deep_struc_ty( num = 1
+ char1 = 'aaa'
+ substruc = VALUE #( int = 123 str = `hallo` ) ).
output->display( input = deep_struc name = `deep_struc` ).
@@ -1335,6 +1335,8 @@ CLASS zcl_demo_abap_constructor_expr IMPLEMENTATION.
output->display( input = str_tab name = `str_tab` ).
+**********************************************************************
+
output->next_section( `42) LET Expressions (2)` ).
"2) LET within a constructor expression with COND: 12 o'clock is
@@ -1354,6 +1356,8 @@ CLASS zcl_demo_abap_constructor_expr IMPLEMENTATION.
output->display( input = time name = `time` ).
+**********************************************************************
+
output->next_section( `43) LET Expressions (3)` ).
"3) An internal table that includes three components is created and
diff --git a/src/zcl_demo_abap_dtype_dobj.clas.abap b/src/zcl_demo_abap_dtype_dobj.clas.abap
index 29da7ac..49b96c1 100644
--- a/src/zcl_demo_abap_dtype_dobj.clas.abap
+++ b/src/zcl_demo_abap_dtype_dobj.clas.abap
@@ -40,7 +40,7 @@
* code.
*
***********************************************************************
-"! ABAP cheat sheets: Data types and data objects
+"! ABAP cheat sheet: Data types and data objects
"! Example to demonstrate data types and data objects in ABAP.
Choose F9 in ADT to run the class.
CLASS zcl_demo_abap_dtype_dobj DEFINITION
PUBLIC
@@ -91,8 +91,7 @@ CLASS zcl_demo_abap_dtype_dobj IMPLEMENTATION.
" CDS entity, which is not covered in this demo example.
"- In ADT and because of the many type declarations, you may want to press
" F2 on the types to get more information.
- "- The examples show a selection. For more information, chheck out the
- " ABAP Keyword Documentation.
+ "- The examples show a selection.
"- Only non-generic types can be used.
output->display( `1) Declaring data types based on elementary types` ).
@@ -760,7 +759,6 @@ CLASS zcl_demo_abap_dtype_dobj IMPLEMENTATION.
"- Must always be performed explicitly using the casting operator ?= and the casting
" operator CAST.
-
"The following example would result in a syntax error due to type incompatibility.
"dref_1_i = dref_3_data.
@@ -775,7 +773,7 @@ CLASS zcl_demo_abap_dtype_dobj IMPLEMENTATION.
dref_1_i = CAST #( dref_3_data ).
"If not caught, the following would result in a runtime error.
- "dref_3_data points to a reference of type i, the static type is dref_2_str is string.
+ "dref_3_data points to a reference of type i, the static type of dref_2_str is string.
"So, the downcast does not work.
TRY.
dref_2_str = CAST #( dref_3_data ).
@@ -973,7 +971,7 @@ CLASS zcl_demo_abap_dtype_dobj IMPLEMENTATION.
**********************************************************************
- output->display( `1) Character strings and text field strings` ).
+ output->display( `12) Character strings and text field strings` ).
"The following example shows the difference between text field strings
"of type c and character strings of type string when it comes to trailing
@@ -990,7 +988,7 @@ CLASS zcl_demo_abap_dtype_dobj IMPLEMENTATION.
**********************************************************************
- output->display( `12) Floating point numbers` ).
+ output->display( `13) Floating point numbers` ).
"The following example shows the difference between binary and decimal
"floating point numbers.
@@ -1005,9 +1003,9 @@ CLASS zcl_demo_abap_dtype_dobj IMPLEMENTATION.
**********************************************************************
- output->display( `13) Byte-like types` ).
+ output->display( `14) Byte-like types` ).
- "The following example shows byte-like types x and xstring..
+ "The following example shows byte-like types x and xstring.
"A byte string is filled with binary data created from a string
"using the convert_out method of the cl_abap_codepage class.
@@ -1058,7 +1056,7 @@ CLASS zcl_demo_abap_dtype_dobj IMPLEMENTATION.
**********************************************************************
- output->display( `14) Date and time` ).
+ output->display( `15) Date and time` ).
"In the example, date and time fields are assigned the current values
"using the cl_abap_context_info class. Calculations follow. The date of next
@@ -1093,7 +1091,7 @@ CLASS zcl_demo_abap_dtype_dobj IMPLEMENTATION.
**********************************************************************
- output->display( `15) Type conversion rules` ).
+ output->display( `16) Type conversion rules` ).
"The purpose of this example is to emphasize the conversion rules
"that should be noted when performing conversions.
@@ -1248,7 +1246,7 @@ CLASS zcl_demo_abap_dtype_dobj IMPLEMENTATION.
**********************************************************************
- output->display( `16) Excursion: RTTI` ).
+ output->display( `17) Excursion: RTTI` ).
"Using RTTI to check type compatibility
"In the following example the applies_to_data method of the RTTI class
@@ -1316,7 +1314,7 @@ CLASS zcl_demo_abap_dtype_dobj IMPLEMENTATION.
**********************************************************************
- output->display( `17) Constants and immutable variables` ).
+ output->display( `18) Constants and immutable variables` ).
"As mentioned above, constants cannot be changed at runtime.
CONSTANTS con_str TYPE string VALUE `hallo`.
@@ -1356,7 +1354,7 @@ CLASS zcl_demo_abap_dtype_dobj IMPLEMENTATION.
**********************************************************************
- output->display( `18) Various ABAP glossary terms on data types and objects in a nutshell` ).
+ output->display( `19) Various ABAP glossary terms on data types and objects in a nutshell` ).
"Standalone and bound data types
"Standalone: Data type that is defined using the statement TYPES in an ABAP program, as
@@ -1570,7 +1568,7 @@ CLASS zcl_demo_abap_dtype_dobj IMPLEMENTATION.
**********************************************************************
- output->display( `19) Generic ABAP types for formal parameters of methods` ).
+ output->display( `20) Generic ABAP types for formal parameters of methods` ).
"Generic data types have already been covered above.
"A generic data type is an incomplete type specification that covers multiple
@@ -1615,7 +1613,7 @@ CLASS zcl_demo_abap_dtype_dobj IMPLEMENTATION.
**********************************************************************
- output->display( `20) Built-in data objects` ).
+ output->display( `21) Built-in data objects` ).
"This example demonstrates the availability of built-in data objects in ABAP..
@@ -1697,7 +1695,7 @@ CLASS zcl_demo_abap_dtype_dobj IMPLEMENTATION.
**********************************************************************
- output->display( `21) Declaration context` ).
+ output->display( `22) Declaration context` ).
"The declaration context of data objects can be problematic.
"The example deals with local declarations and control structures.
diff --git a/src/zcl_demo_abap_dynamic_prog.clas.abap b/src/zcl_demo_abap_dynamic_prog.clas.abap
index c720cee..462468d 100644
--- a/src/zcl_demo_abap_dynamic_prog.clas.abap
+++ b/src/zcl_demo_abap_dynamic_prog.clas.abap
@@ -77,7 +77,7 @@ CLASS zcl_demo_abap_dynamic_prog IMPLEMENTATION.
DATA(output) = NEW zcl_demo_abap_display( out ).
- output->display( `ABAP Cheat Sheet: Dynamic Programming` ).
+ output->display( `ABAP Cheat Sheet Example: Dynamic Programming` ).
**********************************************************************
@@ -953,7 +953,7 @@ CLASS zcl_demo_abap_dynamic_prog IMPLEMENTATION.
* "If the value is 0, the memory area of the entire structure is assigned to the field symbol.
* ASSIGN wa-(0) TO FIELD-SYMBOL().
- "The above statements replace the following syntax syntax
+ "The above statements replace the following syntax
ASSIGN COMPONENT 'CARRID' OF STRUCTURE wa TO FIELD-SYMBOL().
ASSIGN COMPONENT 5 OF STRUCTURE wa TO FIELD-SYMBOL().
diff --git a/src/zcl_demo_abap_internal_tables.clas.abap b/src/zcl_demo_abap_internal_tables.clas.abap
index 26a06f7..c9b9192 100644
--- a/src/zcl_demo_abap_internal_tables.clas.abap
+++ b/src/zcl_demo_abap_internal_tables.clas.abap
@@ -181,7 +181,7 @@ CLASS ZCL_DEMO_ABAP_INTERNAL_TABLES IMPLEMENTATION.
DATA(output) = NEW zcl_demo_abap_display( out ).
- output->display( `Demo: Working with Internal Tables` ).
+ output->display( `ABAP Cheat Sheet Example: Working with Internal Tables` ).
output->display( `Filling and Copying Internal Table Content` ).
output->display( `1) Adding single lines using APPEND/INSERT` ).
diff --git a/src/zcl_demo_abap_objects.clas.abap b/src/zcl_demo_abap_objects.clas.abap
index 3d73400..faaa89a 100644
--- a/src/zcl_demo_abap_objects.clas.abap
+++ b/src/zcl_demo_abap_objects.clas.abap
@@ -97,7 +97,7 @@ CLASS zcl_demo_abap_objects IMPLEMENTATION.
DATA(output) = NEW zcl_demo_abap_display( out ).
- output->display( `Demo: ABAP Object Orientation` ).
+ output->display( `ABAP Cheat Sheet Example: ABAP Object Orientation` ).
output->display( `Working with objects and components` ).
output->display( `1) Declaring reference variables` ).
diff --git a/src/zcl_demo_abap_prog_flow_logic.clas.abap b/src/zcl_demo_abap_prog_flow_logic.clas.abap
index 8e615c9..2c5b72d 100644
--- a/src/zcl_demo_abap_prog_flow_logic.clas.abap
+++ b/src/zcl_demo_abap_prog_flow_logic.clas.abap
@@ -104,7 +104,7 @@ CLASS zcl_demo_abap_prog_flow_logic IMPLEMENTATION.
DATA(output) = NEW zcl_demo_abap_display( out ).
- output->display( `ABAP Cheat Sheet Demonstration Example: Program Flow Logic` ).
+ output->display( `ABAP Cheat Sheet Example: Program Flow Logic` ).
**********************************************************************
diff --git a/src/zcl_demo_abap_rap_draft_ln_m.clas.abap b/src/zcl_demo_abap_rap_draft_ln_m.clas.abap
index 82d69b3..8565d76 100644
--- a/src/zcl_demo_abap_rap_draft_ln_m.clas.abap
+++ b/src/zcl_demo_abap_rap_draft_ln_m.clas.abap
@@ -145,7 +145,7 @@ CLASS ZCL_DEMO_ABAP_RAP_DRAFT_LN_M IMPLEMENTATION.
DATA(output) = NEW zcl_demo_abap_display( out ).
- output->display( `RAP Demo: RAP Calculator Using Managed, ` &&
+ output->display( `ABAP Cheat Sheet Example: RAP Calculator Using Managed, ` &&
`Draft-Enabled RAP BO (Late Numbering)` ).
output->display( `1) Creating Instances and ` &&
`Saving to the database` ).
diff --git a/src/zcl_demo_abap_rap_ext_num_m.clas.abap b/src/zcl_demo_abap_rap_ext_num_m.clas.abap
index 942e084..1fd37c6 100644
--- a/src/zcl_demo_abap_rap_ext_num_m.clas.abap
+++ b/src/zcl_demo_abap_rap_ext_num_m.clas.abap
@@ -184,7 +184,7 @@ CLASS ZCL_DEMO_ABAP_RAP_EXT_NUM_M IMPLEMENTATION.
DATA(output) = NEW zcl_demo_abap_display( out ).
- output->display( `RAP Demo: RAP BO Operations Using a Managed ` &&
+ output->display( `ABAP Cheat Sheet Example: RAP BO Operations Using a Managed ` &&
`RAP BO` ).
**********************************************************************
diff --git a/src/zcl_demo_abap_rap_ext_num_u.clas.abap b/src/zcl_demo_abap_rap_ext_num_u.clas.abap
index ce7bc5f..24b079b 100644
--- a/src/zcl_demo_abap_rap_ext_num_u.clas.abap
+++ b/src/zcl_demo_abap_rap_ext_num_u.clas.abap
@@ -193,7 +193,7 @@ CLASS zcl_demo_abap_rap_ext_num_u IMPLEMENTATION.
DATA(output) = NEW zcl_demo_abap_display( out ).
- output->display( `RAP Demo: RAP BO Operations Using an ` &&
+ output->display( `ABAP Cheat Sheet Example: RAP BO Operations Using an ` &&
`Unmanaged RAP BO (External Numbering)` ).
**********************************************************************
diff --git a/src/zcl_demo_abap_sql.clas.abap b/src/zcl_demo_abap_sql.clas.abap
index ce0e92c..998bf34 100644
--- a/src/zcl_demo_abap_sql.clas.abap
+++ b/src/zcl_demo_abap_sql.clas.abap
@@ -72,7 +72,7 @@ CLASS zcl_demo_abap_sql IMPLEMENTATION.
DATA(output) = NEW zcl_demo_abap_display( out ).
- output->display( `ABAP Cheat Sheet: ABAP SQL in Use` ).
+ output->display( `ABAP Cheat Sheet Example: ABAP SQL in Use` ).
output->display( `Using SELECT for multiple purposes` ).
output->display( `1) Reading a single row from database table ` &&
`into a structure` ).
diff --git a/src/zcl_demo_abap_sql_group_by.clas.abap b/src/zcl_demo_abap_sql_group_by.clas.abap
index 48424bd..6cbdf19 100644
--- a/src/zcl_demo_abap_sql_group_by.clas.abap
+++ b/src/zcl_demo_abap_sql_group_by.clas.abap
@@ -69,7 +69,7 @@ CLASS zcl_demo_abap_sql_group_by IMPLEMENTATION.
DATA(output) = NEW zcl_demo_abap_display( out ).
- output->display( `Demo: Grouping Internal Tables` ).
+ output->display( `ABAP Cheat Sheet Example: Grouping Internal Tables` ).
SELECT *
FROM zdemo_abap_flsch
diff --git a/src/zcl_demo_abap_string_proc.clas.abap b/src/zcl_demo_abap_string_proc.clas.abap
index 6c3f878..67dd869 100644
--- a/src/zcl_demo_abap_string_proc.clas.abap
+++ b/src/zcl_demo_abap_string_proc.clas.abap
@@ -57,7 +57,7 @@ CLASS zcl_demo_abap_string_proc IMPLEMENTATION.
DATA(output) = NEW zcl_demo_abap_display( out ).
- output->display( `ABAP Cheat Sheet Demo Example: String Processing` ).
+ output->display( `ABAP Cheat Sheet Example: String Processing` ).
output->display( `1) Creating Strings and Assigning Values` ).
"Data object declarations providing default values
diff --git a/src/zcl_demo_abap_structures.clas.abap b/src/zcl_demo_abap_structures.clas.abap
index 2ba0c90..b1559bc 100644
--- a/src/zcl_demo_abap_structures.clas.abap
+++ b/src/zcl_demo_abap_structures.clas.abap
@@ -114,7 +114,7 @@ CLASS zcl_demo_abap_structures IMPLEMENTATION.
DATA(output) = NEW zcl_demo_abap_display( out ).
- output->display( `ABAP Cheat Sheet Demonstration Example: Working with Structures` ).
+ output->display( `ABAP Cheat Sheet Example: Working with Structures` ).
**********************************************************************
diff --git a/src/zcl_demo_abap_unit_test.clas.abap b/src/zcl_demo_abap_unit_test.clas.abap
index 5d60380..f875e88 100644
--- a/src/zcl_demo_abap_unit_test.clas.abap
+++ b/src/zcl_demo_abap_unit_test.clas.abap
@@ -178,7 +178,7 @@ METHOD if_oo_adt_classrun~main.
DATA(output) = NEW zcl_demo_abap_display( out ).
- output->display( `ABAP Cheat Sheet Demonstration Example: ABAP Unit Tests` ).
+ output->display( `ABAP Cheat Sheet Example: ABAP Unit Tests` ).
output->display( `1) get_sum Method` ).
"This method demonstrates the use of the setup and teardown methods in the test class.