How To Fix /SCMTMS/MSG473 - Business partner &1 does not exist or is marked for archiving

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/MSG -

• Message number: 473

• Message text: Business partner &1 does not exist or is marked for archiving

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 /SCMTMS/MSG473 - Business partner &1 does not exist or is marked for archiving ?

  The SAP error message /SCMTMS/MSG473 indicates that a business partner (BP) referenced in a transaction does not exist in the system or is marked for archiving. This error typically occurs in the context of SAP Transportation Management (TM) when the system tries to access a business partner that is either not created or has been archived.
  Cause:
  
  Non-Existent Business Partner: The business partner ID referenced in the transaction does not exist in the system.
  Archived Business Partner: The business partner exists but has been marked for archiving, meaning it is no longer active in the system.
  Incorrect Configuration: There may be configuration issues or incorrect data entries that lead to the system not being able to find the business partner.
  Data Synchronization Issues: If the business partner data is maintained in a different system (like SAP S/4HANA or another ERP), there may be synchronization issues.
  
  Solution:
  
  
  Check Business Partner Existence:
  
  Go to the transaction code BP (Business Partner) in SAP.
  Search for the business partner ID mentioned in the error message.
  If it does not exist, you will need to create it.
  
  
  
  Check for Archiving:
  
  If the business partner exists but is marked for archiving, you can check the archiving status.
  Use transaction code SARA to check the archiving status of business partners.
  If the business partner is archived, you may need to unarchive it or create a new active business partner.
  
  
  
  Data Consistency Check:
  
  Ensure that the business partner data is consistent across all relevant systems.
  If you are using multiple systems, ensure that the data is synchronized.
  
  
  
  Review Configuration:
  
  Check the configuration settings in SAP TM to ensure that the business partner settings are correctly defined.
  Ensure that the business partner roles and relationships are properly set up.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to business partner management and archiving for further guidance.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  BP: Business Partner Maintenance
  SARA: Archive Administration
  
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Business Partner Roles: Ensure that the business partner has the necessary roles assigned for the operations you are trying to perform in SAP TM.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or reach out to SAP support for further assistance.