How To Fix 1G086 - Old period could not be read (BKK92)

SAP Error Message - Details

• Message type: E = Error

• Message class: 1G - BKK: Konditionen

• Message number: 086

• Message text: Old period could not be read (BKK92)

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 1G086 - Old period could not be read (BKK92) ?

  The SAP error message 1G086 - Old period could not be read (BKK92) typically occurs in the context of financial transactions, particularly when dealing with bank accounting or cash management. This error indicates that the system is unable to access or read data from a previous accounting period, which may be necessary for processing certain transactions.
  Causes:
  
  Period Closing: The accounting period you are trying to access may have been closed. In SAP, once a period is closed, it is generally not possible to post transactions to that period.
  Authorization Issues: The user may not have the necessary authorizations to access the data for the specified period.
  Data Archiving: The data for the old period may have been archived, making it inaccessible for certain operations.
  Configuration Issues: There may be configuration settings in the financial module that restrict access to old periods.
  
  Solutions:
  
  
  Check Period Status: Verify if the accounting period is closed. You can do this by checking the period status in the financial accounting module (transaction code OB52).
  
  If the period is closed, you may need to reopen it temporarily to perform the necessary transactions, if allowed by your organization's policies.
  
  
  
  User Authorizations: Ensure that the user has the appropriate authorizations to access the required data. This can be checked with your SAP security team.
  
  
  Data Archiving: If the data has been archived, consult with your SAP Basis team to see if the archived data can be accessed or if it needs to be restored.
  
  
  Configuration Review: Review the configuration settings in the financial module to ensure that there are no restrictions on accessing old periods. This may involve checking settings in the financial accounting configuration (transaction code SPRO).
  
  
  Consult Documentation: Refer to SAP documentation or help resources for specific guidance related to the error message and the context in which it occurs.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OB52 (for managing posting periods) and BKK92 (for bank accounting transactions).
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP Notes can provide additional context or solutions.
  Support: If the issue persists, consider reaching out to SAP support or your internal SAP support team for further assistance.
  
  By following these steps, you should be able to diagnose and resolve the issue related to the error message 1G086 in SAP.