C0 Contract Rules for Providers of DDIC Objects

The following sections show the most important C0 contract rules for DDIC objects.

Prerequisites for C0 Release

The following DDIC objects can be released under the C0 contract for extensibility: DDIC structures and DDIC database tables.
The DDIC object must be marked as extensible by means of the annotation @AbapCatalog.enhancement.category. The following annotation values are possible for this annotation for C0 release: #EXTENSIBLE_CHARACTER_NUMERIC and #EXTENSIBLE_ANY.
The DDIC object must define a 3-character long element suffix using the annotation @AbapCatalog.enhancement.fieldSuffix.
Caution: Multiple objects with identical field suffixes can never be included as include structure in the same object.
The DDIC object must define a quota that preserves capacity for extension content. Both annotations @AbapCatalog.enhancement.quotaMaximumFields and @AbapCatalog.enhancement.quotaMaximumBytes are mandatory. The maximum number of fields should be an integer between 100 and 560 and the maximum number of bytes should be set to a value between 1000 and 56.000.
The DDIC object must define a quota share that distributes the field count and byte count between customer and partner extensions. Both annotations @AbapCatalog.enhancement.quotaShareCustomer and @AbapCatalog.enhancement.quotaSharePartner are mandatory. Currently, the value of both annotations must be set to 50.

Stability Rules After Release

The object in question must not be deleted and the release contract must not be removed.
The type of dictionary object must not be changed after a C0 release. That means a database table must not be changed into a structure and vice versa.
The storage type must not be changed from Columns Store to Row Store after C0 release.
The extensibility annotations must not be removed after a C0 release. Changes are allowed within strict limits:
- @AbapCatalog.enhancement.category must not be removed and its value must not be reduced. This means its value must not be changed from #EXTENSIBLE_ANY to #EXTENSIBLE_CHARACTER_NUMERIC. The reverse way is possible, though.
- The maximum field and byte capacity defined in @AbapCatalog.enhancement.quotaMaximumFields and @AbapCatalog.enhancement.quotaMaximumBytes must not be reduced.
- The element suffix defined with @AbapCatalog.enhancement.fieldSuffix must not be changed.
- The quota share values defined in @AbapCatalog.enhancement.quotaShareCustomer and @AbapCatalog.enhancement.quotaSharePartner must not be changed.