Ansicht
Dokumentation

SIMG_CFMENUORKEKEDV - Define Summarization Levels

Addresses (Business Address Services)   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Maintain summarization levels

In this activity you define summarization levels.

For a general overview of 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

The maintenance of the summarization levels consists of a view cluster. When you call the maintenance transaction, the system displays an initial screen containing all the existing levels. You have the following options for navigation:

• In the navigation area you can access:

• the characteristics (here you define which characteristics should be summarized and which should not)

• 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, for example, for a summarization level that only contains the data for a single company code. This summarization level can only be used by the applications if this fixed company code is defined identically.

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 that have the status "Active" can be used by applications.

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 new summarization level. If you have deleted levels, the system deletes the corresponding tables. If you change the characteristics 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 summarization levels. Until you have done so, you cannot use the new summarization levels in your applications.

Characteristics

In the characteristic list for the summarization level, choose which characteristics you want to summarize and which you do not want to summarize. If you change the characteristics, the system deletes all the data in the summarization 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 it is not necessary to define indexes. When you save the summarization levels, the system creates a default, which is usually sufficient. It only makes sense to create indexes when the data in the key table reaches a volume of several tens of thousands of 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 access the detail screen for the summarization level. The detail screen contains statistical information. Interesting pieces of information include 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 helps you to compare levels. It assists you in deciding whether levels can be deleted because they are no longer used, for example, or if new levels need to be created.

• Test mode

Here you can deactivate all the summarization levels for test purposes, in order to compare the data in the summarization levels with the data in the segment level. Run the application 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 test mode, and can still be updated. However, they are not used in applications. Be sure to turn the summarization 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. In this case, the new summarization level will not be created. Next, select the desired reports and save the summarization levels.

Finally, choose "Tools -> Summarization levels" from the application menu and build the new levels.

With the function "Create proposal", it is theoretically possible to create a summarization level that already exists semantically. You should therefore check the overview list first to see if the summarization level already exists. If so, do not save the level.

Tips on optimizing the summarization levels

The detail screen for a summarization level contains some statistical information. This information helps you to decide whether it makes sense to use levels, or if they are to 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 level has the status "To be created", save your entries. If the level has the status "Active, without data", build the level. If the level has the status "Decimal overflow", the level can no longer be used. First, build the level. It may be that the overflow no longer occurs and the level has the status "Active". If the overflow occurs again, 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 ratio (read time / number of accesses) is much greater than for other levels, this may indicate that there are no indexes. Another reason could be that a report uses a summarization level that is more detailed than is actually necessary, meaning a level that contains more information than is required. In this case you should check whether a new level would improve performance for that report.

Notes on transporting

You can use the CO-PA transport tool to transport the settings you made to your productive system.

The system only transports the description of the summarization levels. In the target system, after the import 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 report RKETREGN in the target system. On the initial screen, enter the following (replacing "xxxx" with the name of your operating concern):

Application class KE

Subapplication 01

Table name CE1xxxx (for costing-based CO-PA)
CE0xxxx, for margin analysis

More Information

• Supplying the summarization levels with data

• Examples for defining summarization levels

RFUMSV00 - Advance Return for Tax on Sales/Purchases   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 10070 Date: 20240523 Time: 195329     sap01-206 ( 193 ms )