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


RDSV_FI_XX333 - Overview

  • 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

  • Show details Hide details
  • 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

    Already have an account? Login here!




Instant HelpGet instant SAP help. Sign up for our Free Essentials Plan.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant