How To Fix CRD_MDA104 - Call of versioning terminated with errors

CRD_MDA104 - Overview

• Message type: E = Error

• Message class: CRD_MDA - Messages for Master Data Administration - Credentialing

• Message number: 104

• Message text: Call of versioning terminated with errors

What causes this issue?

The call of versioning during the creation of a
<DS:GLOS.44AE7E27422C5061E10000000A1553FE>credential assignment</>
terminated with an error. The causes for the incorrect call of
versioning may be incomplete effective dates or an external assignment
ID that already exists on the database.
The following assignment to be created caused the error:
<DS:GLOS.44B20C2B4AE64888E10000000A1553FE>Credential type</>: &v1&
<DS:GLOS.44B0EE2DD54B5062E10000000A1553FE>Credential description</>:
&v2&
Efective start date: &v3&
Effective end date: &v4&

System Response

The incorrect assignment is <ZH>not</> created on the database.

How to fix this error?

Check that correct data exists to call the creation of a credential
assignment.

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 CRD_MDA104 - Call of versioning terminated with errors ?

  The SAP error message CRD_MDA104: Call of versioning terminated with errors typically occurs in the context of SAP's Master Data Management (MDM) or related data management processes. This error indicates that there was a problem during the versioning process of master data objects, which can be due to various reasons.
  Causes:
  
  
  Data Integrity Issues: There may be inconsistencies or integrity violations in the data being processed. This could include missing mandatory fields, invalid data formats, or relationships that are not properly defined.
  
  
  Configuration Errors: Incorrect configuration settings in the MDM system or in the versioning process can lead to this error. This includes settings related to versioning rules, data models, or workflows.
  
  
  Authorization Issues: The user or process attempting to perform the versioning may not have the necessary permissions to execute the operation.
  
  
  System Performance: If the system is under heavy load or if there are performance issues, it may lead to timeouts or failures