C0 Contract Rules for Consumers of CDS Behavior Definitions

ABAP - Keyword Documentation → ABAP - Rules for Strict ABAP → Contract Rules for Released APIs → C0 Contract Rules → C0 Contract Rules for CDS Behavior Definitions →

Mail Feedback

The provider rules for objects with C0 contract ensure that released objects are changed only in a very restricted way and help to avoid errors and interruptions after an SAP upgrade. Nevertheless, the rules do not prescribe full downward compatibility and leave some room for necessary enhancements to released APIs. Therefore, users of released APIs still have to consider the allowed compatible changes and access the APIs in such a way that the following errors and interruptions are avoided:

Problems during the upgrade.
Syntax errors after the upgrade.
Runtime errors after an upgrade.
Wrong behavior after an upgrade.

When extending CDS behavior definitions, consumers must obey the following naming rules to avoid naming conflicts.

Naming

If the extension has a namespace prefix, such as /PREFIX/, the names of its elements must not start with a different namespace prefix, nor with Z, nor with Y.
If the name of the extension starts with Z or with Y, there is no check.
In all other cases, the names of the elements must not start with Z, nor Y, nor with a namespace prefix.

The checks apply to the following elements:

Alias names of RAP BO entities.
External names of RAP BO entities.
Alias names of associations, specified using abbreviation.
Alias names of RAP foreign entities.
Names of RAP actions and RAP functions.
External names of RAP actions and RAP functions.
External names of action and function results.
Names of RAP determinations and RAP validations.
Names of RAP BO determine actions.
Names of RAP events.

Example Topics

Example for a C0 released RAP BO which is extended from ABAP for Cloud Development.

Example for a C0 released service projection view which is extended from ABAP for Cloud Development.