Get Example source ABAP code based on a different SAP table
• ENTITY READ ENTITIES • OF READ ENTITIES
READ ENTITIES>, Long Form
ABAP_SYNTAX READ ENTITIES OF bdef $[IN LOCAL MODE> $|PRIVILEGED>>$] ENTITY entity1 operations> $[ENTITY entity2 operations>$] $[...$] $[response_param>>$].>
ABAP Addition 1 ... IN LOCAL MODE ...> 2 ... PRIVILEGED ...> 3 ... response_param.>
What does it do? The long syntax form of the READ> statement is used for collecting multiple read operations (operations>>) on multiple entities of a RAP BO. Yet, it can also be used to just read from a single entity of a RAP BO. bdef> must be a root entity followed by a list of operations grouped by individual entities. entity1>, entity2>, and so on, must be entities contained in the composition tree of the root entity bdef>. The root entity itself can also be inserted in the position of entity1>, for example. Each part of the list of operations specified after READ ENTITIES OF bdef> has the same syntax as the short form>. At least one entry ( ENTITY entity1 > with the operation) must be specified. The same entity can be specified after ENTITY > only once for a read operation. The root entity name can be used more than once but only in the context of read-by-association operations> or executing actions, for example as follows: READ ENTITIES OF bdef> ENTITY bdef ...> ENTITY bdef BY _assoc1 ...> ENTITY bdef BY _assoc2 ...> ...> The root entity name in the position of the first statement, READ ENTITIES OF bdef>, must be the full entity name. entity1>, and so on, should be the entity alias names if provided in the BDEF >. Using the full entity name will cause a warning. If the root entity is used in the list of operations, its alias name, if defined in the BDEF, should be used as well.