Ansicht
Dokumentation
ABAPTYPE_TABLE_FOR - TYPE TABLE FOR
CPI1466 during Backup Vendor Master (General Section)This documentation is copyright by SAP AG.
TYPE TABLE FOR
... TABLE FOR ${ ACTION IMPORT bdef~action $}
$| ${ ACTION RESULT bdef~action $}
$| ${ $[INSTANCE$] AUTHORIZATION KEY bdef$[~group$] $}
$| ${ $[INSTANCE$] AUTHORIZATION RESULT bdef$[~group$] $}
$| ${ CHANGE bdef $}
$| ${ CREATE bdef $[\_assoc$] $}
$| ${ DELETE bdef $}
$| ${ DETERMINATION bdef~det $}
$| ${ EVENT bdef~evt $}
$| ${ FAILED $[EARLY $| LATE$] bdef $}
$| ${ HIERARCHY bdef $}
$| ${ $[INSTANCE$] FEATURES KEY bdef$[~group$] $}
$| ${ $[INSTANCE$] FEATURES RESULT bdef$[~group$] $}
$| ${ FUNCTION IMPORT bdef~function $}
$| ${ FUNCTION RESULT bdef~function $}
$| ${ KEY OF bdef $}
$| ${ MAPPED $[EARLY $| LATE$] bdef $}
$| ${ PERMISSIONS KEY bdef $}
$| ${ READ IMPORT bdef $[\_assoc$] $}
$| ${ READ LINK bdef\_assoc $}
$| ${ READ RESULT bdef $[\_assoc$] $}
$| ${ REPORTED $[EARLY $| LATE$] bdef $}
$| ${ UPDATE bdef $}
$| ${ VALIDATION bdef~valid $} ...
Effect
Special ABAP type that is used for internal tables in the context of RAP to enable the communication between a RAP BO provider and a RAP BO consumer. These internal tables hold input parameters, or output parameters respectively, to enable mass processing of data by bundling READ or MODIFY requests in one method call.
For all operations defined in the BDEF, ABAP types can be derived and used with this special syntax. The use is dependent on the definition in the BDEF. For example, if the operation create is not specified in the BDEF, TYPE TABLE FOR CREATE cannot be used.
The internal tables contain various special components, also depending on the BDEF. Generally, the tables are
standard tables with an empty
primary table key. However, most of the tables have predefined
secondary table keys. Find more information in the topic
Secondary Keys for BDEF Derived Types.
Notes
- The components of BDEF derived types can be checked via the element information in ADT by choosing F2 for the typed variable.
- For a convenient handling and specification of the % components, the ADT code completion shows possible entries and simplifies inserting them without the need to remember the respective field names from the underlying CDS view.
- The components listed in the Components column of the following table might cover
more than mentioned there. It depends on the context. For example, the draft indicator %is_draft
is available in case of drafts only. %pid is only available in
late numbering scenarios.
Overview
The following table covers the variants including information on the BDEF prerequisites and the tables' components.
For details on the components, see Components of BDEF Derived Types. For details on the BDEF specifications, see the subtopics in ABAP CDS - BDL for Behavior Definitions.
| TYPE TABLE FOR ... | Purpose | BDEF Prerequisites | Components |
- The example Display BDEF Derived Type Components allows you to explore multiple BDEF derived type components and their availability in variables typed with TYPE TABLE FOR ... and TYPE STRUCTURE FOR .... The program makes use of three different RAP scenarios: RAP external numbering, late numbering and draft.
- The type TYPE TABLE FOR CHANGE is demonstrated in the following examples:
- - TYPE REQUEST FOR in a managed RAP BO with additional save: Uses a managed RAP BO whose BDEF is specified with with additional save.
- - TYPE REQUEST FOR in a managed RAP BO with unmanaged save: Uses a simple managed RAP BO whose BDEF is specified with with unmanaged save.
- The type TYPE TABLE FOR HIERARCHY is demonstrated in the example Using TYPE TABLE/TYPE STRUCTURE FOR HIERARCHY.
TXBHW - Original Tax Base Amount in Local Currency SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up
This documentation is copyright by SAP AG.
Length: 10203 Date: 20240419 Time: 205316 sap01-206 ( 85 ms )
