Message type: E = Error
Message class: CM_CBESCOM_INB - Message Class for ESComXML Inbound Processing
Message number: 090
Message text: REACH registration number does not exist
The <DS:TX.EHSPRC_ESCOM_INB_REACHREG>REACH registration number</> is not
specified in the ESComXML file.
INCLUDE EHSPRC_ESCOM_INB_CHECK_RREGE OBJECT DOKU ID TX
ELSE
INCLUDE EHSPRC_ESCOM_INB_CHECK_RREGW OBJECT DOKU ID TX
ELSE
INCLUDE EHSPRC_ESCOM_INB_CHECK_RREGI OBJECT DOKU ID TX
You can process the data from the ESComXML file when the file status of
the file is set to <LS>Checked Successfully</> or <LS>Checked with
Warning</>. The file status is set based on the message type for the
check.
If you want to process the ESComXML file anyway, assign the <LS>Warning
</>, <LS>Information</>, or <LS>No Execution</> message type to the <LS>
Check REACH registration number</> check in the Customizing activity
<DS:SIMG.ESEESCC_INBMSG>Specify Message Types for Import Preparation</>.
ELSE
The file status is set based on the message type for the check.
If you do <ZU>not</> want to process the ESComXML file, assign the <LS>
Error</> message type to the <LS>Check REACH registration number</>
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 delete the ESComXML file.
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.
CM_CBESCOM_INB090
- REACH registration number does not exist ?The SAP error message CM_CBESCOM_INB090 indicating that the "REACH registration number does not exist" typically arises in the context of compliance with the REACH (Registration, Evaluation, Authorisation, and Restriction of Chemicals) regulation in the European Union. This regulation requires companies to register chemical substances they manufacture or import into the EU.
Cause: Missing Registration: The most common cause of this error is that the REACH registration number you are trying to use does not exist in the system. This could be due to: The substance has not been registered. The registration number was entered incorrectly (typos, wrong format). The registration number is not associated with the specific material or product in question. Data Synchronization Issues: If your system is integrated with external databases or systems, there may be synchronization issues leading to the absence of the registration number.
Configuration Issues: There may be configuration issues in the SAP system that prevent the proper recognition of the registration
Get instant SAP help. Sign up for our Free Essentials Plan.
CM_CBESCOM_INB089
Details for contributing scenarios could not be generated
What causes this issue? The system could not generate contributing scenario data for an entry in the worklist. The system has determined contributing...
CM_CBESCOM_INB088
&1 ESCom phrases and &2 non-ESCom phrases exist
What causes this issue? The ESComXML file contains &V1& <DS:TX.EHSPRC_ESCOM_INB_ESCOM_PHRAS> ESCom phrases</> and &V2& &l...
CM_CBESCOM_INB091
Error while initializing BAdI BADI_EHSS_ESC_INB_PROCESSING
What causes this issue? Internal system error while determining the implementation of BAdI <DS:SIMG.BADI_EHSS_ESC_INB_PROCESSING>BADI_EHSS_ESC_...
CM_CBESCOM_INB092
No active implementation of BAdI BADI_EHSS_ESC_INB_PROCESSING
What causes this issue? Internal system error while determining the implementation of BAdI <DS:SIMG.BADI_EHSS_ESC_INB_PROCESSING>BADI_EHSS_ESC_...
Click on this link to search all SAP messages.