How To Fix FI742 - Carryforward type not suitable

FI742 - Overview

• Message type: E = Error

• Message class: FI - TR-FM Funds Management

• Message number: 742

• Message text: Carryforward type not suitable

What causes this issue?

You have assigned a carryforward parameter whose carryforward type is
not allowed here.
The following carryforward type allocations are allowed:

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

Carrying forward commitment documents (fiscal year change):
"10": (FYC without acct assgmt change, 1 receiver, 100% or 0%)
"20": (FYC with acct assgmt change, 1 receiver, 100% or 0%)
Budget carryforward (fiscal year change):
"10": (FYC without acct assgmt change, 1 receiver, 100% or 0%)
"20": (FYC with acct assgmt change, 1 receiver, 100% or 0%)
"30": (FYC with acct assgmt change, 1 receiver, breakdown as req.)
"40": (FYC with acct assgmt change, n receivers, breakdown as req.)
Only account assignment changes (without fiscal year change):
"25": (Acct assgmt change only (no FYC), 1 receiver, only 100% or 0%)

How to fix this error?

Choose a carryforward parameter whose carryforward type is suitable.

Error message extract from SAP system. Copyright SAP SE.

FI742 - Details

• The SAP error message FI742 "Carryforward type not suitable" typically occurs during the year-end closing process when the system attempts to carry forward balances from one fiscal year to the next. This error indicates that the carryforward type defined in the system is not appropriate for the specific account or scenario being processed.
  Causes:
  
  Incorrect Carryforward Type Configuration: The carryforward type assigned to the account may not be suitable for the type of account (e.g., balance sheet vs. profit and loss).
  Account Type Mismatch: The account being processed may not be configured to allow carryforward, or it may be a temporary account that should not have a carryforward.
  Missing or Incorrect Settings: The settings in the fiscal year variant or the carryforward settings in the financial accounting configuration may be incomplete or incorrect.
  Data Inconsistencies: There may be inconsistencies in the data that prevent the carryforward process from completing successfully.
  
  Solutions:
  
  
  Check Carryforward Type Configuration:
  
  Go to the