Skip to Content

BCS: Help for understanding Availability Control messages


BCS: Help for understanding Availability Control messages

How often have you received an Availability Control (AVC) error message unexpectedly, claiming there is not enough budget, even though your AVC reports show budget is sufficient?

How often have you investigated why the AVC error is issued, but failed to find the cause?

And, how often have you reported this kind of issues to SAP Support and SAP answer finally was ‘the system is working as expected, in accordance with your settings A, B or C, using X and Y values as basis for calculation….’ and then you told to yourself ‘oh well, how does SAP expects one could have found out that by him/herself?. Most of the time this is tricky and even requires debugging skills…’

Now, additional help tools are available to help customers help themselves.

Let us take this situation as example:

Starting point is a control object where the budget is already exhausted, as seen in transaction FMAVCR01:

Then, an user tries to delete a Purchase Order item (transaction ME22N) but deletion is stopped by a budget exceeded error. Normally, there should be no AVC error while deleting a document because it should “release” budget already consumed, isn't it?.

So, why an AVC error comes out like this?:

Understanding the reason requires deep knowledge: one should know at least the Availability Control object that has been determined for AVC check purposes, along with its corresponding tolerance profile, and the figures used for AVC calculation.

How to find this easily?

Now, help tools are available, see how to use them:

  1. There is new transaction FMAVCDERITRACE that allows multiple trace activation for the derivation of Control Objects, Activity Groups, Checking Horizon and Tolerance profiles:

Simply mark the traces you wish to activate, and click ‘Execute’ (F8). This prepares you for the next analysis steps.

For our example, activation of FMAVCDERIAO and FMAVDERITPROF should be sufficient to know the AVC object/s involved and the tolerance profile determined.

2.  Once the trace is on, you can run the problematic transaction (e.g. ME22N, change a PO by marking one line item for deletion).

Since the traces are active, serveral  trace popups will come out, showing the derivation log on every derivation call (note, they will be called multiple times):

In this example, note the Functional Area value is not part of the Control object. The trace helps analyze how the control object was determined and see if there is aggregation in place.

3. After the control object is derived, the tolerance profile is determined via derivation strategy as well:

Bear in mind the system can derive other tolerance profiles than the defaulted one.

4. Now, knowing the Control object/s and tolerance profile/s involved, you can also access to additional information from the long text of the error message.

For instance, you can easily navigate to FMAVCR01, as the control object will be populated automatically, then you can find out how much is available:

Note the current available amount in this example is Zero:

You can get back to the long text of the AVC error message (by clicking F3), then you can also navigate to the ‘amounts in the current document’ by clicking the link:

6. What do these amounts mean?

On Expenditures, the total amount with negative sign represents and additional budget consumption. On the example given, the PO deletion led to the reopening of the original PR quantity x PR price. If the original PR quantity x price was larger than the PO quantity x price, this results in an additional budget consumption.
If budget is not sufficient, the availability control error will be issued as dictated in your tolerance profile settings.

Knowing the amounts used on AVC calculation facilitates the error analysis and helps understand whether or not the calculation is done properly.

Of course this will not answer all questions but very probably will accelerate the support tasks.

How to make these help features available?:

Transaction FMAVCDERITRACE is delivered in SAP Note number 2003552

The enhancements to AVC messages are only available by implementing a Support Package:

  • EA-PS 600 SAPKGPPD25
  • EA-PS 603 SAPK-60314INEAPS
  • EA-PS 604 SAPK-60415INEAPS
  • EA-PS 605 SAPK-60512INEAPS
  • EA-PS 606 SAPK-60610INEAPS
  • EA-PS 617 SAPK-61702INEAPS

You must read Consulting Note 1898130

And you need these Technical Notes: 1901809 and 1905908