Example: Parallel Availability Control Checks

The following example illustrates how you can carry out parallel availability control checks using two AVC ledgers. To each AVC ledger, you can assign individual tolerance profiles and an individual derivation strategy for the account assignment derivation of availability control objects.

In this case, it is required that the total available budget of an organization should be checked at the top level, up to a maximum of 100% consumption. When this tolerance limit is reached, additional postings are prevented by the system and an error message is issued. A warning message should be issued if the consumption level reaches 90%. In this example, all budget addresses are summarized in one control objectin Strategy I. The total budget distributed among all three account assignments (budget addresses) is checked in a single control object. The consumption of an individual budget address is not relevant, since only the total of all account assignments is checked.

This does not apply to the individual departments represented in this example by the three budget addresses. In individual cases, it should be possible for the system to prevent additional postings when a consumption of 130% is reached. A warning message is issued when 100% is reached. This occurs in Strategy II below, where there is a corresponding control object for each budget address (this derivation strategy corresponds to the default strategy applying a 1:1 assignment for the derivation of the control object).