Vous êtes sur la page 1sur 4

2018-12-19 2311470

2311470 - Automatic carryforward is only allowed for


amount 0 - FMCF101 or FMCF320 in MIRO
SAP Knowledge Base
Version 18 Type
Article
Master
Language English English
Language
Release
Released to Customer Category Problem
Status
PSM-FM-UP-FI-GR (Goods Receipt
Component Released On 11.09.2018
Reduction)

Please find the original document at https://launchpad.support.sap.com/#/notes/2311470

Symptom

You are utilizing Funds Management with MM update set 'Goods Receipts and Invoice receipts' as relevant
for updating
After Fiscal Year change, you are attempting to post Logistic Invoices with transaction MIRO, with reference
to Goods Receipts staying in the previous fiscal year
Invoice postings are stopped by error FMCF 101 'Automatic Carryforward is only allowed for amount 0', or
FMCF 320 'No Customizing data found for FM area', or FI228 'Document item NNNNN/NNN has not yet been
carried forward to the current year'

Environment

IMG Activity "Make Other Settings" (transaction OFUP) set to GR/IR updating

Cause

New checks introduced by SAP Note 2006072 or corresponding Support package of EA-PS

Resolution

This Guided Answers Tree will help you identify appropriate solution:
https://gad5158842f.us2.hana.ondemand.com/dtp/viewer/#/tree/1357/actions/16795

Alternatively, find out details below:

First, review your FM update profile details. You can start report RFFMMONI from transaction code SE38 to
verify if you are using a Period-Based Encumbrance Tracking (PBET) or an Annual/Fiscal Year-Based
Encumbrance Tracking (ABET/YBET) update profile.
Example of RFFMMONI output:

Next, verify your settings for Commitment Carryforward (CCF) in the IMG activities for Closing operations, to
determine if Carryforward of Value type 54 is allowed:

Public Sector Management -> Funds Management Government -> Closing Operations ->Enter Default
Settings: If marked, carryforward of all value types is allowed by default

And:

© 2018 SAP SE or an SAP affiliate company. All rights reserved 1 of 4


2018-12-19 2311470

Public Sector Management -> Funds Management Government -> Closing Operations-> Commitment
Closing Operations -> Enter Settings for Commitment Carryforward Payment Budget. If settings exist, verify
whether CCF is allowed/not allowed per value type.

Correspondingly, if your update profile is set up to value type 54 updating Commitment Budget (CB), verify
the same CCF setting for Commitment Budget in the IMG activity Public Sector Management -> Funds
Management Government -> Closing Operations-> Commitment Closing Operations -> Enter Settings for
Commitment Carryforward Commitment Budget.

With the above, identify your scenario and solution in below table:

PBET profile value type 54 is/can be


PBET YBET (ABET, non P
excluded from PBET
CCF Solution 1 Solution 3 N/A (*)
CCF and value type 54 is/can be
Solution 2 Solution 2 and 3 Solution 3
excluded
No CCF Solution 2 Solution 4 Solution 4

Solution 1
(1) Accept CCF process
or
(2) Disable CCF and PBET for 54 (if not done yet) AND confirm you accept multi year GRs

Solution 2
(1) Accept CCF process
or
(2) Disable PBET for 54 (if not done yet) AND confirm you accept multi year GRs

Solution 3
(1) Accept CCF process
or
(2) Disable CCF for 54 (if not done yet) AND confirm you accept multi year GRs

Solution 4
Confirm you accept multi year GRs

Description of Solutions:

Accept CCF process:

It means you must include the Commitment Carryforward as part of your Business processes

How to disable PBET:

• Choose the IMG menu path Public Sector Management -> Funds Management Government -> Actual
and Commitment Update/Integration -> General Settings -> Override Update Profile
• Create new entries for your FM Update Profile and Value Type '54'.
• Set this entry as FY-Based or Annual-Based Encumbrance Tracking for both Payment Budget and
Commitment Budget.

How to disable CCF:

1.- Via customizing

© 2018 SAP SE or an SAP affiliate company. All rights reserved 2 of 4


2018-12-19 2311470

• Choose the IMG menu path Public Sector Management -> Funds Management Government -> Closing
Operations -> Commitment Closing Operations -> Enter Settings for Commitment Carryforward
Payment Budget - and - Enter Settings for Commitment Carryforward Commitment Budget (if value
type 54 updates CB in your update profile)
• Create entry for your FM Area, Fiscal Year, Value Type '54' and leave option 'Cfwd Allowed' empty.

2.- BAdI enhancement


This option is available only if SAP Note 1991999 is present in your system.
BAdI enhancement allows you to precisely differentiate (comparing to Value Type customizing in Option A)
which documents are relevant for Carry-Forward.
Implement BAdI FM_CCF_REFINE method FILTER_OPEN_ITEMS.
Implementation example code:

IF I_F_FMIFIIT IS SUPPLIED AND I_F_FMIFIIT-BTART = '0200' AND I_F_FMIFIIT-WRTTP = '54' AND


I_F_FMIFIIT-VRGNG = 'RMWE'.
E_NO_CF = ABAP_TRUE.
ENDIF.
Note: BAdI FM_CCF_REFINE method FILTER_OPEN_ITEMS is used within the regular CCF process
(FMJ2), so you must ensure a robust BAdI implementation so that the rest of your CCF operations are not
unexpectedly affected.

How to confirm you accept multi year GRs:

You must implement BAdI FMGR_RED, method ALLOW_MULTI_YEAR_GR.


Implementation example code:

E_ALLOW = ABAP_TRUE.

(*)N/A: CCF execution is required

Additional Information:

When an MM completed invoice is Posted/Changed/Deleted, the system will use the system date for
undoing the existing GR reduction. This may result in unexplainable AVC errors (such as FMAVC005 or
BP629) pointing to the current year.
If you need to influence the FM update date in this situation, you have to implement BAdI FMGR_RED,
method POSTING_DATE_PARKED_IR_RVSL to overwrite proposed Posting Date for GR Reduction
Reversals, delivered with note 2302055
But bear in mind that you cannot post GR Reductions to previous Fiscal Year if postings for same GR
Reductions Clearing Key already exist in the new year (see attachment in SAP Note 1991999 for GR
reduction key definition).
Alternatively to BAdI FMGR_RED, you can use transaction FMOD. Note that transaction FMOD must be
used carefully: the entered FM update date will affect all FM relevant postings for the user maintained. FMOD
must be used in exceptional cases only.

For complete issue resolution, please make sure that the referenced SAP Notes in this KBA and pre-
requisites are installed.

If error FMCF320 remains even after the appropriate solution is fully implemented, make sure SAP Notes
2372856, 2470626 and 2559839 are implemented

See Also

© 2018 SAP SE or an SAP affiliate company. All rights reserved 3 of 4


2018-12-19 2311470

This Guided Answers Tree will help you identify appropriate solution:
https://gad5158842f.us2.hana.ondemand.com/dtp/viewer/#/tree/1357/actions/16795

Keywords

FMFC101, FMCF 101, FMCF 320, ABET, FY-BASED, PBET, YBET, CCF, FMJ2, FI228, FI 228, FI 741,
KBA, FI741, FI031

Products

SAP ERP 6.0


SAP enhancement package for SAP ERP all versions
SAP enhancement package for SAP ERP, version for SAP HANA all versions

Other Components

Component Description

PSM-FM-CL Closing Operations

This document refers to

SAP Note/KBA Title

2559839 FI031 Posting MR8M on old year document not carried forward for at least two years.

2470626 Error message FMCF320 not expected(1)

2372856 Error message FMCF320 not expected

© 2018 SAP SE or an SAP affiliate company. All rights reserved 4 of 4