Ansicht
Dokumentation

ABAPTYPE_STRUCTURE_FOR - TYPE STRUCTURE FOR

ABAP Short Reference Fill RESBD Structure from EBP Component Structure
This documentation is copyright by SAP AG.

TYPE STRUCTURE FOR

... STRUCTURE FOR ${ ACTION IMPORT bdef~action $}
                $| ${ ACTION REQUEST bdef~action $}
                $| ${ ACTION RESULT bdef~action $}
                $| ${ $[INSTANCE$] AUTHORIZATION KEY bdef$[~group$] $}
                $| ${ $[INSTANCE$] AUTHORIZATION REQUEST bdef$[~group$] $}
                $| ${ $[INSTANCE$] AUTHORIZATION RESULT bdef$[~group$] $}
                $| ${ CHANGE bdef $}
                $| ${ CREATE bdef $[\_assoc$] $}
                $| ${ DELETE bdef $}
                $| ${ DETERMINATION bdef~det $}
                $| ${ EVENT bdef~evt $}
                $| ${ FAILED $[EARLY $| LATE$] bdef $}
                $| ${ $[INSTANCE$] FEATURES KEY bdef$[~group$] $}
                $| ${ $[INSTANCE$] FEATURES REQUEST bdef$[~group$] $}
                $| ${ $[INSTANCE$] FEATURES RESULT bdef$[~group$] $}
                $| ${ FUNCTION IMPORT bdef~function $}
                $| ${ FUNCTION REQUEST bdef~function $}
                $| ${ FUNCTION RESULT bdef~function $}
                $| ${ GLOBAL AUTHORIZATION REQUEST bdef$[~group$] $}
                $| ${ GLOBAL AUTHORIZATION RESULT bdef$[~group$] $}
                $| ${ GLOBAL FEATURES REQUEST bdef$[~group$] $}
                $| ${ GLOBAL FEATURES RESULT bdef$[~group$] $}
                $| ${ HIERARCHY bdef $}
                $| ${ KEY OF bdef $}
                $| ${ MAPPED $[EARLY $| LATE$] bdef $}
                $| ${ PERMISSIONS KEY bdef $}
                $| ${ PERMISSIONS REQUEST bdef $}
                $| ${ PERMISSIONS RESULT 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 for structures in the context of RAP. The structures have special components tailored for RAP purposes. Those structures are used to enable the communication between a RAP BO provider and a RAP BO consumer.

In principal, structures typed with TYPE STRUCTURE FOR constitute a helper construct if structures are needed for internal tables in the RAP context. Apart from that, several structures serve distinct purposes. For example, in the context of GET PERMISSIONS statements, a structure of type TYPE STRUCTURE FOR PERMISSIONS REQUEST must be specified as REQUEST parameter to define which operations, fields or actions are respected for the retrieval of permission information.

With the use of TYPE STRUCTURE FOR, it is possible to get the line type of an internal table that is typed with the respective BDEF derived type. In doing so, a type declaration with LINE OF can be avoided.

Notes

Internal tables typed with TYPE TABLE FOR and structures typed with TYPE STRUCTURE FOR largely share the same set of variants, whereas there are more possible variants for the type TYPE STRUCTURE FOR in total.

For details on the components (%cid, %cid_ref, etc.), see the topic Components of BDEF Derived Types.

The components listed in the Components column of the following tables might cover more components or less than mentioned there. It depends on the specification of the BDEF. For example, the draft indicator %is_draft is available in case of drafts only in multiple BDEF derived types. %pid is only available in BDEF derived types in late numbering scenarios.

Overview 1

The following table covers the variants including information on the BDEF prerequisites and the structures' components. The table includes only those variants that are exclusive for TYPE STRUCTURE FOR and not available for TYPE TABLE FOR.

TYPE STRUCTURE FOR ...	Purpose	Prerequisites	Possible Components
ACTION REQUEST	Used to specify whether actions should be executed based on request parameters, i. e. if the result of the action should be returned completely or only parts of it.	The notation result selective must be specified for an action.	Key and data fields are typed with ABP_BEHV_FLAG.
AUTHORIZATION REQUEST \lbr INSTANCE AUTHORIZATION REQUEST	Used to retrieve information on instance-based authorization in the context of handler method implementations of GET PERMISSIONS statements. Request parameters, that have been specified for RAP BO instances to define the conditions of the permission information retrieval, serve as import parameters for the corresponding handler methods. For example, the information retrieval for certain operations can be enabled or disabled. \lbr \lbr A specification with AUTHORIZATION REQUEST is the same as with INSTANCE AUTHORIZATION REQUEST.	An authorization check must be specified in the BDEF using the property instance. See the details in the CDS BDL documentation for authorization.	The availability of the following components depends on the context and definition in the BDEF, that is, only a subset of the components below can be expected to be available. \lbr \lbr Subcomponents of %action and %assoc typed with ABP_BEHV_FLAG \lbr \lbr%create, %delete and %update typed with ABP_BEHV_FLAG
FEATURES REQUEST \lbr INSTANCE FEATURES REQUEST	Used for retrieving instance feature control information in the context of handler method implementations of GET PERMISSIONS statements. Request parameters, that have been specified for RAP BO instances to define the conditions of the permission information retrieval, serve as import parameters for the corresponding handler methods. For example, the information retrieval for certain operations can be enabled or disabled. \lbr \lbr A specification with FEATURES REQUEST is the same as with INSTANCE FEATURES REQUEST.	The property features: instance must be specified in the BDEF.	The availability of the following components depends on the context and definitions in the BDEF, that is, only a subset of the below components can be expected to be available. \lbr \lbr Subcomponents of %action and %assoc typed with ABP_BEHV_FLAG\lbr \lbr%create, %delete and %update typed with ABP_BEHV_FLAG \lbr \lbr Subcomponents of %field typed with ABP_BEHV_FEATURE
FUNCTION REQUEST	Used to specify whether functions should be executed based on request parameters, i. e. if the result of the function should be returned completely or only parts of it.	The notation result selective must be specified for a function.	Key and data fields typed with ABP_BEHV_FLAG.
GLOBAL FEATURES RESULT	Used for retrieving information on global feature control in the context of handler method implementations of GET PERMISSIONS statements. The result contains the outcome of the permission information retrieval for global features based on the request parameters.	The property features: global must be specified in the BDEF.	The availability of the following components depends on the context and definition in the BDEF, that is, only a subset of the below components can be expected to be available. \lbr \lbr Subcomponents of %action and %assoc typed with ABP_BEHV_FLAG \lbr \lbr%create, %delete and %update typed with ABP_BEHV_FLAG
GLOBAL AUTHORIZATION REQUEST	Used to retrieve information on global authorization in the context of handler method implementations of GET PERMISSIONS statements. Request parameters, that have been specified for RAP BO instances to define the conditions of the permission information retrieval, serve as import parameters for the corresponding handler methods. For example, the information retrieval for certain operations can be enabled or disabled.	An authorization check must be specified in the BDEF using the property global. See the details in the CDS BDL documentation for authorization.	The availability of the following components depends on the context and definition in the BDEF, that is, only a subset of the below components can be expected to be available. \lbr \lbr Subcomponents of %action typed with ABP_BEHV_FLAG \lbr\lbr%create, %delete and %update typed with ABP_BEHV_FLAG
GLOBAL AUTHORIZATION RESULT	Used to retrieve information on global authorization in the context of handler method implementations of GET PERMISSIONS statements. The result contains the outcome of the permission information retrieval for global authorization based on the request parameters.	An authorization check must be specified in the BDEF using the property global. See the details in the CDS BDL documentation for authorization.	The availability of the following components depends on the context and definition in the BDEF, that is, only a subset of the below components can be expected to be available. \lbr \lbr Subcomponents of %action and %assoc typed with ABP_BEHV_FLAG \lbr \lbr%create, %delete and %update typed with ABP_BEHV_FLAG
GLOBAL FEATURES REQUEST	Used to retrieve information on global feature control in the context of handler method implementations of GET PERMISSIONS statements. Request parameters, that have been specified for RAP BO instances to define the conditions of the permission information retrieval, serve as import parameters for the corresponding handler methods. For example, the information retrieval for certain operations can be enabled or disabled.	The property features: global must be specified in the BDEF.	The availability of the following components depends on the context and definition in the BDEF, that is, only a subset of the below components can be expected to be available. \lbr \lbr Subcomponents of %action and %assoc typed with ABP_BEHV_FLAG \lbr \lbr%create, %delete and %update typed with ABP_BEHV_FLAG
PERMISSIONS REQUEST	Used to retrieve permission information in the context of GET PERMISSIONS statements. Request parameters are specified for RAP BO instances to define the conditions of the permission information retrieval, for example, if information retrieval for certain operations is enabled or disabled.	Operations, actions, associations and fields must be specified in the BDEF so that the respective components are available in the structure. For details on the BDEF specifications, see the subtopics in ABAP CDS - BDL for Behavior Definitions.	The availability of the following components depends on the context and definitions in the BDEF, that is, only a subset of the below components can be expected to be available. \lbr \lbr Subcomponents of %action and %assoc typed with ABP_BEHV_FLAG \lbr \lbr%create, %delete and %update typed with ABP_BEHV_FLAG \lbr \lbr Subcomponents of %field typed with ABP_BEHV_FEATURE
PERMISSIONS RESULT	Used to retrieve permission information in the context of GET PERMISSIONS statements. The result contains the outcome of the permission information retrieval for global and instance authorization, global and instance feature control and static feature control.	Operations, actions, associations and fields must be specified in the BDEF so that the respective components are available in the structure. For details on the BDEF specifications, see the subtopics in ABAP CDS - BDL for Behavior Definitions.	The availability of the following components depends on the context and definition in the BDEF, that is, only a subset of the below components can be expected to be available. \lbr \lbr Internal table instances holding the following components: \lbr Key names directly (not %keys etc.) retaining the full line type; \lbr subcomponents of %action and %assoc typed with ABP_BEHV_FLAG; \lbr %delete and %update typed with ABP_BEHV_FLAG; \lbr subcomponents of %field typed with ABP_BEHV_FEATURE; the permissions can also be addressed via the component group %perm \lbr \lbr Structure global holding the following components: \lbr Subcomponents of %action and %assoc typed with ABP_BEHV_FLAG ; \lbr %create, %delete and %update typed with ABP_BEHV_FLAG; \lbr subcomponents of %field typed with ABP_BEHV_FEATURE

Overview 2

The following table covers the variants that are available for both TYPE STRUCTURE FOR and TYPE TABLE FOR.

TYPE STRUCTURE FOR ...	Purpose	Prerequisites	Components

The example Display BDEF Derived Type Components allows you to explore the various BDEF derived type components and their availability in variables type 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 STRUCTURE 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 STRUCTURE FOR HIERARCHY is demonstrated in the example Using TYPE TABLE/TYPE STRUCTURE FOR HIERARCHY.

Addresses (Business Address Services) BAL_S_LOG - Application Log: Log header data
This documentation is copyright by SAP AG.

Length: 26579 Date: 20240423 Time: 134403 sap01-206 ( 349 ms )

Ansicht Dokumentation