cancel
Showing results for 
Search instead for 
Did you mean: 

COPA datasource enhancement

Former Member
0 Kudos

I need to add two more fields to the extract structure namely the USNAM and HZDAT both of which lie in the underlying CE1-XXXX table itself. I did the append structure with the ZZ* fields , but rsa3 still dosent whoe these fields. Is there something im missing or is there a way in COPA to bring these fields in the Datasource without appending the structure?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

this fields are part of the datasource for CE1xxxx (xxxx=operating concern), add them to your infosource

/manfred

Former Member
0 Kudos

how do i see these fields in the datasource, COPA does not show these fields while creating a DS in KEB0. how do i add them to my infosource

Former Member
0 Kudos

ups,

you are correct, than I would try to add the fieldnames to the append structure with their original name (hoping the extractor does a move-corresponding), if it not help I'm afraid you have to expand the extractor itself.

/manfred

Former Member
0 Kudos

You <b>cannot</b> enhance a COPA datasource. You have to recreate a new one. Hope this helps.

I am not able to copy the link for this forum...but a brief search in the forums got me to the following post (Please note that the original author of the following text is Soumya Mishra).

Steps would be:-

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.

PS: For more info, please search in the fourms with key words COPA DATASOURCE ENHANCEMENT.

Good luck!

Former Member
0 Kudos

@manfred----- ill try giving the same field name and extracting, but im more concerned about the expanding part as ive tried expanding it and it dosent bring the fields.

@sudheer----the operating concern has the field and so the tables CE1-xxxx, ce2-xxx all have the fields in them, but im stuck because the datasource does show these fields for selection.

Former Member
0 Kudos

Hi, I think you ment transaction KEB0 to delete and recreate the DataSource. WIth KEB2 you are aible only to display Detailed Information about the DS, nothing more.

Cheers

Esteban

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Gokul,

Were you able to resolve the problem of adding the HZDAT field to the Datasource. I have the same problem i need to add HZDAT which is in the table CE1xxxx but not in the Datsource.

Let me know if you resolved it.

Thanks,

Vani.

Former Member
0 Kudos

Hello,

I'm having the same problem.

Did someone scucceded to bring HZDAT to the COPA datasource?

Thank you,

David

Former Member
0 Kudos

Had the issue today with HZDAT - here's what I did.

Did the config in KEB0 and generated the COPA datasource

Located and changed the extract structure for the COPA datasource using transaction SE11 (added a new field named HZDAT)

Changed function module(transaction SE37 - you'll need a key) RSA2_SYSTEMTYPE_GET and added the following lines just before the endfunction...

context

  • SAPI 30C SP7 [ot]

TRANSLATE e_systemtype TO UPPER CASE. "#EC TRANSLANG

insert the following lines

  • Usernamed access to core SAP func/BI

if sy-uname = 'WHOEVER'.

e_systemtype = 'SAP'.

endif.

Then using transaction RSA2 - changed datasource so the new field HZDAT to be selectable (changed from 3 to X)

Saved and tested..

/MiB