Get Example source ABAP code based on a different SAP table
VERSION 5 OUT ID SET-ENTITIES ID SET-CURRENT-ENTITIES • SET ENTITIES OF ABAP_STATEMENT_EML • BLOCKED SET ENTITIES OF • UNBLOCKED SET ENTITIES OF
SET ENTITIES
ABAP_SYNTAX SET ENTITIES OF root_ent BLOCKED$|UNBLOCKED.
ABAP Addition 1 ... BLOCKED 2 ... UNBLOCKED
What does it do? Blocks or unblocks the ABAP_EML access to RAP business objects. The statement can only be used in ABAP behavior pools. root_ent stands for the full name of a RAP BO root entity which must be specified. The statement is only allowed in the ABAP behavior pool of the specified RAP BO root entity. The following restrictions apply to the specification of root_ent. These are not allowed:
Child entities
Abstract root entities
Interface root entities
Projection root entities
Extensions ABAP_EML requests are blocked or unblocked for the following statements when using the SET ENTITIES statements for the specified root entities:
MODIFY ENTITY, ENTITIES
READ ENTITY, ENTITIES
GET PERMISSIONS
SET LOCKS The blocking is valid until the end of a RAP transaction . For each RAP BO root entity blocked in one or more statements, an internal counter is incremented in case of a SET ENTITIES OF ... BLOCKED statement and decremented in case of a SET ENTITIES OF ... UNBLOCKED statement. The counter cannot be negative. The value 0 in the counter means unblocked and a value greater than 0 means blocked. The value in the counter is only visible in the short dump message mentioned below. sy-subrc is set by the statement with both additions BLOCKED and UNBLOCKED in the same way:
0: The blocking status has changed successfully.
4: Set whenever the status blocked or unblocked has not changed for the specified root entity.
Latest notes:
A short dump is raised for blocked statements with the exception CX_ABAP_BEHV_RUNTIME_ERROR. The short dump contains the following information:
The affected RAP BO root entity
The current blocking counter for the affected root entity
The source position of the last SET ENTITIES OF ... BLOCKED statement for the affected root entity
ABAP_EML statements with the addition IN LOCAL MODE are affected in the same way as ABAP_EML statements without the addition.
In RAP create-by-association and read-by-association operations in the context of cross-BO associations , the affected source root entity and affected target root entity are checked for blockings. NON_V5_HINTS ABAP_HINT_END
ABAP Addition
What does it do? Blocks the ABAP_EML access to RAP business objects.
ABAP Addition
What does it do? Unblocks the ABAP_EML access to RAP business objects.
ABAP_EXAMPLE_ABEXA The example SET ENTITIES demonstrates the SET ENTITIES statements with a managed RAP BO. Note that this example produces a short dump. ABAP_EXAMPLE_END
