Get Example source ABAP code based on a different SAP table
• RESULT ABAP_STATEMENT_EML • RESULT MODIFY ENTITY • RESULT MODIFY ENTITIES • RESULT READ ENTITY • RESULT READ ENTITIES • RESULT GET PERMISSIONS ENTITY • RESULT GET PERMISSIONS OF • RESULT GET PERMISSIONS OPERATIONS
ABAP_EML - RESULT result_tab
ABAP_SYNTAX ... RESULT result_tab ...
What does it do? Used to store results of the following operations in an internal table result_tab:
All READ operations.
A MODIFY operation executing an action. The internal table result_tab must be typed with a specific BDEF derived type depending on the operation performed. The use of RESULT is mandatory for all operations except for the modify operation executing an action. The internal tables comprise nested structures that contain special components. See the details on the components in the documentation for Components of Derived Types. The following table provides an overview on those operations offering a result, what their BDEF derived type is and which components are relevant for the internal tables: ContextTypes Possible Components of Structures in Internal Table result_tab READ operations (excluding functions) TABLE FOR READ RESULT bdef[ _assoc] %data lbr %key lbr %pky lbr %tky READ operations executing functions (READ ... EXECUTE) TABLE FOR FUNCTION RESULT bdef~function %key lbr %param lbr %pky lbr %tky MODIFY operations executing an action (MODIFY ... EXECUTE) TABLE FOR ACTION RESULT bdef~action %cid_ref lbr %key lbr %param lbr %pky lbr %tky
Latest notes: Additional components are possible for all contexts: If late numbering is defined for a BO, the component %pid is available. In case of a draft-enabled BO, the component %is_draft is available. NON_V5_HINTS ABAP_HINT_END
