How To Fix WP999 - Date of transaction to old

SAP Error Message - Details

• Message type: E = Error

• Message class: WP - Messages from POS interface

• Message number: 999

• Message text: Date of transaction to old

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 WP999 - Date of transaction to old ?

  SAP Error Message:
  
  WP999 - Date of transaction too old
  
  Cause:
  This error occurs when you try to post a transaction with a posting date that is earlier than the allowed posting period or the system's configured tolerance for old dates. Essentially, the system is preventing you from entering a transaction date that is considered too far in the past based on the current posting period settings or validation rules.
  Common reasons include:  
  
  The posting date is before the open posting period in the relevant company code or ledger.  
  The posting date is outside the allowed tolerance period for back-dated postings configured in the system.  
  The fiscal year variant or posting period variant restricts postings to certain date ranges.  
  Custom validations or user-exits that restrict old dates.
  
  
  Solution:
  
  
  Check Posting Periods:
  
  Go to transaction OB52 (Maintain Posting Periods).
  Verify if the posting period for the relevant company code and account type is open for the date you are trying to post.
  If the period is closed, open the relevant posting period or use a valid posting date within an open period.
  
  
  
  Check Tolerance for Old Dates:
  
  Some configurations or validations restrict how far back you can post.
  Check if there is a custom validation or user-exit restricting old dates.
  If applicable, adjust the tolerance settings or update the posting date.
  
  
  
  Adjust Posting Date:
  
  Use a posting date within the allowed posting period.
  If the transaction date is a business requirement, request the responsible controlling or finance team to open the required posting period.
  
  
  
  Fiscal Year Variant and Posting Period Variant:
  
  Verify the fiscal year variant assigned to the company code (transaction OB29).
  Check the posting period variant (transaction OB52) to ensure the periods are correctly maintained.
  
  
  
  Check for Custom Validations:
  
  Sometimes, custom ABAP code (user-exits, BAdIs) may enforce date restrictions.
  Review any custom code that might be causing this error.
  
  
  
  
  Related Information:
  
  Transaction Codes:
  
  OB52 – Maintain Posting Periods
  OB29 – Fiscal Year Variant
  FB50 / FB60 / FB70 – Posting transactions where the error might occur
  
  
  SAP Notes: Search for SAP Notes related to WP999 for any specific patches or updates.
  User-Exits / BAdIs: Check for enhancements that might restrict posting dates.
  Authorization: Sometimes, posting in closed periods requires special authorization (check via transaction SU53 after the error).
  
  
  Summary:
  The error WP999 "Date of transaction too old" is triggered because the posting date is outside the allowed posting period or tolerance for old dates. To resolve it, ensure the posting period is open for the date, adjust the posting date, or modify the posting period settings accordingly. Also, verify if any custom validations are enforcing stricter date rules.
  
  If you need help with a specific scenario or system, please provide details such as the transaction code used, company code, and posting date attempted.