Do you have any question about this error?
Message type: E = Error
Message class: CM_EHDGM_API_CRR_TBR - TBR Pattern-specific Messages for CRR API
Message number: 060
Message text: &1, &2: Company Substance &3 is not valid.
You want to import a content-based regulation for a dangerous goods
assessment for an unpackaged product. However, you have provided a
company substance for one or more of the following fields that are not
available in the system:
- Technical Name 1 / 2 / 3
- Marine Pollutant Name 1 / 2
- Reportable Quantity Name 1 / 2
Without a valid company substance, the system does not import the data.
Provide a valid company substance for the dangerous good assessment and
start the import again.
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_EHDGM_API_CRR_TBR060
- &1, &2: Company Substance &3 is not valid. ?The SAP error message CM_EHDGM_API_CRR_TBR060 typically indicates that there is an issue with the company substance specified in the transaction or process you are trying to execute. This error message is often related to the management of substances in the context of compliance, regulatory reporting, or environmental health and safety (EHS) modules within SAP.
Cause:
Invalid Company Substance: The company substance you are trying to use is not recognized in the system. This could be due to:
- The substance not being created or activated in the system.
- A typo or incorrect entry in the substance code.
- The substance being marked as inactive or deleted.
Configuration Issues: There may be configuration issues in the EHS module or the specific area where the substance is being used.
Data Consistency: There might be inconsistencies in the data related to the company substance, such as missing or incorrect master data.
Solution:
Verify Substance Existence:
- Check if the company substance exists in the system. You can do this by navigating to the relevant transaction (e.g., EHS-related transactions) and searching for the substance using its code.
Check Substance Status:
- Ensure that the substance is active and not marked as inactive or deleted. You can check the status in the substance master data.
Correct Entry:
- If there is a typo or incorrect entry, correct it and try the transaction again.
Create/Activate Substance:
- If the substance does not exist, you may need to create it. Ensure that all required fields are filled out correctly and that the substance is activated.
Review Configuration:
- If the issue persists, review the configuration settings in the EHS module to ensure that everything is set up correctly.
Consult Documentation:
- Refer to SAP documentation or help resources for specific guidance on managing substances in your version of SAP.
Contact Support:
- If you are unable to resolve the issue, consider reaching out to your SAP support team or consulting with SAP support for further assistance.
Related Information:
By following these steps, you should be able to identify the cause of the error and implement a solution.
Get instant SAP help. Start your 7-day free trial now.
CM_EHDGM_API_CRR_TBR056
&1, &2, &3, &4: Basic description has no parent assessment.
What causes this issue? You want to import a dangerous goods basic description for a dangerous goods assessment for an unpackaged product. However, y...
CM_EHDGM_API_CRR_TBR055
&1, &2: No basic description provided for language "&3".
What causes this issue? You want to import data for a dangerous goods assessment. However, you have not provided a text for the dangerous good descri...
CM_EHDGM_API_CRR_TBR100
Creating dangerous goods assessment not possible due to dependent data.
What causes this issue? The creation of dangerous goods assessments is not possible. This is the case because the first step - creating the unpackage...
CM_EHDGM_BO_CRR000
&4 Before releasing, classify the product.
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.