How To Fix FMCF779 - Carryforward of document &1/&2 reset; automatic carryforward forbidden

SAP Error Message - Details

• Message type: E = Error

• Message class: FMCF -

• Message number: 779

• Message text: Carryforward of document &1/&2 reset; automatic carryforward forbidden

What causes this issue?

The line &V2& in the accounting document &V1& was first carried forward
to the fiscal year &V3&. Following this, the carryforward was reset
manually using transaction <ZH>FMJ3</>.

System Response

Since the one-level approval procedure has been activated for the
commitment carryforward, the current program assumes that the commitment
carryforward has approved this document line in error.
Since however the standard fiscal year change using the transaction <ZH>
FMJ2</> is the prerequisite for a new automatic commitment carryforward,
the current program cannot perform this automatic commitment carry
forward.

How to fix this error?

If necessary, carry the document &V1& forward to the fiscal year &V3&
using transaction <ZH>FMJ2</>.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FMCF779 - Carryforward of document &1/&2 reset; automatic carryforward forbidden ?

  The SAP error message FMCF779 indicates that the carryforward of a document has been reset, and automatic carryforward is forbidden. This typically occurs in the context of financial accounting, particularly when dealing with year-end closing processes or the carryforward of balances from one fiscal year to the next.
  Cause:
  
  
  Document Status: The document specified (identified by &1/&2) may have been marked in a way that prevents it from being carried forward. This could be due to various reasons, such as the document being incomplete, having errors, or being in a status that does not allow carryforward.
  
  
  Configuration Settings: The system settings may be configured to disallow automatic carryforward for certain types of documents or under specific conditions.
  
  
  Posting Period: The posting period may be closed, or the document may be dated in a period that is not eligible for carryforward.
  
  
  Manual Reset: The carryforward process may have been manually reset by a user or through a process that requires user intervention.
  
  
  Solution:
  
  
  Check Document Status: Review the status of the document in question. Ensure that it is complete and does not have any errors that would prevent carryforward.
  
  
  Review Configuration: Check the configuration settings in the SAP system related to carryforward processes. This may involve looking at the settings in the Financial Accounting (FI) module to ensure that automatic carryforward is allowed for the relevant document types.
  
  
  Open Posting Period: Ensure that the posting period for the document is open and eligible for carryforward. If necessary, adjust the posting period settings.
  
  
  Manual Carryforward: If automatic carryforward is not allowed, consider performing a manual carryforward for the document. This may involve creating a new document or adjusting existing entries.
  
  
  Consult Documentation: Refer to SAP documentation or help resources for specific guidance on the carryforward process and any related configuration settings.
  
  
  Contact Support: If the issue persists, consider reaching out to your SAP support team or consulting with an SAP expert who can provide more tailored assistance based on your specific system configuration and business processes.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as F.01 (Financial Statement), F.16 (Carryforward Balances), and others that may be involved in the carryforward process.
  SAP Notes: Check for any SAP Notes related to FMCF779 or carryforward processes that may provide additional insights or solutions.
  User Exits and BAdIs: If custom logic is implemented in your SAP system, review any user exits or Business Add-Ins (BAdIs) that may affect the carryforward process.
  
  By following these steps, you should be able to identify the cause of the FMCF779 error and implement a suitable solution.