Hierarchy
EA-PS (Software Component) SAP Enterprise Extension Public Services⤷
PSM-FM-MD (Application Component) Master Data⤷
FMCC (Package) FIFM: Cash budget management customizing
IMG Activity
| ID | _ISPSFM_OF20 | Define Tolerances for Availability Control |
| Transaction Code | S_KI4_55000134 | IMG Activity: _ISPSFM_OF20 |
| Created on | 19991215 | |
| Customizing Attributes | _ISPSFM_OF20 | Define Tolerances for Availability Control |
| Customizing Activity | _ISPSFM_OF20 | Define Tolerances for Availability Control |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | _ISPSFM_OF20 |
Availability control (AVC) can promptly identify an excessive funds assignment in a Budget Structure and trigger various actions.
You configure availability control separately for each FM area/budget profile/activity group combination. For each action and combination you can define an absolute and/or relative tolerance limit for the Payment Budget and for the Commitment Budget.
If an absolute or relative tolerance limit is reached or exceeded, the R/3 System triggers the action you specified (warning, warning with Mail to funds center manager, error message).
You need to maintain the following parameters in availability control:
- FM area
- Budget profile
Availability control against overall/annual budget or overall/annual release. You must enter these settings in the "Set up budget profiles" step.
The Overall flag works in connection with the Releases flag
as follows:
"Overall" flag "Releases" flag Availability control checks against...
X - Overall budgets
- - Annual budgets
X X Released overall budgets
- X Released annual budgets
- You can define tolerance limits for the following activity groups:
- earmarked funds
- Purchase requisition
- Purchase order
- Actual posting
- Controlling posting
- Trips
- Payroll accounting
- Budget
- You need this group so that availability control can take account of subsequent budget changes (supplements, returns, transfers).
- You may need to change your budget, even when funds assignments have already been made. If this means that a tolerance limit is exceeded, the R/3 System directs your attention to the error log when you check or save the budget.
- This log contains the warnings or error messages triggered by the system when tolerance limits were exceeded. You can access explanatory texts for the warnings and error messages.
- All activity groups
- This activity group makes data input easier. You must only use it if you do not want to define separate tolerance limits for each activity group.
NOTE:
The tolerance limit for the next activity up only comes into effect if the assigned value is increased by this activity.
Example
You enter a purchase requisition for $1000. However, the amount in the purchase order is $1200 because you order more items or because the price has gone up. In this event, the tolerance limits specified for purchase orders come into play because the assigned value has increased. If you enter a purchase order in an amount less than or equal to the purchase requisition amount, availability control is not activated.
- Action
- Usage in %
An entry of 80 % means, for example, that the action is triggered if funds assignments amount to more than 80% of the distributable budget. 130 % means that funds assignments may exceed the budget by up to 30% before the action is triggered.
- Absolute variance
If the difference between funds assignments and budget exceeds the absolute variance, availability control executes the action you specified. If, for example, you have a budget of $1000 and an absolute variance of $200, the action is triggered when the total of all funds assignments exceeds $1200.
- Not active
If you choose this parameter, the tolerance limits do not apply to the activity group specified.
Note the following:
- If you have defined tolerance limits for "All activity groups", but do not want the selected action triggered for a particular activity group, you must make a separate entry for that activity group and set it to "Not active".
- If you have defined tolerance limits for "All activity groups", but want to define different tolerances for a particular activity group, make the new entry with the corresponding settings. This entry takes precedence over the settings for "All activity groups". This also applies if you have deactivated the tolerance limits for "All activity groups".
Recommendation
Define your tolerance limits for "All activity groups". If you want to define different tolerance limits for the individual activity groups, the tolerance limits for the activities lower down in the activity chain have to be stricter or they will have no effect.
Requirements
You have activated availability control. For further information on deactivating availability control, go to the Funds Management Public Authorities implementation guide and read "Activate/Deactivate Availability Control".
Standard settings
If you do not define any tolerances for availability control, assigned values are then updated if availability control is active, but no action is triggered if the tolerance is exceeded.
AVC does not take the tolerances into account for the following functions, it always assumes a usage rate of 100%:
- Unilateral and reciprocal cover eligibility
- Revenues increasing the budget
Recommendation
Define your tolerance groups for all "Activity groups". However, if you want to specify different tolerance limits for the individual activity groups you should note that the tolerance levels are set more severely within the activity chain, for the lower activities.
Activities
Enter the settings you require.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | _ISPSFM_OF20 | 0 | KI48000002 | Availability Control |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| V_TBPFE_M | V - View | OF20 | ISPSFMOF20 | Funds Management Availability Control: Tolerance Limits | ||
| V_TBPFE_M | V - View | OF20 | ISPSFM0F20 | Funds Management Availability Control: Tolerance Limits |
History
| Last changed by/on | SAP | 20001215 |
| SAP Release Created in |
