Ods Vs Delta Update

hi all...please clarify me what is the necessity of delta update if ods is there to get new /changed records by eliminating duplicates?
<Please avoid Typing in CAPS - Caps is not going to get you that additional bit of attention for people to respond to your question faster... >
Edited by: Arun Varadarajan on Oct 15, 2008 4:55 PM

Hi,
Delta menas it will only take new or changed records ...
In ODS, the delta records are handled based on the type of aggregation..
if its an overwrite ODS then the older records with same technical key are overwritten with the new records..
if its an additive ODS, then the new delta records are added to the existing reords with the same technical key...
In ODS as u r aware there are 3 tables..
Active table, activation queue and Changelog..
Whenever a new record comes..consider in this case if its an additive ODS..
during activation the newer record wil be added to the existing one in the Active table..
but whereas in changelog.. this reord will be add as one more new entry and the old ones will be retained as such..
ex: old record : customer ID -498, goods supplied - 50
new record :customer ID -498, goods supplied - 100
then now the contents in active table wil be as
customer ID -498, goods supplied -150
whereas in changelog it will be as
customer ID -498, goods supplied - 50
customer ID -498, goods supplied - 100
This kind data in changelog will be useful when we want to datamart delta records further to any other reporting cube and if the delta update type from the source system cannot support infocubes..
to check some more on this ..
http://help.sap.com/saphelp_erp2004/helpdata/en/84/81eb588fc211d4b2c90050da4c74dc/frameset.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/57/b9d43d89e6b34aa2c6fa9fe2ab243f/frameset.htm..
Hope this helps you ..
Reagrds,
Shikha

Similar Messages

Get back the Data mart status in ODS and activate the delta update.

I got a problem when deleting the requests in ODS.
actually there is Cube(1st level. it gets loaded from an ODS(2nd level). this gets loaded from 3 ODS'S( 3rd level). we were willing to delete recents requests from all the data tardets and reload from PSA. but while delting in the request in ODS(2nd level), it has displayed a window, showing as follows.
- the request 132185 already retrived by the data target BP4CLT612.
-Delta update in BP4CLT612 must be deactivated before deleting the request.
- Do you want to deactivate the delta update in data target BP4CLT612.
I have clicked on execute changes in the window. it has removed the data mart status for all the request which i have not deleted.
in the same it happened inthe 3 ODS's(3rd level).
I got clear that if we load further data from source system. it will load all the records from starting.
so to avoid this can any body help me how to reset the Data mart status and activate the delta update.

Hi Satish,
U have to make the requests RED in cube and back them out from cube,before u can go for request deletions from the base targets(from which cube gets data).
Then u have to reset data mart status for the requests in your 'L2 ODS' before u can delete requests from ODS.
Here I think u tried to delete without resetting data mart status which has upset the delta sequence.
To correct this..
To L2 ODS,do an init without data transfer from below 3 ODS's after removing init request from scheduler menu in init infopackage.
Do similar from L2 ODS to Cube.
then reconstruct the deleted request in ODS.It will not show the tick mark in ODS.Do delta load from ODS to Cube.
see below thread..
Urgentt !!! Help on reloading the data from the ODS to the Cube.
cheers,
Vishvesh

Deactivate delta update before deleting the request from ODS

Hi all,
Happy New Year wishes to all.
I have a scenario, where I am feeding the data to ODS from flat file and from ODS to Cube. Here ODS is a Data mart. Flat file to ODS full update and ODS to Cube First Initialization and Delta.
I deleted the latest request from ODS, at the I got the message dialog box and it is saying that
Request 98888 already retrieved by data target BWVCLNT
Delta update in data target BWVCLNT must be deactivate before deleting the request
Do you want to deactivate the delta update in data target BWVCLNT?
So I pressed Execute changes, then after I loaded the data in to ODS and when I am trying to load the data into Cube, once I pressed execute button it is displaying the message dialog box like
Delta request is incorrect REQXXXXXXX in the monitor
A repeat needs to be requested
Data target still include delta request REQXXXXX
If the repeat is now loaded, then after the load
There could be duplicate data in the data targets
Request the repeat?
After execute changes it is showing only zero Records only.
What is that mean and why zero records it is displaying instead of delta records.
Anybody faces this type of problem please let me know. This is somewhat urgent to me
Thanks and Regards
Satish Chowdary

Hi Satish,
First Switch off the ODS ( automatic Update of Datatarget ) , though not really necessary. delete the Req from the Infocube, then delete from the ODS . Now delete the Init Req from the Infopackage for datamart infopackage.then Do an Init without datatransfer into Infocube. Later load data into ODS and then go for delta update to Infocube.
I hope this helps.
Thanks,
Krish
Dont Forget to assign Points.
Dude, you just repeated my answer I gave a few hours ago. Are you hungry for points?

Delta Update in data Target Must be Deactivated Before deleting the request

Hi Experts,
I got an error while deleting a request from an ODS target. In breaf Let me explain..
Today one data load got failed. The data source 0CRM_SALES_CONT_I ( CRM Sales Contract : Item ) is updating data to 4 ( Four ) ODS targets.
So I forcefully made the request red to delete the request from the targets. But I unfortunately deleted another request without making it RED, I reconstructed it. Everything is looking fine.
   But the thing is , when I tried to Delete the ERROR request from the other two related Data Targets ( 0CRM_CN2P and   0CRM_CNT1) , I fount these warnings..
                --> Request 140522 already retrieved by Data Target BWPCLNT600
                --> Delta update in Data Target BWPCLNT600 must be DEACT. before deleting the request.
                --> Do you want to DEACTIVATE the Delta Update in the Data Target BWPCLNT600   ?
   I clicked on YES.
I am having doubt, will it make any problem in future ? Or How Can I Resolve this problem   ?
Thanks,
Utpal.

Hi shanthi bhaskar ,
Thank you. But the client no which I have mentioned is not our. That is different, I have given for the example. Bur the DS and ODS name are as it is.
   and Shanthi, Won't be any problem as I got the warning as mentioned above.. ?
Thanks,
Utpal

How to Delta Update in Flat Files

Hi all,
I would like to know is delta update is supported in flat files ? If yes how does this work ..... is there a SAP white paper or document on this
Thanks
Nathan

Hi......
Yes Delta upload is supported by Flat files..........In this case........when the delta data records are loaded by flat file......... This delta type is only used is 'F'.......for DataSources for flat file source systems. Flat files are imported to the PSA when you execute the InfoPackage. The staging process then begins.........The delta queue is not used here.
As Siggi already told in the Following thread......post your flatfile data to an ods object with update mode overwrite. The ods object will do the delta for you then.........
Delta Upload for Flat File
Also Check this.......
SAP NetWeaver 7.0 BI: Data Transfer Process with Only get Delta Once
SAP NetWeaver 7.0 BI: Data Transfer Process (DTP) / The Normal DTP ...
Hope this helps........
Regards,
Debjani........
Edited by: Debjani Mukherjee on Nov 12, 2008 9:40 AM

How to use Delta Update in InfoSpoke

How to use Delta Update in InfoSpoke & to include in Process Chain

Initialization / delta updates are what we do every day, and it is usually the update method of choice for most data targets. The delta mechanism ensures the consistency of transactional data. So if some data is wrong in the early stage of data flow, we have to not only correct the data itself but also the related records in subsequent data targets.
Unfortunately, such data can't be avoided in daily extractions. In some situations, the data to ODS is correct but reports errors while loading from ODS to Cubes.
Here is one example:
Some FI documents transferred in R/3 with LSMW's background mode and one of the line items 'Negative posting signal' was inserted with 'x' while the right one should be 'X'.
This line time stays cool in my ODS Z1CCWO01, but encounters errors while loaded into several Cubes when the process chain's running.

Activation of Delta Update Mode:

Dear
Experts:
I have loaded the data with full update mode in ods, now i want to data with delta,
I have init with out datatransfer for enbaling delta, it is throwing an error msg mention below
Full updates already available in ODS ZODS_O06 ; Cannot update init./delta RSM 98
Need suggestion to move further:
Regards
Radha.

You have to convert the full update request to Repair full requests.
You can use RSSM_SET_REPAIR_FULL_FLAG program or RSSM_SET_REPAIR_FULL_REQUESTS function module.
In the program give Infocube as DSO name, datasource and source system from where you are loading data.
After this you would be able to load init request properly.
Pravender
Edited by: Pravender on Jun 2, 2010 5:40 PM

Error in 0CFM_DELTA_POSITIONS Delta Update

Hi,
We had followed all the steps given in your post to upload CFM data.
Initialization with cube and delta is done without any error .
after that we extracted data with update mode 'D' datasource 0CFM_DELTA_POSITIONS . and there is not any problem with data extraction.
But when we are trying to upload data to ODS with Delta we are getting error as 'Error with data selection'
Can anybody help me out for this problem.
Regards,
Renu

Thank you for the translation Shabar.
With other values for TR_ACC_CODE the extraction works fine, but there are no records. All information will be saved using same TR_ACC_CODE, in this case 001.
The problem is that i can't use value 001 anymore since i ran the inital load for the cube. Before, the extraction worked fine for value 001, so i guees it must be something else.
Any other idea what can i do?

Issue With R/3 Extractor 2LIS_13_VDITM and 2LIS_11_VAITM during Delta Updat

Hi all,
We are using 2LIS_13_VDITM and 2LIS_11_VAITM Datasources to upload sales overview cube directly as well as a custome ODS seperately using Direct Delta method.
Now first time upload was perfect(Initialization) but if any changes are made to the existing data or if any new entries are entered in the source system, R/3 extractor (2LIS_13_VDITM and 2LIS_11_VAITM) is not pulling those records.
Once we tried deleting SETUP table and reloaded it, extractor was able to pull the records but again the issue crops up for any new entries or changes made in source system.
This is stopping us from completing the project. So any suggestions the would help us solving the issue is most welcome.
Regards,
Surendhar.

Hi,
If you have selected the 'Queue delta' Update method for applications 11 and 13,then make sure that the "update" job is scheduled to move the data from LBWQ to RSA7. Once the data available in RSA7, you can execute the infopackage with delta load.
If you have selected the 'Direct delta' Update method for applications 11 and 13,then there is no need of "update" job to move the data from LBWQ to RSA7. Once the data available in RSA7, you can execute the infopackage with delta load.
With rgds,
Anil Kumar Sharma .P

Delta update for datastore is invalidated

Hi experts,
we're on SCM 7.0 and I'm trying to copy data from livecahce into a cube for backup. Have set up the datasource, dso and cube and this has been working. We had this process running with the data extracting to the cube all fine.
Something has happened to cause this error below and I'm not able to fix.
The delta update for the InfoCube DS_PAGGL is invalidated. The can be due to one of the following:
1. A request, which was already retrieved from the target system, was deleted from the InfoCube.
2. A request, which was not yet retrieved from the target system, was compressed in the InfoCube.
Procedure
Initialize your delta update again.
The data load to the dso work no problem but when it trys to transfer to the cube where it errors. it shows as a Repeat of the last delta in the type of data update. Request status stays yellow but if you call the monitor is shows as red with message above.
Error message no. is RSBM113
The dso is on a full update and the cube is on a delta.
I can't reinatialise this as when i call up the IP this option is greyed out.
I've deleted the update from the cube, dso and psa but when its rerun it comes up with the same error each time.
If we can't initialise, then what other options do we have?
Thanks
Edited by: Paul_111 on May 11, 2011 5:15 PM

Hi Venkat,
Delta request REQU_429VZAIHRVBTP2OUFU2AP8T4Q is incorrect in the monitor A repeat needs to be requested
This is bcoz, Your last delta from ODS to CUBE is not success full.
Just delete the initialization from ODS to CUBE and reinitalize with out data transfer. And pull the delta from ODS to cube after initialization. It will solve the problem.
Hope it Helps
Srini

Delta update for ... is invalidated

I try to load my cube from another cube (as an infosource) via an ODS.
In the InfoPackage I select 'Full update'. Under 'Processing' I have checked 'Data Targets Only'. Under 'Data Selection' I have selected a limited set of data to load (one month).
When the loading process is finished, I get a popup message "Express document "Check Load from InfoSource 8ZOSACTCV" received..." When opening this document I read "Check Load from InfoSource 8ZOSACTCV , Packet Delta Package for Update by ODS ZOSACTCV".
The loading of the ODS is completed successfully. When monitoring the InfoCube loading process, I get a red light. The error message is "Delta update for ZOSACTCV is invalidated".
Both the ODS and the cube was empty before loading (although I first tried it with existing data in the cube). What is wrong? I see the request in the cube is called "Delta Package for Update by ODS ZOSACTCV". Why is it called a delta package when I requested a full load? Is this a part of the problem? I have tried "Delta Update" and "Initialize Delta Process" with "Initialize Without Data Transfer". I always get the same result.

Hai,
I understand that you are loading from Cube to ODS and then to another cube from this ODS. The data load from Cube to ODS is sucessful but the full load from ODS to Cube doesnot work. Is it?
Check few things below for load between ODS and the final cube:
1. See if there is any active initialization in the infor package. Go to your infopack and in Menu>Scheduler>Intilization option for source system.
If there is any delete it and try the load. A full load destroys a prior initilaztion.
2. If step is not the case, delete all the contents of the Cube and load. You can do this by hitting 'Delete' icon and 'delete all entries' or by right clicking on the cube and 'delete data'.
3. If even thats not the case, try to just load till PSA and then go to your PSA and simulate the upadte. See whats the problem is...you can find more details in the details tab screen in Monitor.
Let em know if these doesn't work. Provide me any other relavent information. We can work it out.

Delta update for 0FIGL_O02 is invalidated"

Hi Gurus,
I am facing the above stated message when i am loading the delta from ODS to Cube.
What happened.
we r deleted a request which is having data mart satus ok.
After that we reconstructed the same request into ODS.
After that the delta to cube from the same ods is giving the message like
"Delta update for 0FIGL_O02 is invalidated"
What i have to do in this case.
May i reinit cube.
Or any other way to solve this .
The data mart status for all requests in ODS is vanished.

Hi
See if the steps followed for delta are Init without data transfr, full repair and then delta if this is not the case follow the steps mentioned and if it is so u can do one more thing
do init with data transfer once again this will include each and every data but first delete the previous req of init. There is no need to do delta up till the time next delta comes after init with data transfer is done
Hope it helps Assign Points if applicable
Thanks
Puneet

Delta update for ZPUR_O04 is invalidated

We r loading ODS ZPUR_O04 from 2LIS_02_SCL data source daliy in production.
this is delta load.
In second layer, we r loding ODS ZPUR_O02 from this 8ZPUR_O04 ODS.
this is also delta load from 8ZPUR_O04->ZPUR_O02 .
But we didn't get data mart flag in ZPUR_O04 .But the data were coming correclty in ZPUR_O02 from 8ZPUR_O04 in a daily process chain in production.
Problem---->Now we have loaded repeat last delta in ZPUR_O04 bcz last delta was incorrect.This repeat last delta came correct but we r getting problem in 8ZPUR_O04->ZPUR_O02 saying that Delta update for ZPUR_O04 is invalidated.
Pls suggest me load the data to this data target ZPUR_O02 from ZPUR_O04

Hi,
Before doing Repeat last delta to ODS ZPUR_O04, I hope, you deleted the last delta request from ODS ZPUR_O04. But might be the delta laod was over to ODS ZPUR_O02 between the uploading of the the lase delta request and deleting that request from ODS ZPUR_O04 for starting repeat delta. So you had to delete the request from ODS ZPUR_O02 ,if you want to delete teh request from ODS ZPUR_O04.The procedure for that one is:
http://help.sap.com/saphelp_nw2004s/helpdata/en/67/54ec83b3ba7945bdfc044c8bc37a6b/frameset.htm
If you have not follwed the steps mentioned above , if will get the problems like you mentioned.
Now I hope, only one thing left to you,that is Delta init to ODS ZPUR_O02.
With rgds,
Anil Kumar Sharma .P

Delta update for a characteristic

Hello,
Is it possible to adjust a delta update for a characteristic? I use an InfoSource with Flat Files on BW 3.5. Hope that somebody could help me.
Regards,
David

Hello again,
I try to clarify this.
My data flow: Source System -> PSA -> ODS -> InfoCube.
For example I load this kind of flat file full into the ODS:
NOTE: The entries are only IDs for the Text!
characteristic
characteristic
characteristic
key figure
key figure
ABC
DEF
GHI
123
456
JKL
MNO
PQR
STU
456
VWX
YZA
SAP
HII
456
Then i change the the first entry second column in my flat file:
characteristic
characteristic
characteristic
key figure
key figure
ABC
HEL
GHI
123
456
JKL
MNO
PQR
STU
456
VWX
YZA
SAP
HII
456
After the second load i have of course this:
characteristic
characteristic
characteristic
key figure
key figure
ABC
DEF
GHI
123
456
ABC
HEL
GHI
123
456
JKL
MNO
PQR
STU
456
VWX
YZA
SAP
HII
456
But i need this:
characteristic
characteristic
characteristic
key figure
key figure
ABC
HEL
GHI
123
456
JKL
MNO
PQR
STU
456
VWX
YZA
SAP
HII
456
Is there any solution for this? Of course i can delete the request an load again, but i won't.
Regards,
David

Delta update for Info cube, How it will be works, what are mode to select.

Hi all,
              How delta update works for info cube, Generic data source delta update options are
              1) time stamp
              2) Calday
              3) Nemeric pointer
Please explain briefly delta update for infocube and delta init and delta update.
Thanks,
Gowda

Hi,
How delta update works for info cube
When you are updateing the data to cube from ods then data would extracted from change log their delta pointer get setup in the source request (in Source you can check the option beside the reqest says updated to target object.... it means the records are updated to target hence we would not update the same request )
Incase of PSA to cube Also in the PSA request get stamped as last updated .
Regarding Generic Datasource
When we don't find any standard extractor then we can go for Generic(if i want information sales along with finance information in a data source then generally we dont get standard one hence we can go for generic DS)
Check the below link for More about generic DS .
http://wiki.sdn.sap.com/wiki/display/BI/Generic+Extraction
for Delta capturing you can use
Timestamp(if the table has time stamp filed so it can stamp the last changed record in that table hence it is easy to get delta based on the time stamp)Calday- (If the table doesn't have the Timestamp filed then search for Calday where you can stamp the delta based on the date when documents are changed )
Numericpointer : If the table doesn't above both then we go for this option where you can the numeric value change stamp )
Re: Extraction, Flat File, Generic Data Source, Delta Initialization
Regards,
Satya

Ods Vs Delta Update

Similar Messages

Maybe you are looking for