Why at all setup table

There is no really good document on why different SAP applications use different extraction methods. Basically it goes down to the R/3 database design. CO and FI are both document driven and store line items with timestamps. This makes it easy to implement a delta based on the timestamp but makes it vulnerable to database deletes by ABAP. Logistics uses no clear line item concept but different tables that store the current status of the different LO objects. To enable a clear reporting the LIS was invented and this was the best source for BW extraction.

Best regards

Dirk

Hello Sriram,

not a direct answer to your question but there is a document, that might be helpfull. There is an FAQ-Document 'Around SAP BW DeltaQueue (RSA7)' that explains some details. You can find it in the BW-Area under 'Services & Implementation'. It also directs you to some OSS-Notes that give you some good details.

hth

Stefanie Schaaf

You have to remember that FI and similar extractors suffer from the fact that they provide only after images necessitating an ODS layer in BW. They also generally require a safety interval therefore precluding extraction of current data (e.g. make a J/E in FI and pull it in right away). LO extractors are V1 or V3 updates and not "after-the-fact" pulls from the base R/3 tables. Even with FI extractors, the requirement for "quiet time" on R/3 does not go away, although there are workarounds to this in FI and LO. The LO set-up tables can be deleted after data validation in BW. They are cluster tables storing history in an optimal manner. Finally, if your R/3 and BW have simultaneous go-lives, you do not need the set-up table.