Introduction to COPA and COPA Realignment

Transcription

1 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 AG 1

2 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 Effect of Realignment on COPA Delta Loads:... 8 To Overcome the COPA Realignment Effects on Delta Load... 8 Related Content Disclaimer and Liability Notice SAP AG 2

3 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. CE3XXXX & CE4XXXX: These two tables give information about Profitability Segment SAP AG 3

4 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 1 C1 P1 US NORTH 2 C2 P1 US NORTH CE1XXXX Profitability Segment No Posting Date Gross Revenue 1 6/28/ $ 2 6/28/ $ 1 6/30/ $ 2 6/30/ $ CE3XXXX Profitability Segment No Posting Period Gross Revenue 1 Jun $ 2 Jun $ 2011 SAP AG 4

5 Realignment of COPA Data: Realignment of COPA Data indicates change in the characteristic combination set in profitability Segment. Considering above example, Data before realignment: CE4XXXX Profitability Segment No Customer Product Business Unit 1 C1 P1 US NORTH 2 C2 P1 US NORTH Data after realignment: CE4XXXX Profitability Segment No Customer Product Business Unit 1 C1 P1 US NORTH WEST 2 C2 P1 US NORTH EAST Some Possible Reasons for Realignment: 1. Change in the Organization Structure: Let s consider an example. Initially the US business of the organization was divided into two Business Units US NORTH & US- SOUTH. Now, restructuring of organization takes place & each region is further divided into East & West. The US business is divided into four Business Units North East, North West, and South East & South West. 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. The customer Master data has been updated with this new Business Units. But the records which were posted previously in COPA will still have Business Units as US NORTH & US SOUTH. To reflect the new Business Units, a Realignment Run is executed in R/3. 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. Incorrect Master Data Assignments: Consider an example, A company creates a new product P1. An incorrect Brand has been assigned to this Product, say Fungicides. Some transactions are logged against the product with incorrect product brand. When this mistake is realized, the Product master data is corrected, say the Brand has been changed from Fungicides to Insecticides. As explained above, the records which were posted in COPA will still have brand as Fungicides SAP AG 5

6 To correct this, Realignment Run is executed in R/3. To maintain the data integrity the original line items posted before realignment are also maintained. In R/3, if you execute the transaction KE24 (To display actual line items), there are two options available Under Mode of Access. - Read as Posted Displays data which as per original postings (Before Realignment) - Read acc to current structure - Displays realigned data. Realignment Run at R/3: Transaction KEND is used to create realignment run in SAP R/3. Realignment run consists of one or more realignment requests. A realignment request consists of a set of selection criteria and a conversion rule, Selection Criteria The selection criteria help to define the data set on which conversion rule will be applied. Example A particular product Number or business area.. Conversion Rule A conversion rule defines the changes to be done for different characteristics during realignment run. One of the following changes can be done. 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 SAP AG 6

7 2. Provide selection crieteria 3. Define Conversion Rule 4. Save & Schedule the Realignment Run SAP AG 7

8 Design Guidelines to Handle COPA Realignment at BW side. 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 Then, identify the fields which undergo frequent realignments. - In the example considered above it will be Business Unit 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. Effect of Realignment on COPA Delta Loads: 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. To Overcome the COPA Realignment Effects on Delta Load To overcome this problem and get the delta records even after realignment, we need to use the table TKEBWL - CO-PA Connection to SAP BW: InfoSources The table TKEBWL contains a flag called FLAG DIRTY - Without Consistency Check. 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 SAP AG 8

9 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: 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 SAP AG 9

10 Related Content service.sap.com For more information, visit the EDW homepage 2011 SAP AG 10

11 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. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, 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, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document SAP AG 11