Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
KAUC (Package) Customizing R/3 Cost Accounting, Orders
IMG Activity
| ID | SIMG_ORKAOPI1 | Value Categories |
| Transaction Code | S_ALR_87004365 | IMG Activity: SIMG_ORKAOPI1 |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_ORKAOPI1 | Value Categories |
| Customizing Activity | SIMG_ORKAOPI1 | Value Categories |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_ORKAOPI1 |
In this IMG activity, you define value categories. Value categories are cost elements, intervals from cost elements or cost element groups.
You need these for...
- updating the project information database.
- interest calculation for orders
- defining structure reports for costs, revenues and commitments
You store keys and names for the new value categories in this workstep. You also specify which cost elements belong to a value category and can check the assignment of the cost elements to the value categories. With correct assignments, only cost elements of the same category should exist for each value category (that is, only costs or only revenues). Each cost element can be assigned to only one value category.
As this consistency check adversely affects system performance, you should perform it only when you have maintained all value categories.
After the consistency check, the system creates a list containing information for each controlling area about the assignment of value categories.
The traffic lights at the end of the nodes help you to perform targeted searches.
- Green traffic light:
There are no incorrect assignments within this hierarchy level.
- Yellow traffic light:
- There are cost elements that were not assigned, or
- the cost element to which the value category displays, does not exist in the system.
- Red traffic light
There are serious errors in the assignment. Example: A cost element was assigned to several categories or a category was assigned to cost elements with a different cost element category.
The state of the traffic light is transmitted upwards through the hierarchy.
Cost elements are displayed in different colors depending on their category.
The following cost element categories are distinguished by colors:
- Costs
- Revenues
- undefined cost elements.
Activities
- To create value categories or to change names for value categories, choose "Maintain value categories"
- To assign a cost element, cost element interval or a cost element group to a value category, choose "Save cost elements as value categories".
- To check the assignment of cost elements to value categories, choose "Consistency check: Check value category assignments"
Enter for which controlling area you want to carry out the consistency check.
You can branch direct from the log into cost element maintenance. Choose "Display" or "Change".
The changes are then displayed in the log, after you have selected "Refresh".
Example
Further notes
If you change value categories at a later data and planning data already exists, you must Reconstruct the Project Info Database. You need to reconstruct the project info database, to avoid data inconsistencies.
It is therfore advisable, to summarize cost elements in value categories to reduce the volume of data. If you still want to create a value category for each cost element, you can get the system to create the value categories automatically. For more info see the IMG for the Project System under Set Update Controlling.
Business Attributes
| ASAP Roadmap ID | 207 | Establish Reporting |
| Mandatory / Optional | 1 | Mandatory activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | SIMG_ORKAOPI1 | 0 | HLA0001407 | Periodic Order Closing |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| IMGDUMMY | D - Dummy object | CJVC | OPA-ZINS | Consistency check: check value category assignment |
History
| Last changed by/on | SAP | 19981222 |
| SAP Release Created in |
