How To Fix FARR_CONTRACT_DB095 - Cannot save application log.

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_CONTRACT_DB - Revenue Accounting - Contract DB Access

• Message number: 095

• Message text: Cannot save application log.

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 FARR_CONTRACT_DB095 - Cannot save application log. ?

  The SAP error message FARR_CONTRACT_DB095: Cannot save application log typically indicates an issue with the application log system in SAP, particularly related to the Financial Accounting (FI) module or Asset Accounting (AA) module. This error can occur due to various reasons, including database issues, authorization problems, or configuration errors.
  Causes:
  
  Database Issues: The database may be full, or there may be issues with the database connection.
  Authorization Problems: The user may not have the necessary authorizations to write to the application log.
  Configuration Errors: There may be issues with the configuration of the application log settings in the system.
  Log Table Issues: The application log tables may be locked or corrupted.
  System Performance: High system load or performance issues may prevent the log from being saved.
  
  Solutions:
  
  
  Check Database Space:
  
  Ensure that there is enough space in the database. If the database is full, you may need to free up space or increase the database size.
  
  
  
  Review Authorizations:
  
  Check the user’s authorizations to ensure they have the necessary permissions to write to the application log. You can use transaction code SU53 to analyze authorization issues.
  
  
  
  Check Application Log Configuration:
  
  Review the configuration settings for the application log. You can check the settings in transaction code SLG0 (Application Log: Object Management).
  
  
  
  Check Log Tables:
  
  Use transaction code SE11 to check the application log tables (e.g., SLG1, SLG2). Ensure that they are not locked or corrupted. You may need to perform a database consistency check.
  
  
  
  System Performance:
  
  Monitor system performance and check for any background jobs or processes that may be causing delays. You can use transaction codes SM37 (Job Monitoring) and ST22 (Dump Analysis) to investigate.
  
  
  
  Clear Old Logs:
  
  If the application log tables are filled with old logs, consider archiving or deleting old logs to free up space. You can use transaction SLG2 to manage application logs.
  
  
  
  Check for Notes and Patches:
  
  Check the SAP Support Portal for any relevant SAP Notes or patches that may address this specific error.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SLG0: Application Log: Object Management
  SLG1: Display Application Log
  SLG2: Delete Application Log
  SE11: Data Dictionary
  SM37: Job Monitoring
  ST22: Dump Analysis
  
  
  
  SAP Notes: Search for specific SAP Notes related to the error message FARR_CONTRACT_DB095 in the SAP Support Portal for additional guidance and solutions.
  
  
  If the issue persists after trying the above solutions, it may be necessary to involve your SAP Basis team or SAP support for further investigation.