COPA Performance Improvement using Summarization Levels

Issue:
Very long processing time or frequent TIME_OUT errors while execution of COPA
reports (KE30) or assessment cycles.
Solution:
1. Activate CO-PA log (T-Code KEDZ, Program: RKE_PROT_EVALUATE)
Purpose:
Any COPA report/cycle execution or data access from COPA tables would be
recorded in the log after this activation. This allows SAP to analyze the CO-PA usage
pattern /access information based on which automated summarization levels could
be created to improve COPA performance.
Execution Steps:
Execute t-code KEDZ

Enter the Operating Concern (PI02) and click "Activate" (Ctrl+F1)

2. Collect CO-PA log data for a few weeks or months. (T-Code KE30, KEU2,
etc)
This will be done automatically by the system when COPA reports or assessment
cycles are executed.
For quick resolution in reports with poor performance, you may choose to execute
all COPA reports /cycles, for which performance improvement is required to update
the log data.
3. Create Summarization levels proposal (T-Code: KEDVP, Program:
RKETRERU)
Purpose:
In this step, the system would read the access log information as recorded in step 2
and present a proposal to create summarization levels according to the database
access patterns identified in the COPA log.
Execution steps:
Execute t-code KEDVP

Enter Operating Concern

Select COPA Type (Costing Based /Account Based)

Select the type of proposal to be created

-_Enhancement: Existing summarization levels are taken into account during
optimization, and only additional summarization levels are proposed
- Replacement: With this type of proposal, all existing summarization levels are
ignored. The proposed summarization levels replace the existing levels. Even
replacement proposal does not delete any existing summarization levels. However
existing levels can be manually deleted using T-Code KEDV

Select the period (select maximum period for which log data is available) for
which logged COPA transaction data should be considered to create the proposal.

Click "Create Levels" button to accept the summarization level proposal

displayed
Note: The analysis can take quite a long time. If the program aborts during dialog
processing, due to run time being exceeded, restart the program in background
processing. To display the result when the program has completed, choose Display
last proposal.
4. Build Summarization levels (T-Code: KEDU)
*Purpose:*Large volume of data available in COPA tables is organized into various
summarization levels using this transaction, which allows for quick data access at
the summary levels for various reports and cycle executions instead of the high
time and system consuming process of direct data retrieval from COPA tables.
Execution Steps
Execute t-code KEDU

Enter Operating Concern

Choose type of Profitability analysis (Costing/Account)

Select "Build new Levels"

Execute in background mode only using menu option Program > Execute in
Background (F9)

Click "Immediate"

Click "Save"
5. Wait for the summarization level build process to complete (T-Code:
SM37)
Status of the background job scheduled in step 4 can be using t-code SM37 with
job name "RKETRER
6. Schedule a Daily Background Job to refresh summarization level data (TCode: KEDU/SM36)
Purpose: The summarization levels created above would hold only the data
available in COPA tables as on 30 minutes before the build process. To update the
summary tables with the latest transaction data, summarization level refresh
process needs to be executed daily.
Execution Steps:
Execute t-code KEDU

Enter Operating Concern

Choose type of Profitability analysis (Costing/Account)

Select "Refresh"

Save as a variant "COPA Summarization Refresh"

Execute t-code SM36

Click "Job Wizard" button

Click Continue

Enter a descriptive job name (example: COPA summarization refresh) and

priority, leave the target server blank and click "continue"
Select "ABAP Program Step" and click "Continue"
Enter ABAP program name as "RKETRERU" and choose variant "COPA
Summarization Refresh" and click "Continue"

Do not select add additional steps and click "Continue"

Select option "Date/Time" and click "Continue"

Enter a scheduled start date and time (non- business hour) , Check "Periodic"
and click "Continue"

Select "Daily" and click "Continue"

Click "Complete"
Notes:
- Report for which performance improvement is sought must be configured to use
the summarization levels in the report option field for presummarized data
- Population of initial summarization level , could be a very time consuming job and
hence it may require to be executed into multiple parts with different executions for
different summarization levels.
- Do not execute t-code KEDV while trying to execute a background job for
summarization level population using KEDU.

Error Message:
"KEPM Missing Data During Entry or Message no. K9031"
Component:
CO-PA
How to fix it?
The possible reason for the error is that the field catalog is inconsistent in
your Unicode system. Then I Please refer to the following steps as I
believe it will prove useful in resolving this issue properly.
Solution
Please <Execute> report RKEAGENF in SE38 as follows:
Operating concern: " " (Actived)
Structure: leave blank
Type of CO-PA: "1"
Refill? : "X".

Afterwards <Execute> KEPM again and your issue will be solved.

Archiving Profitability Segments

Skip to end of metadata

Attachments:2

Added by Lucas Michel, last edited by Lucas Michel on Feb 14, 2012 (view
change)

show comment

Go to start of metadata
Purpose
The purpose of this WIKI is to show the difference between archiving in different
releases and provide the necessary steps for all of them.
Overview: An introduction of archiving:
Definition
When you generate an operating concern in Profitability Analysis (CO-PA), the
system automatically generates the following archiving objects and the
corresponding write, delete, and reload programs (xxxx is the name of the
operating concern):

For costing-based Profitability Analysis:

COPAA_xxxx

COPAB_xxxx

COPA1_xxxx

For account-based Profitability Analysis: COPA2_xxxx

For Profitability Segments: COPAC_xxxx

The archiving objects COPAA_xxxx and COPAB_xxxx replace the archiving object
COPA1_xxxx.
Although the archiving object COPA1_xxxx can still be used, we recommend only
using the new archiving objects. For example, only these archiving objects have an
IMG activity for preparing archiving in Customizing, whereas the archiving object
COPA1_xxxx does not.
Structure
You can archive the following tables in costing-based Profitability Analysis:

Actual line items (table(s) CE1xxxx) with the archiving object COPAA_xxxx
or COPA1_xxxx (not recommended)

Plan line items (table(s) CE2xxxx) with the archiving object COPAA_xxxx or
COPA1_xxxx (not recommended)

Segment level (table(s) CE3xxxx) with the archiving object COPAB_xxxx or

COPA1_xxxx (not recommended)

Transaction-based distribution (table CEALE01) with the archiving object

COPAA_xxxx or COPA1_xxxx (not recommended)

Table CEAL01 can only be archived if distributed Profitability Analysis (with ALE) is
active and data is distributed by transaction. Table CEALE01 in the target system
contains the references to the line items in the sender system.
For background information on tables in costing-based Profitability Analysis,
see Database Tables for CO-PA Transaction Data.)
In account-based Profitability Analysis, you can use archiving object
COPA2_xxxx to archive the following:

CO line items (tables concerned: COEP, COEJ, COBK)

Totals record tables (tables concerned: COSS, COSP, COKA)

For both forms of Profitability Analysis, you can use archiving object
COPAC_xxxx or COPA1_xxxx (not recommended) to archive the following:

Profitability segments (table(s) concerned: CE4xxxx)

Account assignment number (tables concerned: CE4xxxx_ACCT,

CE4xxxx_FLAG)

To restrict the data to be archived, you can select different selection parameters in
archiving. For this, you can choose from some fixed selection parameters
(see Creating Archive Files (CO-PA)). Moreover, in Customizing for Profitability
Analysis under Tools Utilities Prepare Archiving, you can select characteristics
from the profitability segment characteristics (segment level characteristics) and
define them as selection parameters.
Integration
Archive Information System (AS)
Since the archiving objects in Profitability Analysis depend on the operating concern
(which is generated at customer) and on the Customizing settings under Tools

Utilities Prepare Archiving, the corresponding information structures and the field
catalog must also be generated for the Archive Information System (AS).
The information structure and the field catalog are generated on the basis of
the data object definition that you created in the IMG activity Prepare Archiving.
From the technical standpoint, a data object corresponds to all data records in an
archive file with the same combination of parameter values. With an optimal data
object definition, the time required for AS to access the data in the archive can be
reduced considerably. For more information, see the documentation on the IMG
activity Prepare Archiving.
The information structure and the field catalog are also generated in the IMG
activity Prepare Archiving. The following archiving objects are generated for the
individual archiving objects:

Archiving object COPAA_xxxx: Field catalog and information structure

SAP_COPAA_xxxx

Archiving object COPAB_xxxx: Field catalog SAP_COPAB_xxxx

Archiving object COPA2_xxxx: Field catalog and information structure

SAP_COPA2_xxxx

In order that it be possible to use the information structures in a production

system, they then have to be activated in AS. For more information about
information structures, see Using the Archive Information System. For information
about field catalogs, see under Field Catalogs.
To display archived data from the segment level (table CE3xxxx), you can (and
should) use the Information System in Profitability Analysis. Here, you can define
profitability reports that access the archive. When you define a profitability report
(see Defining Profitability Reports), you activate the selection Use archived data on
the Options tab page.
To display archived data from line items (tables CE1xxxx, CE2xxxx for costingbased Profitability Analysis and COEP, COEJ, COBK for account-based Profitability
Analysis), you can and should use the transactions for displaying line items: KE24,
KE25, and KE30 (for reports based on line items). You can display the data from the
archive once you have set the Archive indicator in the menu under Extras Data
Source.
Symptom
For releases 4.5B to 6.0:

It is not possible to archive profitability segments from tables CE4XXXX or

CE4XXXX_ACCT as of Release 4.5 by using the generated archiving
objects COPA1_XXXX and COPA2_XXXX (XXXX = operating concern).
From release 6.0 and above:
You need a suitable archiving object for your CE4XXXX_ACCT table.
Archiving in older releases (5.0 and below)
You use the commom archiving objects COPA1_XXXX and COPA2_XXXX. You
notice that regular table are selected (COBK, COEP, etc...), however, CE4* tables
are not.
You have data in CE4XXXX_ACCT and need to stop updating this table for any
reason (such as an iminent upgrade).

SOLUTION:
Program RKEREOCE4 must be used in this case.
It is necessary to deactivate the profitability segments that must be archived (in <
6.0 Releases).
Note 383728 provides special programs regarding the profitability segment tables:

ZZREOCE4_40.TXT for Release 4.0

ZZREOCE4_NEW_45.TXT for Release 4.5

ZZREOCE4_NEW_46B.TXT for Release 4.6B

ZZREOCE4_NEW_46C.TXT for Release 4.6C

ZZREOCE4_NEW_470.TXT for Release 4.70

As of Release 4.70 Support Package 13, the function for archiving unused
profitability segments and account assignment numbers is contained in
the standard system. In addition, standard program RKEREOCE4 determines the
unused profitability segments and account assignment numbers. The
only difference between standard program RKEREOCE4 and program
ZZREOCE4_NEW_470 stored on sapserv3 is that in the standard program, the
unused 'CE4<operating concern>_FLAG' entries are deactivated on the basis of
unused account assignment numbers ('CE4<operating
concern>_ACCT') in addition, or the deactivated 'CE4<operating concern>_FLAG'
entries are reactivated in program mode 'Reactivate
profitability segments'.
IMPORTANT: Do not use standard program RKEREOCE4 up to and
including Release 4.70 Support Package 13 because it is incorrect. Up to
and
including Release 4.70 Support Package 13, use the program that is stored
on sapserv3.

Archiving in 6.0 and above:

You may use archiving object COPAC_XXXX to archive the obsolete profitability
segments.