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_CFMENUORKEKE1I | Define Ratios and Ratio Schemes |
| Transaction Code | S_ALR_87005578 | IMG Activity: SIMG_CFMENUORKEKE1I |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CFMENUORKEKE1I | Define Ratios and Ratio Schemes |
| Customizing Activity | SIMG_CFMENUORKEKE1I | Define Ratios and Ratio Schemes |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUORKEKE1I |
In this step you define ratios for use in planning. A ratio is the quotient between two value fields, such as price = sales/quantity or commission rate = commission/sales. (Note that ratios cannot be defined with a quantity field for a numerator and a value field for a denominator, such as "quantity field / value field".)
Ratios can be used in two ways:
- To simulate price and quantity changes (in manual planning)
In planning, you can change quantities, values or ratios directly in the planning layout. You can select ratios when you define the planning layout, just like you would value fields.
If you change a quantity, value or ratio, special rules determine which of the other two is recalculated. You define these calculation rules via calculation types which you maintain when defining the ratio. The ratio scheme is not involved in this function.
- To valuate a quantity plan with prices stored calculated in another plan version or in actual data (in manual and in automatic planning)
Using a ratio scheme, you can define which ratios should be used in which order for valuation (similar to using the calculation scheme for conditions).
You must assign at least one access-level characteristic to each ratio in a ratio group.
Access-level characteristics determine, for each ratio, which combination of characteristics the system should use to access the valuation. This makes it possible, for example, to calculate the average price for a product group. The calculation types for the ratios are not involved in this function.
Requirements
Standard settings
Recommendation
Activities
Further notes
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_CFMENUORKEKE1I | 0 | HLA0009431 O | |
| SIMG | SIMG_CFMENUORKEKE1I | 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 |
| VC_TKEQUO | C - View cluster | KE1I | 01 | Maintain ratios |
History
| Last changed by/on | SAP | 19990209 |
| SAP Release Created in |
