06620 - Price date lies in the past

SAP Error Message - Details

• Message type: E = Error

• Message class: 06 -

• Message number: 620

• Message text: Price date lies in the past

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 06620 - Price date lies in the past ?

  The SAP error message "06620 Price date lies in the past" typically occurs in the context of pricing and procurement processes, particularly when dealing with purchase orders, contracts, or pricing conditions. This error indicates that the price date you are trying to use is earlier than the current date, which is not allowed in the system.
  Cause:
  
  Price Date Configuration: The price date you are trying to enter or use is set to a date that has already passed. This can happen if you are trying to create or modify a document with a price condition that is no longer valid.
  Document Date: The document date (e.g., purchase order date) may also be set to a past date, which can affect the validity of the pricing conditions.
  Validity Period of Pricing Conditions: The pricing conditions may have a defined validity period, and if the current date is outside this range, the system will throw this error.
  
  Solution:
  
  Check the Price Date: Ensure that the price date you are entering is set to the current date or a future date. You can do this by reviewing the date fields in the transaction you are working on.
  Update Pricing Conditions: If the pricing conditions are outdated, you may need to update them to include the current date or a future date. This can be done in the condition records (transaction codes like MEK1, MEK2, MEK3 for maintaining pricing conditions).
  Review Document Dates: Make sure that the document date (e.g., for purchase orders or contracts) is also set correctly and is not in the past.
  Consult with Your SAP Administrator: If you are unsure about the pricing conditions or how to update them, consult with your SAP administrator or a colleague who has experience with pricing in SAP.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as ME21N (Create Purchase Order), ME22N (Change Purchase Order), MEK1 (Create Condition), MEK2 (Change Condition), and MEK3 (Display Condition).
  SAP Notes: Check SAP Notes for any specific patches or updates related to pricing issues.
  Documentation: Review SAP documentation or help files related to pricing and procurement processes for more detailed guidance.
  
  By following these steps, you should be able to resolve the "06620 Price date lies in the past" error in SAP.