on ‎2012 Aug 31 5:52 AM
Request clarification before answering.
Hi Shalaka,
In the Lo cockpit we have the mechanism of Setup tables.For full and Init loads we used the setup tables.
The base tables data is stored in these setup tables when we filled.According the requirement we can use these set up tables data.We can fill these tables based on Restirctions of data like co code, org...
If u came to know the data discrepancy in the target and u have deleted the Data in PSA. Then u should take the data from Source system.If u filled the setup tables that data is available for our requirement In this case there is no disturbance of delta loads..
This is the mandatory for all LO Cockpit datasources.
Regards,
Babu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
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.
Hope it will help you.
Regards,
Anand Mehrotra.
| User | Count |
|---|---|
| 7 | |
| 5 | |
| 5 | |
| 4 | |
| 4 | |
| 4 | |
| 3 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.