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_CFMENUORKEKEA6 | Maintain Value Fields |
| Transaction Code | S_ALR_87005756 | IMG Activity: SIMG_CFMENUORKEKEA6 |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CFMENUORKEKEA6 | Maintain Value Fields |
| Customizing Activity | SIMG_CFMENUORKEKEA6 | Maintain Value Fields |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUORKEKEA6 |
In this activity, you can define your own value fields. Frequently used value fields, such as "Revenue" and "Sales quantity", are already predefined in the standard system.
You define these values independent of any operating concern and any client.
Before you create a new value field, you should take a look at the ones that already exist. It may be that you can use a value field you have already define or one defined in the standard system.
Once you are in the "change" mode, you can define a new value field by choosing the "Create" icon:
Enter a 4- or 5-character name that begins with "VV" for your value field. Here you also need to specify whether this field is a quantity field or a field for currency amounts. All the currency fields in any single line item use the same currency. This currency is defined in the attributes of each operating concern. Each quantity field, on the other hand has its own field that defines the unit of measure. Thus you can have quantities in different units in the same line item.
On the next screen, you can enter texts to describe the value field, as well as how the values in this field are to be aggregated over characteristics of time. In most cases, you will use the aggregation rule "SUM" (summation) to add up the values over periods. The aggregation rules "Last value" (LAS) and "Average" (AVG) are only of significance if the value field is to contain a statistical non-cumulative value.
Further notes
- If necessary, you can change the attribute "Currency or quantity field" as long as this value field is not used in any operating concern.
- You can change the texts for user-defined value fields at any time.
- You can delete any value field that is not being used in an operating concern.
- On the initial screen, you can use the repair function Extras -> Field catalog -> Reorganization to synchronize the CO-PA-specific field catalog with the ABAP Dictonary. This function is not needed under normal circumstances. It merely helps you remove inconsistencies following modifications or transport errors.
Standard settings
Recommendation
Activities
- Create your value fields and then activate your entries.
- To add your value fields to operating concerns, call up the function "Operating Concern -> Change data structures" in Customizing.
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| 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_CFMENUORKEKEA6 | 0 | HLA0100152 | Structures |
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 |
| KEA0 | T - Individual transaction object | KEA6 | 03 | CO-PA: Maintain Value Fields |
History
| Last changed by/on | SAP | 19981222 |
| SAP Release Created in |
