How To Fix SDDL_PARSER_MSG143 - Old and new client annotations must not be combined

SDDL_PARSER_MSG143 - Overview

• Message type: E = Error

• Message class: SDDL_PARSER_MSG - Message Class for DDL Parser

• Message number: 143

• Message text: Old and new client annotations must not be combined

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message SDDL_PARSER_MSG143 - Old and new client annotations must not be combined ?

  The SAP error message SDDL_PARSER_MSG143 indicates that there is a conflict between old and new client annotations in your SAP system. This typically occurs when there is an attempt to use both old-style and new-style annotations in the same context, which is not allowed.
  
  Cause:
  
  Mixing Annotations: The error arises when both old and new client annotations are used together in a single request or configuration. This can happen during the development of OData services or when configuring SAP Gateway services.
  Inconsistent Metadata: If the metadata definitions for the service are not consistent, it can lead to this error. This might occur if there are changes in the service definitions that have not been properly updated or synchronized.
  
  
  Solution:
  
  
  Review Annotations: Check the annotations used in your OData service or configuration. Ensure that you are using either the old or the new style, but not both. 
  
  Old annotations typically start with @ and are used