How To Fix /SCMB/MDL_BASIC143 - Partner key &1 (category DUNS) not found

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMB/MDL_BASIC -

• Message number: 143

• Message text: Partner key &1 (category DUNS) not found

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 /SCMB/MDL_BASIC143 - Partner key &1 (category DUNS) not found ?

  The SAP error message /SCMB/MDL_BASIC143 Partner key &1 (category DUNS) not found typically occurs in the context of SAP Supply Chain Management (SCM) when the system is unable to find a partner key (in this case, a DUNS number) that is required for a specific business process. The DUNS (Data Universal Numbering System) is a unique identifier for businesses, and it is often used in supply chain and logistics processes.
  
  Cause:
  
  Missing DUNS Number: The most common cause of this error is that the DUNS number for the specified partner is not maintained in the system.
  Incorrect Partner Configuration: The partner profile may not be correctly configured, or the partner may not be set up in the system.
  Data Synchronization Issues: If the data is being pulled from an external system, there may be synchronization issues leading to missing or incorrect data.
  Incorrect Partner Key: The partner key being referenced may be incorrect or not