How To Fix MDG_BS_BP_DATAREPL122 - Creditworthiness data transferred in two diff. nodes of service msg type

SAP Error Message - Details

• Message type: E = Error

• Message class: MDG_BS_BP_DATAREPL - Messages for Business Partner Data Replication

• Message number: 122

• Message text: Creditworthiness data transferred in two diff. nodes of service msg type

What causes this issue?

Service interface BusinessPartnerSUITEBulkReplicateRequest_In contains
two nodes for transferring creditworthiness data of a business partner:
CREDITWORTHINESS
CREDIT_MANAGEMENT_CREDIT_WORTH.
While calling the service interface creditworthiness data were
transferred in both nodes. In order to avoid data inconsistencies this
is not allowed.
Node CREDIT_MANAGEMENT_CREDIT_WORTH shall not be used any more. Please
use node CREDITWORTHINESS.

System Response

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

How to fix this error?

If you call the service from a custom environment, make sure that you
transfer creditworthiness data only in node CREDITWORTHINESS. If the
error occurs in a standard scenario, please implement BAdI
FSBP_ACTIVATE_OUTBOUND in the sender system according to SAP note
2858939 and deactivate the sending of the data in the obsolete credit
management node. You can use the example class of the BAdI for this.

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 MDG_BS_BP_DATAREPL122 - Creditworthiness data transferred in two diff. nodes of service msg type ?

  The SAP error message MDG_BS_BP_DATAREPL122 indicates that there is an issue with the creditworthiness data being transferred in two different nodes of the service message type during a data replication process in SAP Master Data Governance (MDG) for Business Partners (BP). This typically occurs when the system detects that the same creditworthiness data is being sent in multiple places within the same message, which can lead to inconsistencies or conflicts.
  Cause:
  
  Duplicate Data Nodes: The error is often caused by the presence of duplicate nodes in the service message. For example, if creditworthiness data is defined in both the "Creditworthiness" node and another related node, the system will raise this error.
  Configuration Issues: There may be a misconfiguration in the data model or service definition that allows for creditworthiness data to be included in multiple places.
  Data Replication Logic: The logic used for data replication might be incorrectly set up, leading to the same data being replicated in different parts of the message.
  
  Solution:
  
  Check the Service Message Structure: Review the structure of the service message being used for data replication. Ensure that creditworthiness data is only defined in one node.
  Adjust Data Model Configuration: If you have access to the data model configuration, ensure that the creditworthiness data is correctly mapped and not duplicated across different nodes.
  Review Replication Logic: Check the replication logic and ensure that it is correctly set up to avoid sending the same data in multiple nodes.
  Test with Sample Data: After making adjustments, test the replication process with sample data to ensure that the error does not occur again.
  Consult Documentation: Refer to SAP documentation or notes related to MDG and the specific service message type for any additional guidance or known issues.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  MDG Configuration: Familiarize yourself with the configuration settings in SAP MDG, especially those related to Business Partner data and replication processes.
  Debugging: If you have access to debugging tools, you can trace the replication process to identify where the duplicate nodes are being generated.
  Community Forums: Consider reaching out to SAP community forums or support channels for additional insights from other users who may have encountered similar issues.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.