Introduction to COPA and COPA 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

Company: Infosys Technologies Limited Created on: 14 June, 2011

Author Bio
Pradnya Sawant -working as a Technology Analyst in Infosys Technologies Limited in SAP BI domain.

SAP COMMUNITY NETWORK © 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 1

........................................................ 8 Related Content ......................................................... 6 Design Guidelines to Handle COPA Realignment at BW side................................................................................................................................................sap......................................................................... .................................................................................................... 11 SAP COMMUNITY NETWORK © 2011 SAP AG SDN ............... 10 Disclaimer and Liability Notice ..............................................................uac................sap................................................................................................................................. 4 Realignment of COPA Data: ....................................................................................sap.....................com | BOC ............Introduction to COPA and COPA Realignment Table of Contents Introduction to COPA: ..........................com | BPX ................................ 3 Profitability Segment: . 5 Realignment Run at R/3: ................ 8 Effect of Realignment on COPA Delta Loads: .......................bpx.............................................................................................................. 3 Operating Concern: ...................sdn..sap....................................................................................................................... 8 To Overcome the COPA Realignment Effects on Delta Load ...................................................................com 2 ..............................................com | UAC .............................................................................................................................. 5 Some Possible Reasons for Realignment: ........... 3 Database Tables for COPA Model: ..........................................................................................boc................................................................. 3 Types of Profitability Analysis: .....

Data is stored at most detailed level.  Characteristic combination gives a level of analysis. Gross Sales.sdn. Additional Expenses. All planned data. Discounts.sap.Introduction to COPA and COPA Realignment Introduction to COPA:   The SAP module COPA . Types of Profitability Analysis:  Costing-based Profitability groups costs and revenues according to different value fields.e.  Account-based Profitability Analysis is s organized in accounts and using an account-based valuation approach.com | UAC . i.Controlling Profitability Analysis enables an organization to evaluate their profitability by strategic business units. You will get the Information of Invoice Numbers. Apart from the daily invoices. CE2XXXX: This Table contains Forecasted sales information. 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. different estimates are stored in this table. Product) & key Figures (Sales Qty.sap.com | BPX .com 3 . Invoices are captured in this table. CE3XXXX and CE4XXXX. Customer in this table. CE2XXXX. Net Sales) to analyze its profitability. Posting dates. Database Tables for COPA Model: The COPA model is based on four tables: CE1XXXX. Organizations can also submit their different forecasts for various organizational units for different time periods in COPA.com | BOC .sap. CE1XXXX: This Table contains Actual sales information. specific to organization.boc. The Costing Based COPA has been considered here. XXXX denotes Operating concern. Daily transactions. against which fields the sales information is to be analyzed. CE3XXXX & CE4XXXX: These two tables give information about Profitability Segment. SAP COMMUNITY NETWORK © 2011 SAP AG SDN . overhead costs and thus gives the organization actual profit details & helps them to analyze the trends & make better decisions.bpx. it captures the details of various discounts.  Operating Concern:  An organization identifies its operating concern which constitutes of a particular combination of Characteristics (such as Sales Org.sap. expenses. Customer.uac.

sap.sdn. Product Brand.sap. Profitability segment no 1 indicates Customer C1. The table CE4XXXX contains a field ‘Profitability Segment Number ‘as key which is assigned to a particular combination of characteristic values.bpx. Example: CE4XXXX Profitability Segment No 1 2 CE1XXXX Profitability Segment No 1 2 1 2 CE3XXXX Profitability Segment No 1 2 Customer C1 C2 Product P1 P1 Business Unit US NORTH US NORTH Posting Date 6/28/2009 6/28/2009 6/30/2009 6/30/2009 Gross Revenue 100 $ 100 $ 200 $ 250 $ Posting Period Jun-09 Jun-09 Gross Revenue 300 $ 350 $ SAP COMMUNITY NETWORK © 2011 SAP AG SDN . Brand – B1 Business Unit – US North. but the aggregated value of all transactions for a particular time period. Expenses are logged. CE3XXXX gives sales information for profitability Segments not at line item level as in CE1XXXX does. Discounts.Introduction to COPA and COPA Realignment Profitability Segment: Profitability Segment corresponds to one particular Market Segment of the organization against which Revenues. E.com 4 .sap. Product P1.boc.sap. In CE1XXXX Daily Sales are posted against a particular profitability Segment No.uac. it indicates a unique set of characteristics values like Product.g.com | BPX .com | BOC . All other tables have ‘Profitability segment No’ as one of the Keys.com | UAC . and Customer. Technically.

A company creates a new product P1. Now there are no Business Units named US NORTH & US SOUTH and all the customers which belong to US NORTH are aligned to NORTH East or West. North West. a Realignment Run is executed in R/3.bpx.com | BPX . Incorrect Master Data Assignments: Consider an example.sap. To reflect the new Business Units. Some transactions are logged against the product with incorrect product brand. When this mistake is realized. SAP COMMUNITY NETWORK © 2011 SAP AG SDN . say Fungicides. Initially the US business of the organization was divided into two Business Units US NORTH & USSOUTH. Change in the Organization Structure: Let’s consider an example.sap. the records which were posted in COPA will still have brand as Fungicides. An incorrect Brand has been assigned to this Product. Considering above example.sap. Data before realignment: CE4XXXX Profitability Segment No 1 2 Customer C1 C2 Product P1 P1 Business Unit US NORTH US NORTH Data after realignment: CE4XXXX Profitability Segment No 1 2 Customer C1 C2 Product P1 P1 Business Unit US NORTH WEST US NORTH EAST Some Possible Reasons for Realignment: 1.sap.com | UAC . and South East & South West. Now. As explained above. The customer Master data has been updated with this new Business Units.uac.boc. the Product master data is corrected. restructuring of organization takes place & each region is further divided into East & West. say the Brand has been changed from Fungicides to Insecticides.com 5 . After the realignment the Business Units will be updated in Profitability Segment (CE4XXXX) & all the transactions posted will now start referring to the new structure. 2.Introduction to COPA and COPA Realignment Realignment of COPA Data: Realignment of COPA Data indicates change in the characteristic combination set in profitability Segment. But the records which were posted previously in COPA will still have Business Units as US NORTH & US SOUTH.sdn.com | BOC . The US business is divided into four Business Units North East.

com 6 . Some Organizational characteristics are highlighted. In R/3. Conversion Rule A conversion rule defines the changes to be done for different characteristics during realignment run.    Derive characteristic again – This table should contain all the characteristics which are to be derived again based on the changed Master Data. Read as Posted – Displays data which as per original postings (Before Realignment) Read acc to current structure . these characteristics cannot be used for realignment to ensure the consistency. Realignment run consists of one or more realignment requests. Replace with fixed value – The characteristic is replaced by the fixed value provided.uac.boc.sap.sap. Go to Transcation KEND. Example – A particular product Number or business area. Selection Criteria The selection criteria help to define the data set on which conversion rule will be applied.sap. Do not change – This contains the list of characteristics which are not required to be changed.Create a new reallignment run & reallignment Request.sap. if you execute the transaction KE24 (To display actual line items).Displays realigned data.com | UAC . Realignment Run at R/3: Transaction KEND is used to create realignment run in SAP R/3. Realignment Run is executed in R/3. A realignment request consists of a set of selection criteria and a conversion rule.Introduction to COPA and COPA Realignment To correct this.. One of the following changes can be done. there are two options available Under ‘Mode of Access’.com | BOC . SAP COMMUNITY NETWORK © 2011 SAP AG SDN .sdn. Steps: 1. To maintain the data integrity the original line items posted before realignment are also maintained.com | BPX .bpx.

sap.com | BPX . Save & Schedule the Realignment Run.boc.sdn.com | BOC .com | UAC . Provide selection crieteria 3. SAP COMMUNITY NETWORK © 2011 SAP AG SDN .sap.com 7 . Define Conversion Rule 4.sap.Introduction to COPA and COPA Realignment 2.sap.uac.bpx.

In the example considered above it will be ‘Customer’ Then. SAP COMMUNITY NETWORK © 2011 SAP AG SDN . By doing this we can get the sales information both before & after realignment. With the error message as ‘Delta Update is no longer possible due to Realignment in the Source System’.     By Default this flag is not set (empty) for the COPA DataSource. we need to use the table ‘TKEBWL .sdn.     Effect of Realignment on COPA Delta Loads:   When the COPA realignment happens in the source system delta load fails in BW. To Overcome the COPA Realignment Effects on Delta Load  To overcome this problem and get the delta records even after realignment.Without Consistency Check’. This can be achieved by updating Customer Master Data.com | BPX . Instead of storing Business Unit directly in the Info cube/DSO.bpx.sap. Such a mechanism to align all the transactional COPA data records against the updated Profitability segment is not available in BW.uac.Introduction to COPA and COPA Realignment Design Guidelines to Handle COPA Realignment at BW side. this flag needs to be set. This flag cannot be set manually in the source system.    As mentioned above.In the example considered above it will be ‘Business Unit’ Now.CO-PA Connection to SAP BW: InfoSources ‘  The table TKEBWL contains a flag called ‘FLAG DIRTY . To set this flag for the COPA DataSource. the entries in the profitability segment are updated.com 8 . whenever the COPA data is realigned.com | UAC .boc. So each record in the transactional data will be aligned against the current Business Unit of the corresponding Customer. To achieve this at BW side follow the below steps:    Identify the fields in the Profitability Segment which do not undergo frequent realignments.sap.sap.com | BOC . Maintain the latest Business unit for every customer. . we need to write a program. identify the fields which undergo frequent realignments.sap. In order to ensure that delta records continue to come in spite of the realignment. make Customer a master data object with a Navigational attribute ‘Business Unit’. no further records are updated in the delta queue. . use it as a Navigational Attribute of Customer. So there will be a validity period assigned for each Business Unit. We can also make Customer as Time Dependent Master Data.

MESSAGE I000 (ZCO_COPA).com | BOC .sap.sap.sap.sap. and then the realignment happens. You would not have to reinitialize the DataSource.sdn. ** Message indicating Flag is Set ***     Once you run the program.com | UAC . the deltas would start flowing in.boc.bpx.Introduction to COPA and COPA Realignment  Code Snippet REPORT COPA_FLAGSET TABLES: TKEBWL.sap. So even those delta records which are missed due to the load failures would come in. These records will contain all deltas since the last successful delta load.sap.uac. UPDATE TKEBWL SET flag_dirty = 'X'.com/sap/support/notes/400576  If the COPA Datasource is enhanced. You need to follow the same procedure mentioned above to continue the deltas flowing in. and the FLAG DIRTY indicator is set.com 9 . If this flag is set. then also the FLAG_DIRTY indicator is reset.com/sap/support/notes/696936 https://service. then deltas would continue to come in without any issue Link to Related SAP Notes: https://service.com | BPX . SAP COMMUNITY NETWORK © 2011 SAP AG SDN .

bpx.sap.sap. visit the EDW homepage SAP COMMUNITY NETWORK © 2011 SAP AG SDN .Introduction to COPA and COPA Realignment Related Content http://help.sdn.com | UAC .com/ http://www.com For more information.sap.uac.boc.sap.com | BOC .sap.sap.sap.sdn.com 10 .com | BPX .com/irj/sdn service.

You agree that you will not hold.com | BPX .boc.uac.sdn. SAP will not be held liable for any damages caused by using or misusing the information.Introduction to COPA and COPA Realignment Disclaimer and Liability Notice This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP.com 11 . SAP COMMUNITY NETWORK © 2011 SAP AG SDN .com | BOC . code or methods suggested in this document.sap.sap. or seek to hold. SAP responsible or liable with respect to the content of this document. Changes made based on this information are not supported and can be overwritten during an upgrade.com | UAC . and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample.sap. including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP.bpx.sap.

Sign up to vote on this title
UsefulNot useful