ABAP Addition 1 ... IN LOCAL MODE ...> 2 ... PRIVILEGED ...> 3 ... response_param.>
What does it do? The dynamic form of the READ> statement enables the collecting of read operations for multiple RAP BOs in one READ ENTITIES OPERATIONS ...> statement. There is no short form available for the dynamic version. op_tab> must be a table of type ABP_BEHV_RETRIEVALS_TAB>>. This table has specific components: Component>Details> OP>It is a mandatory component and specifies the operation to be executed. It can be set with the defined constants, for example, OP-R-READ > etc., of interface IF_ABAP_BEHV>> or just the predefined value for the operation in the interface, for example 'R'> for a read operation (OP = 'R'>) or 'N'> for a read-by-association operation (OP = 'N'>). ENTITY_NAME> It is a mandatory component and specifies the name of the RAP BO entity for which the operation is executed. The name must be provided using capital letters. SUB_NAME>Only relevant for specifying association names in case of read-by-association operations or for functions. In these contexts, the specification is mandatory. INSTANCES>Mandatory component. It specifies a reference to an internal table holding the input keys. The table must be typed with the required BDEF derived type for the operation. FULL>An optional flag specifying whether all target instances (and not just links) are retrieved in the context of read-by-association operations. It is of type c> with length 1, i. e. full> specified with abap_true> or 'X'> respects all target instances. lbr ABAP_NOTE Currently, the behavior is as follows: If full> is specified with abap_true> or 'X'>, all target instances are retrieved in any case. When specified otherwise, the instances might be retrieved or not. RESULTS>It specifies a reference to an internal table with the required BDEF derived type for the read results. LINKS>It specifies a reference to an internal table with the required BDEF derived type holding the key pairs of the source and target.