Get Example source ABAP code based on a different SAP table
ID GET-FEATURES ID GET-GLOBAL-FEATURES ID GET-GLOBAL-FEATURES-DYN ID GET-FEATURES-DYN • GET FEATURES ABAP Statement • GET GLOBAL FEATURES ABAP Statement
GET FEATURES
ABAP_SYNTAX_OBS Syntax Forms Short Form
GET FEATURES ENTITY bdef FROM keys REQUEST request RESULT result_tab $[response_param$].
GET GLOBAL FEATURES ENTITY bdef REQUEST request RESULT result_tab .
Long Form
GET FEATURES OF bdef ENTITY bdef1 FROM keys REQUEST req RESULT result_tab $[ENTITY bdef2 FROM keys REQUEST req RESULT result_tab$] $[...$] $[response_param$].
GET GLOBAL FEATURES OF bdef ENTITY bdef1 FROM keys REQUEST req RESULT result_tab $[ENTITY bdef2 FROM keys REQUEST req RESULT result_tab$] $[...$] .
BEGIN_SECTION VERSION 5 OUT Dynamic Form
GET FEATURES OPERATIONS features_tab $[response_param$].
GET GLOBAL FEATURES OPERATIONS global_features_tab. END_SECTION VERSION 5 OUT
ABAP_ALTERNATIVES: 1 GET FEATURES ENTITY..., GET GLOBAL FEATURES ENTITY ... 2 GET FEATURES OF ..., GET GLOBAL FEATURES OF ... 3 GET FEATURES OPERATIONS ..., GET GLOBAL FEATURES OPERATIONS ...
What does it do? GET PERMISSIONS statements should be used instead. Retrieves information about the following:
Global feature control: Feature controls that depend on external factors like specific user settings or the business scope.
Instance feature control: Checks depending on the state of an entity instance.
Static feature control: Specifies individual fields of an entity that have certain access restrictions, for example, fields that are marked as readonly in the BDEF. For all characteristics, the information retrieval must be user-implemented in RAP BO provider implementations except for static feature controls. In latter case, the access restriction is directly defined in the BDEF. One example is when a field is marked as readonly. Syntax Details Syntax PartDetails bdefSpecifies the name of the RAP BO root entity. keysSpecifies an internal table of type TYPE TABLE FOR $[INSTANCE$] FEATURES KEY . ENTITY bdef1, ENTITY bdef2, ... bdef1, bdef2 , ..., specify the names of the entities that are part of the composition tree of bdef . They follow the keyword ENTITY. lbr lbr A list of queries follows OF bdef. Each query (ENTITY bdef1 ... RESULT result_tab) of the list has the same syntax as the short form. At least one query must be specified. The root entity itself can also be inserted in the position of bdef1, for example. bdef1, and so on, should be the entity alias names if provided in the BDEF. Using the full entity name causes a warning. If the root entity is used in the list of operations, its alias name, if defined in the BDEF, should be used as well. reqSpecifies the request parameters in a structure of type TYPE STRUCTURE FOR $[INSTANCE$] FEATURES REQUEST or TYPE STRUCTURE FOR GLOBAL FEATURES REQUEST respectively. result_tabSpecifies an internal table containing the result of the information retrieval. See more information here . response_paramSpecifies the response parameters. See more information here. features_tabSpecifies an internal table for the dynamic form. It is of type ABP_BEHV_FEATURES_TAB . global_features_tabSpecifies an internal table for the dynamic form. It is of type ABP_BEHV_GLOBAL_PERMISSION_TAB.
Latest notes: If the recommended notation strict is used in the BDEF, GET FEATURES statements are not possible and the use of GET PERMISSIONS statements is enforced. ABAP_HINT_END
ABAP Alternative 1 GET FEATURES ENTITY..., GET GLOBAL FEATURES ENTITY ...
What does it do? The short form of the statement allows information to be retrieved about a single entity.
ABAP Alternative 2 GET FEATURES OF ..., GET GLOBAL FEATURES OF ...
What does it do? The long form of the statement allows information to be retrieved about multiple entities.
ABAP Alternative 3 GET FEATURES OPERATIONS ..., GET GLOBAL FEATURES OPERATIONS ...
What does it do? The dynamic form of the statement allows multiple instances to be collected for which information should be retrieved in multiple entities in one statement.
