Correct content
This commit is contained in:
@@ -606,7 +606,7 @@ SELECT FROM zdemo_abap_flsch
|
||||
|
||||
"The following clause shows all options having the same effect
|
||||
UP TO 3 ROWS. "Untyped numeric literal
|
||||
"UP TO int4`3` ROWS. "Typed numerice literal
|
||||
"UP TO int4`3` ROWS. "Typed numeric literal
|
||||
"UP TO @upto ROWS. "Host variable
|
||||
"UP TO @( 10 - 7 ) ROWS. "Host expression
|
||||
```
|
||||
@@ -1087,7 +1087,7 @@ topic.
|
||||
| `<=`, `LE` | The content of one operand is less than or equal to the content of the other operand.|
|
||||
| `>=`, `GE` | The content of one operand is greater than or equal to the content of the other operand.|
|
||||
| `... [NOT] BETWEEN ... AND ...` | The value of an operand is (not) between the value of the two other operands.|
|
||||
| `... [NOT] LIKE ...` | The content of an operand matches (does not match) a specified pattern. The pattern can be specified by using wildcard characters. `%` stands for any character string, including an empty string.◾`_` stands for any character.|
|
||||
| `... [NOT] LIKE ...` | The content of an operand matches (does not match) a specified pattern. The pattern can be specified by using wildcard characters. `%` stands for any character string, including an empty string. `_` stands for any character.|
|
||||
| `... IS [NOT] INITIAL ...` | The value of an operand is (not) the initial value of its built-in dictionary type.|
|
||||
| `... EXISTS ...` | Checks the result set of a [subquery](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abensubquery_glosry.htm "Glossary Entry"). The expression is true if the result set contains at least one row. See more information [here](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenwhere_logexp_subquery.htm).|
|
||||
| `... [NOT] IN ( ... )` | Checks whether the operands on the left side match a value from a set of values specified in parentheses. On the left side, a single operand or an operand list are possible. On the right side, a comma-separated lists or subqueries can be specified.|
|
||||
|
||||
@@ -475,7 +475,7 @@ for example, using `DATA`. In this case, the name of the class must be placed af
|
||||
instance constructor. See more information:
|
||||
[here](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abennew_constructor_params_class.htm).
|
||||
- The operator
|
||||
basically replaces the syntax [CREATE OBJECT](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abapcreate_object.htm) you might stumble on.
|
||||
basically replaces the syntax [`CREATE OBJECT`](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abapcreate_object.htm) you might stumble on.
|
||||
|
||||
``` abap
|
||||
"Declaring object reference variable
|
||||
@@ -1056,7 +1056,7 @@ tests](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file
|
||||
- Impact of friendship:
|
||||
- Access is granted to all components, regardless of the visibility section or the addition `READ-ONLY`.
|
||||
- Friends of a class can create instances of the class without restrictions.
|
||||
- Friendship is a one-way street, i. e. a class granting friendship to another class is not granded friendship the other way round. If class `a` grants friendship to class `b`, class `b` must also explicitly grant friendship to class `a` so that `a` can access the invisible components of c `b`.
|
||||
- Friendship is a one-way street, i. e. a class granting friendship to another class is not granded friendship the other way round. If class `a` grants friendship to class `b`, class `b` must also explicitly grant friendship to class `a` so that `a` can access the invisible components of class `b`.
|
||||
- Friendship and inheritance: Heirs of friends and interfaces that contain a friend as a component interface also become friends. However, granting friendship is not inherited, i. e. a friend of a superclass is not automatically a friend of its subclasses.
|
||||
|
||||
|
||||
|
||||
@@ -719,7 +719,7 @@ DATA(b) = SWITCH #( a
|
||||
|
||||
Examples:
|
||||
```abap
|
||||
"FILTER an conditions based on single values
|
||||
"FILTER and conditions based on single values
|
||||
"Assumption the component num is of type i.
|
||||
DATA itab1 TYPE SORTED TABLE OF struc WITH NON-UNIQUE KEY num.
|
||||
DATA itab2 TYPE STANDARD TABLE OF struc WITH NON-UNIQUE SORTED KEY sec_key COMPONENTS num.
|
||||
|
||||
@@ -25,7 +25,7 @@
|
||||
|
||||
- The name `itab` of the data object is determined at compile time and remains stable throughout the execution of the program.
|
||||
- However, there can also be use cases where the attributes of such a data object are not statically determined. This is where dynamic aspects enter the picture: Attributes, names, types etc. are not determined at compile time but rather at runtime.
|
||||
- There are ABAP statements that include these dynamic aspects in the syntax. Assume you have simple program and a UI that includes an input field storing the input in a data object named `dbtab`. As input, you expect the name of a database table to be provided. In the end, you want to retrieve all entries of the database table and store them in an internal table. This table should be displayed. So, there is random input at runtime and your program must be able deal with.
|
||||
- There are ABAP statements that include these dynamic aspects in the syntax. Assume you have simple program and a UI that includes an input field storing the input in a data object named `dbtab`. As input, you expect the name of a database table to be provided. In the end, you want to retrieve all entries of the database table and store them in an internal table. This table should be displayed. So, there is random input at runtime and your program must be able to deal with it.
|
||||
- See the following `SELECT` statement. As also shown further down, the `FROM` clause does not include a statically defined table to be selected from. Instead, there is a pair of parentheses including a data object. Assume the data object holds the name of the database table. At runtime, the data retrieval happens from the database table that was inserted in the input field.
|
||||
|
||||
```abap
|
||||
@@ -100,7 +100,7 @@ ENDLOOP.
|
||||
**Assigning data objects**
|
||||
|
||||
[`ASSIGN`](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abapassign.htm)
|
||||
statements assigns the memory area of a data object to a field symbol.
|
||||
statements assign the memory area of a data object to a field symbol.
|
||||
Once the memory area is assigned, you can work with the content.
|
||||
|
||||
``` abap
|
||||
@@ -538,6 +538,9 @@ For the rich variety of options (where dynamic specification is possible for ABA
|
||||
|
||||
"In newer ABAP releases, you can dynamically specify structure components using this syntax
|
||||
ASSIGN struc-(comp1) TO <fs>.
|
||||
|
||||
"Accessing components of structures that are referenced by a data reference variable
|
||||
ASSIGN dref->(comp1) TO <fs>.
|
||||
```
|
||||
|
||||
- Dynamically specifying data types
|
||||
|
||||
@@ -362,11 +362,9 @@ METHODS some_action FOR MODIFY
|
||||
of RAP BO instances as import parameter. Therefore, instance data
|
||||
must be handled via the transactional buffer when self-implementing
|
||||
the saver methods.
|
||||
- All saver methods are called after at least one successful
|
||||
modification of data in the current RAP LUW, for example, by
|
||||
triggering the save sequence using a [`COMMIT
|
||||
- Saver methods are called when the RAP save sequence has been triggered a [`COMMIT
|
||||
ENTITIES`](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abapcommit_entities.htm)
|
||||
statement.
|
||||
statement. Note that in natively supported RAP scenarios, for example, an SAP Fiori app using OData, the `COMMIT ENTITIES` call is performed implicitly and automatically by the [RAP runtime engine](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenrap_runtime_engine_glosry.htm).
|
||||
- Find more information on RAP saver methods
|
||||
[here](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenabp_saver_class.htm).
|
||||
|
||||
@@ -878,13 +876,13 @@ READ ENTITIES OF root_ent
|
||||
ENTITIES`](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abapcommit_entities.htm)
|
||||
statement triggers the RAP save sequence. Without such a statement,
|
||||
the modified RAP BO instances that are available in the
|
||||
transactional buffer are not persisted to the database.
|
||||
transactional buffer are not persisted to the database. As mentioned above, in case of a natively supported RAP
|
||||
scenario (for example, when using OData), the `COMMIT
|
||||
ENTITIES` request is executed automatically.
|
||||
- `COMMIT ENTITIES` implicitly includes [`COMMIT
|
||||
WORK`](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abapcommit.htm).
|
||||
- Note: `COMMIT ENTITIES` statements cannot be used
|
||||
in behavior implementations. In case of a natively supported RAP
|
||||
scenario (for example, when using OData), the `COMMIT
|
||||
ENTITIES` request is executed automatically.
|
||||
in behavior implementations.
|
||||
- There a multiple variants available for the statement as described
|
||||
in the ABAP Keyword Documentation
|
||||
[here](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abapcommit_entities.htm).
|
||||
|
||||
@@ -66,7 +66,7 @@
|
||||
* Choosing the 'Go' button refreshes the list. At first use, there
|
||||
* might not be any entry. You can create an entry choosing the 'Create'
|
||||
* button.
|
||||
* The late numbering aspects enters the picture when you, for
|
||||
* The late numbering aspects enter the picture when you, for
|
||||
* example, create a new instance, i. e. create a new calculation, and
|
||||
* you keep a draft version of it instead of saving it to the database.
|
||||
* The calculation ID which represents the key of the instance has an
|
||||
|
||||
Reference in New Issue
Block a user