What does it do? The following annotations are required for C0 release of a DDIC structure. They are evaluated only in the context of C0 release for developer extensibility .
@AbapCatalog.enhancement.fieldSuffix defines a 3-character element suffix suffix. This suffix is to be used for all fields of an extension created by customers or partners from a restricted ABAP language version. The purpose is to avoid field naming clashes. The following rules apply:
suffix must consist of exactly 3 alphabetical characters [A-Z].
If the object is a partner or customer object, the suffix must begin with Y or Z.
If the object is an SAP object, the suffix must not begin with Y or Z.
Field suffixes should be unique. If the specified field suffix is already registered by a different development object, a syntax check warning occurs.
@AbapCatalog.enhancement.quotaMaximumFields defines the maximum number of fields that can be appended to the corresponding object by customers and partners. In other words, it reserves a field count for customer and partner extensions. The annotation value integer must be an integer between 0 and 1000. A value between 100 and 560 is recommended. Otherwise, a syntax check warning occurs. The sum of fields of the original object and reserved fields must not exceed the technical limitations of the object in question. Current technical limitations are:
DDIC database table that is part of the software component SAP_BASIS : 750 fields.
DDIC database table, storage type Row Store: 1000 fields.
DDIC database table, storage type Column Store: 1500 fields.
DDIC structure: 9999 fields.
@AbapCatalog.enhancement.quotaMaximumBytes defines the maximum byte capacity that can be appended to the corresponding object by customers and partners. In other words, it reserves a byte capacity for customer and partner extensions. The annotation value integer must be an integer. The sum of bytes of the original object and reserved bytes must not exceed the technical limitation of 2 to the power of 19 minus 1 bytes (2^19-1). The recommended number of reserved bytes is between 1.000 and 56.000 bytes per structure.
@AbapCatalog.enhancement.quotaShareCustomer assigns a percentage of the defined field count and byte capacity to customer extensions. The annotation value integer can be an integer between 0 and 100. The customer quota share and the partner quota share must together add up to 100. ABAP_CAUTION Currently, a quota share of 50 is enforced.
@AbapCatalog.enhancement.quotaSharePartner assigns a percentage of the defined field count and byte capacity to partner extensions. The annotation value integer can be an integer between 0 and 100. The customer quota share and the partner quota share must together add up to 100. ABAP_CAUTION Currently, a quota share of 50 is enforced.
ABAP_FURTHER_INFO C0 Contract Rules for DDIC Objects
Latest notes:
The same annotations can also be specified in the definition of a DDIC database table using DEFINE TABLE for C0 release of the database table in question. NON_V5_HINTS
Extensibility annotations of DDIC structures and DDIC database tables can only be maintained in ABAP Development Tools . Maintenance in transaction SE11 is not supported. ABAP_HINT_END
