You are on page 1of 9


Title: PTP-BCD-Summarization Levels

Team / Area (SAP System PTR/CO Date: 07/10/2009


Document History:
Document Location
<< This is a snapshot of an on-line document. Paper copies are valid only on the day they are printed.
Please refer to the author / responsible team if you have any questions. >>

Revision History
Revision Revision Summary of Changes Revised By
Number Date
1 07/13/2009 Initial updates Saket Saraf
02/10/2009 Added details Sirshendu

<< The approval process for this document will be managed from within solution manager. >>

FS Enhancements V 1.0 Page 1 of 9
1. Prerequisites

Definition of PA operating concern along with characteristics

2. Dependencies
Characteristics obtain their values from other modules like OTC for invoicing information(sales order, qty,
value, customer etc), Data(material master), etc.

3. Configuration Rationale
3.1 Functional Requirements and Decisions from Blueprint and Detail Design
The summarization levels allow for better system performance when accessing the data
intensive COPA tables. The reason for creating the summarization levels for Keystone is
because the COGS postings in FI are to be made using data in COPA. This posting is to be
made at a company code/profit center level. If the regular line item tables will be accessed in
COPA this would cause the COGS program to cause system performance issues due to the
vast number of line items that need to be accessed from the table.

The summarization levels would create separate tables with data that is updated at a higher
level (company code/profit center), which could be accessed for making the updates rather
than using the regular tables.

At a periodic interval these summarization levels would have to be refreshed in order to have
the current data.

3.2 Configuration Details

The sequence of steps for defining summarization levels are as follows.

FS Enhancements V 1.0 Page 2 of 9
a. Defining the summarization level(give a number and description)
b. Defining the characteristics for the summarization level
c. Defining indexes for the summarization level(only if change required from

Go to transaction KEDV.

Click on the button New entries to give a name to the summarization level. This has to
be a numerical value. Also give a description.

Click on the back button to go to the previous screen as below.

FS Enhancements V 1.0 Page 3 of 9
Highlight the summarization level defined and then click on the magnifying glass for the
characteristics. This will show a list of characteristics.

Against each characteristic that you want to include in the summarization level, enter a
*. For Keystone, we have defined the characteristics :
Company Code, fiscal year, period, Controlling Area, Profit Center, plan/actual indicator,
version, record type, distribution channel as the characteristics to be included in the
summarization level.

FS Enhancements V 1.0 Page 4 of 9
Click on the back button.

Select the magnifying glass next to indexes. This would show the proposed indexes.
These can be modified to add new fields to existing indexes or define new indexes.

In Keystone, we are using the system defined indexes. The indexes that are defined for
Keystone are Company code, controlling area, profit center, version, record type and
plan/actual indicator.

FS Enhancements V 1.0 Page 5 of 9
Once the summarization levels have been defined, save the same.

Once saved the Hierarchy status is changed to active, without data

FS Enhancements V 1.0 Page 6 of 9
Note: In order to populate the summarization levels with data, periodically these
have to be refreshed using an update program. The transaction code for doing
the same is KEDU

Configuration for Del Monte Foods (DLM)

It is not decided whether DLM will use COGS Split enhancement for posting to FI. The summarization
levels are therefore not yet defined for DLM

FS Enhancements V 1.0 Page 7 of 9
4. Configuration Procedure

Transport Request # EE1K902854

Short Description PTR-CO-GL-APR10-NT-COPA Operating Concern Structures KE3I

T-Code Menu Path

SPRO IMG Controlling-->Profitability AnalysisToolsSummarization levelsDefine

Summarization levels


5. Supporting Documents
<<Include text or attach documentation for this configuration. For example, if you are configuring
company codes, attach an excel file listing those company codes and the corresponding details. Using
OLE objects will help keep this document concise. >>

FS Enhancements V 1.0 Page 8 of 9
6. Impact Areas
<<This section is optional. This section is used as a checklist during the realization phase to drive
communications and to ensure no upstream / downstream processes have been overlooked.>>

7. QA Checklist
<<This section isummarizes the minimum steps that the Configuration Lead should complete as part of
the QA review. It is not necessary to document anything in this area, the completion of the QA checklist
is documented by the status being changed to CONFIG_LEAD_APPROVED in Solution Manager>>
Ensure that related transaction has been unit tested and is documented in SolMan / UTP
(unit test plan) document
Each object included in transport is assigned to appropriate process in SolMan before it is
Ensure that all transports are released
Ensure that BCD is completed and accurate

Integration and Technical Lead assessment of cross integration impacts of configuration

FS Enhancements V 1.0 Page 9 of 9