How to create Summarization level in KEDV for COPA Cycle?
Please help me in create Summarization Level for COPA Assessment Cycle
Kindly provide me the steps to create *Summarization level for COPA Cycle to improve the performance.
Define Summarization Levels
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.
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.
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.
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.
Build Summarization Levels for Profitability Analysis
Use program RKETRERU to populate your summarization levels with data.
You can populate summarization levels with data using a number of different methods:
When you define a new summarization level, this level has the status "active, without data" until you supply it with data. This step of supplying a level with data for the first time is referred to as "building" the level. When you do this, the status changes to "active", and you can use the summarization level in your application.
To keep the data in your active summarization levels current, you need to update them in regular intervals. When you do this, the system adds the changes made since the last update to the summarization level. Schedule this program to be executed in the background at regular intervals (i.e. daily or hourly).
If you have a lot of new data, it may make more sense to delete the data in the summarization level and rebuild the level.
When you rebuild a summarization level, the system selects the data from an existing summarization level where this is possible.
To ensure that all your data remains consistent, the system excludes any data posted in the last 30 minutes before execution (so-called "safety delta"). Consequently, the time of execution shown in the log is always half an hour before the actual time of execution.
Do not start the program to update within 30 minutes of a data transfer (batch transfer, for example), because the data just posted will not be included in the summarization level.
If you have a large data volume, you may encouter long runtimes which prohibit running this program online. If this is the case, execute it in the background.
Damage caused to data by errors
If the program terminates abnormally (i.e. due to a power failure), start it again. Updates start again exactly where they left off. Builds, on the other hand, need to start over.
A log is displayed telling you whether or not the summarization levels were filled properly.