Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CA-GTF-BS (Application Component) Business Application Support⤷
KABP (Package) Cost Accounting budget and planning
Basic Data
| Data Element | FM_ALWAYS_AVA_CHECK |
| Short Description | Check for Every Activity Within The Activity Chain |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | X | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Always AVK |
| Medium | 13 | Always check |
| Long | 35 | Availability Control Always Checks |
| Heading | 36 | Availability Control Always Checks |
Documentation
Definition
Stipulates that active availability control (AVC) checks the tolerance limits for each transaction in a "transaction chain".
Use
If you set this indicator, the tolerance limit of the relevant transaction (such as a purchase requisition, a purchase order or an invoice) applies when you post a business transaction.
For example, by restricting the tolerance limits more strictly for a purchase order than for a purchase requisition, you can determine that in your organization the budget can be exceeded by purchase requisitions but not by purchase orders.
If you do not set this indicator, the tolerance groups only apply for the business transactions posted in a "transaction chain", if the transaction increases the assigned value. For more information on this feature of AVC, see section Define Tolerances for Availability Control.
Example
Dependencies
The check is only active within the transaction chain, if availability control is active. If you deactivate availability control by setting the Not Active indicator, no check will be performed within the transaction chain.
Example
History
| Last changed by/on | SAP | 20010720 |
| SAP Release Created in | 462 |
