How To Fix SDDL_PARSER_MSG130 - Inconsistent annotation for client handling

SDDL_PARSER_MSG130 - Overview

• Message type: E = Error

• Message class: SDDL_PARSER_MSG - Message Class for DDL Parser

• Message number: 130

• Message text: Inconsistent annotation for client handling

What causes this issue?

Inconsistent annotations for client handling were discovered.
The following error situations can occur:
The different annotations for client handling must not be used in
combination: <NP>@ClientDependent</> or <NP>@ClientHandling.type</>, or
<NP>@ClientHandling.algorithm</>
An invalid value was used for one of the annotations <NP>
@ClientHandling.type</>, <NP>@ClientHandling.algorithm</>, or <NP>
@ClientDependent</>.
The combination of values for the annotation <NP>@ClientHandling.type</>
and <NP>@ClientHandling.algorithm</> is not allowed.
In this case, the inconsistencey that occurred refers to &V1&.

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.

SDDL_PARSER_MSG130 - Details

• The SAP error message SDDL_PARSER_MSG130 indicates that there is an inconsistency in the annotations related to client handling in your SAP system. This error typically arises when there are discrepancies in the way client handling is defined in the system's data model or configuration.
  
  Cause:
  
  
  Inconsistent Annotations: The error usually occurs when there are conflicting or inconsistent annotations in the data model regarding how client handling should be managed. This can happen if different parts of the model specify different client handling strategies (e.g., whether a certain entity should be client-specific or client-independent).
  
  
  
  Configuration Issues: If the configuration settings for client handling are not aligned across different components or if there are missing configurations, this can lead to the error.
  
  
  Transport Issues: If changes were transported from one system to another (e.g., from development to production) and the annotations were not properly aligned, this could also trigger the error.
  
  
  
  Solution:
  
  
  Review Annotations: Check the annotations in