Hierarchy
SAP_ABA (Software Component) Cross-Application Component⤷
CA-GTF-TS (Application Component) Technical Application Support⤷
BK (Package) CO Cross-application Objects
Basic Data
| Data Element | LATYP_ABC |
| Short Description | Allocation Category (CO-OM-ABC) |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | LATYP | |
| 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 | ALLOC_CATEGORY | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Alloc. cat |
| Medium | 15 | Alloc. category |
| Long | 20 | Allocation category |
| Heading | 5 | AlCat |
Documentation
Definition
Indicator determining the method of plan activity planning and allocation.
- Allocation category 1 (Manual entry, manual allocation)
Actual activity quantities in internal activity allocation are entered based on transaction. Plan allocation takes place via activity input planning on the different receiver objects. This may require reconciliation of plan activity quantities and scheduled activity.
Actual activity quantities are entered as part of internal activity allocation.
- Allocation category 2 (Indirect calculation, indirect allocation)
Activity quantities produced cannot be calculated or only with great effort. The plan and actual activity quantities are determined in indirect activity allocation using defined sender/receiver relationships and receiver tracing factors or fixed quantities (defined in the segments)
Allocating the activities also takes place automatically through indirect activity allocation as described above.
The actual and plan activity quantities result from the sum of the activity inputs calculated from the tracing factors on the individual receivers.
Plan and scheduled activity quantities are therefore automatically reconciled.
- Allocation category 3 (Manual entry, indirect allocation)
Activity quantities are planned manually. Entering the actual activity quantity takes place on a transaction-related basis using a special function (Non-allocatable activities) for which no receiver objects can be given.
The plan and actual activity quantities are allocated indirectly using defined sender/receiver relationships. The R/3 System calculates the activity quantity to be allocated for each receiver based on the ratios of tracing factors for all receivers. The manually planned or posted activity is thereby completely allocated to the receivers.
This always ensures that the plan activities are fully reconciled after carrying out indirect activity allocation.
- Allocation category 4 (Manual entry, no allocation)
Activity allocation uses actual activity quantities entered on a transaction-related basis using a special function (Non-allocatable activities) where no receiver objects can be entered.
Use
You can save a default value in the master data for an activity type or a business process for allocatable activity type categories or allocation categories (category 1, 2 or 3). You can change the default value within planning to a different allocatable activity type category or allocation category if you are planning for the first time.
You can only change non-allocatable activity type categories or allocation categories (category 4) to an allocatable activity type category or allocation category (or vice versa) if activity-dependent data exists.
History
| Last changed by/on | SAP | 20000128 |
| SAP Release Created in |
