Get Example source ABAP code based on a different SAP table
VERSION 5 IN VERSION X OUT
ABAP_CDS - Restrictions in DCL in Cloud Development In CDS DCL, the following restrictions apply to CDS roles and CDS access policies defined by customers and partners in ABAP_SAP_BTP_ENV and ABAP_S4_CLOUD_ENV :
An access control can use other development objects when these either belong to the same software component or are a released API with the C1 contract. This affects the following usage types:
CDS entities as data source for data source in PFCG mappings and user-defined aspects.
CDS entities or database tables which act as association target in any used path expression.
CDS entities used as inheritance source for access conditions or as selector for role-based inheritance.
Authorization objects
The following usage types cannot yet be released and are therefore limited to customer objects in the same software component:
Access roles used as inheritance source for role-based inheritance.
User-defined aspects and PFCG mappings.
SACF scenarios.
The protected entity itself can only be in the same software component as the access control.
In entity-based condition inheritance when inheriting from an entity not in the same software component, the following restrictions apply:
The usage of replacement step ROOT WITH is mandatory.
Replacement steps PARAMETER WITH and PFCG FILTER are allowed.
All other replacement steps cannot be used.
In role-based condition inheritance, the flavor without selector (GRANT SELECT ON ... INHERIT ...) is not allowed.
Latest notes: See Released APIs for a list of repository objects that are released as APIs in the current system. NON_V5_HINTS ABAP_HINT_END
