How To Fix /SRMSMC/MDG_SUPPLIER010 - No contact person relationship exists for contact person &1

SAP Error Message - Details

• Message type: E = Error

• Message class: /SRMSMC/MDG_SUPPLIER -

• Message number: 010

• Message text: No contact person relationship exists for contact person &1

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message /SRMSMC/MDG_SUPPLIER010 - No contact person relationship exists for contact person &1 ?

  The SAP error message /SRMSMC/MDG_SUPPLIER010 indicates that there is no contact person relationship defined for the specified contact person in the context of Supplier Master Data Governance (MDG). This error typically arises when trying to create or update a supplier record that includes a contact person, but the system cannot find a valid relationship for that contact person.
  Cause:
  
  Missing Relationship: The contact person you are trying to associate with the supplier does not have a defined relationship in the system.
  Incorrect Data Entry: The contact person may not be correctly entered or may not exist in the system.
  Configuration Issues: There may be issues with the configuration of the contact person relationships in the MDG system.
  
  Solution:
  
  
  Check Contact Person Data:
  
  Verify that the contact person exists in the system. You can do this by searching for the contact person using their ID or name.
  Ensure that the contact person is active and not marked as inactive or deleted.
  
  
  
  Define Relationships:
  
  If the contact person exists but lacks a relationship, you need to create a relationship between the supplier and the contact person. This can typically be done in the MDG application by navigating to the relevant section for managing contact persons and suppliers.
  Ensure that the relationship type is correctly defined (e.g., primary contact, billing contact, etc.).
  
  
  
  Review Configuration:
  
  Check the configuration settings in the MDG system to ensure that the relationship types for contact persons are properly set up.
  Consult with your SAP Basis or MDG configuration team to ensure that all necessary settings are in place.
  
  
  
  Data Consistency:
  
  Ensure that the data being entered is consistent with the existing data in the system. Sometimes, discrepancies in data formats or values can lead to errors.
  
  
  
  Testing:
  
  After making the necessary changes, test the process again to see if the error persists.
  
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like BP (Business Partner) to manage contact persons and their relationships.
  MDG Configuration: Familiarize yourself with the MDG configuration settings related to business partners and contact persons.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance on managing contact person relationships.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or refer to SAP documentation for further troubleshooting.