Hierarchy
⤷ CA-GTF-TS (Application Component) Technical Application Support
⤷ BK (Package) CO Cross-application Objects
Basic Data
Data Element | LATYP |
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 | ACTIVITY_CAT | |
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 | 5 | ATC |
Documentation
Definition
Indicator determining the method of activity quantity planning and activity allocation.
- Activity type category 1 (Manual entry, manual allocation)
Activity types of this category use plan activity quantities. The plan activity is allocated to the different receiver objects using activity input planning. It may be necessary to reconcile the activity quantities and the plan scheduled activity.
Actual activity quantities are entered for each business transaction using internal activity allocation.
- Activity type category 2 (Indirect calculation, indirect allocation)
The quantities produced by the activity types in this category cannot be calculated or only with great effort. The plan and actual activity quantities are determined in indirect activity allocation using one of the following:
- The defined sender/receiver relationshps
- The receiver tracing factors
- Fixed quantities (defined in the segments)
Allocating the activities also takes place automatically through indirect activity allocation as described above.
The actual and planned 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.
- Activity type category 3 (Manual entry, indirect allocation)
Activity types of this category use activity quantities entered manually. Entering the actual activity quantity takes place on an activity-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 ensures that plan activities are fully reconciled after carrying out indirect activity allocation.
- Activity type category 4 (Manual entry, no allocation)
Activity types of this category use activity quantities entered manually. Allocations to other objects are not possible.
The actual activity quantity is entered for each transaction using a special function (Non-allocatable activities). 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.
Supplementary Documentation - LATYP 0001
Use
The following activity type categories exist.
- 1: Standard activity type
- 2: Activity types whose activity quantities are indirectly calculated from the receiver tracing factors
- 3: Activity types whose activity quantites are indirectly calculated and automatically allocated on the basis of receiver tracing factors.
- 4: Non-allocable activity types
- Non-allocable activity types are activity types that cannot be assigned to other account assignment elements (cost centers or orders). This type of activity type usually occurs in final cost centers.
Supplementary Documentation - LATYP 0009
Procedure
In plan, use activity type category 1, 2, 3, or 4.
Dependencies
If you do not fill the field "Activity type category" under "Variant values for actual allocation", the category entered here is valid for both plan and actual.
Note
Field changes
This field can be changed on the fiscal year level.
- Changing activity type categories 1, 2, and 3 is possible at any time, even if activity type planning took place, because they are merely defaults.
- Changing the allocation type for category 4 activity types, or changing category 4 to another category, is possible only if the fiscal year with the corresponding activity type has not yet been planned.
Time dependency
This field is always stored as time-based.
Supplementary Documentation - LATYPI 0009
Use
You only need to make an entry if you are using a different activity type category in the actual data than the one in the plan data. You can use activity type categories one, two, three, four, or five in the actual data.
Dependencies
If you do not make an entry in this field, then the indicator that you entered under "activity type category" is also valid in the actual data.
Notes
Field changes
You can change this field at fiscal year level (for example, for a new fiscal year).
- You can switch between categories one, two, three, and five. This is the case even if you already used the corresponding activity type for planning, as these are only default values.
- You can only change the activity allocation type in activity type category four, or from activity type category four to another activity type category, but only if you have not made any postings in the fiscal year using the corresponding activity type for either planning or actual data.
Time dependency
This field is always time-dependent.
History
Last changed by/on | SAP | 20000128 |
SAP Release Created in |