/CEERE/DM260 - Inconsistency between posting date &1 and period &2

SAP Error Message - Details

• Message type: E = Error

• Message class: /CEERE/DM -

• Message number: 260

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

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.

AnswerBot

• What is the cause and solution for SAP error message /CEERE/DM260 - Inconsistency between posting date &1 and period &2 ?

  The SAP error message /CEERE/DM260 Inconsistency between posting date &1 and period &2 typically indicates that there is a mismatch between the posting date of a document and the fiscal period that the system expects based on the configuration of the financial calendar. This can occur in various SAP modules, particularly in Financial Accounting (FI) and Controlling (CO).
  Cause:
  
  Posting Date Issue: The posting date of the document falls outside the allowed periods defined in the fiscal calendar. For example, if the posting date is in a closed period, the system will raise this error.
  Period Locking: The period may be locked for posting due to various reasons, such as month-end closing activities or year-end closing activities.
  Configuration Errors: There may be configuration issues in the fiscal year variant or the posting periods that do not align with the posting date.
  Document Type Restrictions: Certain document types may have restrictions on the periods they can be posted to.
  
  Solution:
  
  Check Posting Date: Verify the posting date of the document. Ensure that it falls within an open period in the fiscal calendar.
  Open the Period: If the period is closed and you need to post to it, you may need to open the period temporarily. This can be done by navigating to the transaction code OB52 (Change View "Posting Periods": Overview) and adjusting the period settings.
  Review Configuration: Check the configuration of the fiscal year variant and ensure that the periods are set up correctly. This can be done in the transaction code OB29 (Define Fiscal Year Variant).
  Document Type Settings: Review the settings for the document type being used to ensure that it allows postings to the specified period.
  Consult with Finance Team: If you are unsure about opening periods or making changes, consult with your finance team or SAP administrator to ensure compliance with accounting policies.
  
  Related Information:
  
  Transaction Codes:
  
  OB52: Change View "Posting Periods": Overview
  OB29: Define Fiscal Year Variant
  FB50: Enter G/L Account Document (for testing posting)
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to this error message.
  Documentation: Review SAP documentation on fiscal year variants and posting periods for a deeper understanding of how they work.
  
  By following these steps, you should be able to resolve the inconsistency error and successfully post your document.