Availability Control (AVC) problems in BCS: how to address them (PSM-FM-BCS-AC)
How to address AV AVC related relate d isses While running regular business process, you might encounter unjustified Availability Availability Control (AVC) errors, like FAVC!!", FAV!!#, FAVC!!$, or the AVC figures in reporting do not match your e%pectations& When an AVC error is raised, it is often looked as a pure AVC problem& 'oever, AVC calculation engine uses the amounts sent by the calling interface (e&g& commitmentsactuals)& *f there is a problem in the documents involved in the posting, or eventually a bug outside the AVC functions, an end user may not kno e%actly here the problem arises& +herefore, one needs to look at the scenario and process behind& +here can be multiple causes that are not easy to tackle, since the analysis path depends on the postings involved& +his is a list of common issues and hints for resolution •
-eporting ismatch beteen AV AVC totals and .rilldon
•
-eporting ismatch beteen totals at Control /bject level versus 0udget1osting address
•
AVC messages during Commitment 2pdate
•
AVC messages during 3-454 1osting
•
AVC messages during *-/
•
AVC AV C messa messages ges during .ocument Cancel Cancellation lation.ele .eletion tion
•
AVC messages during Commitment Carryforard Carr yforard
•
Finding root cause +ips and tricks
•
-elated Content o
-elated .ocuments
o
/ther related 6otes70As
!eportin": Mismat#h between AVC totals and $rilldown
*n non S%&HA'A systems, AVC reporting (such as transactions FAVC-!8, FAVC-!", FC5/6!8) is based on totals database table FAVC+& .rilldon is based on corresponding feeder tables like F0.+ (for 0udget figures) and F*+ (for commitmentactuals)& *f the drilldon to Commitment%A#tals does not mach the AVC total figure, first make sure that totals table F*+ is consistent&
8& -un transaction FAF in test mode& *f it finds differences, run it in 2pdate mode& A ne test run should no longer find differences "& -un transaction FAVC-5*6*+ to synchroni9e totals table F*+ ith totals table FAVC+ 6ote corrective actions must be performed hen no other F relevant operations are running& /therise you may cause encounter further differences *f the drilldon to Bd"et do#ments does not mach the AVC total figure, use transaction FMB$$FF (report -FF72:A6A;<=5:./C256+4) to identify potential inconsistencies in 0udget documents& *f they are found, contact 4A1 4upport choosing 14> F>0C4>02 as component&
!eportin": Mismat#h between totals at Control *b+e#t level verss Bd"et%Postin" address +ransaction FMAVC$FF can identify and analy9e inconsistencies beteen AVC data and the corresponding contributions from the F totals tables (commitmentactuals and budget data)& *f it shos differences, AVC data need reconstruction& •
*n non 4?'A6A systems, use transaction FAVC-5*6*+& ake sure 4A1 6ote "8@#8! > Wrong AVC data after e%ecuting transaction FAVC-5*6*+ or corresponding support package is installed&
•
*n 4?'A6A systems, besides FAVC-5*6*+, transaction FAVC.*FF provides the option to correct AVC data& 4ee 6ote """@"!B > 5nhancements for transactions FAVC*6.*6C/6 and FAVC.*FF & For a mass reconstruction, using FAVC-5*6*+ ill take less time&
*n addition, refer to 4A1 6ote B"#" to identify the conditions reDuiring reconstruction of AVC data& Application component 14>F>0C4>02&
AVC messa"es drin" Commitment pdate At the time of document creation (1-, 1/, 5armarked Funds&&), first step is to identify here the AVC check takes place& /ne thing is the postin" address (F account assignment specified in the document) and a different thing is the #ontrol ob+e#t derived for AVC checks& +his can be e&g& a superior Funds CenterCommitment item or a Cover 3roup number& 2se the trace feature of the derivation strategy for control objects, (t>code FAVC.5-*A/) at runtime, to ensure the AVC check is done on the e%pected control object& +race feature for derivation tools is described in 4A1 6ote @""& *f the document is referenced to a previous one, the commitment interface ensures that the documents involved in the chain (1-, 1/, 5armarked Funds) are consistently updated in F& *n other ords the commitment update is self corrective& As a result, the AVC calculation ill react based on the difference beteen old and ne amounts if the overall result leads to additional budget consumption, an AVC message ill be shon in accordance ith your customi9ing& 'oever, sometimes data correction is not possible on the fly& *f manual reconstruction is needed, tools are listed in 4A1 6ote 8$B8 ore details info about Commitment 2pdate in Troubleshooting Guide for Commitment Update. Application component 14>F>21>C&
AVC messa"es drin" ,!%SS Postin"
1ossible reasons 8&> 0ased update profile, and 3-454 and reference 1/ are in different fiscal years& At the time of posting a 3-454, the budget consumption ill be done in the Fiscal
"&> +he reference 1/ as fully consumed already by previous 3-454& @&> For 4ervices, consider this information •
o
o
4ettings for 2nit of easure& ore information here *f you posted documents in this seDuence 1/ >E partial 454 >E *- ith e%cess amount >E second partial 454, and you are receiving AVC errors even though the 1/ open amount is sufficient, be aare that there is a gap beteen > 4-V and Funds anagement, and such functionality is currently limited& ore info in 70A "8@?$B@
Application component 14>F>21>C&
AVC messa"es drin" M!* *f your customi9ing is set to 3-*- 2pdate G 3- and *nv& in F customi9ing activity ake /ther 4ettings (transaction /F21), there might be AVC errors in *-/ oing to problems during 3- reductions by *-s& ore information in Troubleshooting Guide for GR/IR Application component 14>F>21>F*>3-
AVC messa"es drin" $o#ment Can#ellation%$eletion As a general rule, hen a document that is referenced to a previous one is cancelled or deleted, the reduction of reference document is undone& +his means that the reference document is restored (reopened)& *f the reference document resides in a different fiscal year, this ill lead to a budget consumption in the fiscal year here the document belongs to& As a conseDuence, if the available amount is not sufficient, an AVC message ill be issued in accordance ith your customi9ing& ore information in 70A "888 and also in this link & Application component 14>F>21>C
AVC messa"es drin" Commitment Carry.orward Commitment Carryforard (t>code FH") transfers the open items from one year to the folloing one& +herefore the budget consumption ill be undone in the sender year and updated in the receiver year& *f budget is not sufficient, an AVC error ill be shon in the log of FH"& +hese options are available ith 0C4, as an alternative for entering consumable budget in the receiver fiscal year prior to e%ecution of FH" 8&> *mplement 0udget Carryforard for Commitments this is the recommended one& 6ote that, if you are using 0udget -eleases, a 0udget document type set up for automatic release is necessary& /therise the commitments ill be carried forard along ith their budget, but such budget ill not be consumable& ore information in 70A 8$##"! "&> Choose I6o Availability ControlI or I2pdate ithout checksI for Availability Control in the 1rocess Control bo% of FH"& 0ear in mind that the budget can be e%ceeded in the receiver year& -efer to the online documentation of FH"& Application component 14>F>0C4
Findin" root #ase: /ips and tri#0s
*nconsistencies should not occur during regular business operations& *f they are detected by either transaction FAF or FAVC.*FF, the root cause needs to be identified& +ry to find a reproducible e%ample that can be analy9ed (i&e& inconsistencies after 1/ changes, *nvoice postings, payments&&&)& *f you fail to find it, these actions can help 8&> /ut of business hours, schedule a daily (or nightly) e%ecution of FAF in test mode& +he output log should help at least find hat account assignments and value types are affected& +hat ay you can detect the documents posted that day and identify the problematic ones "&> /ut of business hours, schedule a daily (or nightly) e%ecution of FAVC.*FF the output should help identify the account assignments affected and hether budgeting or consumption figures are affected& 6ote if you have an 4?'A6A system, do not select option ICorrect AVC dataI so that the figures are not changed& @&> *n non 4?'A6A systems, you can activate the change log of AVC data& 4ee 4A1 6otes 8!?8?"@ > Change history for table FAVC+ and 888# > -eport to find single line items & /nce the change log is active, you can detect relevant AVC entries that might have caused problems ?&> 4A1 6ote 8## > AVC data inconsistencies after une%pected C/*+ W/-7 must be present in your system& With this 6ote in place, a dump ill occur if AVC is not checked
as e%pected& 6ote that this kind of dump is triggered hen an une%pected commit ork is performed&
!elated Content:
!elated $o#ments 0C4 'elp for understanding Availability Control messages
*ther related 'otes%1BAs "!@B8$ > 5rror FAVC!!# hen posting a don payment reDuest referenced to a funds reservation "@8?"@# > 6egative available amount in FAVC-!8F-1:-W:02.C/6 "8@#8! > Wrong AVC data after e%ecuting transaction FAVC-5*6*+
