Generic Delta: Init, Full Upload and Deltas...

Dear All,
Last week on 10.04.2014 I've created "Generic DataSource with Generic Delta" and used CalDay as Delta-Specific Field and lower limit kept to blank and upper limit to 1. On 11.04.2014 I've initialized the Delta with Data Transfer using Process Chain: Time 1:15 p.m (Note: Posting was on)
see below screen shot:
Result: Process Chain was scheduled to immediate and it executed and initialized the delta and brought records as well. See below screen shot of RSA7:
Q: 1: Why generic delta current status is 10.04.2014, as I'v scheduled delta through process chain on 11.04.2014 @ 20:50: and why Total column is showing 0 records? Even I've checked Display Data Entries with Delta Repetition, but could not find any records?
Following is the InfoPackages which I created for Delta Loads and used in another Process Chain for Delta scheduled (daily @ 20: 50).
Following is the DTP used into Delta Process Chain:
On 12/04/2014 when I checked my InfoCube, and found that same number of records being loaded again despite InfoPackage and DTP were created as Delta, see screen shot:
On 12/04/2014 See below PSA table:
On 14/04/2014 when I checked InfoCube and I saw deltas being loaded successfully: see below screen shot:
On 14/04/2014 see below PSA table:
On 14/04/2014 see below RSA7 BW Delta Queue Maintenance screen shot:
Q: 2: Why am I unable to load the Delta records on the day(11/04/2014) when I initialized it with Data and why same number of records being loaded again on 11/04/2014?
Q: 3: On 11/04/2014, around 1:15 p.m I've initialized Delta with Data successfully and the same day (11/04/2014) was my first load of delta records (Time: 20: 50), could this be a problem? as the posting period was on when I initialized and I tried to load the delta on the same day?
Q: 4: Why the pointer is showing me Current Status: 12/04/2014 today and this time around I can find last delta records from "Display Data" option with Delta Repetition?
Q: 5: Have I missed something in the design or data flow?
Q: 6: How can I verify deltas records accuracy on daily basis; is it from RSA3?
or How can I verify daily deltas with ECC delta records?
Q: 7: What is the best practice when you load full data and initialized delta and schedule deltas for Generic DataSources with CalDay as delta specific field?
I will appreciate your replies.
Many Thanks!!!
Tariq Ashraf

I clearly got ur point.....But
If i have situation like ....." I loaded the LO data from R/3 with Init delta......then i loaded 5 loads of delta too.......due to some error in data now i am trying to load all th data......In this case if i do Full upload it is going to bring all the data till 5 th delta load .......If i do Init delta again it is going to bring the same data as full upload..........In LO while loading both Full load or delta init load we need to lock R/3 users....I believe we can load delta even after full upload by using "Init delta without data transfer"............So that wont be the barrier....then what is the difference or how should i figure out which load should i do.............If i am wrong please correct me.......
Thanks

Similar Messages

Full upload then delta?

Hi all,
We have a scenario where the ODS object contains 2 billion records.
we want to load this data in to new cubes.
Since we have huge data:
-can we go for delta init and then subsequent deltas?
-Can we go for a full load (by time selections in the infopackage) and then can we define a delta?
What would be the ideal solution since ODS contains 2 billion rec
Regards
Naveen

Hi Bhanu
Let me know weather I am right:
1. I create a info package and run with the option Init with out data transfer
2. Create several infopackages with selection options (based on time) and run with repair requests
eg if i have data from 2005 - till date then I create 5 infopackages. the first 4 info packages are restricted each for 3 months and the 5 or last info package for 2006-tilldate
After al these jobs
Now I create a new infopaackage with delta loads for future data ?
Let me know ny suggestions
Best Regards
Naveen

Full Load and delta loads of HR Data using ABAP Program

Hi All,
I need to write an ABAP program that will pull some HR data from some of the infotypes.When i run it for the first time it should pull all the data for all the employees but in the subsequent runs it should run only the delta changes
for example
inital run is on 04/30 it should pull all the data for all the employees
next run 05/02 then it should pull onlly the infotypes for which there is a change between 04/30 and 05/02
Please let me know the solution
Thanks
Bala Duvvuri

Rob,
I understand that I need to AEDTM field but the problem is
during the initial load i will not have any control date stored in the z table so i will fetch all the records using the select queries on various infotypesin the if condition but the problem is i need to repeat the same queries by adding the AEDTM condition in the else condition where control date is not initial(not an initial load) so it will be a duplicacy of all the select queries.
is it a good programming style?please let me know your thoughts on this
if p_ctrl is initial " Initial load
select queries
else " subsequent runs
same select queires with AEDTM condition
endif.
Thanks
Bala Duvvuri

What is the diffrence between full load and delta load in DTP

hI ,
I am trying to load the data into CUBE from another cube using DTP ..
There are 2 DTPS ..
1: DTP with full load
2: DTP with DELTA load ..
what is the diffrence betwen thse two in DTP ...
Please can somebody help me

1: DTP with full load - will update all the requests in PSA/source to the target,
2: DTP with DELTA load - will update only new requests to the datatarget
The system doesnt distinguish new records on the basis of changed records, rather by the request. Thats the reason you have datamart status to indicate if the request has been loaded to further datatargets.

Two Extractor logics for full and delta?

Hi,
I have a situation where in the logics for full upload and delta uploads are drastically dfifferent!
What is best way to deal it?
shuould i have two different extractors for full and delta ?
Raj

Hi Raj,
I hope that u are working with the Generic Extractors. If the volume of the posting is too high then u need to restrict the data definitely from R3 side interms of the performance. And u need to maintain the Delta Functionality for the same.
If u cannt maintain the Delta from the R3 side then atleast try to restrict the same from BW side at the infopack level where u can extract the data based on the changed on and created with the two different IP's and update the same to the ODS(here make sure all the objects are with the overwrite).... and then u can maintain the Delta load from ODS to the Cube easily..
If the volume of the data is pretty less then u can use Full load to the ODS and then Delta to the Cube.
Thanks
Hope this helps..

Filling of set up tables for Full and Delta updates

Dear Gurus,
How do I go about filling the set up tables if I want to load historical data to BW using LO **** pit when set up table is running on delta ?
I want to know how many set up tables will be there for each data source, Because if set up table is running on delta and using the same table I want to load historical data also then will I have to delete and fill set up tables or there will be a separate set up table for full upload and delta ?
If we have multiple set up tables for one data source then in the T-code OLI*Bw, where * -> App logistics num, so to fill I just say OLI6BW, then which set up table it is going to refer.
Clarify my doubt and get rewarded with plenty of points.
Regards
Mohan

Hi,
Filling up the set up tables depends on the datasource.
there are different T-codes for the respective extract structures
OLIIBW transaction PM data
OLI1BW INVCO Stat. Setup: Material Movemts
OLI2BW INVCO Stat. Setup: Stor. Loc. Stocks
OLI3BW Reorg.PURCHIS BW Extract Structures
OLI4BW Reorg. PPIS Extract Structures
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
OLIIBW Reorg. of PM Info System for BW
OLIQBW QM Infosystem Reorganization for BW
OLISBW Reorg. of CS Info System for BW
OLIZBW INVCO Setup: Invoice Verification
OLI7BW is the tcode for Sales Order.
Hope this solves Ur issue....
Assign points if helpful..
Rgs,
I.R.K

Change load full data to Delta

Hi!!
In the past, we load Full data for a customized DataSourece. Now I changed the DataSource to load delta datas.
This data source was connected a ODS and when I tried to initialize delta process I received the error message. "Full updates already available in ODS 0SAL_DS01 ; Cannot update init./delta".
Someone know, How can I Initialize Delta Process?
Regards,
Cesar G. Batista

Hi.............
ODS does'nt support Full upload and delta upload parallely..........suppose a ODS is getting loaded with delta upload...........then if u do a full upload.........then ODS activation will with this error...........then u have to convert full upload to full repair...........
Go to SE38 >> Program : RSSM_SET_REPAIR_FULL_FLAG...................this program also exists in 3.5.............check it properly............
Check SAP note 689964 ........
Hope this helps........
Regards,
Debjani.........

Difference between fullupload and delta

hai i am doing extraction from flatfile to bw.when i am sheduling the data i seen one option dataupload(full upload,delta) i need the differnce between full upload and delta
Please search the forum before posting a thread
Edited by: Pravender on Jun 22, 2010 10:44 AM

Hi,
Suppose ur implementing BW for XYZ company.its having data from past eg 5 years.and every the data will add as per the business.
What we do is we will send all the past or historical data first in BW system ,that is FULL load and every day data data adds as per our schedule thats delta.
once full load get success we wil enable delta.
plz find the forum for more information and plz close the question.
regards...KP

Full Load" and "Full load with Repair full request"

Hello Experts,
Can any body share with me what is the difference between a "Full Load" and "Full load with Repair full request"?
Regards.

Hi......
What is function of full repair?? what it does?
How to delete init from scheduler?? I dont see any option like that in infopackage
For both of you question there is a oss note 739863-Repairing data in BW ..........Read the following.....
Symptom
Some data is incorrect or missing in the PSA table or in the ODS object (Enterprise Data Warehouse layer).
Other terms
Restore data, repair data
Reason and Prerequisites
There may be a number of reasons for this problem: Errors in the relevant application, errors in the user exit, errors in the DeltaQueue, handling errors in the customers posting procedure (for example, a change in the extract structure during production operation if the DeltaQueue was not yet empty; postings before the Delta Init was completed, and so on), extractor errors, unplanned system terminations in BW and in R/3, and so on.
Solution
Read this note in full BEFORE you start actions that may repair your data in BW. Contact SAP Support for help with troubleshooting before you start to repair data.
BW offers you the option of a full upload in the form of a repair request (as of BW 3.0B). If you want to use this function, we recommend that you use the ODS object layer.
Note that you should only use this procedure if you have a small number of incorrect or missing records. Otherwise, we always recommend a reinitialization (possibly after a previous selective deletion, followed by a restriction of the Delta-Init selection to exclude areas that were not changed in the meantime).
1. Repair request: Definition
If you flag a request as a repair request with full update as the update mode, it can be updated to all data targets, even if these already contain data from delta initialization runs for this DataSource/source system combination. This means that a repair request can be updated into all ODS objects at any time without a check being performed. The system supports loading by repair request into an ODS object without a check being performed for overlapping data or for the sequence of the requests. This action may therefore result in duplicate data and must thus be prepared very carefully.
The repair request (of the "Full Upload" type) can be loaded into the same ODS object in which the 'normal' delta requests run. You will find this request under the "Repair Request" option in the InfoPackage (Maintenance) menu.
2. Prerequisites for using the "Repair Request" function
2.1. Troubleshooting
Before you start the repair action, you should carry out a thorough analysis of the possible cause of the error to make sure that the error cannot recur when you execute the repair action. For example, if a key figure has already been updated incorrectly in the OLTP system, it will not change after a reload into BW. Use transaction RSA3 (Extractor Checker) in the source system for help with troubleshooting. Another possible source of the problem may be your user exit. To ensure that the user exit is correct, first load a user exit with a Probe-Full request into the PSA table and check whether the data is correct. If it is not correct: Search for the error in the exit user. If you do not find it, we recommend that you deactivate the user exit for testing purposes and request a new Full Upload. It If the data arrives correctly, it is highly probable that the error is indeed in the user exit.
We always recommend that you load the data into the PSA table in the first step and check the result there.
2.2. Analyze the effects on the downstream targets
Before you start the Repair request into the ODS object, make sure that the incorrect data records are selectively deleted from the ODS object. However, before you decide on selective deletion, you should read the Info Help for the "Selective Deletion" function, which you can access by pressing the extra button on the relevant dialog box. The activation queue and the ChangeLog remain unchanged during the selective deletion of the data from the ODS object, which means that the incorrect data is still in the change log afterwards. After the selective deletion, you therefore must not reconstruct the ODS object if it is reconstructed from the ChangeLog. (Reconstruction is usually from the PSA table but, if the data source is the ODS object itself, the ODS object is reconstructed from its ChangeLog). You MUST read the recommendations and warnings about this (press the "Info" button).
You MUST also take into account the fact that the delta for the downstream data targets is created from the changelog. If you perform selective deletion and then reload data into the deleted area, this may result in data inconsistencies in the downstream data targets.
If you only use MOVE and do not use ADD for updates in the ODS object, selective deletion may not be required in some cases (for example, if incorrect records only have to be changed, rather than deleted). In this case, the DataMart delta also remains intact.
2.3. Analysis of the selections
You must be very precise when you perform selective deletion: Some applications do not provide the option of selecting individual documents for the load process. Therefore, you must first ensure that you can load the same range of documents into BW as you would delete from the ODS object. This note provides some application-specific recommendations to help you "repair" the incorrect data records.
If you updated the data from the ODS object into the InfoCube, you can also delete it there using the "Selective deletion" function. However, if it is compressed at document level there and deletion is no longer possible, you must delete the InfoCube content and fill the data in the ODS object again after repair.
You can only perform this action after a thorough analysis of all effects of selective data deletion. We naturally recommend that you test this first in the test system.
The procedure generally applies for all SAP applications/extractors. The application determines the selections. For example, if you cannot use the document number for selection but you can select documents for an entire period, then you are forced to delete and then update documents for the entire period in the data target. Therefore, it is important to look first at the selections in the InfoPackage exactly before you delete data from the data target.
Some applications have additional special features:
Logistics cockpit: As preparation for the repair request, delete the SetUp table (if you have not already done so) and fill it selectively with concrete document numbers (or other possible groups of documents determined by the selection). Execute the Repair request.
Caution: You can currently use the transactions that fill SetUp tables with reconstruction data to select individual documents or entire ranges of documents (at present, it is not possible to select several individual documents if they are not numbered in sequence).
FI: The Repair request for the Full Upload is not required here. The following efficient alternatives are provided: In the FI area, you can select documents that must be reloaded into BW again, make a small change to them (for example, insert a period into the assignment text) and save them -> as a result, the document is placed in the delta queue again and the previously loaded document under the same number in the BW ODS object is overwritten. FI also has an option for sending the documents selectively from the OLTP system to the BW system using correction programs (see note 616331).
3. Repair request execution
How do you proceed if you want to load a repair request into the data target? Go to the maintenance screen of the InfoPackage (Scheduler), set the type of data upload to "Full", and select the "Scheduler" option in the menu -> Full Request Repair -> Flag request as repair request -> Confirm. Update the data into the PSA and then check that it is correct. If the data is correct, continue to update into the data targets.
And also search in forum, will get discussions on this
Full repair loads
Regarding Repair Full Request
Instead of doing of all these all steps.. cant I reload that failed request again??
If some goes wrong with delta loads...it is always better to do re-init...I mean dlete init flag...full repair..all those steps....If it is an infocube you can go for full update also instead of full repair...
Full Upload:
In full upload all the data records are fetched....It is similar to full repair..Incase of infocube to recover missed delta records..we can run full upload.....but in case of ODS does'nt support full upload and delta upload parallely...so inthis case you have to go for full repair...otherwise delta mechanism will get corrupted...
Suppose your ODS activation is failing since there is a Full upload request in the target.......then you can convert full upload to full repair using the program : RSSM_SET_REPAIR _ FULL_FLAG
Hope this helps.......
Thanks==points as per SDN.
Regards,
Debjani.....
Edited by: Debjani Mukherjee on Oct 23, 2008 8:32 PM

ODS optioin- Is it going to be full upload or init delta?

Hi frnds,
I got a query where the scenerio goes like this,
Data loading from ods to infocube. Let us suppose in ods settings, i have selected the option Update data targets from ODS object automatically. Then my question is whether it will be a init delta or full upload.....please explain the scenerio.
thanks in advance
regards,
dubbu.

Hi Vinit,
This will be dependent to the load in ODS,
if the load is init in ods the further upload will be init.
If the load to ods is delta the further upload will be delta
Reward if useful
Manish

Full repair or Delta Init?

Hi Experts
I need your suggest
a)
Sometime we need made a re-load one month, and Im using a 'full repair'; but this give me errors (duplicate or missing records) where users are working in R/3 at the same time. Other posibilite is a 'full load' + 'delta init with out records'. Which is better in this case?
b) People say than after use a 'full load' you lose the init flag and is necessary made a init again.
In this case a made a 'full load' for 001.2008, and 'full repair' for 002.2008; and the init flag / delta load seemed ok. Is this possible?
c) When use a 'full repair', (with selection scope = 001.2008), how does it work? read from R/3 again or repeat the delta loads for the month specified in the selection, in the infopackage?
Thank you in advance!!

Hello,
Pls see these links
data extraction via combination of full + init updates
How to load init -delta requests when full load already exist
Full Upload and Init Delta Load
Thanks
Chandran

Full upload misses records while delta brings them

Hi experts,
I'm using 2LIS_12_VCHDR extractor and with delta exctractions everything is worknig correct. The problem comes when I want to make a full upload. It is not taking the last records (while delta took them). It is not bringing records into BW since the exact day I reloaded the 12 LIS tables.
If I create a sales order, and this order is delivered, my delta infopackage brings it into BW, but my full infopackage is not bringing it.
Any clues?
Points will be given,
Thanks

My scenario is the next one for 2LIS_12_VCHDR:
- Full upload on Nov 13th (6 months ago) and it takes 170103 records.
- I make another full upload today and I obtain 107103 records (the same as 6 months ago, and there are a lot more).
- I make an init request > I create a delivery in ECC> I make a delta upload an it takes it.
- Then I make a full upload and it is not taking it. I still have 170103 records.
Do I have to reiniciate the 2LIS_12 in ECC (OLI8BW)?
In the other hand I have the 2LIS_12_VAITM working with delta every day. How it will affect to this extractor if I reiniciate all the 2LIS_12? I'm going to miss data? I'm going to duplicate data?
Thanks

Delta upload full upload

Hi Gurus,
In ODS already delta is loading every half an hour. But, I don't see any data for one field in ODS. In that case, I want to load the data again to see if i can get the data? how can i do a full upload while delta is enabled? do i need to stop this delta and enable the full upload? or just full upload?
any help appreciated.
thanks

hi S.K.B,
i guess you enhanced business content datasource,
yes you need to populate the new added field in r/3
via user exit zxrsau01 (transaction data), take a look
sample code
Enhancement
User exit
and
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/59069d90-0201-0010-fd81-d5e11994d8b5
also weblogs on enhancement
/people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
/people/ajay.das/blog/2005/03/28/custom-fields-in-standard-extractors--making-a-mixed-marriage-work--part-12
(http://www.ko-india.com/content/weblogs/weblog_custom_fields_1.pdf)
hope this helps.

Interfaces- full and delta

Hi everybody,
I have a question on Interfaces-full file and delta file...Like is there a way to find out(either by looking at the program or the job, related to that pgm) as to wht exactly the outputof that particular interface, gives u(like the full file or a changes file only)? Or is there ny other method to find it out in SAP R/3 environment? As far as my knowledge goes, I think in BW we can find out using the Infopackages, am I right?
Thank You,
Appreciated a quick response,
Kaya.

Please search the forums. This topic has already been discussed a lot of times.

Delta to Full load

BW gurus
I have ODS1 updating to ODS2, ODS3,ODS4 and cube1, ODS2 is updating to cube2.
All data targets are delta update.
Now if I change to full load for ODS1 only ,will be there any problem with data in ODS2,ODS3,ODS4,cube1 and cube2.
will the Delta functionality works for other ODS s and cube s ?
There are few reports on ods2, cube1 and cube2.
Will be there any problem?
Any advice greatly appreciated.

Hi Manoj,
If you change the Upload mode to Full Upload for ODS1. The final data in the Active table of ODS1 is not effected as the data which is already uploaded will be overwritten in Change log table.
The delta from ODS1 is always from Change Log table so the delta data from ODS1 to ODS2, ODS3 and ODS4 is taken from changelog table of ODS1. Because of Change Log concept of ODS the final data (Active Table) in these three ODS are not effected.
The delta to the Cube1 will not be effected as well. Because according to Cube's Delta management all the data in the full upload is Delta. Since the delta data is always taken from Change Log the volume of delta data from ODS1 to Cube1 might be huge but the final data for reporting is unaffected. ( This Delta to Cube will actually pick the Before Image and After Image records from ODS Change log. )
Also the delta from ODS2 to Cube 2 is not effected and all the reports on these Infoproviders gives the correct values.
Thus your change in Upload Mode does not effect any of the Cubes or ODS
Hope this helps...
Cheers,
Raj
Message was edited by: V.P.R

Generic Delta: Init, Full Upload and Deltas...

Similar Messages

Maybe you are looking for