Hierarchy

⤷

⤷

IMG Activity
ID | _ISPSFM_N_AVC_TOLPRF | Edit Tolerance Profiles |
Transaction Code | S_KI4_38000344 | (empty) |
Created on | 20001124 | |
Customizing Attributes | _ISPSFM_N_AVC_TOLPRF | Edit Tolerance Profiles |
Customizing Activity | _ISPSFM_N_AVC_TOLPRF | Edit Tolerance Profiles |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | _ISPSFM_N_AVC_TOLPRF |
Note:
The settings affected here are exclusively reserved for the use of the Budget Control System (BCS).
Use
In this IMG activity, you define the tolerance profile for the availability control in BCS.
For each tolerance profile, you define whether you only want to work with percentage usage rates or also with maximum permissable absolute differences. If you allow absolute variances as tolerance limits, you must assign a currency to the tolerance profile - this currency must match your FM area currency.
In a tolerance profile you group together the tolerance limits for the different activity groups. You can define one or more tolerance limits for each activity group by specifying different usage rates or also absolute variances. You also define the check sequence of the different tolerance limits. Assign a message type to each of these defined check events. As message type, an error message, a warning, or an information can be issued.
Ceiling Type
You can use the ceiling type to control whether the availability control should limit expenditures (outgoing amounts and/or revenues (incoming amounts) from bottom to top.
Normally the availability control checks only expenditures (for example, outgoing payments). Under the revenues ceiling type, you can also maintain tolerance limits to check revenues (for example, incoming payments).
Usage Type for Tolerance Limits
If you allow both percentage usage rates and absolute variances in your tolerance profile, you can use indicator Usage Type for Tolerance Limits to control whether the tolerance limit is derived only from the usage rate or whether the tolerance rate is determined as minimum or maximum value from both values.
Event Control
You can assign an availability control check to each check event. This event is triggered if you post your document despite the tolerance limit being overrun. At the moment, you can only send mails from SAP office for this. You can define whether the system only sends a mail the first time, the specified tolerance limit is exceeded, or whether a mail should be sent each time the tolerance limit is exceeded when a document is checked.
Deactivating Individual Check Events
You can exclude individual check events from the active availability control by setting the Inactive indicator.
Procedure for Searching for Matching Entries
The active availability control proceeds as follows when searching for matching entries:
- Determines the tolerance profile to be used
- Determines all matching entries (check events with their tolerance limits) of the tolerance profile, which fit the activity group
- Checks the tolerance limit in inverted sequence of the check events, starting with the highest percentage tolerance limit
- Determines the action (=message type and if necessary event) when the first of these tolerance limits is exceeded.
- Suppresses the action found, if the Inactive indicator is set for the entry.
Note
Note that all tolerance limits for each activity group must be entered in order of the check events (with increasing values).
Example
The tolerance limits of the availability control for actual postings (activity group 40) could, for example, be defined in a tolerance profile such as this for example:
Activity Group Sequence Message Type Usage rate
40 01 Information 70%
40 02 Warning 85%
40 03 Error Message 100%
Standard settings
If no matching entry is found for a tolerance profile, the checks are carried out according to the following standard setting:
- Ceiling type: expenditures (outgoing amounts)
- Message type: error message
- Usage rate: 0%
- Usage type for tolerance limits: only usage rate
- Check: active
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
Mandatory / Optional | 1 | Mandatory activity |
Critical / Non-Critical | 1 | 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_N_AVC_TOLPRF | 0 | ALN0000196 | 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 |
VC_BUAVCTOLLIM_FM | C - View cluster | SM34 |
History
Last changed by/on | SAP | 20011211 |
SAP Release Created in | 462 |