How To Fix 1E129 - Selection of accounts after closure date

SAP Error Message - Details

• Message type: E = Error

• Message class: 1E - BCA: Account

• Message number: 129

• Message text: Selection of accounts after closure date

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 1E129 - Selection of accounts after closure date ?

  The SAP error message 1E129 ("Selection of accounts after closure date") typically occurs when a user attempts to access or process financial data for accounts that have been closed for a specific period. This is a common issue in financial modules, particularly in SAP FI (Financial Accounting), where periods are closed to prevent further postings.
  Cause:
  The error is triggered when:
  
  A user tries to post a transaction or run a report for a period that has already been closed.
  The system settings or configuration do not allow postings to closed periods, which is a standard practice to maintain the integrity of financial data.
  
  Solution:
  To resolve this error, you can consider the following steps:
  
  
  Check the Posting Period:
  
  Verify the current posting period in the system. You can do this by navigating to the transaction code OB52 (Change View "Posting Periods": Overview).
  Ensure that the period you are trying to access is open for posting.
  
  
  
  Open the Period:
  
  If you need to make adjustments or postings for a closed period, you can temporarily open the period in transaction OB52. However, this should be done with caution and typically requires appropriate authorization.
  After making necessary adjustments, it is advisable to close the period again to maintain data integrity.
  
  
  
  Review Configuration:
  
  Check the configuration settings for your company code to ensure that the period control settings align with your business processes. This can be done in the configuration menu under Financial Accounting.
  
  
  
  Consult with Finance Team:
  
  If you are unsure about opening a closed period or if it is against company policy, consult with your finance team or SAP administrator for guidance.
  
  
  
  Use Alternative Reporting:
  
  If the error occurs while trying to generate reports, consider using alternative reporting methods or tools that do not require access to closed periods.
  
  
  
  Related Information:
  
  Transaction Codes: 
  
  OB52: Change Posting Periods
  FBV0: Park Document
  FB60: Enter Incoming Invoice
  
  
  SAP Notes: Check for any relevant SAP Notes that may provide additional insights or updates related to this error message.
  Documentation: Review SAP documentation for financial period closing procedures to understand best practices and implications of opening closed periods.
  
  Best Practices:
  
  Always follow your organization's policies regarding financial period management.
  Document any changes made to posting periods for audit purposes.
  Regularly communicate with your finance team to ensure alignment on financial processes.
  
  By following these steps, you should be able to address the error message 1E129 effectively.