How To Fix REXCSK260 - Inconsistency between posting date &1 and period &2


SAP Error Message - Details

  • Message type: E = Error

  • Message class: REXCSK - Localzation SK

  • Message number: 260

  • Message text: Inconsistency between posting date &1 and period &2

  • Show details Hide details


  • 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 REXCSK260 - Inconsistency between posting date &1 and period &2 ?

    The SAP error message REXCSK260 indicates an inconsistency between the posting date and the period in the context of financial postings. This error typically arises when a transaction is being processed, and the posting date does not align with the defined periods in the financial calendar.

    Cause:

    1. Posting Date Issue: The posting date of the transaction falls outside the open periods defined in the financial settings. For example, if the posting date is in a closed period, the system will throw this error.
    2. Period Locking: The financial period may be locked for posting, preventing any transactions from being recorded in that period.
    3. Configuration Errors: There may be misconfigurations in the fiscal year variant or period settings in the system.

    Solution:

    1. Check Posting Date: Verify the posting date of the transaction. Ensure that it falls within an open period. If necessary, adjust the posting date to a valid period.
    2. Open Periods: Review the period settings in the financial module (Transaction code: OB52) to ensure that the period for the posting date is open for posting.
    3. Unlock Period: If the period is closed but needs to be opened for specific transactions, you can unlock it temporarily in the period settings.
    4. Fiscal Year Variant: Ensure that the fiscal year variant is correctly configured and that the periods are set up as intended.
    5. Consult with Finance Team: If you are unsure about changing any settings, consult with your finance team or SAP administrator to ensure compliance with accounting policies.

    Related Information:

    • Transaction Codes:
      • OB52: To manage the open and closed periods.
      • OB29: To check and configure fiscal year variants.
    • SAP Notes: Check for any relevant SAP Notes that may address specific issues related to this error message.
    • Documentation: Review SAP documentation on financial posting and period management for further insights into handling posting date and period issues.

    By following these steps, you should be able to resolve the REXCSK260 error and ensure that your financial postings are processed correctly.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


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's SAP support assistant is amazing. Saves me countless hours trying to solve complex SAP issues myself. It's a real game changer!
Rate 1
Thomas Michael
SAP Consultant, Author & Speaker