Professional Documents
Culture Documents
Realignment
Applies to:
SAP BI Consultants & Developers working on COPA Data Model. For more information, visit the EDW
homepage
Summary
This document gives a brief introduction of SAP COPA module & underline database tables. It covers
realignment of COPA Data and its impact on BW delta loads & way to correct that. This document also
provides information about steps to create Realignment run at R/3 side & few Design Guidelines to handle
COPA Realignment in BW .
Author:
Pradnya Sawant
Author Bio
Pradnya Sawant -working as a Technology Analyst in Infosys Technologies Limited in SAP BI domain.
Table of Contents
Introduction to COPA: ......................................................................................................................................... 3
Operating Concern: ......................................................................................................................................... 3
Types of Profitability Analysis: ........................................................................................................................ 3
Database Tables for COPA Model: ................................................................................................................. 3
Profitability Segment: ...................................................................................................................................... 4
Realignment of COPA Data: ............................................................................................................................... 5
Some Possible Reasons for Realignment: ..................................................................................................... 5
Realignment Run at R/3: .................................................................................................................................... 6
Design Guidelines to Handle COPA Realignment at BW side. .......................................................................... 8
Effect of Realignment on COPA Delta Loads: .................................................................................................... 8
To Overcome the COPA Realignment Effects on Delta Load ........................................................................ 8
Related Content ................................................................................................................................................ 10
Disclaimer and Liability Notice .......................................................................................................................... 11
Introduction to COPA:
The SAP module COPA - Controlling Profitability Analysis enables an organization to evaluate their
profitability by strategic business units.
Apart from the daily invoices, it captures the details of various discounts, expenses, overhead costs
and thus gives the organization actual profit details & helps them to analyze the trends & make better
decisions.
Organizations can also submit their different forecasts for various organizational units for different
time periods in COPA. This helps the organization to compare the forecasts & actual sales done so
that the performance of different business units can be analyzed and corrective actions can be
taken.
Operating Concern:
An organization identifies its operating concern which constitutes of a particular combination of
Characteristics (such as Sales Org, Customer, Product) & key Figures (Sales Qty, Gross Sales,
Discounts, Additional Expenses, Net Sales) to analyze its profitability.
Characteristic combination gives a level of analysis, i.e. against which fields the sales information is
to be analyzed.
Types of Profitability Analysis:
Costing-based Profitability groups costs and revenues according to different value fields.
Account-based Profitability Analysis is s organized in accounts and using an account-based
valuation approach.
The Costing Based COPA has been considered here.
Database Tables for COPA Model:
The COPA model is based on four tables: CE1XXXX, CE2XXXX, CE3XXXX and CE4XXXX.
XXXX denotes Operating concern, specific to organization.
CE1XXXX:
This Table contains Actual sales information. Daily transactions, Invoices are captured in this table. Data is
stored at most detailed level.
You will get the Information of Invoice Numbers, Posting dates, Customer in this table.
CE2XXXX:
This Table contains Forecasted sales information. All planned data, different estimates are stored in this
table.
Profitability Segment:
Profitability Segment corresponds to one particular Market Segment of the organization against which
Revenues, Discounts, Expenses are logged.
Technically, it indicates a unique set of characteristics values like Product, Product Brand, and Customer.
The table CE4XXXX contains a field Profitability Segment Number as key which is assigned to a particular
combination of characteristic values.
E.g. Profitability segment no 1 indicates Customer C1, Product P1, Brand B1 Business Unit US North.
All other tables have Profitability segment No as one of the Keys.
In CE1XXXX Daily Sales are posted against a particular profitability Segment No.
CE3XXXX gives sales information for profitability Segments not at line item level as in CE1XXXX does, but
the aggregated value of all transactions for a particular time period.
Example:
CE4XXXX
Profitability Segment No
Customer
Product
Business Unit
C1
P1
US NORTH
C2
P1
US NORTH
Profitability Segment No
Posting Date
Gross Revenue
6/28/2009
100 $
6/28/2009
100 $
6/30/2009
200 $
6/30/2009
250 $
Profitability Segment No
Posting Period
Gross Revenue
Jun-09
300 $
Jun-09
350 $
CE1XXXX
CE3XXXX
Profitability Segment No
Customer
Product
Business Unit
C1
P1
US NORTH
C2
P1
US NORTH
Profitability Segment No
Customer
Product
Business Unit
C1
P1
US NORTH WEST
C2
P1
US NORTH EAST
Read as Posted Displays data which as per original postings (Before Realignment)
Derive characteristic again This table should contain all the characteristics which are to be derived
again based on the changed Master Data.
Do not change This contains the list of characteristics which are not required to be changed. Some
Organizational characteristics are highlighted; these characteristics cannot be used for realignment
to ensure the consistency.
Replace with fixed value The characteristic is replaced by the fixed value provided.
Steps:
1. Go to Transcation KEND.Create a new reallignment run & reallignment Request.
As mentioned above, whenever the COPA data is realigned, the entries in the profitability segment
are updated.
Such a mechanism to align all the transactional COPA data records against the updated Profitability
segment is not available in BW.
To achieve this at BW side follow the below steps:
Identify the fields in the Profitability Segment which do not undergo frequent realignments.
- In the example considered above it will be Customer
Now, make Customer a master data object with a Navigational attribute Business Unit.
Maintain the latest Business unit for every customer. This can be achieved by updating
Customer Master Data.
Instead of storing Business Unit directly in the Info cube/DSO, use it as a Navigational
Attribute of Customer.
So each record in the transactional data will be aligned against the current Business Unit of
the corresponding Customer.
We can also make Customer as Time Dependent Master Data. So there will be a validity
period assigned for each Business Unit.
By doing this we can get the sales information both before & after realignment.
When the COPA realignment happens in the source system delta load fails in BW.
With the error message as Delta Update is no longer possible due to Realignment in the Source
System; no further records are updated in the delta queue.
By Default this flag is not set (empty) for the COPA DataSource.
In order to ensure that delta records continue to come in spite of the realignment, this flag needs to
be set.
This flag cannot be set manually in the source system.
To set this flag for the COPA DataSource, we need to write a program.
Code Snippet
REPORT COPA_FLAGSET
TABLES: TKEBWL.
UPDATE TKEBWL SET flag_dirty = 'X'.
MESSAGE I000 (ZCO_COPA). ** Message indicating Flag is Set ***
Once you run the program, and the FLAG DIRTY indicator is set, the deltas would start flowing in.
These records will contain all deltas since the last successful delta load. So even those delta records
which are missed due to the load failures would come in.
You would not have to reinitialize the DataSource.
If this flag is set, and then the realignment happens, then deltas would continue to come in without
any issue
Link to Related SAP Notes:
https://service.sap.com/sap/support/notes/696936
https://service.sap.com/sap/support/notes/400576
If the COPA Datasource is enhanced, then also the FLAG_DIRTY indicator is reset. You need to
follow the same procedure mentioned above to continue the deltas flowing in.
Related Content
http://help.sap.com/
http://www.sdn.sap.com/irj/sdn
service.sap.com
For more information, visit the EDW homepage