How To Fix CM_CBESCOM_INB121 - Non-ESCom phrase &3 exists: attribute '&1', section '&2'

CM_CBESCOM_INB121 - Overview

• Message type: E = Error

• Message class: CM_CBESCOM_INB - Message Class for ESComXML Inbound Processing

• Message number: 121

• Message text: Non-ESCom phrase &3 exists: attribute '&1', section '&2'

Information

What causes this issue?

The following attribute contains a <DS:TX.EHSPRC_ESCOM_INB_NON_ESCPHR>
non-ESCom phrase</> &V3&:
Attribute: &V1&
Section: &V2&

System Response

The <DS:DE.ESEESC_FILE_STATUS>file status</> of the ESComXML file is set
to <LS>Checked Successfully</>. The <DS:DE.ESEESC_INB_PROC_STATUS_ICON>
processing status</> of the import request is set to <LS>Check Completed
</>.

How to fix this error?

When you import ESComXML data, the system replaces non-ESCom phrases
with the <DS:TX.EHSPRC_ESCOM_PLHD_PHRASE>placeholder phrase</> and
copies these to the characteristic values of the specifications.
You then need to replace the placeholder phrases with your phrases. Use
the extended safety data sheet (eSDS) to assign the correct phrases.
The file status is set based on the <DS:DE.ESEESC_INB_CHECK_ID>message
type</> for the check. If you do <ZU>not</> want to process the ESComXML
file, assign the <ZH>Error</> message type to the <LS>Non-ESCom Phrase
Is Assigned</> check in the Customizing activity
<DS:SIMG.ESEESCC_INBMSG>Specify Message Types for Import Preparation</>.
The system sets the file status to <LS>Checked with Errors</> and the
file cannot be processed.
You can then delete the ESComXML file.

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message CM_CBESCOM_INB121 - Non-ESCom phrase &3 exists: attribute '&1', section '&2' ?

  The SAP error message CM_CBESCOM_INB121 indicates that there is a non-ESCom (Enterprise Services Communication) phrase that exists in the system. This error typically arises in the context of managing communication and integration scenarios within SAP, particularly when dealing with phrases or messages that are not properly defined or are conflicting with existing definitions.
  
  Cause:
  
  Non-ESCom Phrase: The error suggests that there is a phrase that is not part of the ESCom framework, which may lead to inconsistencies in communication scenarios.
  Attribute and Section Issues: The error message specifies an attribute and a section, indicating that there is a specific configuration or definition that is causing the issue. This could be due to:
  Incorrect or missing definitions in the communication setup.
  Conflicts between existing phrases and the new phrases being defined.
  Misconfiguration in the communication settings or integration scenarios.
  
  
  
  
  Solution:
  
  Check Phrase Definitions: Review the definitions of the phrases in the system. Ensure that the phrases are correctly defined