How To Fix RDSV_FI_XX333 - Posting date &1 is currently not possible; date &2 is locked by &3

SAP Error Message - Details

• Message type: E = Error

• Message class: RDSV_FI_XX - Regulatory Document and Signature Validation in FI

• Message number: 333

• Message text: Posting date &1 is currently not possible; date &2 is locked by &3

What causes this issue?

Another user is currently creating a document with a date that is
earlier or later than the date in your document. To ensure that all
documents with digital signatures are numbered chronologically, the
other user must save their document first before you try to create your
document.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

System Response

The system does not let you post your document.

How to fix this error?

Try again later.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message RDSV_FI_XX333 - Posting date &1 is currently not possible; date &2 is locked by &3 ?

  The SAP error message RDSV_FI_XX333 indicates that there is an issue with the posting date in a financial transaction. Specifically, it means that the posting date you are trying to use is currently not possible because the date is locked by a specific user or process. Here’s a breakdown of the cause, potential solutions, and related information:
  Cause:
  
  
  Date Locking: The posting date you are trying to use is locked for posting by a user or a process. This can happen if:
  
  The period is closed for posting in the financial module.
  A user has locked the date for specific transactions.
  There are ongoing processes (like month-end closing) that prevent postings on that date.
  
  
  
  Configuration Settings: The system may have specific configuration settings that restrict postings to certain dates or periods.
  
  
  Solution:
  
  
  Check Lock Status:
  
  Use transaction code SM12 to check for any locks on the posting date. Look for entries that correspond to the date you are trying to post.
  If you find a lock that is no longer needed, you can delete it (if you have the necessary authorizations).
  
  
  
  Review Period Closing:
  
  Check if the financial period is closed. You can do this by going to transaction code OB52 (Change View "Periods": Overview).
  If the period is closed, you may need to open it again temporarily to allow postings, or you may need to post in the next open period.
  
  
  
  Consult with Users:
  
  If the date is locked by a specific user, consult with that user to understand why the lock is in place and if it can be released.
  
  
  
  Adjust Posting Date:
  
  If the posting date is not critical, consider using a different date that is open for posting.
  
  
  
  Check Configuration:
  
  Review the configuration settings in the financial module to ensure that there are no restrictions that are causing the lock.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SM12: To view and manage locks.
  OB52: To check and manage posting periods.
  FB50: To post general ledger entries (if applicable).
  
  
  
  User Authorizations: Ensure that you have the necessary authorizations to view locks and change posting periods.
  
  
  Documentation: Refer to SAP documentation or help resources for more detailed information on financial posting and period management.
  
  
  If the issue persists after trying the above solutions, it may be necessary to involve your SAP Basis or technical support team for further investigation.