SAP BI - What are the Setup Tables?
The Setup Tables are the objects from which the Business Warehouse system is going to extract data for Full loads and Initialization on LO DataSources.
When a Full extraction or a Delta Initialization is going to be performed, the Setup Tables need to be filled with all the historical data to be loaded to the Business Warehouse system. This ensures the extractors won't need to access the always busy application tables (like EKKO or VBAK).
Their content can be deleted any time, without affecting the R/3 transaction data. In fact, after the full/Init load has been performed, it is highly likely that the information contained in the Setup Tables is already not up-to-date anymore. Therefore, it would be no harm at all to delete their content. You may think of it as a "PSA" on the R/3 side.
If the load performed was an Initialization, the next records to be extracted will be sent to the Delta Queues.
Customizing Cockpit: Managing delta queues when structure changes
Overview
As we know the Logistics Customizing Cockpit enables you to enhance the Datasources of the logistics listed there from a pool of predefined fields and before changing the extract structures in Customizing cockpit (transaction LBWE).
We must carry out several tasks to avoid inconsistencies into the system because when you change a DataSource or their extract structure, the data that is saved in the old form of the structure is no longer interpreted correctly.
This guide will give you some steps to help you to avoid inconsistencies problems.
http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/18676
What is the difference between outer join and inner join ?
You use INNER JOIN to return all rows from both tables where there is a match. i.e. in the resulting table all the rows and columns will have values.
In OUTER JOIN the resulting table may have empty columns. Outer join may be either LEFT or RIGHT
LEFT OUTER JOIN returns all the rows from the first table, even if there are no matches in the second table.
RIGHT OUTER JOIN returns all the rows from the second table, even if there are no matches in the first table.
