How To Fix EWA670 - Customer &1 is locked on order date &2 (Loc: &3, Cont. &4)

SAP Error Message - Details

• Message type: E = Error

• Message class: EWA - IS-U-WA: Waste Management

• Message number: 670

• Message text: Customer &1 is locked on order date &2 (Loc: &3, Cont. &4)

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 EWA670 - Customer &1 is locked on order date &2 (Loc: &3, Cont. &4) ?

  The SAP error message EWA670 indicates that a customer is locked for a specific order date, which can prevent certain operations from being performed, such as creating or modifying orders for that customer. Here’s a breakdown of the cause, potential solutions, and related information for this error:
  Cause:
  
  
  Customer Locking: The customer is locked in the system for the specified order date. This could be due to various reasons, such as:
  
  The customer has outstanding issues (e.g., credit holds, disputes).
  The customer is locked for maintenance or administrative reasons.
  The order date falls within a period where the customer is not allowed to place orders (e.g., due to a business rule or policy).
  
  
  
  Configuration Settings: There may be specific configuration settings in the SAP system that enforce customer locking based on certain criteria.
  
  
  Solution:
  
  
  Check Customer Status: 
  
  Use transaction codes like XD03 (Display Customer) or VD03 (Display Customer Sales Area) to check the status of the customer. Look for any indicators that show the customer is locked or has issues.
  
  
  
  Unlock the Customer:
  
  If the customer is locked due to administrative reasons, you may need to unlock them. This can typically be done by a user with the appropriate authorization using transaction codes like XD02 (Change Customer) or VD02 (Change Customer Sales Area).
  
  
  
  Review Order Date:
  
  Ensure that the order date you are trying to use is valid and does not fall within a restricted period for that customer.
  
  
  
  Consult with Relevant Departments:
  
  If the lock is due to credit issues or disputes, consult with the finance or sales department to resolve any outstanding issues.
  
  
  
  Check Configuration:
  
  If the locking behavior seems unusual, it may be necessary to review the configuration settings in the SAP system. This may require assistance from an SAP Basis or configuration expert.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as XD03, VD03, XD02, and VD02 for customer management.
  User Authorizations: Ensure that you have the necessary authorizations to view and change customer data.
  Documentation: Refer to SAP documentation or help files for more detailed information on customer management and locking mechanisms.
  Support: If the issue persists, consider reaching out to your SAP support team or consulting SAP Notes for any known issues related to this error message.
  
  By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.