Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
KIST (Package) Cost Accounting actual data RK-S
Basic Data
| Data Element | LATYP_DOC |
| Short Description | Activity type category |
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 | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | ATyp cat. |
| Medium | 15 | ATyp category |
| Long | 20 | ATyp category |
| Heading | 1 | C |
Documentation
Definition
Sets the category of activity allocation.
- Activity Type Category 1 (manual entry, manual allocation)
Manual planning of activity quantities. Plan allocation is made via activity input planning to the varying receiver objects. Reconciliation of plan activity quantities and plan scheduled activity must be made where necessary.
Actual activity quantites are entered within the internal activity allocation framework based on transactions.
- Activity Type Category 2 (indirect entry, indirect allocation)
Activity quantities produced cannot be calculated, or only with great difficulty. Activity quantity calculation therefore takes place in plan and actual in the indirect activity allocation framework using the defined sender/receiver relationships and the receiver tracing factors, or via fixed quantities determined in segment definition.
Activity allocation similarly takes place automatically via indirect activity allocation as described above.
Actual and plan activity quantity result from the sum of calculated activity inputs of the individual receivers based on the tracing
Plan and scheduled activity quantities are thus automatically reconciled.
- Activity Type Category 3 (manual entry, indirect allocation)
Manual planning of activity quantities. Entry of actual activity quantities takes place based on transactions via a separate entry function (non-allocatable activities), whereby no receiver objects can be entered here.
Activity quantity allocation in plan and actual takes place indirectly via sender and receiver relationships defined here. The SAP System calculates the allocatable quantities per receiver based on the tracing factor connections of all receivers. Manually planned or posted activity quantities are thus allocated completely to the receivers.
This results in complete reconciliation of plan activity types after execution of indirect activity allocation.
- Activity Type Category 4 (manual entry, no allocation)
Actual activity quantities are entered based on transaction via a separate entry function (non-allocatable activities), whereby no receiver objects can be entered here.
- Activity Type Category 5 (calculation and allocation via target=actual activity allocation)
Used in target=actual allocation.
Because this allocation is used only for allocation of actual values, activity types used in target=actual activity allocation must be assigned different categories for plan and actual allocation. In actual allocation, activity type category 5 must be used. In plan allocation, categories 1, 2, or 3 may be used, but as a rule category 1 is used.
History
| Last changed by/on | SAP | 19960725 |
| SAP Release Created in |
