/ACCGO/FEE136 - Accrual posting started

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/FEE -

• Message number: 136

• Message text: Accrual posting started

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 /ACCGO/FEE136 - Accrual posting started ?

  The SAP error message /ACCGO/FEE136 Accrual posting started typically indicates that an accrual posting process has been initiated but has not been completed successfully. This message is often related to the Accrual Engine in SAP, which is used for managing and posting accruals in financial accounting.
  Possible Causes:
  
  Incomplete Configuration: The accrual engine may not be properly configured, leading to issues during the posting process.
  Missing Data: Required data for the accrual posting may be missing or incorrect, such as account assignments, amounts, or periods.
  Locking Issues: Another process may be locking the necessary tables or data, preventing the accrual posting from completing.
  Authorization Issues: The user may not have the necessary authorizations to perform the accrual posting.
  System Errors: There may be underlying system errors or inconsistencies in the database that are preventing the posting from completing.
  
  Solutions:
  
  Check Configuration: Review the configuration settings for the accrual engine to ensure everything is set up correctly.
  Validate Data: Ensure that all required data for the accrual posting is present and correct. This includes checking the relevant master data and transaction data.
  Monitor Locks: Use transaction codes like SM12 to check for any locks on the relevant tables and resolve them if necessary.
  Review Authorizations: Ensure that the user has the necessary authorizations to perform the accrual posting. This can be checked in transaction SU53 or by consulting with your security team.
  Check Logs: Review the application logs (transaction SLG1) for any additional error messages or warnings that may provide more context on the issue.
  System Health Check: Perform a system health check to identify any underlying issues that may be affecting the accrual posting process.
  
  Related Information:
  
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  ACCRUALS: For managing accruals.
  SLG1: For checking application logs.
  SM12: For monitoring locks.
  SU53: For checking authorization issues.
  
  
  
  Documentation: Refer to SAP documentation or help resources for detailed information on the accrual engine and its configuration.
  
  
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address known issues related to this error message.
  
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or reach out to SAP support for further assistance.