ABAP CDS Access Control in ABAP Release 7.55

ABAP - Keyword Documentation → ABAP - ABAP Release News → News for ABAP Release 7.5x → News for ABAP Release 7.55 →

1. Check with element IS [NOT] INITIAL in a Literal Condition

2. Addition bypass when

3. Check on the User Name in User Conditions

4. Data Types

5. Aspect Bypass Conditions

6. Quantifier Operators

Modification 1

Check with element IS [NOT] INITIAL in a Literal Condition

In a literal condition, IS [NOT] INITIAL can now be used to check whether the value of the left side matches (does not match) the initial value of the ABAP data type that matches the element.

Modification 2

Addition bypass when

The addition BYPASS WHEN can now be used to specify a bypass condition for an element. If the condition is met, the element in question is not used for authorization filtering.

Modification 3

Check on the User Name in User Conditions

When the user name is checked in user conditions, the following can now be checked instead of the user name:

The value of the alias.
The number of the business partner assigned to the user.

Modification 4

Data Types

The operand that can be specified on the left side of a condition of an access rule of a CDS role can now have the built-in ABAP Dictionary data type RAW.

Modification 5

Aspect Bypass Conditions

IS [NOT] INITIAL and IS INITIAL OR NULL are now possible as aspect bypass conditions.

Modification 6

Quantifier Operators

With the new addition ALL, access conditions can express that access shall only be granted when from a set-valued association all values satisfy the condition.

WHERE ALL toItem.State = 'A'

To accompany this use case, the BYPASS WHEN operator has been extended to literal conditions also.

A dedicated operator EXISTS can be used when different access conditions using the same set-valued association shall not be coupled in their fields by means of a common join expression.

More Information