Hierarchy
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ KBAS (Package) Overhead Cost Controlling
Attribute
Message class | BK | ||
Short Description | Create, Display, Reverse Controlling Document | ||
Message Number | 128 | ||
Documentation status | Space: object requires documentation | ||
Authorization check Error Message | |||
Changed On | 20100310 |
Message Text
Help Document
Diagnosis
In business transaction you entered activity type , category . This category is not allowed in business transaction .
System Response
You can use only activity types of given categories in a given business transaction.
The following activity type categories are valid for a given business transaction:
- RKL (Direct Activity Allocation):
- Category 1 (manual entry, manual allocation)
- RKN, RKIL (Indirect Activity Allocation):
- Category 3 (manual entry, indirect allocation)
- Category 4 (manual entry, no allocation)
RKLT (Template Allocation Actual):
Category 1 (manual entry, manual allocation)
Category 2 (indirect calculation, indirect allocation) - RKPS (Template Allocation Plan):
- Category 1 (manual entry, manual allocation)
- Category 2 (indirect calculation, indirect allocation)
NoteYou can post category 2 (indirect calculation, indirect allocation) and
category 5 (calculation and allocation using target=actual activity allocation) activity types
manually only if the indicator Manual actual quantity is set in the activity type master data.
If this indicator is set for an activity type of category 1, 2 or 5, you can post the activity types in the same posting transaction (entry
of sender activities) and together with activity type categories
3 and 4.
Procedure
Enter an activity type with a category valid for business transaction .
Note
If you have not yet carried out any postings in actual or plan, you can overwrite the activity type category defined in the activity type master record in planning.
This activity type category is then valid for the entire fiscal year in both actual and plan. Making a change to master data at a later date affects the current fiscal year and therefore not the
current posting.
History
Last changed on/by | 20100310 | SAP | |
SAP Release Created in |