White Lotus

COPA Performance Tools

COPA Performance Tools Page 1

White Lotus

Contents
1. Unit Summary.................................................................................................. 3 2. Overview of topics covered ............................................................................. 3 3. Planning Process - Business example .............................................................. 3 4. Summarization levels....................................................................................... 3 5. Maintaining Summarized Data (Regular Activity)............................................. 7 6. Summarization settings in Report Settings ...................................................... 8

COPA Performance Tools Page 2

White Lotus
1. Unit Summary
This lesson explains the need for summarization. It also explains how to define and activate summarization levels in COPA.

2. Overview of topics covered

Concept of COPA Summarization Definition and activation of summarization levels

3. Planning Process - Business example

ACL would like to implement a COPA in the SAP system. ACL is keen on understanding the performance features of COPA especially f the data volume is high. It would like to understand the functionality of summarization levels, summarized data, and frozen data.

4. Summarization levels
In COPA has a normalized table structure, when a COPA document is posted. The relevant information is stored in three tables. CE1XXXX - Line item table CE3XXXX - Segment Level Table CE4XXXX - Segment table

The segment table contains the profitability segments and their characteristic values. The segment level contains the value fields for profitability segments and the characteristics of time in the primary summarized form. The line item table contains the value fields for profitability segments. This data is stored for each individual COPA document line item. The segment level is updated simultaneously with each transaction instead of periodically, therefore contains up-to-date data because it. This structure allows archival of detailed line item data, without removal of summarized data, thereby, retaining the ability to report based on the summary data for past periods.

COPA Performance Tools Page 3

White Lotus
Every item of a sales order is sent to the CO-PA database as a line item. This therefore can lead to a huge amount of data within a very short period of time, possibly leading to report runtimes of several hours. The COPA summarization feature in SAP can be used to reduce the volume of data that has to be read online. COPA reports can be defined to extract data in either of the following ways Only the data from the summarization level, which means that report considers only data until the last time the level was updated. The current data, in which case the system reads the summarization level and then adds the line items that have been posted since the last update. If a suitable summarization level is not identified, the system can be set up to display a warning. When current period reports are being executed, then the report must be set up access current data. The most recent summarized data is to be used when reports are executed for period that has been closed. This approach makes sense because the data is not going to change anymore. If the option to store the summarization data for a report is selected, the system creates report by reading a summarization level. This means that less data the system has to read from the level, and hence better performance. When a report is executed and a suitable summarization level is not found. The system can respond in three possible ways. The option selected by SAP depends on the settings made in the report. Continue executing using data from current tables continue executing with a warning message that it could take some time, stop executing the report.

At the report level it is possible to define, whether a report should access the data - from a summarization level alone or - from a summarization level and also from current data, requiring the addition of data from any line items that have been posted since the level was last updated. To use summarization levels, the following steps need to be performed 1. Define the summarization levels in configuration. 2. Fill the summarization levels with data from the segment-level summary records. 3. Update the summarization levels periodically in the background.

COPA Performance Tools Page 4

White Lotus
Every summarization level consists of two tables in the database, a key table and a total records table. Definition of summarization levels Menu Path Transaction codes IMG - > Controlling -> Profitability Analysis -> Tools -> Summarization levels -> Define Summarization levels KEDV

The summarization levels can be defined by clicking on the Characteristics button

COPA Performance Tools Page 5

White Lotus

The value in the characteristic value field determines if the field is summarized or not. -

If the field is left blank then the values of these characteristics are summarized and are not available for analysis (in reporting, etc.) If the field is * then the values of these characteristics is summarized fully. All possible values are available for selection in reports using the summarized data Instead of entering "*", a single characteristic value can also be entered. This makes sense if only one value of the characteristic needs to be analyzed. Once the summarization levels are defined, data needs to be updated into the summarization tables. This is done by executing a program.

COPA Performance Tools Page 6

White Lotus
5. Maintaining Summarized Data (Regular Activity)
Menu Path Transaction codes Easy Access - > Accounting -> Controlling -> Profitability Analysis -> Tools -> Summarization levels -> Define Summarization levels KEDU - Refresh

Once the program is executed, the summarization level statistics are updated

COPA Performance Tools Page 7

White Lotus
6. Summarization settings in Report Settings
Menu Path Transaction codes Easy Access - > Accounting -> Controlling -> Profitability Analysis -> Information System -> Define reports -> Change KE32 Change Report

Use Summarized Data

Use a Summarization Level Use current data

Respone if no summarization data exists

Summarization data is a pre-summarized set of report data stored in the database. This data can be read from the database and displayed immediately when the report is called. This data if available is used first. The data from the summarization level is used to generate the report. If this indicator is active, system includes line item data that was posted after the last update of the summarization. Error Message: Report is not processed, error message is displayed Warning: Warning message is displayed, however, user an chose to proceed with the execution of the report Execute report: Report is executed without any warning

COPA Performance Tools Page 8