SETUP TABLES :-
Are used when doing full load or Delta Init load, or
we can say that when we load historical documents then they are transfered
from the application tables to setup tables and from there to BW.
The reason for using setup tables is that SAP doesn't
allow the extractor to directly get into the application tables.
Setup tables deletion have absolutely any impact on your
existing delta flows.
Setup tables are only used when you do an init or a full
load, but after having done these activities, you don't need its data anymore
(since you have not updated and old records) and what you do don't have
any relation to your flows!
Setup tables are used only for logistics extraction. You perform a setup right before you do your first initial load of 'historic' data to BW. After the load the delta queue takes care about the changes of data.
Setup Table are purely related LO Right.If you want do the extraction using LO-Mechanisim we must fill the setup tables.whenever you filled the setup tables the extractstructure got filled with the data.Whenever we say schedule infopackge using FULL/INITIALIZE DELTA from BW,the data picked from the setup tables.
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 init loads in BW pull data from the set up tables. The setup tables are only used in case of first init/full loads.
The logistics extractors from Logistic Cockpit (LBWE) was designed to replace the LIS info structures (Snnn). When you create, change or delete documents in the applications, the resulting data is staged online in LIS communication structures. In addition, data is transferred from the LIS communication structure, using extract structures, into a central delta management area (using different delta method). So, delta management acts as a buffer for data that can be requested from the BW via an infopackage with the update mode "delta upload".
When you use infopackages with the update mode "delta initialization" (even "full"), your scope is to used to transfer existing or archived documents. Only afetr this step (initialization) any modification will be available as delta, following the schema explained before. In OLTP (R/3) the infopackages retrieve data from the setup tables (and no postings have to be in the meanwhile, otherwise there would be some data loss!), which are assigned to the extract structures.
You fill these tables using special setup transactions in OLTP (OLI*BW).
For each extract structure, one setup table with the name of the extract structure and ‘SETUP’ as a suffix, exists.
Example: Extract structure MC02M_01TM, setup table MC02M_01TMSETUP.
Since you are using cluster tables, it does not make sense
to display the entries with transaction SE16.
You cannot determine the number of entries from the number
of data records.
However, you can display data using transaction RSA3,
since this transaction uses data from the setup tables.
The reason of using Set up table is that the SAP doesn't permit the extraction structure tables to access the database tables directly like.Rather than getting the data directly from the source tables (EKPO, MARC, VBRP, VBRK ), the data is stored in Set up tables, which you can use for update to BW.
After that all transaction data is posted to the delta queues in the source system. After a sucessful full upload you can delete the setup tables.
Setup tables are an essential part of LO extraction.
Comming to how to set up the V3 job.
Select the Update Method (Queue Delta) and click on Job
Control.
Click on create job(you need to schedule the job).
Then fill the Print Settings.
