How To Fix /SCMB/MDL_BASIC123 - Location key &1 (category DUNS+4) not found

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMB/MDL_BASIC -

• Message number: 123

• Message text: Location key &1 (category DUNS+4) 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_BASIC123 - Location key &1 (category DUNS+4) not found ?

  The SAP error message /SCMB/MDL_BASIC123 Location key &1 (category DUNS+4) not found typically occurs in the context of SAP Supply Chain Management (SCM) or Advanced Planning and Optimization (APO) when the system is unable to find a specific location key that is expected to be present in the database. The location key in this case is identified by the DUNS+4 category, which is a specific format used for identifying locations.
  Cause:
  
  Missing Location Data: The location key (DUNS+4) that you are trying to use does not exist in the system. This could be due to data not being uploaded or created in the system.
  Incorrect Configuration: The configuration settings for location management may not be set up correctly, leading to the system not recognizing the location key.
  Data Synchronization Issues: If the data is supposed to be synchronized from another system (like an ERP system), there may be issues with the data transfer or mapping.
  Typographical Error: There may be a typographical error in the location key being referenced.
  
  Solution:
  
  Verify Location Key: Check the location key you are using to ensure it is correct. Look for any typographical errors.
  Check Location Master Data: Go to the relevant transaction in SAP (e.g., /SCMB/MDL_LOC or similar) to check if the location key exists. If it does not, you may need to create it.
  Create Missing Location: If the location key is indeed missing, you will need to create it in the system. Ensure that you have the necessary permissions to do so.
  Data Upload: If the location data is supposed to be uploaded from another system, ensure that the upload process has been completed successfully and that there are no errors in the data transfer.
  Consult Documentation: Review the relevant SAP documentation or configuration guides to ensure that the DUNS+4 format is being used correctly and that all necessary settings are in place.
  Check for Customizations: If your SAP system has custom developments or enhancements, check if they might be affecting the location key retrieval process.
  
  Related Information:
  
  DUNS+4: This is a unique identifier for businesses, consisting of a DUNS number followed by a four-digit extension. It is often used for identifying specific locations of a business.
  Master Data Management: Ensure that your master data management processes are robust and that all necessary data is maintained accurately in the system.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  Transaction Codes: Familiarize yourself with relevant transaction codes for managing location data, such as /SCMB/MDL_LOC for location management.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or a technical consultant who specializes in SAP SCM or APO.