Basically, COPA will be used to evaluate the “Profitability” of an organization . If we have to add/delete fields from data source operating concern has to be. SAP copa datasource tcodes (Transaction Codes). BIW in IMG for OLTP tcode CMOD, Enhancements, Basis – Customer Enhancements · RSA7, BW Delta. Cost based is done mainly in manufacturing and production Industry.. Account based is done in Service Industries COPA datasources have 3.

Author: Voodoojas Tauzragore
Country: Libya
Language: English (Spanish)
Genre: Relationship
Published (Last): 17 December 2004
Pages: 177
PDF File Size: 10.59 Mb
ePub File Size: 20.14 Mb
ISBN: 992-5-59145-550-8
Downloads: 56418
Price: Free* [*Free Regsitration Required]
Uploader: Mezirisar

COPA Extraction Steps

Here, 2 types of operating concerns would be defined. We can check the Operating Concern structure in the transaction code: Used for Product based industries. Used in service based industries.

You can copy this operating concern to create your own operating concern. When you activate the data structures of your operating concern, the system creates the following objects in the ABAP Dictionary: Do not change anything. You can add additional characters. The name of copa data source always start with the numeric One. Now, you could be able to select the required fields. Select all Characteristics from the segment level and Select all Value Fields.


Choose InfoCatalog from the application toolbar.

For costing-based Profitability Analysis, select the value fields and datasoyrce key figures that are to be included in the DataSource. It is useful to include all the value fields of the operating concern. These value fields are already selected but you can deactivate them if necessary.

SAP BW COPA Extraction in detail, Delta Mechanisms and few challenges faced during Implementation

The system checks that the units of measure relating to the value fields are also transferred. Along with the selected characteristics and value fields, the fiscal year variant and the record currency are also included enhxncement the replication so that the data in SAP BW can be interpreted correctly. The Create Object Directory Entry dialog box is displayed requesting the user to enter a development class.

Enter a development class in the customer namespace and choose Save or choose Local object. Customer version Edit screen: Select all possible checkboxes in column Selection. In the information dialog box, choose Enter.

Then replicate the datasource in BW and generate the data flow. You cannot change a DataSource once created. You can, however, delete it and then create a DataSource with the same name but with different technical properties. You should not upload metadata between these two steps.


In the ECC System: You need to delete enhancemenr data source and then need to re-create using KEB2 transaction. Just replicate the new data source in BW side and map the new field in info-source. 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.

I would personally suggest keep the same old data source name as before. If you are adding datasourde fields enhzncement the same “Operating concern” then goto KE24 and edit the dataaource and add your fields. 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.

In the BW System: Find the line s corresponding to the problem datasource. Now you will be able to open the infopackage. So now you can ReInit.

But before you try to ReInit Posted by Rakesh Dama at 8: Newer Post Older Post Home.