Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
KC (Package) Cost Accounting Controlling EIS
IMG Activity
| ID | OKCM_KCDV | Define summarization levels |
| Transaction Code | S_ALR_87000411 | IMG Activity: OKCM_KCDV |
| Created on | 19981222 | |
| Customizing Attributes | OKCM_KCDV | Define summarization levels |
| Customizing Activity | OKCM_KCDV | Define summarization levels |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OKCM_KCDV |
The maintenance of the Summarization levels is described in the following.
Example
Requirements
You have read the corresponding section in the Online handbook on EC-EIS and EC-BP.
You have analyzed the distribution of your master data with the Database statistics.
Standard settings
Activities
Initial screen
After getting into the definition of the summarization levels you see a list of the defined summarization levels with a text description and the current status. The Status of a level shows
whether a level can be used or not. Only those summarization levels with the status "Active" can be used.
Characteristics
On the characteristic list, you enter which characteristics should be summarized and which should not for each summarization level. You can find further information in the field documentation for Characteristic value in the catalog of the
summarization level.
Use fixed values sparingly, e.g. for a summarization level which only contains the data of a single company code. This summarization can only be used by the applications if this fixed company code is identically entered.
A later change to the characteristics in the summarization level results in all summarization levels which contain data being deleted. You must rebuild the summarization level accordingly after the change.
Indices
Indices offer you the chance to optimize the access to the summarization levels. At first you do not need to define any indices. The system creates a suggestion when you create the summarization levels, which is sufficient in most cases. It is not until the volume of data in the key table goes above several tens of thousand of records (see detail screen) that an optimization is sensible at this juncture. Please maintain the characteristics before you define the indices.
Creating a suggestion
Under 'Extras -> Create suggestion', you can automatically create summarization levels for reports. Please enter a number from which the summarization levels should be created.
Select the desired report. The system analyzes the reports and suggests a summarization level for each report. As a rule, you should check the suggestions. In addition to this, please read the recommendations below and the rules of thumb given in the online handbook.
Please note that unnecessary summarization levels can be created with the function 'Create suggestion'. These may be contained in other summarization levels.
Saving and activating the summarization levels
Go back to the initial screen in order to save your summarization levels. After creating or changing, the summarization levels are first in 'To be created anew' status. Data structures in the ABAP/4-Dictionary are created for the summarization levels during saving. After you have saved the summarization levels, they are in the 'Active without Data' status.
So that the summarization levels can be used by reports, they have to be supplied with data. To this effect, plan a job for the Building of summarization levels in the background processing (Report RKCTRERU). It is only that the summarization levels are 'Active' and can be used by reports.
Note for the system administrator
Tables are created in the ABAP/4-Dictionary and on the database with all new summarization levels. You can find the name of the created tables on the detail screen of the summarization levels.
Further notes
If you suspect that there is incorrect data in the summarization levels you can deactivate their use for test purposes under 'Extras -> Test mode'. This enables you to compare the data from the summarization levels with the data from the transaction database.
Run the report once with and once without the test mode. The same numbers must be displayed in both cases. When the test mode is turned on all of the summarization levels remain in 'Active' status and are updated; but they are not used by a report anymore. Do not forget to turn the use of the summarization levels back on after a test.
Recommendation
Notes for optimizing the summarization levels
Under 'Goto -> Detail' you can find statistical information about a summarization level, such as the number of accesses to a level or the number of available records.
Under 'Extras -> Overview' you can compare the characteristic definitions with their levels.
This information will help you to decide whether a level should be changed or deleted.
In the following, some rules of thumb explain when there is potential for improvement for your summarization levels and how you can optimize them:
Define as few summarization levels as possible
Attempt to use as few summarization levels as possible as the required memory space increases with the number of levels. You can create further summarization levels later and delete the ones no longer in use.
Use fixed values sparingly in the definition
Because of fixed values an existing summarization level cannot be used by new reports if the report does not contain all of the limitations. You should overwrite the fixed values with a '*' with summarization levels suggested from reports, so that the summarization levels can be used more generally.
Level is contained in another level
On the overview screen you can compare the characteristics of several summarization levels, in order to find out if one summarization level is contained in another.
Two situations are explained in the following example. The table represents a table from the overview screen, the row 'Number of record records' is the "Number of totals records" from the detail screen.
Characteristics Level 1 Level 2 Level 3
Company code * * 0001
Customer group * *
Customer * * *
Number of records 50.300 50.100 5.000
- In level 2, unlike in level 1, the characteristic customer group is summarized. Therefore, the number of records in summarization level 2 should be a lot less than in summarization level 1. This is not the case as the customer group depends on the characteristic customer. The slightly higher number of records in level 1 may be due to the fact that there are customers which are sometimes viewed as wholesalers and sometimes as retailers. As level 1 is more detailed than level 2 it can be used instead of level 2 for the reading process. As the number of records in level 1 is hardly more than the number in level 2 there is almost no noticeable difference in performance when calling up a report. In this case you can delete level 2. The advantage is that the data must be updated one level lower.
- In level 3 we are dealing with a summarization level with the same summarization as level. The level 3, however, only contained the data from one company code. A report which reads its data from summarization level 3, no longer has to read records from level 1 as it only needs the data from company code 0001. Level 3 can be deleted.
In order to improve the selection of data from level 1, an index can be created about the field company code.
Result: Summarization levels 2 and 3 are contained in level 1 and can be deleted. When calling up the summarization levels level 1 must then be updated less.
Level is not being used
If a level is not used it can be deleted. You can glean this from the date of the last access and the number of access (on the detail screen).
Length of access is long
The total time for accesses to a level is shown on the detail screen. The number of accesses is also shown.
If the quotient (total time / number of accesses) is markedly more than on other levels this can be a sign that a too-detailed level is being used for a report, meaning a level that contains more information than is needed. In this case a more highly summarized level can bring improvements in performance.
Business Attributes
| ASAP Roadmap ID | 207 | Establish Reporting |
| Mandatory / Optional | 2 | Optional 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 | OKCM_KCDV | 0 | HLA0009495 | Data Basis |
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_TKETRL | V - View | KCDV | EC-EIS | Define summarization levels |
History
| Last changed by/on | SAP | 19981222 |
| SAP Release Created in |
