How To Fix WS473 - &1: &4 to customer &2 (condition type &3)

SAP Error Message - Details

• Message type: E = Error

• Message class: WS - Supplier Billing Document

• Message number: 473

• Message text: &1: &4 to customer &2 (condition type &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 WS473 - &1: &4 to customer &2 (condition type &3) ?

  Certainly! Here's a detailed explanation for the SAP error message:
  
  SAP Error Message:
  WS473 &1: &4 to customer &2 (condition type &3)
  
  1. Cause of the Error
  This message typically occurs during pricing or condition processing in Sales and Distribution (SD) when the system tries to apply a condition record to a customer but encounters an issue related to the condition type or customer master data.
  
  &1: Usually the message class or context (e.g., "Pricing error" or "Condition error").
  &2: Customer number.
  &3: Condition type (e.g., PR00, K004).
  &4: Specific error text or description related to the condition application.
  
  Common causes include:
  
  The condition record for the specified condition type (&3) is not valid or missing for the customer (&2).
  The customer master data is incomplete or missing relevant pricing or condition data.
  The condition type is not maintained or allowed for the customer or sales area.
  The validity period of the condition record does not cover the document date.
  Pricing procedure does not