How To Fix CM_EHDGM_COMMON003 - &2, &1: A new version could not be created.

CM_EHDGM_COMMON003 - Overview

• Message type: E = Error

• Message class: CM_EHDGM_COMMON - Common messages for Dangerous Goods Management

• Message number: 003

• Message text: &2, &1: A new version could not be created.

What causes this issue?

You want to create a new version for dangerous goods classification
records that are in status <LS>Historical</> or <LS>In Progress.</>
However, a new version can only be created for dangerous goods
classification records in status <LS>Released</>.

System Response

The system only allows the creation of a new version for dangerous goods
classification records in status<LS> Released</>.

How to fix this error?

Make sure the dangerous goods classification records you want to create
a new version for are in status <LS>Released</>.

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.

CM_EHDGM_COMMON003 - Details

• The SAP error message CM_EHDGM_COMMON003 typically indicates that there was an issue when trying to create a new version of a document or object in the SAP system. The message format includes placeholders like &1 and &2, which are replaced with specific details relevant to the error context.
  Possible Causes:
  
  Missing Authorizations: The user may not have the necessary permissions to create a new version of the document or object.
  Locking Issues: The object may be locked by another user or process, preventing the creation of a new version.
  
  Configuration Issues: There may be configuration settings in the system that are preventing the versioning process.
  Data Integrity Issues: There could be issues with the data that is being used to create the new version, such as missing mandatory fields or invalid data.
  Technical Errors: There may be underlying technical issues, such as database problems or system inconsistencies.
  
  Solutions:
  
  Check Authorizations: Ensure that the user has the necessary authorizations