ABAP for Cloud Development, ©Copyright 2024 SAP SE. All rights reserved.

ABAP - Keyword Documentation →  ABAP - Rules for ABAP Cloud →  Contract Rules for ABAP Released APIs →  C1 Contract Rules →  C1 Contract Rules for API Providers → 

C1 Contract Rules for Providing Objects Implemented in ABAP

Others than the following objects cannot be classified with the C1 contract.

• Classes and Interfaces
  • Classes must be final or abstract and the instantiation must be private.
  • Changes to public elementary types must follow the rules for elementary data types.

    No components can be removed from public structured types.

    Public table types must not be generic. Their row types and table keys must not be changed.

  • Attributes and method parameters must not be changed. Their data types must be released.
  • Methods must not be deleted, their kind (static, instance) must not be changed and visibility must not be reduced. They must raise class-based exceptions only.
  • Interface methods cannot be added without defining a default behavior.
  • Optional parameters can be added to methods and events. The preferred parameter must be stable. An optional parameter cannot become mandatory.
• AMDP classes

  AMDP classes are classes that implement the tag interface IF_AMDP_MARKER_HDB. AMDP classes must obey the general rules for classes listed above and the following special rules:

  • Optional parameters must not be added to methods.
  • The order of parameters must not be changed.
  • The property READ-ONLY must not be removed. It can be specified either in the method declaration with the addition AMDP OPTIONS READ-ONLY or in the method implementation with the addition OPTIONS READ-ONLY. It must not be fully removed, but it can be moved from the method declaration to the method implementation or vice versa.
  • The option CDS SESSION CLIENT must not be added or removed.
  • The addition CDS SESSION CLIENT CURRENT must not be changed to CDS SESSION CLIENT clnt.
  • The option CLIENT INDEPENDENT must not be removed.
  • The addition FOR DDL OBJECT must not be added or removed.
  • The method implementation must not be changed from an AMDP method to an ABAP method.
  • The implementation language, specified using the addition LANGUAGE, must not be changed.
  • An AMDP method can be an AMDP procedure, an AMDP function, or a graph workspace. The type of method must not be changed.
• Function modules
  • Function modules can only be released for language version ABAP for Cloud Development.
  • Remote-enabled or update function modules cannot be changed to regular ones and their properties must be stable.
  • Parameters must not be changed.
  • Optional parameters can be added. An optional parameter cannot become mandatory.
  • Exceptions cannot be added and non-class-based exceptions must not be deleted.