SAP READ ENTITY ENTITIES ABAP Statements



Get Example source ABAP code based on a different SAP table
  


ID READ-BEHV
• READ ENTITIES ABAP_STATEMENT_EML
• READ ENTITY ABAP_STATEMENT_EML
• READ ENTITIES OPERATIONS ABAP_STATEMENT_EML

READ ENTITY, ENTITIES

ABAP_SYNTAX_FORMS

READ ENTITY, Short Form
1 READ ENTITY $[IN LOCAL MODE $|PRIVILEGED$] entity operations $[response_param$].

READ ENTITIES, Long Form
2 READ ENTITIES OF bdef $[IN LOCAL MODE $|PRIVILEGED$]
ENTITY entity1 operations
$[ENTITY entity2 operations$]
$[...$]
$[response_param$].


READ ENTITIES OPERATIONS,Dynamic Form
3 READ ENTITIES $[IN LOCAL MODE $|PRIVILEGED$] OPERATIONS op_tab $[ response_param$].

What does it do?
Used to perform read-only operations on RAP BO instances. Read operations always return a result and can be carried out on RAP BO entities by default (excluding the implementation type abstract) provided that the entities are part of a behavior definition after a declaration with define behavior for.
The following variants of the READ statement can be used to read from RAP BO entities:
READ ENTITY, Short Form The short form of the READ statement allows reading multiple instances of a single entity.
READ ENTITIES, Long Form The long form of the READ statement allows reading multiple instances of multiple entities.
READ ENTITIES OPERATIONS, Dynamic Form The dynamic form of the READ statement allows collecting multiple instances to be read in multiple entities in one READ statement.



Latest notes:

ABAP_EML is used to read RAP BO node instances. From a RAP BO consumer perspective, the returned data of read operations include the current transactional image, i. e. the currently persisted values in the database and, additionally, the still unsaved changes from the current LUW.
ABAP_EML READ statements in RAP BO consumers and RAP BO provider trigger the calling of RAP handler method FOR READ.