Setup tables

[Former Member]

Hi, please explain what are Setup table and what is the use of it.

Thanks and regards

Samran

[Former Member · Accepted solution]

HI,

SETUP TABLES

/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146

/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146

Tarak

[Former Member]

Hi,

Thanks for the Answer, I do have one more question what does over writing DSO means, is it up dating the records?

In info cube does updating of records happen or not.

Thanks and regards

Samran Pasha.

[Former Member]

Hi,

Your question is :-

"what does over writing DSO means, is it up dating the records?"

Yes it means updation of records in DSO .Suppose I have the below record in dso

Key: customer number

customer number___sales____quan

p001_____________34______2

The next record that comes in :-

customer number___sales____quan

p001_____________44________29

The previous record will be updated/overritten( since the key is same in the next record)

The final record will be:

customer number___sales____quan

p001_____________44________29

Hope this explains you the overwrite functionality in dso

Manish

[Former Member]

hi,

setup tables holds the historical data. LO Extractor does not allow to extract the data from application tables(vbak, vbap etc...) when you say full or initload in BW infopackage. when you are doing full or init bw extracts data from setup tables rather than application tables, so that we need to fill the setup tables(ex. oli7bw for 2LIS_11_VAHDR, oli8bw for 2LIS_11_VAITM ). its better practice to delete the setup tables to avoid the duplicate data.

SO MAKE SURE WHILE YOU ARE FILLING THE SETUP TABLES THE SETUP TABLES MUST BE EMPTY.

setup tables are kind of interface between the application tables and extractor.

when you say delta load in bw the data extracts from RSA7. you need to set the job in job control in LBWE transaction code.

plz assign points if helpful

regards

vadlamudi

[Former Member]

Hi Samran Pasha,

Setup tables are kind of interface between the extractor and application tables. These setup Tables are used for temporary data storage. LO extractor takes data from set up table while initialization and full upload by this hitting the application table for selection is avoided. As these tables are required only for full and init load, you can delete the data after loading in order to avoid duplicate data. Setup tables are filled with data from application tables. The setup tables sit on top of the actual application tables (i.e the OLTP tables storing transaction records). During the Setup run, these setup tables are filled. Normally it's a good practice to delete the existing setup tables before executing the setup runs so as to avoid duplicate records for the same selections.

The LO setup table run is used when you are extracting logistics data (eg MM/SD)

TCode on source system eg R/3 4.6c: SBIW --> settings for Application

Specific datasources --> Logistics Mapping extract structures -->Initialization --> filling the setup table  select application specific statistical data --> eg: purchasing

The structures (setup tables) filled can be see on SE16.

MC03UM0SETUP

MC03BF0SETUP

MC03BX0SETUP

Let me know if you need any further information.

Regards.