Get Example source ABAP code based on a different SAP table
• EXTEND OWN AUTHORIZATION CONTEXT ABAP_BDL_EXTENSION
ABAP_RAP - extend own authorization context
ABAP_SYNTAX extend own authorization context { $[AuthObject1;$] $[AuthObject2;$] $[...$] }
What does it do? Extends a full authorization context using the statement extend own authorization context by adding further authorization objects AuthObject1, AuthObject2, ... to the context. If the original BDEF defines a full authorization context and the extension implementation uses authorization objects which are not used in the original implementation, you should extend the full authorization context to ensure a complete and exhaustive list. Like for the original BDEF, the full authorization context is evaluated by certain contract checks and if it is not complete, a runtime error occurs. As a prerequisite, the original BDEF must define a full authorization context. If this is the case, the full authorization context can be extended without any explicit extensibility enabling. If the original BDEF does not define a full authorization context, it must not be added via an extension. An extension full authorization context may be defined before, between, or after the other components of an extension BDEF. It is also possible to define an empty own authorization context. For details on the concept of an own authorization context, see topic TITLE .
ABAP_EXAMPLE_VX5 The following BDEF extension DEMO_RAP_EXT_AUTH_CONTEXT extends the RAP behavior definition DEMO_RAP_OWN_AUTH_CONTEXT. It adds one further authorization object to the context. ABAP_NOTE This example is intentionally kept short and simple and serves demonstration purposes only. The RAP handler methods of the ABAP behavior pool are not implemented here. In a real-life scenario, AUTHOBJ5 would be implemented in the ABAP behavior pool. BDEF DEMO_RAP_EXT_AUTH_CONTEXT ABAP_EXAMPLE_END
