AVC Monitors Used in Reporting 
BCS availability control (AVC) has the following monitoring transactions, enabling you to carry out evaluations and reporting for your AVC data.
FMAVCR01 : Display Annual Values of Control Objects
Use this to display the annual values for your control objects.
FMAVCR02 : Display Overal Values of Control Objects
Use this to display the overall values for your control objects (that is, for all years since AVC activation).
FMAVCDIFF : Display Availability Control Discrepancies
Use this to identify where any inconsistencies arise between AVC data and Funds Management (FM) totals records and to analyze those inconsistencies.
See the Prerequisites section under BCS Availability Control .
The reports work as follows:
Display Annual Values of Control Objects
With this report you can display the hierarchy of availability control objects, such as budget addresses and posting addresses, as well as annual AVC values for specific account assignments.
The report displays the hierarchy of control objects, containing budget and posting address. The selection is determined by derivation strategies for availability control and the budget structure. For each hierarchy node, the annual values of Consumable Budget, Consumed Amount and the difference between these two values (the Available Amount ) for a selected AVC ledger are output.
Display Overall Values of Control Objects
With this report you can display the hierarchy of availability control objects, such as budget and posting addresses, as well as overall AVC values f or specific account assignments.
For each control object selected, the report displays the overall values of the Consumable Budget , Consumed Amount and the difference between these two values - the Available Amount - for a selected AVC ledger.
Display Availability Control Discrepancies
With this report, you can detect inconsistencies between AVC totals and FM updatetotals. You can then reconstruct the AVC data using transaction FMAVCREINIT .
You can run this report as a regular batch job. If inconsistencies occur, you must analyze transactions occurring since the last batch job and this one to identify their source.
See the system documentation on each report for more information.