Skip to end of metadata
Go to start of metadata

How to address AVC related issues

While running regular business process, you might encounter unjustified Availability Control (AVC) errors, like FMAVC002, FMAV005, FMAVC008, or the AVC figures in reporting do not match your expectations.

When an AVC error is raised, it is often looked as a pure AVC problem. However, AVC calculation engine uses the amounts sent by the calling interface (e.g. commitments/actuals). If there is a problem in the documents involved in the posting, or eventually a bug outside the AVC functions, an end user may not know exactly where the problem arises.

Therefore, one needs to look at the scenario and process behind. There can be multiple causes that are not easy to tackle, since the analysis path depends on the postings involved.

One premise is to always refer to AVC reporting tools (transactions FMAVCR01, FMAVCR02, FMAVCH01, FMCEMON01) as "source of truth" to know the available amounts. Other reports like the report writer (RW) based, e.g. RMRP_RW_BUDCON, do not contain the AVC logic, so they would not show the real AVC figures per control object.
 
This is a list of common issues and hints for resolution:

 

Reporting: Mismatch between AVC totals and Drilldown


In non S/4HANA systems, AVC reporting (such as transactions FMAVCR01, FMAVCR02, FMCEMON01) is based on totals database table FMAVCT. Drilldown is based on corresponding feeder tables like FMBDT (for Budget figures) and FMIT (for commitment/actuals).

If the drilldown to Commitments/Actuals does not match the AVC total figure, first make sure that totals table FMIT is consistent as follows:

  1. Run transaction FMAF in test mode. If it finds differences, run it in Update mode. A new test run should no longer find differences

  2. Make sure that Note  2135190 is implemented and run transaction FMAVCREINIT to synchronize totals table FMIT with totals table FMAVCT

    Note: corrective actions must be performed when no other FM relevant operations are running. Otherwise you may cause encounter further differences

  

If the drilldown to Budget documents does not mach the AVC total figure, use transaction FMBUDDIFF (report RFFMKU_ANALYZE_DOCUMENTS) to identify potential inconsistencies in Budget documents. If they are found, contact SAP Support choosing PSM-FM-BCS-BU as component.

 

Reporting: Mismatch between totals at Control Object level versus Budget/Posting address


Transaction FMAVCDIFF can identify and analyze inconsistencies between AVC data and the corresponding contributions from the FM totals tables (commitment/actuals and budget data). If it shows differences, AVC data need reconstruction.

In addition, refer to SAP Note 725266 to identify the conditions requiring reconstruction of AVC data. 

Application component:  PSM-FM-BCS-BU.



AVC messages during Commitment Update


At the time of document creation (PR, PO, Earmarked Funds..), first step is to identify where the AVC check takes place. One thing is the posting address (FM account assignment specified in the document) and a different thing is the control object derived for AVC checks. This can be e.g. a superior Funds Center/Commitment item or a Cover Group number.

Use the trace feature of the derivation strategy for control objects, (t-code FMAVCDERIAO) at runtime, to ensure the AVC check is done on the expected control object.
Trace feature for derivation tools is described in SAP Note 666322.

If the document is referenced to a previous one, the commitment interface ensures that the documents involved in the chain (PR, PO, Earmarked Funds) are consistently updated in FM. In other words: the commitment update is self corrective.

As a result, the AVC calculation will react based on the difference between old and new amounts: if the overall result leads to additional budget consumption, an AVC message will be shown in accordance with your customizing.

However, sometimes data correction is not possible on the fly. If manual reconstruction is needed, tools are listed in SAP Note 189761

More details info about Commitment Update in Troubleshooting Guide for Commitment Update .

Application component:  PSM-FM-UP-CM.



AVC messages during GR/SES Posting


Possible reasons:

1.- You are using a Fiscal Year-Based update profile, and GR/SES and reference PO are in different fiscal years. At the time of posting a GR/SES, the budget consumption will be done in the Fiscal Year where the GR/SES belongs to, and corresponding PO reduction will be done in an old fiscal year.

(Note: AVC during GR posting is active if SAP Note 2166821 or corresponding support package is present in your system. Otherwise, no AVC error will be raised, but the budget will be consumed anyway)

2.- The reference PO was fully consumed already by previous GR/SES.

3.- For Services, consider this information:

    • Settings for Unit of Measure. More information here
    • If you posted documents in this sequence: PO -> partial SES -> IR with excess amount -> second partial SES, and you are receiving AVC errors even though the PO open amount is sufficient, be aware that there is a gap between MM-SRV and Funds Management, and such functionality is currently limited. More info in KBA  2134873   
       

Application component: PSM-FM-UP-CM.


AVC messages during MIRO

If your customizing is set to "GR/IR Update = GR and Inv." in FM customizing activity "Make Other Settings" (transaction OFUP), there might be AVC errors in MIRO owing to problems during GR reductions by IRs.

More information in Troubleshooting Guide for GR/IR
Application component: PSM-FM-UP-FI-GR



AVC  messages during Document Cancellation/Deletion


Scenario A: Cancelation/Deletion of a document with reference to a previous one

As a general rule, when a document that is referenced to a previous one is cancelled or deleted, the reduction of reference document is undone. This means that the reference document is restored ("reopened").

If the reference document resides in a different fiscal year, this will lead to a budget consumption in the fiscal year where the document belongs to if there is no sufficient budget.

As a consequence, if the available amount is not sufficient, an AVC message will be issued in accordance with your customizing.
More information in KBA 2116616 and also in this link.

Example:

1) Initial situation in budget 2017: 

Consumable AmountConsumed AmountAvailable Amount
50050

2) Posting a PO in 2017:  PO consumes 50 from budget in 2017

FMIOI table:

Amount typeAmountYear
10050-2017

Budget in 2017:

Consumable AmountConsumed AmountAvailable Amount
50500

3) Posting GR in 2017:  The consumption is still the same because the GR consumes from PO not from budget

FMIOI table:

Amount typeAmountYear
10050-2017
20050+2017

FMIFIIT table:

Amount TypeAmountYear
10050-2017

Budget in 2017

Consumable AmountConsumed AmountAvailable Amount
50500

4) Cancellation of GR in 2018 The reversal is in 2018 and the PO is in 2017.

Consumption in 2017 is the sum of all records in 2017 = -50 +50 -50 -50 = 100-

Consumption in 2018 is the sum of all records in 2018 = 50+

Amount from PO in 2017 is taken from budget (risen and error if defined in customizing) and the amount for the reversal is added to the budget in 2018

FMIOI table

Amount TypeAmountYear
10050-2017
20050+2017
20050-2017

FMIFIIT table

Amount typeAmountYear
10050-2017
20050+2018

Budget in 2017:

Consumable AmountConsumed AmountAvailable Amount
50100-50


Budget in 2018

Consumable AmountConsumed AmountAvailable Amount
0-50+50


Possible solutions:

1) If it is necessary to cancel the GR in 2018.

1.1) You can carryforward the PO with FMJ0 if there is no open amount, or with FMJ2 if there is some open amount . In case of FMJ2, carryforward to 2018 with its own budget and then cancel the GR in 2018. If you dont carryforward the budget to 2018, the carryforward will consume budget.

or

1.2) If you dont want to carryforward the PO to 2018. You need to add more budget in 2017. Taking into account there would be more budget available in 2018 because of the cancellation

or

2) If it is not necessary to cancel the GR in 2018:

Post the cancellation in 2017.


Application component: PSM-FM-UP-CM


Scenario B: Cancellation/Reversal of a document without reference


If AVC errors arise unexpectedly while reversing standalone documents (e.g. reversing an FI document with transaction FB08), review your Tolerance Profile and Ceiling types.

Reversal of an Expenditure document is treated as 'Incoming amount'
Reversal of a Revenue document is treated as 'Outgoing amount'

If the Tolerance Profile is not set up to handle Incoming amounts, you may be receiving AVC errors unexpectedly
Additional information in SAP Note 985689 - Messages from availability control for revenue items

Application component PSM-FM-BCS-AC


AVC messages during setting final invoice indicator in the PO when referencing an EFD


The earmarked funds consumption can be updated by purchase orders with the final invoice indicator flag set. 

When the final invoice indicator is set in the PO (please refer to "PO flags affecting documents section" in UP-CM troubleshooting for PO's) the amount in the EFD for the consumption will be updated with the amount in the IR.

This includes two movements:

1) Returning the left amount to the budget in the year the PO is posted. The reduction of reference document is undone

2) Consuming the left amount from the budget in the year the EFD is posted. This means that the reference document is restored ("reopened").

You may receive an error if the PO and the EFD are posted in different years (for example because of a carryforward for the PO) in case there is no sufficient buget in the EFD's posting year.

Example:

1) Initial situation in budget 2017: 

Consumable AmountConsumed AmountAvailable Amount
50050

2) Posting an EFD in 2017:  EFD consumes 50 from budget in 2017

FMIOI table:

Amount typeAmountYear
10050-2017

Budget in 2017:

Consumable AmountConsumed AmountAvailable Amount
50500

3) Posting PO in 2018 (or carryforward a PO from 2017 to  2018) :  

Budget in 2018 (before posing PO)

Consumable AmountConsumed AmountAvailable Amount
50050

FMIOI table for EFD:

Amount typeAmountYear
10050-2017
20050+2017

FMIOI table for PO:

Amount TypeAmountYear
10050-2018

Budget in 2017

Consumable AmountConsumed AmountAvailable Amount
50500

Budget in 2018

Consumable AmountConsumed AmountAvailable Amount
50500


4) IR posted in 2018. The PO will be reduced by GR or IR (by the highest amount)

 

FMIOI table for EFD:

Amount typeAmountYear
10050-2017
20050+2017

FMIOI table for PO:

Amount TypeAmountYear
10050-

2018

200202018

FMIFIIT table for invoice:

Amount TypeAmountYear
10020-2018

The budget consumed is still the same for both years

Budget in 2017

Consumable AmountConsumed AmountAvailable Amount
50500

Budget in 2018

Consumable AmountConsumed AmountAvailable Amount
50500

4) Set final invoice indicator in the PO

This will mean:

  • The consumption for the EFD now will be the amount in the invoice.
  • The PO will be completed.

FMIOI table for EFD, the reduction amount changes to 20, so the available amount should be 30 in the budget( if there is no enough budget the AVC error will appear):

Amount typeAmountYear
10050-2017
200202017

FMIOI table for PO, the PO will be completely reduced.

Amount TypeAmountYear
10050-2018
200202018
500302018

FMIFIIT table for invoice:

Amount TypeAmountYear
10020-2018


Consumption in 2017 would be the sum of amounst in 2017: -50 + 20 = -30

Consumption in 2018 would be the sum of amounts in 2018 = -50 + 20 +30 - 20 = -30. This means there is no extra consumption and the PO is completely reduced. 

The consumption in budget before final invoice indicator was 50, with the final invoice indicator set it will be 30.


AVC messages during Commitment Carryforward


Commitment Carryforward (t-code FMJ2) transfers the open items from one year to the following one. Therefore the budget consumption will be undone in the sender year and updated in the receiver year. If budget is not sufficient, an AVC error (e.g. FMAVC005) will be shown in the log of FMJ2.

These options are available with BCS, as an alternative for entering consumable budget in the receiver fiscal year prior to execution of FMJ2:

1.- Implement Budget Carryforward for Commitments: this is the recommended one. Note that, if you are using Budget Releases, a Budget document type set up for automatic release is necessary. Otherwise the commitments will be carried forward along with their budget, but such budget will not be consumable. More information in KBA 1859520
2.- Choose 'No Availability Control' or 'Update without checks'  for Availability Control in the Process Control box of FMJ2. Bear in mind that the budget can be exceeded in the receiver year. Refer to the online documentation of FMJ2.

Application component: PSM-FM-BCS


Negative budget after transfer

If there is no positive budget consumption posted yet for the relevant control object, you will not receive any AVC error message when you decrease the budget in a way that the budget becomes negative.

See note 983853 - Missing errors from availability control for negative budget


Finding root cause of inconsistencies: Tips and tricks

 

Inconsistencies should not occur during regular business operations. If they are detected by either transaction FMAF or FMAVCDIFF, the root cause needs to be identified.

Try to find a reproducible example that can be analyzed (i.e. inconsistencies after PO changes, Invoice postings, payments...). If you fail to find it, these actions can help:

1.- Out of business hours, schedule a daily (or nightly)  execution of FMAF in test mode. The output log should help at least find what account assignments and value types are affected. That way you can detect the documents posted that day and identify the problematic ones

2.- Out of business hours, schedule a daily (or nightly) execution of FMAVCDIFF: the output should help identify the account assignments affected and whether budgeting or consumption figures are affected. Note: if you have an S/4HANA system, do not select option 'Correct AVC data' so that the figures are not changed.

3.- In non S/4HANA systems, you can activate the change log of AVC data. See SAP Notes 1041423 - Change history for table FMAVCT  and   1919156 - Report to find single line items . Once the change log is active, you can detect relevant AVC entries that might have caused problems

4.- SAP Note  1666556 - AVC data inconsistencies after unexpected COMMIT WORK   must be present in your system. With this Note in place, a dump will occur if AVC is not checked as expected.
Note that this kind of dump is triggered when an unexpected commit work is performed. You must avoid usage of commit work statements in your custom coding as described in the Note.

5.- Another known cause is related to incorrect custom implementation of BAdI FMAVC_ENTRY_FILTER. Make sure your coding is robust, not based on values like SY-TCODE that would not be consistently handled when the BAdI is called.

Related Content:


Related Documents

 BCS: Help for understanding Availability Control messages

Other related Notes/KBAs

2037198 - Error FMAVC005 when posting a down payment request referenced to a funds reservation
2314235 - Negative available amount in FMAVCR01/FMRP_RW_BUDCON

2135190 - Wrong AVC data after executing transaction FMAVCREINIT