How To Fix W+673 - Reference customer & does not exist

SAP Error Message - Details

• Message type: E = Error

• Message class: W+ -

• Message number: 673

• Message text: Reference customer & does not exist

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 W+673 - Reference customer & does not exist ?

  SAP Error Message:
  
  W+673 Reference customer & does not exist
  
  Cause:
  This warning message occurs when a reference customer number entered in a transaction or master data does not exist in the system. Essentially, the system is trying to find a customer record with the given customer number, but it cannot locate it in the customer master data (usually in tables like KNA1).
  Common scenarios include:
  
  Entering a reference customer number that is mistyped or incorrect.
  Using a reference customer number that has been deleted or not yet created.
  Data migration or integration issues where reference customer numbers are inconsistent.
  Custom developments or enhancements that expect a valid reference customer but receive an invalid one.
  
  
  Solution:
  
  
  Verify the Reference Customer Number:
  
  Check the customer number entered as the reference customer.
  Use transaction XD03 or FD03 to display the customer master and confirm if the customer exists.
  
  
  
  Correct the Reference Customer Number:
  
  If the number is incorrect, update it with the correct customer number.
  If the reference customer is optional and not needed, consider removing it.
  
  
  
  Create the Missing Customer Master Record:
  
  If the reference customer does not exist but is required, create the customer master record using XD01 or FD01.
  
  
  
  Check Data Consistency:
  
  For data migration or batch input, verify the source data for accuracy.
  Run consistency checks or reports to identify missing or invalid reference customers.
  
  
  
  Review Custom Code or Enhancements:
  
  If the error arises from custom developments, debug the code to ensure it handles reference customers correctly.
  Add validations or error handling as needed.
  
  
  
  
  Related Information:
  
  Message Class: W+673 is typically a warning message, so it may not stop processing but indicates a data issue.
  Tables Involved:  
  
  KNA1 (General Customer Data)  
  KNVV (Customer Sales Data)  
  KNB1 (Customer Company Code Data)
  
  
  Transactions to Check Customer Master:  
  
  XD03 - Display Customer (Sales Area)  
  FD03 - Display Customer (Accounting)  
  XD01 / FD01 - Create Customer
  
  
  Notes and SAP Help:  
  
  Check SAP Notes related to customer master data inconsistencies.
  Review SAP documentation on customer master data and reference customer fields.
  
  
  
  
  Summary:
  The warning W+673 Reference customer & does not exist indicates that the system cannot find the specified reference customer number. To resolve it, verify and correct the reference customer number or create the missing customer master record. Also, ensure data consistency and review any custom logic that might be causing the issue.