How To Fix WS642 - Inconsistent address data (&1/&2/&3)

SAP Error Message - Details

• Message type: E = Error

• Message class: WS - Supplier Billing Document

• Message number: 642

• Message text: Inconsistent address data (&1/&2/&3)

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 WS642 - Inconsistent address data (&1/&2/&3) ?

  SAP Error Message:
  
  WS642 - Inconsistent address data (&1/&2/&3)
  
  Cause:
  The error WS642 occurs when there is inconsistent or conflicting address data in the system. This typically happens during address maintenance or when the system tries to validate or synchronize address information across different components or tables. The placeholders (&1, &2, &3) represent specific fields or data elements that are inconsistent or conflicting.
  Common causes include:  
  
  Mismatched or incomplete address fields (e.g., postal code, city, country).  
  Conflicts between address data in different tables or modules (e.g., between customer master and vendor master).  
  Incorrect or missing mandatory address components.  
  Data inconsistencies due to manual changes or data migration errors.
  
  
  Solution:
  To resolve the WS642 error, follow these steps:
  
  
  Identify the conflicting fields:
  
  Check the message details to see which fields (&1, &2, &3) are causing the inconsistency.
  
  
  Review the address data:  
  
  Go to the relevant master data (e.g., customer, vendor, or business partner address).  
  Verify that all mandatory fields are correctly filled and consistent.  
  Check for typos, incorrect postal codes, or mismatched country codes.
  
  
  
  Correct the address data:  
  
  Update the inconsistent fields to ensure they align with each other and with SAP’s validation rules.  
  Use transaction codes like XD02 (Change Customer), MK02 (Change Vendor), or BP (Business Partner) to edit the address.
  
  
  
  Check integration points:
  
  If the address is used across modules (e.g., SD, MM, FI), ensure synchronization is correct. Sometimes, re-saving the address or running synchronization programs can help.
  
  
  Use SAP standard tools:  
  
  Run address validation or standard consistency checks if available.  
  Use transaction SARA for archiving and consistency checks if relevant.
  
  
  
  Consult SAP Notes:
  
  Search for SAP Notes related to WS642 for any known bugs or patches.
  
  
  
  Related Information:
  
  
  Transaction Codes:  
  
  BP – Business Partner maintenance  
  XD02 – Change Customer  
  MK02 – Change Vendor  
  SARA – Archive Administration (for consistency checks)
  
  
  
  Tables involved:  
  
  ADRC (Address table)  
  KNA1 (Customer master)  
  LFA1 (Vendor master)  
  BUT000 (Business Partner general data)
  
  
  
  SAP Modules:  
  
  SD (Sales and Distribution)  
  MM (Materials Management)  
  FI (Financial Accounting)  
  CRM (Customer Relationship Management)
  
  
  
  
  Summary:
  WS642 indicates that the system found inconsistent address data in certain fields. The fix involves identifying the conflicting fields, verifying and correcting the address data in the master records, and ensuring consistency across integrated modules. Always validate mandatory fields and use SAP standard transactions and tools to maintain address integrity.
  
  If you provide the exact values of &1, &2, &3 from the error message, I can help you pinpoint the exact fields causing the issue.