How To Fix ARS_DEP_ATC000 - API State: Consistency Checks for Objects Released as APIs

SAP Error Message - Details

• Message type: E = Error

• Message class: ARS_DEP_ATC - Dependency and Basic Release Checks – ATC Messages

• Message number: 000

• Message text: API State: Consistency Checks for Objects Released as APIs

What causes this issue?

SAP can release development objects like CDS views, classes or
interfaces as stable APIs for a dedicated purpose. Depending on the
purpose, these objects must comply to a corresponding compatibility
contract:
C0 (Add Custom Fields via Key User App)
This contract ensures stability at dedicated extension points in APIs.
These extension points are defined using transaction SCFD_REGISTRY and
must only be used for adding custom fields using app <ZK>Custom Fields
and Logic</>.
C1 (System-Internal Use)
This contract ensures a technically stable public interface for
system-internal use. Compatibility of the public interface includes all
its existing parameters, elements, associations to released targets, and
their technical data types. Further optional parameters, elements, or
associations might be added later, but existing parameters, elements, or
associations must not be changed or even removed. Alphanumeric elements
might be elongated but will never be shortened.
C2 (Use as Remote API)
This contract ensures a technically stable public interface for use as
remote API. Similar to contract C1, compatibility of the public
interface includes all its existing parameters, elements, associations
to released targets, and their technical data types. Further optional
parameters, elements, or associations might be added later, but existing
parameters, elements, or associations must not be changed or even
removed. But in addition to contract C1, to ensure that external
consumers of the API do not need to be adjusted after an upgrade, also
the elongation of its elements and parameters is not allowed.
C3 (Manage Configuration Content)
This contract ensures a stable persistence for own configuration content
that can be exported, imported, displayed and edited using dedicated
APIs and editors. Compatibility of the persistence includes its key
definition and all the fields. Optional non-key fields might be added
later, but existing fields must not be changed or even removed.
Alphanumeric fields might be elongated but will never be shortened.
Furthermore, the customer namespace reservations for a released table
must not be changed.
To be usable by customers in a restricted development environment,
released APIs must fulfill increased consistency requirements.

System Response

Each released API is checked for consistency. These checks comprise of
<ZK>dependency checks</> (i.e. whether only other released development
objects are referenced in the public part of the API),
<ZK>object-type-independent checks</> (e.g. whether an appropriate
successor was specified for a deprecated API), <ZK>object-type-specific
checks</> (e.g. whether a released class is FINAL) and
<ZK>domain-specific checks </>(e.g. whether the use of a specific
annotation is allowed in a CDS view released for system-internal use)

How to fix this error?

Each check message describes an inconsistency in a development object
which was released as API.
Depending on the severity of the inconsistency, an error, warning or
info is raised. Errors must be solved by removing the inconsistency.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.