Generic extractor on Table EINE & EORD

[Former Member]

Hello experts,

Client requirement is to bring in Purchase info record purchase org data into BW.

Basically we want to get all the data from EINE table (tcode - ME1M & ME13) and from table EORD into our BW environment. I went through the standard BW datasources and did some research but did not found any standard datasources which can extract info record's purchase org information and the purchasing sourcing list information.

There is the attribute datasource for Info record but it can only give us General data information of Purchasing info record.

So we are thinking of building an generic extractor on table EINE and EORD. so my question, will it be fine to just create a Table datasource on table EINE & EORD to pull the information into BW via full loads or it is better to go with function module generic extractor. Our system has only ard 55k info record entries in EINE and around 4740 records in EORD.

Any inputs/suggestions will be very valuable and highly appreciated....

Regards,

Sunny.

Edited by: Sunny Deshmukh on Apr 9, 2010 12:45 AM

[Former Member]

55k + 4k data is quite small. It is alright to create generic extractor with View(Join) Table and full loads.

[Former Member]

Raymond,

Thank you for your reply. I researched abt these a bit on sdn and came accross that experts adviced to create custom datasource using Function module, so thats why I am confused whether to go with function module route or by generic table datasource.

Hi Experts,

What do you think - should I just add the fields of EINE as attributes of the info record by having Purchase org,Purchase info record category, plant as compounded characteristics or should I just create a ODS with Info rec, Pur Org, Inf rec category and plant as the key and then create a Infoset on top of the info rec info object and this ODS for reporting purposes ?

I just want to evaluate the best way to provide this reporting solution.

Any help in this regards will be highly appreciate in SDN way....

Thanks & regards,

Sunny.

[Former Member]

Thank you for your reply. I researched abt these a bit on sdn and came accross that experts adviced to create custom datasource using Function module, so thats why I am confused whether to go with function module route or by generic table datasource.

This is usually done if the delta mechnism for these tables is based on multiple values like created + modified dates etc - to handle delta mechanisms that are more than one field specific you might have to go the FM Extractor way - else you can do the same with a view...

[Former Member]

Hi Arun,

Thanks a lot for your inputs on this. But can you please guide me as to whether I should add the fields of the table EINE as attributes of the standard 0INFO_REC info-object with compounding on Pur org, plant, info rec category OR should I create an ODS with Info rec, info rec category, pur org & plant as the key and then build a Info-set on top of this ODS & 0INFO_REC info-object for the reporting purposes.

I want to evaluate the best practises in providing the reporting solution for this.

Thanks & regards,

Sunny.