Showing results for 
Search instead for 
Did you mean: 

what are setup tables and what are it signficance in lis

Former Member
0 Kudos

Hi all,

what are setup tables and what are it signficance in lis. is there any setup tables

in lo? Pls explain setup tables with an scenario.



Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

we have setup tables concept for only LO... not for LIS.

Hitory or Full Load or Initi with Data transfer will read from Setup tables.

Delta records will be read from Delta Queue.

Which seperates BW Extractors from SAP R/3 Application tables... and stores in Setup tables. i.e. data is not directly reading from base tablesi.e. VBAK, VBAP etc.

Nagesh Ganisetti.

  • Assign points if it helps.

Answers (5)

Answers (5)

Former Member
0 Kudos

Hi all,

Thanxs for the information. I have assigned points.



Active Contributor
0 Kudos

hi Hari,

the tcodes are OLI*BW


OLI1BW INVCO Stat. Setup: Material Movemts

OLI2BW INVCO Stat. Setup: Stor. Loc. Stocks

OLI3BW Reorg.PURCHIS BW Extract Structures

OLI4BW Reorg. PPIS Extract Structures

OLI6BW Recompilation Appl. 06 (Inv. Ver.)

OLI7BW Reorg. of VIS Extr. Struct.: Order

OLI8BW Reorg. VIS Extr. Str.: Delivery

OLI9BW Reorg. VIS Extr. Str.: Invoices

OLIABW Setup: BW agency business

OLIFBW Reorg. Rep. Manuf. Extr. Structs

OLIGBW Reconstruct GT: External TC

OLIIBW Reorg. of PM Info System for BW

OLIKBW Setup GTM: Position Management

OLILBW Setup GTM: Position Mngmt w. Network

OLIQBW QM Infosystem Reorganization for BW

OLISBW Reorg. of CS Info System for BW

OLIZBW INVCO Setup: Invoice Verification

hope this helps.

Former Member
0 Kudos

Hi ajay,

Is therey any transaction code for set up tables. I have assigned points.



Active Contributor
0 Kudos


Goto OLI*BW where * is your application component.

OLI7bw is for filling the sales order....

Document Data restriction

Archiving session

Sales Organization

Company code

Sales document

You can restrict the datas for the fiels given above.

Hope this helps..

Former Member
0 Kudos


Setup tables are kind of interface between the extractor and application tables. LO extractor takes data from set up table while initalization and full upload and 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 applcation 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 existing data in the application tables is in a sense copied to the setup tables, when you do the extraction you are not hitting the application tables.

When you are doing a fresh setup you want to delete the Setup tables before you fill them, since when they are loaded it is essentially an APPEND operation and unless you have a clean start (after deleting) you may end up with duplicate records.

ya every set up tables have standard structure 2_lis_(obj name)

from RSA3 transaction we can view the no of records avail for particular setup tables.

Former Member
0 Kudos

Hi Hari,

Set up tables is to store and pull the historic data in BW.

Once you do an init and stsrt filling the set up tables the delta queue is created in RSA7 which stores the delta.

So once your set up tables are finished you do full repair or full load from the data ousrce to target and then you run the delta's.

Just remeber that set up tables are just the storage of data of the records before records stsrts moving into the delta queue.

The practice is to first do init W/0 data transfer in the data source and then start filling the set up table.

AS you will you do the init w/0 data transfer you will have all the new records pulled into the delta queue and after that you start filling the set up tables.

This can bring the new records which are also going to the delta queue but after the set up tables are filled the full loads to the target will be followed by delta loads which will overwrite with the new records.

If its a functioanl module based generic datasource no setup tables are required. Its only required in case of LO datasources.

for steps.. go thru this link...

Filling up setup tables:

follow the navigation :

TCODE : SBIW. Drill down Settings for Application-Specific DataSources -> Logistics -> Managing Extract Structures -> Initialization.

select the aplication area you require and fill the setup tables,

we use setup tables to do initialization or a full load ( all Historical data ) ,

Deleting the set up tables :

deleting and filling the setup tables will restructure the setup tables , For example when a LO extracter is enhanced with additional fields , and if you require to get the historical data for the newly added fields ,

we will delete the setup tables and again fill them as it will restructure the setup table for the additional fields and fetches all the required data for them also,