char

KeyFure

: 1.
" n5 f4 `6 h8 m- B

query
8 C4 V1 K% m1 l7 R1 X5 W# {

2. compounding,) \/ _0 _8 R6 i: v7 k
7 j& k' ]! N& ~& U8 E2 n1 R

item head / G0 u$ J1 H5 t7 e

3. cube & \7 Z3 S

}, E4 H5 p

16 4 Cube request id add request with zero 0 compression of the cube

/ v" ^; d- I; q, l [

4. 1 sid SAP 2 20% cube 1 2 ) I6 p- ~- l& ]6

j7 V& M' {" M I

3 4 Outline Sparse/Dense Partition DataLoad File outline 1..n OLAP

) @& t+ P! i' F% Q4 x

5. Multiprovider infoset Multi Provider InfoSet virtual Provider MultiProvider InfoSet InfoProvider l . InfoCubes l . DataStoreobjects l . InfoObjects l . InfoSets l . Aggregation levels (slices of aInfoCube to support BI Integrated Planning) MultiProvider InfoSet InfoProvider multiprovider union infoset inner joinleftout join . T' _* n2 h$ n 6. BW , z" Q6 Q x! f4 L# P/ W: v1 R currency translation type query key figure query currency translation type TcodeRSCUR create currency translation type Report Query
; X, o) O d6 ]

WHD Actual Forecast Actual

Forecast 2 MM 1. Currency ConversionType

COPA Extraction Steps

The below are the command steps and explanation. COPA Extraction -steps R/3 System 1. KEB0 2. Select Datasource 1_CO_PA_CCA 3. Select Field Name for Partitioning (Eg, Ccode) 4. Initialise 5. Select characteristics & Value Fields & Key Figures 6. Select Development Class/Local Object 7. Workbench Request 8. Edit your Data Source to Select/Hide Fields 9. Extract Checker at RSA3 & Extract 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 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 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)
COPA datasource enhancement for PAOBJNR
I have a requirement where in I need to extract the PAOBJNR (profitability segment no) field from the COPA tables (CE1XXXX, C4XXXX). This field is meant for internal COPA use only and so it is not available for extraction. But still i need to get it to BW side........

I also tried searching for this on SDN but cud not find anything useful. If someone has already worked on this kind of requirement then please let me noe...

Regards

Gaurav

Correct Answer by Daniel Purucker on Mar 3, 2009 3:17 PM

Hi,

writing any code or user exit won't be necessary. Actually enhance the COPA extractor for this field is a fairly easy task Just do the following:

a) Add an append to the COPA Extract Structure

b) Add a field named: PAOBJNR (Component type RKEOBJNR)

c) In the datasource mark this field as "Selection"

That's it.

See the answer in context

1765 Views

o
Average User Rating (0 ratings)

176
Topics: Enterprise Data Warehousing/Business Warehouse

Re: COPA datasource enhancement for PAOBJNR

Fernando Ariel Angueira Feb 27, 2009 7:56 PM (in response to Gaurav Raka)

Have you tried to append this field to the extractor and filling it with a User Exit?

Fer...

o o

Report Abuse Like (0)

Re: COPA datasource enhancement for PAOBJNR

Koundinya Karanam Feb 27, 2009 8:01 PM (in response to Gaurav Raka)

Hi Gaurav,

Check the below link it might be useful to you in appending the field to the extract structure and filling it with user exit.

https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/901c6d37-ebd8-2b10-bb97-b2b885f6794b

Regards,

KK.

o o o

Report Abuse Like (0)

Re: COPA datasource enhancement for PAOBJNR

Gaurav Raka Mar 3, 2009 4:47 AM (in response to Koundinya Karanam)

Hi

Writing a code wont be a simple task as PAOBJNR is a key field in all the COPA tables and we need to extract tat field only....

The COPA datasource uses a std func mod RKE_BIW_GET_DATA_API to extract data. PAOBJNR being a ADMIN Field, the func mod does not extract data for PAOBJNR.

Making a slight change to this func mod could have resolved the issue but this being a std SAP func mod we cant even do tat...

Regards

Gaurav

Report Abuse Like (0)

Correct AnswerRe: COPA datasource enhancement for PAOBJNR

Daniel Purucker Mar 3, 2009 3:17 PM (in response to Gaurav Raka)

Hi,

writing any code or user exit won't be necessary. Actually enhance the COPA extractor for this field is a fairly easy task Just do the following:

a) Add an append to the COPA Extract Structure

b) Add a field named: PAOBJNR (Component type RKEOBJNR)

c) In the datasource mark this field as "Selection"

That's it.

Report Abuse Like (0)

Re: COPA datasource enhancement for PAOBJNR

Gaurav Raka Mar 4, 2009 8:05 AM (in response to Daniel Purucker)

Hi Daniel

I tried doing tat as well...but its not working for me....

did u work on a similar senario.....n did tat solution work for you??

Thanks

Gaurav

Report Abuse Like (0)

Re: COPA datasource enhancement for PAOBJNR

Bharath Kumar K Mar 4, 2009 8:49 AM (in response to Gaurav Raka)

Hi Gaurav,

CO-PA datasource functionality doesnot allow you to enhance it. You cannot enhance any CO-PA datasoure by appending any field to it.

If the field you mentioned exists in the four COPA tables then you have the following two ways to bring it into BW.

1) Create another CO-PA datasource in KEB0 and select the desired field and stage that into BW or

2) Delete the existing CO-PA datasource and create it again with the same technical name and then select all the fields including the new field and replicate that in BW. With this option there is no need to delete anything from BW side. Just you need to replicate the datasource and do a data load.

Regards,

Bharat

Report Abuse Like (0)

Re: COPA datasource enhancement for PAOBJNR

Daniel Purucker Mar 4, 2009 10:32 AM (in response to Gaurav Raka)

Hi Gaurav,

try selectingg a value range for PAOBJNR in the InfoPackage for Extracting COPA (eg. 00000 to XXXX).

I did it this way myself and it worked.

br,

Daniel

Report Abuse Like (0)

Re: COPA datasource enhancement for PAOBJNR

Gaurav Raka Mar 4, 2009 12:54 PM (in response to Daniel Purucker)

Hi Daniel

Thanks a lot for the help.......

Regards

Gaurav

Report Abuse Like (0)

Re: COPA datasource enhancement for PAOBJNR

Patrick Yolabo Oct 15, 2011 9:51 AM (in response to Daniel Purucker)

Hi Daniel,

you meant to say for all those missing fields which exist in the CE1XXX table and not in the datasource we only have to enhance the datsource by creating an append structure with those fields. And once that is done just do the selection for those fields in the infopackage?

Could you please explain why those fields are not shown?

Are we allow to enhance COPA datasource?

Thanks

Report Abuse Like (0)

Re: COPA datasource enhancement for PAOBJNR

Sathya Anumolu Oct 15, 2012 4:35 PM (in response to Patrick Yolabo)

COPA Datasource Enhancements possible.

add append structure, add fields to the data source.

write exit program or ZBWI_1_COPA_XXX, XXX = data Source name and write normal code to populate the fields from CE1EU00.

Thanks