How To Fix CM_EHFND_API_CCI072 - &1: New version of &2 was not created.

SAP Error Message - Details

• Message type: E = Error

• Message class: CM_EHFND_API_CCI - Messages for chemical compliance view API

• Message number: 072

• Message text: &1: New version of &2 was not created.

What causes this issue?

The system could not create a new version of compostion &V2& for the
object &V3& with number &V1&.

System Response

The system does not change the compostion &V2& for the object &V3& with
number &V1&.

How to fix this error?

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CM_EHFND_API_CCI072 - &1: New version of &2 was not created. ?

  The SAP error message CM_EHFND_API_CCI072 typically indicates that there was an issue with creating a new version of a specific object (like a business object or configuration) in the SAP system. The message format suggests that it is related to a specific entity (denoted by &2) and that the operation did not succeed.
  Cause:
  
  Missing Required Data: The new version may not have been created due to missing mandatory fields or data that is required for the versioning process.
  Authorization Issues: The user may not have the necessary permissions to create a new version of the object.
  System Configuration: There may be configuration issues in the system that prevent the creation of new versions.
  Technical Errors: There could be underlying technical issues, such as database locks, system performance issues, or bugs in the application.
  
  Solution:
  
  Check Required Fields: Ensure that all mandatory fields are filled out correctly before attempting to create a new version.
  Review Authorizations: Verify that the user has the necessary authorizations to perform the action. This can be done by checking the user's roles and permissions in the SAP system.
  System Logs: Check the system logs (transaction codes like SLG1) for any additional error messages or warnings that could provide more context about the failure.
  Configuration Review: Review the configuration settings related to the object in question to ensure that everything is set up correctly.
  Technical Support: If the issue persists, consider reaching out to your SAP Basis or technical support team to investigate any underlying technical issues or bugs.
  
  Related Information:
  
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error message or provide patches and updates.
  Documentation: Review the official SAP documentation for the specific module or functionality you are working with to understand the requirements for creating new versions.
  Community Forums: Check SAP Community forums or other user groups for similar issues and solutions shared by other users.
  
  If you continue to experience issues after following these steps, it may be beneficial to provide detailed information about the context in which the error occurs to your SAP support team for further assistance.