Kontakt

Ansicht
Dokumentation

CRMVC_FM_AVCT_PRO - Define Availability Control (AVC) Tolerance Profiles

CRMVC_FM_AVCT_PRO - Define Availability Control (AVC) Tolerance Profiles

ROGBILLS - Synchronize billing plans   PERFORM Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

You can use availability control (AVC) to ensure that the consumed amounts in claims and funds management do not reach a given percentage of the consumable budget or a given absolute delta value of the consumable budget.

You use this IMG activity to define tolerance profiles and define the tolerance parameters related to a given tolerance profile, for example, message types and tolerance limits.

Message Types

  • If you leave Application Area and Message No. blank here, a hard coded message appears when tolerance limits are reached.
  • You can define your own messages in Message Maintenance (SE91) which you can use here.
  • Additionally, you can use the Business Add-In BAdI: Availability Control (AVC) to Filter Postings on Fund and Fund Usage to define the variables used in your messages.

You define tolerance limits for a specific message type.

You must complete the IMG activitiesDefine Availability Control (AVC) Check Rules and Define Availability Control (AVC) Tolerance Profiles before you can complete the IMG activity Define Availability Control (AVC) Profiles.

You must complete these AVC customizing activities to use AVC with claims and funds management.

Optionally, you have defined AVC authorization levels in the IMG activity Define Availability Control Authorization Levels.

  1. Define a tolerance profile that includes a profile category and currency.
  2. Select a profile category to indicate if you are defining tolerance limits based only on usage rates or based on usage rates and absolute variances.
  3. Define the AVC message types associated with a tolerance profile, for example, error message and warning.
  4. Maintain the tolerance limits for each message type. You define the values based on the profile category selected.
    1. You leave Auth Level blank so that the tolerance profile applies to all users.
    2. If you choose a profile category for your tolerance profile that is usage rates and absolute variances allowed, then, in Use of Tolerance Limits, you can indicate whether you want to use the maximum or minimum tolerance from usage rate and absolute variance.

Note: Maximum and minimum refer to the degree of tolerance. For example, minimum tolerance indicates that any variance is recognized at the strictest value calculated, either on the absolute value or the usage rate.

The following example illustrates the use of the maximum and minimum tolerance setting.

,,Budget 1 = EUR 1 000 000

,,Budget 2 = EUR 1 000

,,Customizing = EUR 20 000 absolute variance, 95% usage rate

  • You want to consume EUR 20 from Budget 2.
  • You will receive an error message if minimum tolerance is defined, (EUR 1000 - EUR 20 = EUR 980 variance, which is less than the absolute variance of EUR 20 000).
  • The maximum tolerance should be used in this case because you are far from depleting Budget 2.
  • 95% usage rate of EUR 1 000 budget = EUR 950 or EUR 50 absolute variance. EUR 50 absolute variance is less than the customized EUR 20 000 absolute variance, so the decision logic will only consider EUR 50.

For large budgets, a 95% usage rate may be too intolerant.

  • You want to consume EUR 970 000 from Budget 1.
  • You would get an error message if minimum tolerance is set (95% usage rate of a EUR 1 000 000 budget = EUR 950 000).
  • This may be too strict, depending on the transaction type, because there is still a budget of EUR 1 000 000 - EUR 970 000 = EUR 30 000 remaining.
  • If maximum tolerance is set, then customized absolute variance of EUR 20 000 will be considered and no error message appears.
  • In this scenario:
  • 95% rule is appropriate for small budgets and for big budgets

  • Customized EUR 20 000 absolute variance avoids the intolerance of the 95% rule






CPI1466 during Backup   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 4945 Date: 20240523 Time: 154520     sap01-206 ( 69 ms )