Generic Extractors with different ways

Will try to start the answers..

1) We use when there is a scenario where the total table ( may be few fileds) has to be processed and pulled into

BW with out much or any caliculations..

2) The infoset and FM are just little opposite where u need complex routines and joining several logics..

regards,

Hari

hi kishan,

look at this weblog:

/people/sap.user72/blog/2005/09/05/sap-bw-and-business-content-datasources-in-pursuit-of-the-origins

regards

sham'm

Hi Kishan,

Which option to go for to create a Generic Delta is solely depends on the requirement and study done to fullfil that need, however in case when we have a customer defined table and the relevant datasource is not available, go for the first option by using Tables/Views.

In other cases, when it comes to the complex scenarios, we go for Function Modules/Infoset Query.

Hope it helps!!!!

Amit

we can greate generic datasources for customer defined tables as well as when we need to extract data from the existing r/3 tables.

when the client wants his own table to be build and he wants to extract data from that table go for generic.

when we need to extract data from r/3 table ex. purchase requistions are stored in eban table if you want that data in bw create a generic datasource based on table and extract data.

If you want to extract data from two or more r/3 tables then go for view.

infoset is a semantic view of data source and it is not a physical data target. infoset is a view but allows outer joins between tables. in that scenario go for infoset.

when some function modules are retrieving data in r/3 then u can use those function modules to retreive data in BW.