AS ABAP Release 758, ©Copyright 2024 SAP SE. All rights reserved.

ABAP - Keyword Documentation →  ABAP - Rules for ABAP Cloud →  Contract Rules for ABAP Released APIs →  C0 Contract Rules →  C0 Contract Rules for RAP Behavior Definitions → 

C0 Contract Rules for Consumers of RAP Behavior Definitions

The provider rules for objects with a 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, the 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 an upgrade.
• Syntax errors after an upgrade.
• Runtime errors after an upgrade.
• Wrong behavior after an upgrade.

When extending BDEFs, consumers must obey the following naming rules to avoid naming conflicts.

Naming Rules  

The following applies to extensions in ABAP for Cloud Development:

1. If the extension has a namespace prefix, such as /PREFIX/, its elements must also have this prefix.
2. If the name of the extension starts with Z or with Y, its element names must begin with ZZ or with YY. Additionally, if the element name begins with YY, this prefix YY must not be followed by A, M, S, or the digits 1 to 9.
3. Otherwise, if the name of the extension does not start with Z or with Y, the element name must not begin with a namespace prefix, nor with ZZ or YY.
4. If the behavior for an extension node is defined (extension entity behavior definition), the element names inside this entity must either be without prefix, or they are checked against the name of the extension according to the rules above.

The following applies to extensions in Standard ABAP:

• Element names must either be without prefix, or the element names are checked against the name of the extension according to rules 1 - 3 listed above.

The checks apply to the following elements:

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

Example Topics  

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

Example for a C0 released projection BDEF which is extended from the language version ABAP for Cloud Development.