Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
KE0C (Package) Customizing for Profitability Analysis
IMG Activity
| ID | SIMG_CFMENUORKEOKEQ | Maintain Versions |
| Transaction Code | S_ALR_87005722 | IMG Activity: SIMG_CFMENUORKEOKEQ |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CFMENUORKEOKEQ | Maintain Versions |
| Customizing Activity | SIMG_CFMENUORKEOKEQ | Maintain Versions |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUORKEOKEQ |
In this step you define the CO versions you want to use for your operating concern. These versions are valid for all of CO and for all operating concerns.
In Profitability Analysis, you can only use versions for plan data. Consequently, the fields "Actual" and "Exclusive use" are not relevant for CO-PA.
Each version has attributes which are only valid for one operating concern.
The attributes determine the following:
- whether you can plan a version
The Version locked indicator lets you lock a plan version so that no more changes can be made to it.
- which currency type should be used to store the data in this version
If, alongside the operating concern currency, the company code currency or the profit center valuation are also active in your operating concern, you need to specify the currency type for each version.
- which exchange rate should be used to translate foreign currencies to the local currency
- for what date the system should derive characteristics
In planning, the system always tries to derive values for the characteristics which you do not specify. Since these derivation rules are time-dependent, you can specify which date the system should use when it performs derivation.
- which plan structure is checked for the plan version
You can enter a plan structure here to ensure that plan data for different profitability segments corresponds to a pre-defined plan structure.
For the transfer of plan data to SOP, you can determine:
- which characteristic group, if any, is used
An interface in planning lets you transfer planned sales quantities to Sales and Operations Planning. You can specify for each plan version which characteristic group, if any, should be provided to the user as an entry aid.
(See the example in the online documentation (F1).)
If you plan in weeks, you also need to specify:
- which rule is used to distribute the weekly plan values to plan periods
This rule determines how the weekly values are distributed to periods when a week cannot be assigned to one period.
(See the example in the online documentation (F1).) - which calendar is used as a basis for this distribution.
Actions
Define your CO version and select the "Plan" indicator. Then maintain the operating concern settings.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-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_CFMENUORKEOKEQ | 0 | HLA0009431 O | |
| SIMG | SIMG_CFMENUORKEOKEQ | 1 | I070004708 | Profitability Analysis |
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 |
| VERSION_A | C - View cluster | SM34 | Maintain Versions (General) |
History
| Last changed by/on | SAP | 20011214 |
| SAP Release Created in |
