Availability Control in Claims and Funds 
You can use availability control (AVC) in claims and funds management to control fund consumption.
You link an AVC profile to a transaction type to specify the control mechanisms for this type of transaction, such as the key figures that are used to calculate the consumption, and what kind of error message is given to the user once a specified fund consumption limit has been reached.
Make the following settings in Customizing for Customer Relationship Management (CRM) under :
Define the AVC check rules that identify the key figures used in AVC calculations in Define Availability Control (AVC) Check Rules
Define authorization levels to use with AVC under Define Availability Control (AVC) Authorization Levels
Define the AVC tolerance profiles that identify the tolerance limits and messages types under Define Availability Control (AVC) Tolerance Profiles
Define an AVC profile that identifies the level at which AVC checks are performed under Define Availability Control (AVC) Profiles
Assigned an AVC profile to specific transaction type in funds and claims in Customizing for CRM under or under .
You can assign AVC profiles to specific transaction types so that the system notifies you of fund consumption levels as you perform various transactions, such as budget transfers, prepayments or deduction claims.
You can identify tolerance limits based on a percentage or on specific fund consumption amounts.
You can identify what type of message is used to notify the user of the fund consumption limits, such as error, warning or information. You can create your own messages or use the messages provided in the standard.
Optionally, you can modify fund postings values before the AVC check is performed and change the message variables by implementing the Business Add-In: BAdI: Fund Postings and AVC Message Variables. Choose .
This table shows an example of how of how AVC can be used to control fund consumption.
Check Rule Setup |
Consumable key figures value categories:
|
Consumed Key figures value categories
|
|
Tolerance Profile Setup |
Only usage rates allowed |
Message Types:
|
Tolerance limits: Error message:
Information message:
|
Scenario 1 |
Scenario 2 |
Scenario 3 |
|
Transaction is performed. AVC profile verified |
70% of budget is already consumed. User with Auth. Level 1 performs transaction that consumes 30% more of the budget. |
70% of budget is consumed. User with Auth. Level 2 performs transaction that consumes 20% more of the budget. |
70% of budget is consumed. User with Auth. Level 1 performs transaction that consumes 12% more of the budget. |
Results |
User receives error message and is prevented from completing the transaction. |
User receives error message and is prevented from completing the transaction. |
User receives information message on fund consumption but is permitted to complete transaction. |