COPA Extraction Steps

The below are the command steps and explanation. COPA Extraction -steps R/3 System 1. 2. 3. 4. 5. 6. 7. 8. 9. BW 1. Replicate Data Source 2. Assign Info Source 3. Transfer all Data Source elements to Info Source 4. Activate Info Source 5. Create Cube on Infoprovider (Copy str from Infosource) 6. Go to Dimensions and create dimensions, Define & Assign 7. Check & Activate 8. Create Update Rules 9. Insert/Modify KF and write routines (const, formula, abap) 10. Activate 11. Create InfoPackage for Initialization 12. Maintain Infopackage 13. Under Update Tab Select Initialize delta on Infopackage 14. Schedule/Monitor 15. Create Another InfoPackage for Delta 16. Check on DELTA OptionPls r 17. Ready for Delta Load LIS, CO/PA, and FI/SL are Customer Generated Generic Extractors, and LO is BW Content Extractors. LIS is a cross application component LIS of SAP R/3 , which includes, Sales Information System, Purchasing Information System, Inventory Controlling.... Similarly CO/PA and FI/SL are used for specific Application Component of SAP R/3. CO/PA collects all the OLTP data for calculating contribution margins (sales, cost of sales, overhead costs). FI/SL collects all the OLTP data for financial accounting, special ledger
Page 1 of 2

KEB0 Select Datasource 1_CO_PA_CCA Select Field Name for Partitioning (Eg, Ccode) Initialise Select characteristics & Value Fields & Key Figures Select Development Class/Local Object Workbench Request Edit your Data Source to Select/Hide Fields Extract Checker at RSA3 & Extract

Reference OSS note: 852443 1.. In the infopackage go to the 'Scheduler' menu > 'Initialization options for the source system' and delete the existing INIT (if one is listed) *-. You need to delete the data source and then need to re-create using KEB2 transaction. Delete the line(s) in question from RSSDLINIT table 6. sometimes there is nothing here for the datasource. Since CO-PA is a regenerating application you can't add the field directly to the CO-PA data source.. You can check the load status in RSRQ using the RNR from the table 5. So now you can ReInit. On BW go to SE16 and open the table RSSDLINIT 3.Chand Page 2 of 2 . Find the line(s) corresponding to the problem datasource. (just to see. 4. If you are adding the fields from the same "Operating concern" then goto KE24 and edit the dataaource and add your fields. 3) 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. I would personally suggest keep the same old data source name as before.1) Add the fields to the operating concern. Check RSA7 on your R3 to see if there is any delta queue for COPA. CE3XXXX etc. 2) After you have enhanced the operating concern then you are ready to add it to the CO-PA data source.. However if you are adding fields outside the "Operating concern" then you need to append the extract structure and populate the fields in user exit using ABAP code. But before you try to ReInit . Just replicate the new data source in BW side and map the new field in info-source. So that the required field is visible in CE1XXXX table and other concerned tables CE2XXXX. sometimes there is) 2. If you re-create using a different name then you will be needing extra build efforts to take the data into BW through IS all the way top to IC. 7. Now you will be able to open the infopackage.