CO-PA Data Source

The main entity for a Co-PA data source is "Operating Concern", which would be given by COPA Consultants.

Here, 2 types of operating concerns would be defined. We can check the Operating Concern structure in the transaction code: KER1/KEAS or KEA0(to create and to display).
1. Cost Based : Used for Product based industries.
2. Account Based: Used in service based industries.


The standard R/3 System contains the sample operating concern "S001". 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:

Type	Name	Description
Structure	CE0xxxx	logical line item structure
Table	CE1xxxx	actual line item table
Table	CE2xxxx	plan line item table
Table	CE3xxxx	segment level
Table	CE4xxxx	segment table
Table	CE4xxxx_KENC	realignments
Table	CE4xxxx_ACCT	account assignments
Table	CE4xxxx_FLAG	posted characteristics
Structure	CE5xxxx	logical segment level
Structure	CE7xxxx	internal help structure for                                                                                                              assessments
Structure	CE8xxxx	internal help structure for assessments

for Account based PA its extracted from

COPE-Actual line items
COEJ-plan line items
COSP COSS-summary table
CE4XXXX-segment table
 
In these names, "xxxx" stands for the name of the operating concern.
Creating CO-PA Data Source:

1. After getting the Operating Concern from the functional team, go to the tcode KEB0 or follow the below mentiond path in SBIW.


Data Transfer to the SAP Business Information Warehouse -> Settings for Application-Specific DataSources -> (PI)Profitability Analysis -> Create Transaction Data DataSource.

In the COPA DataSource for Transaction Data screen: 1_CO_PA%CL%ERK is automatically generated. Do not change anything. You can add additional characters.
Note: The name of copa data source always start with the numeric One. Here CL is your client number and ERK is your operating concern name.
Select Field Name for Partitioning (Eg, Ccode(BUKRS) for cost based Profit Centre(PRCTR) for account based).
In the transaction bar enter the tcode =INIT . 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.
a). For costing-based Profitability Analysis, select the value fields and calculated 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. The system checks that the units of measure relating to the value fields are also transferred.

Technical notes:
Along with the selected characteristics and value fields, the fiscal year variant and the record currency are also included in the replication so that the data in SAP BW can be interpreted correctly.


The technical field PALEDGER (currency type) in Profitability Analysis is encrypted as CURTYPE (currency type) and VALUTYP (valuation) during the transfer to SAP BW.


The plan/actual indicator (PLIKZ) is copied to SAP BW as value type (WRTTP).

2. 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.
3. On the DataSource: Customer version Edit screen:
      a. Select all possible checkboxes in column Selection.
      b. Choose Save.
4. In the information dialog box, choose Enter.
5. Then replicate the datasource in BW and generate the data flow.
6. To maintain the deltas, maintain the time stamp in KEB2/KEB5.

CO-PA Datasource Enhancement:

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:

1) Add the fields to the operating concern. So that the required field is visible in CE1XXXX table and other concerned tables CE2XXXX, CE3XXXX etc.

2) After you have enhanced the operating concern then you are ready to add it to the CO-PA data source. Since CO-PA is a regenerating application you can't add the field directly to the CO-PA data source. You need to delete the data source and then need to re-create using KEB2 transaction.

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. 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 the fields from 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. Reference OSS note: 852443

In the BW System: 

1. Check RSA7 on your R3 to see if there is any delta queue for COPA. (just to see, sometimes there is nothing here for the datasource, sometimes there is)

2. On BW go to SE16 and open the table RSSDLINIT

3. Find the line(s) corresponding to the problem datasource.

4. You can check the load status in RSRQ using the RNR from the table 

5. Delete the line(s) in question from RSSDLINIT table 

6. Now you will be able to open the infopackage. So now you can ReInit. But before you try to ReInit .... 

7. In the infopackage go to the 'Scheduler' menu > 'Initialization options for the source system' and delete the existing INIT (if one is listed)

•