CO-PA DATASOURCE CO-PA stands for Cost & Profitability Analysis It is a module under the CO Application Component.

nt. It provides accounting data for creating management reports BASIC OBJECTS IN CO-PA 1. Characteristics levels on which you need a CO-PA Report e.g. Region / Division 2. Characteristic Values values that can be assumed by a CHAR e.g. SDiv, WReg 3. Profitability Segment combination of char values/organizational data e.g. 4. Value Fields are key figures Maximum Amt of Char in CO-PA Datasource 69 19 Fixed Characteristics 50 Additional Char. When you create a CO-PA datasource on operating concern level the profitability segment will be the operating concern. MODULES INTEGRATED IN CO-PA SD Billing Doc FI Posting to a GL Account CO-PC Product Costing CO-OM General Cost Controlling cost centers, orders, processes CO-PA ORGANIZATION STRUCTURE Operating Concern Is the main entity in an Organization that makes decision for entire org e.g. GM CO Area Profit Center PC1 / PC2 entity that handles all profits occurring in an org. PC receives Company Code Pontiac / Buick / Chevrolet Sister Concern (subdivision) of an Operating Concern Business Area (Entity within Comp Code) P (NY) / B (MA) C (RI) Geographical location in which a Company Code has its operations.

CO-PA DATABASE STRUCTURE The CO-PA DB structure is made up of 4 TABLES delivered by SAP in the CO-PA Tool. After a selection of fields has been made the data is generated tables based on the table. Segment level CE3 stores only value fields no time stamp equivalent to fact table in BW Segment Table CE4 contains only char values equivalent to dim table in BW. No time stamp. Actual Line Items CE1 contains detailed data at document/record/ transaction level Planned Line Items CE2 CE1 / CE2 both have time stamp. OTHER TERMINOLOGIES Profitability Segment Number it is equivalent to Dim id in BW. It links the segment table to the segment level through primary /foreign key relationship. Both CE3 and CE4 have profitability segment number Summarization Levels r equivalent to aggregates in BW. They r used to speed up access to data during reporting and they are updated at regular intervals (every day). Update is controlled by time stamp. Load method full /delta Time stamp determines which data has already been loaded into BW. A CO-PA Datasource can be defined at the Operating Concern level / Client level. All updates (full / delta) get their data from the line items table. Never specify very large period intervals. The system will crash because the memory is over loaded. Use FYEAR intervals instead. NAMING CONVENTION FOR CO-PA For Tables: <Table name><name of operating concern> For CO-PA Datasource

1_CO_PA_<SYS ID><CLIENT><Name of Operating Concern>

IMPORTANT TRANSACTION CODES FOR CO-PA DATA EXTRACTION KEQ3 For maintaining Characteristics for Segment level KE30 For create and running CO-PA reports in R/3 / ECC KEDV For maintaining Summarization levels KEB5 For simulating the initialization of the delta process KEB2 show detailed info about CO-PA datasource KE24 for editing the datasource and adding new fields Table KEB2 Shows no of records read and no of records transferred to BW CO-PA DATASOURCE TYPES COSTING BASED actual values ACCOUNT BASED means planning i.e. plan based RESTRICTIONS FOR DEFINING AN ACCOUNT BASED CO-PA DATASOURCE 1. Company Code BUKRS, CO Area KOKRS and Cost Element KSTAR are mandatory 2. datasource does not contain chars i.e. no chars available from the line items table 3. there is only 1 amount (in 3 currencies) and 1 quantity /quantity unit 4. there are no value fields or calculated key figures available 5. CO Area and PERIO must be selected as in the transfer structure 6. other restrictions apply for data load CO-PA DATASOURCE ENHANCEMENT / CO-PA REALIGNMENT While re-creating the data source use the same old name so that there won't be any changes in the BW side when you need to assign the data source to info-source. Just replicate the new data source in BW side and map the new field in info-source. CREATING A CO-PA DATASOURCE 1. Create Datasource 1. Go to TCode KEB0

2. Enter datasource name 3. Choose the operating concern 4. Choose the create function 5. Designate either account based or costing based 6. Choose the required fields o Costing Based Characteristics from segment level Characteristics from segment table Fields for unit of measure Characteristics from the line item Value fields Calculated key figures from the key figure scheme

o Account Based Characteristics from segment level Characteristics from segment table One unit of measure Record currency from the line item and key figures

2. Activate Business Content

Activate at least one part of the Business Content of CO-PA, in particular the InfoObjects of the InfoCubes CO-PA: Published Key Figures 0COPA_C01 CO-PA: Quick start (S_GO). 0COPA_C03

3. Replicate Datasource from Source System 4. Create Infosource Create Infosource if you are implementing 3.x dataflow For BI 7.0 you can migrate the datasource or use emulation concept

5. Map Datasource Fields to Infosource Fields / Transformation 6. Create InfoCube Using existing CO-PA cube as templates

7. Create Update Rules / Transformation 8. Initialize Delta Method 9. Create InfoPackage / DTP