Delta Documents missing

Question

Hi Experts,
I have been loading daily deltas from ERP to ODS and then to cube datasouce 2lis_13_VDITM but users found that some of the billing doc missing already deltas are upload from ODS to Cubes and  we cant delete the data . the data is huge . is there any way that we can upload the missing documents .
Thanks

Answer 1

Hi,
Yes correct, make sure you load Full repair and not Full.
Full repair can be said as a Full with selections. But the main use or advantage of Full repair load is that it wont affect
delta loads in the system. If you load a full to a target with deltas running you again will have to initialize them for
deltas to continue. But if you do full repair it wont affect deltas.
This is normally done we when we lose some data or there is data mismatch between source system and BW.
Check the OSS Note 739863 'Repairing data in BW' for all the details.
Refer.
Repair full request
Re: Repair full request
Steps to perform repair full request
Repair bad data and subsequent data targets with
delta update
/people/aaron.wang3/blog/2007/04/11/repair-bad-data-and-subsequent-data-targets-with-delta-update
Setup tables
Setup tables hold historical data. Setup tables are based on the concept of Cluster tables means the data will be stored in a big table in database layer and it can be viewed in multiple smaller tables in application layer.
Before doing Full or Init we have to do statistical setup. When we run statistical setup tables will be filled with the data,
normally historical data, the data goes from database tables to Setup table. If you run the full or Init in BW then the data
will be extracted from the setup tables. If you run the Delta then it will fetch from the delta queue. We use setup tables
while we are doing Repair full request also. Repair full is nothing but extraction the historical data without disturbing the
delta loads.
Before running Statistical setup its good practice to delete setup tables’ contents to avoid data redundancy.
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 successful full upload you can delete the setup tables.
Only after this step (initialization) any modification will be available as delta, following the schema explained before. In
OLTP (R/3) the info packages 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.
for sales order setup tables will be like this
for header : mc11va0hdrsetup
for item level : mc11va0itmsetup
for schedule line : mc11va0sclsetup
u can view the data of setup tables in se11 or se16.
Check this blogs from Roberto for Logistics Extraction:
/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
/people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
/people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
/people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
/people/sap.user72/blog/2005/04/19/logistic-cockpit-a-new-deal-overshadowed-by-the-old-fashioned-lis
These blogs will explain what, why and when of setup tables .
Hope this helps.
Thanks,
JituK