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_CFMENUORKEKEDV | Define Summarization Levels |
| Transaction Code | S_ALR_87005563 | IMG Activity: SIMG_CFMENUORKEKEDV |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CFMENUORKEKEDV | Define Summarization Levels |
| Customizing Activity | SIMG_CFMENUORKEKEDV | Define Summarization Levels |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUORKEKEDV |
Maintain summarization levels
In this activity you define summarization levels.
For a general overview on summarization levels, see the corresponding chapter in the CO-PA online manual. The following text describes how you maintain summarization levels. To learn how to define them for a specific use, see the examples.
Navigation functions
When you call up the transaction for maintaining summarization levels, the system displays a view containing all the existing levels. You can navigate in the following manners:
- In the navigation area at the top of the screen, you can call up:
- the characteristics (here you define which characteristics should be summarized and which not)
- and the indexes (to fine-tune the way the system accesses the summarization levels)
- The function "Detail" (magnifying glass icon or double-click) displays statistical information.
- Under the menu "Extras" you can access an overview list of fields in all of the (selected) summarization levels.
Recommendation
Use fixed values sparingly for the characteristics. If, for example, you define a summarization level which contains the data for one company code only, you can only use it when you are working in that company code.
At first you do not need to define any indexes. Indexes let you fine-tune how the system accesses the summarization levels. If you do not define any indexes here, the system will create a default when you save. This default should be sufficient in most cases. You should not need to change this until your summarization levels contain a large amount of data in the key table.
Initial screen
The system displays a list of all the existing summarization levels, their descriptive texts, and their current status. The status of a level tells you whether the level can be used in your application. Only those summarization levels can be used which have the status "active".
Technically you can create up to 5000 summarization levels. However, you should try to get by with as few levels as possible, since increasing the number of levels increases the amount of memory space required and the amount of time needed to build them. You can create additional levels later as required. You can also delete the ones you no longer need.
The function "Save" is only available on the initial screen. When you save, the system creates tables in the ABAP/4 Dictionary and in the database for each summarization level. If you have deleted levels, the system deletes the corresponding tables. If you change the fields or the indexes in the summarization level, the system deletes the tables and then recreates them.
Once you have saved the summarization levels, you need to run the program for building the levels, that is, supplying them with data. Until you have done so, you cannot use the summarization levels in your applications.
Characteristics
In the characteristic list for the summarization level, choose which characteristics you want to summarize and which not. If you change the characteristics, the system deletes all the data in the level. For more information, see characteristic value in the summarization level catalog.
Indexes
Indexes let you optimize the way the system accesses the summarization levels.
At first you do not need to define any indexes. When you save the levels, the system creates a default, which should be sufficient in most cases. It only makes sense to create indexes when the data in the key table reaches a volume of several thousand records (see detail screen).
Maintain the characteristics before you define indexes.
Detail screen
By double-clicking on a level or clicking on the "Detail" pushbutton, you obtain the detail screen for the summarization level. The detail screen contains various statistical information, including how often the level has been accessed or how many records it contains. This data tells you how often the level is used and how high the degree of summarization is.
Menu "Extras"
The menu "Extras" contains the following additional functions:
- Overview list
This function gives you an overview of the existing levels. This list makes it possible to compare the levels side by side, which helps you decide whether or not you can delete certain levels or whether you need to create new ones.
- Test mode
Here you can deactivate all the summarization levels for test purposes, in order to compare the data in the levels with the data in the segment level. Run a function once with the test mode and once without. In both cases, the same data must appear. The summarization levels retain the status "active" even when you are in the test mode, and can still be updated. However, they are not used in applications. Be sure to turn the levels on again after you have finished testing.
- Create proposal
Here you can have the system automatically propose summarization levels for one or more reports. First enter a number for the summarization level. If you want to create more than one proposal, the system assigns numbers sequentially starting with the number you entered. Existing numbers are not overwritten.
Next, select the desired reports and save the summarization levels.
Finally, choose "Tools -> Summarization levels" from the application menu and build the new levels.
Note: With the function "Create proposal", it is theoretically possible to create a summarization level that already exists. You therefore should check the overview list first to see if the level already exists. If so, do not save the level.
Tips on optimizing the summarization levels
The detail screen for a summarization level gives you some informational statistics that can help you decide whether your levels are being put to good use or whether they can be deleted.
The overview list lets you compare the definition of characteristics in your levels.
- Level is contained in another level.
By comparing how often the levels are used, you can decide whether you need both levels. If the number of records in the levels does not differ greatly, you can delete the one which is summarized to a higher degree to save memory space.
- Level is not used.
If a level is not used or hardly used, you can delete it.
- Level not in status "active".
If the status is "To be created", save the level. If it has the status "active, without data", build the level. If the level has the status "decimal overflow", the level can no longer be used. It may be that the overflow no longer occurs when you rebuild it, otherwise delete the level.
- Long read times.
The detail screen shows the aggregated time needed to read the level and how often it was read. If the average is much longer than with other levels, this may indicate that there are no indexes. Another reason could be that a report uses a level which is more detailed than is actually necessary. In this case you should consider whether you can create a special level to improve performance for that report.
Notes on transporting
You can transport the settings you make to your productive system using the CO-PA transport tool.
The system only transports the description of the summarization levels. Once you have transported the levels, you need to call up the maintenance transaction for summarization levels once and press "Save" to create the corresponding tables.
As an alternative to this, you can execute program RKETREGN. On the initial screen, enter the following (replacing "xxxx" with the name of your operating concern):
Application class KE
Subclass 01
Table name CE1xxxx (for costing-based CO-PA)
CE0xxxx (for account-based CO-PA)
Additional information
Business Attributes
| ASAP Roadmap ID | 306 | Establish System Administration |
| 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_CFMENUORKEKEDV | 0 | HLA0100164 O | |
| SIMG | SIMG_CFMENUORKEKEDV | 1 | I070004701 | 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 |
| V_TKETRLF | V - View | KEDV | 0000000000 | Generated table maintenance: V_TKETRLF | ||
| V_TKETRL | V - View | KEDV | CO-PA | Define summarization levels | ||
| V_TKETRLX | V - View | KEDV | 0000000000 | Generated table maintenance: V_TKETRLX |
History
| Last changed by/on | SAP | 19981222 |
| SAP Release Created in |
