How To Fix VFRR104 - Log could not be written; changes not saved

SAP Error Message - Details

• Message type: E = Error

• Message class: VFRR - SD revenue recognition

• Message number: 104

• Message text: Log could not be written; changes not saved

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 VFRR104 - Log could not be written; changes not saved ?

  SAP Error Message:
  
  VFRR104: Log could not be written; changes not saved
  
  Cause:
  This error typically occurs during the execution of a transaction or process that involves logging changes or updates in SAP, particularly in the context of vendor invoice verification, invoice processing, or related financial postings. The system attempts to write an entry to a log table or change document but fails due to one or more of the following reasons:
  
  Database or table lock: The log table or related database object is locked by another process, preventing write access.
  Authorization issues: The user does not have sufficient authorization to write to the log or change document.
  Missing or inconsistent configuration: The logging mechanism or change document object is not properly configured or activated.
  Database or system errors: Underlying database errors, such as insufficient space, database inconsistencies, or transport errors.
  Custom enhancements or user exits: Custom code interfering with the logging process.
  Transport or client copy issues: Missing or inconsistent transport objects related to logging.
  
  
  Solution:
  To resolve the VFRR104 error, consider the following steps:
  
  
  Check system logs and dumps:
  
  Use transaction SM21 (System Log) and ST22 (ABAP Runtime Errors) to identify any related errors or dumps that provide more details.
  
  
  Check table locks:
  
  Use transaction SM12 to check for locks on the log tables or related objects. If locks exist, investigate and release them if appropriate.
  
  
  Verify authorizations:
  
  Ensure the user has the necessary authorizations to write change documents or logs. Check roles and profiles, especially for change document objects related to the process.
  
  
  Check change document configuration:  
  
  Use transaction SCDO to verify that the change document object related to the process is active and correctly configured.
  If the process involves vendor invoice verification, check the relevant change document objects (e.g., VBRK, RBKP).
  
  
  
  Database consistency and space:  
  
  Check database space and consistency.
  Run database consistency checks if necessary.
  Consult your database administrator if you suspect database issues.
  
  
  
  Review custom code:
  
  If there are user exits, BADIs, or enhancements in the process, review them for errors or improper handling of logging.
  
  
  Transport and client copy:
  
  Ensure that all relevant transport requests related to logging and change documents have been imported correctly and that the client copy is consistent.
  
  
  Retry the transaction:
  
  After resolving the above issues, retry the transaction to confirm the problem is fixed.
  
  
  
  Related Information:
  
  
  Transaction codes:  
  
  SM12 – Lock entries  
  SM21 – System log  
  ST22 – Dump analysis  
  SCDO – Change document objects  
  SE38 / SE80 – For checking custom code or logs
  
  
  
  SAP Notes:
  
  Search SAP Support Portal for notes related to VFRR104 or logging issues in invoice verification.
  
  
  Change Documents:
  
  SAP uses change documents to log changes to business objects. If these are not properly configured or activated, logging fails.
  
  
  Common modules involved:  
  
  FI (Financial Accounting)  
  MM (Materials Management)  
  Vendor Invoice Verification (transaction codes like MIRO)
  
  
  
  
  If the problem persists after these checks, consider raising a support ticket with SAP, providing detailed logs and system information.