Delta Update for ODS

Hi,
We have created a view on R/3 side based on MARA and MARC. Using this view created a Datasource in R/3 side with Generic Delta on Matnr Field as a numeric pointer and safety interval Lower limit = 10.
In BW Side we have replicated the datasource and in the transfer structure mapped all the datasource fields with ODS Fields. But 0RECORDMODE is not mapped. Not sure what needs to be mapped to this field.
When i execute the Delta Infopackage the changes in not reflected in the ODS. Can any one help me in this.
Regards,
Subbu

Hi,
If you want the information from MARA and MARC then you dont have to create a view on these 2 tables. Its because, 0MATERIAL gets data from 0MATERIAL_ATTR and 0MATERIAL_TEXT which gets data from MARA and MAKT respectively. For MARC, you have 0MAT_PLANT in BW which gets the data from 0MAT_PLANT_ATTR and 0MAT_PLANT_TEXT in R/3. So try to use these 2 info objects delivered by SAP. If you want to report on both of them then you may go for an infoset in BW may be. Anyways, even if you create a view on these 2 tables, you will get only the common materials from them or you can say only the Materials from MARC as MARA has all of them and in addition you may have few more in MARA. But if you use an infoset in BW and join them by using Left Outer join, you will get all the material numbers from MARA.
Hope it helps...

Similar Messages

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

Delta update for deleted records

Hi,
I use delta update for my data. As destination I use ODS object and this ODS contains two keys: key1 and key2. On step of preparing data for extraction, key2 is lost(we can't determine it) - key1 is known only.
I'm finding a way how to update ODS by deleted records('D' update mode) if this records contain only key1 value(key2 is empty). I need to delete all records with key1 only, key2 is not important for this update.
Is it possible to set key2 some BW specific value, which will be accepted as equal for old key2 values ?
Or some other standart ways are known for this situation ?
Thanks in advance,
Fiodar.

I would use the update rules to read the active data table of the ODS. There you can read all the key2 values for a given key1.
If you get one row with key1 filled and key2 = '*' (for example you could split it into multiple records, one per key2. A sample coding might look like:
LOOP AT DATA_PACKAGE into l_d_data_package.
IF key2 = '*'.
    DELETE DATA_PACKAGE.
    SELECT * FROM /BIC/AMY_ODS00 INTO l_d_my_ods
      WHERE key1 = l_d_data_package-key1.
      l_d_data_package-key2 = l_d_my_ods-key2.
      append l_d_data_package to DATA_PACKAGE.
    ENDSELECT.
ENDIF.
ENDLOOP.
Best regards
   Dirk

The delta update for the InfoCube ZCUBE is invalidated

Hi BI Experts,
I am working on BW 3.5.
For the datasource 2LIS_13_VDITM there were some requests(deltas) missing for 3 days. So I got all the documents there were missing or not updated in BW. I deleted the setup tables and filled them with the new document numbers.
I did a full repair request from the Infopackage level and the data got updated in ODS.
But the DM Status is missing for all the requests in the ODS.
And the data for the full repair request didnt get updated in the Cube and I got the following error:-
The delta update for the InfoCube ZCUBE 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.
And the following delta was also not successfull.. How can I clear up this mess and ensure smooth flow of deltas. How can I set the DM status.
Thanks
Kumar

Thanks for your reply.
When I did a Full Repair Request on the ODS the data is in the New table and the DM status got reset(vanished). And the following day delta got failed( data for that request did not get updated in ODS and Cube)
How can we bring back the DM Status and make the deltas successfull.
Thanks
Kumar

Resumable downloads and delta updates for App Store

Hi all,
since I didn't find any place where to add product improvement suggestions, I post it here and hopefully someone can point me (and or this post) to the correct location.
I'd like to vote for resumable downloads (even a shutdown is in between) and delta updates for the Mac App Store. The main reason for this are big apps (i. e. Xcode) which I simply can't update without having the mac running the whole day (and night).
Thanks and regards,
Michael

Hi Michael!
Apple employees are not going to see feature feedback posted here, but you can use the Apple Feedbck site. There is not currently a category for the App Store but you can use the OSX feedback form here:
http://www.apple.com/feedback/macosx.html
The main reason for this are big apps (i. e. Xcode) which I simply can't update without having the mac running the whole day (and night).
Curious, are you on dial-up or satellite? As I live in a low-population state with lots of miles between towns of even modest size, I hear the slow connection issue a lot when helping users locally. We get 50mbps service in Lewiston, but people in the back country are struggling with some really slow satellite providers.

Delta update for 0CRM_CN2P is invalidated

Hi Experts,
I am getting the same error from last three days while monitoring.
The error message is :
Delta update for 0CRM_CN2P is invalidated.
The delta update for the InfoCube 0CRM_CN2P 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.
Please suggest , what will be the solution.

Hi,
Do a Full repair then again start the delta.
Some delta entry is missing either in source or target.
I hope it will help.
Thanks,
S

Delta update for 0FIA_DS11 is invalidated

Hi All,
The below description explain about the error that I am facing. But it is in the case of an Info cube that this description is valid. Now, I am facing this error when I am updating data into DSO, Info Cube from another DSO. I am performing delta update from DSO 0fia_ds11 to 0fia_ds12, 0fia_ds13 and Info cube 0fiaa_c11. Can anyone suggest if you know about this how to resolve.
Delta update for 0FIA_DS11 is invalidated
Message no. RSBM113
Diagnosis
The delta update for the InfoCube 0FIA_DS11 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.

Hi,
Have you checked whether the initialization was successful? Go to the info package and select Initialization options for source system and check initialization is successful.
It is better to re initialize the delta after deleting contents of the cube.
With Regards

Delta Update for Characteristic info object

Hi
Can anyone tell me how can i adjust a delta update for a characteristic?
Regards
S

Hi Sancho,
A great deal of InfoObjects carrying master data and texts are already delivered delta-capable (e.g. 0MATERIAL_ATTR, 0CUSTOMER_ATTR).
The master data extraction in the delta mode is possible for a large number of R/3 tables and views. To do this, the transaction for which data is to be created and changed must be linked to the change document update. This service has been implemented for most of the master data in the R/3 System.
The update occurs in most cases for the transparent tables in which R/3 master data is stored (for example, for MARA or KNA1). If a field changes in a data record of the table the key to this record is recorded in a delta table. When reading the table in a BW, this key is used to fill the extract structure. Thus, you can extract master data delta in several ways:
The extract structure equals the transparent table in the database, whose maintenance is added to the change documents.
The extract structure is a view over one or more transparent tables whose maintenance is added to the change documents, for example, a view via KNA1 (customer) and KNB1 (customer and company code).
A basic requirement for the usability of a table for an InfoObject is that the key for this table explicitly specifies a record of the extract structure (key word compounding). Besides, you should make sure that the data elements of all the extract structure fields are relevant to the change document in the respective table. In other words: as soon as a field changes a record which is part of the extract structure, it must be updated in the delta pot.
According to the assignment InfoObject/table, the following steps must be executed:
1. Check, whether the ALE changepointer are active in your source system (Transaction BD61) and whether the number range is maintained (Transaction BDCP).
2. In addition, check in the ALE Customizing, whether all message types you need are active (Transaction SALE -> Model and implement business processes -> Configure the distribution of master data -> Set the replication of changed data -> Activate the change pointer for each message type ).
3. Check, whether the number range for the message type BI_MSTYPE is maintained (Transaction SNUM -> Entry 'BI_MSTYPE' -> Number range -> Intervals). The entry for 'No.' must be exactly '01'. In addition, the interval must start with 0000000001, and the upper limit must be set to 0000009999.
4. Go to your BW system and restart the Admin. workbench.
All of the following activities occur in the InfoSource tree of the Admin. Workbench.
5. Carry out the function "Replicate DataSource" (1.2 local meta data upload) on the affected attached source system for the InfoObject carrying the master data and texts.
6. Activate the delta update
a) for master data and textsby activating the transfer rules.
b) for texts the entry is in the menu of the right mouse button via the source system: Activate the text delta transmission.
All changes, all initial data creations and deletions of records from now on are recorded in the source system.
7. Create an InfoPackage for the source system. In the tabstrip 'update parameter', there are three alternative extraction modes:
Full update
Delta update
Initialization of delta procedure
First, initialize the delta procedure and then carry out the
delta update.
Addition for incorrect delta requests:
After an incorrect delta request, you often have to re-initialize. A possibility of avoiding this consists in setting the incorrect request manual via QM activity to green. If the request was processed successfully in the source system, and was finished with the information IDoc 'Data selection ended', but the BW reports a processing error, the request must be re-initialized in any case in order to avoid data inconsistencies.
Constraints
The total length of the key fields in the table or view for which change pointers are produced must not exceed 70 characters.
Transferring deleted records using the ALE delta is impossible since a corresponding indicator is missing in the extracted record.
Hope this helps.
Thanks
CK

Delta update for Cube : 0CRM_PRI - Service Orders and Confirmations: Item

Dear experts,
For Cube : 0CRM_PRI - Service Orders and Confirmations: Item
Source data is from Two ODS
1. Confirmations (Item Data) : 0CRM_CNFI and
2. Service Orders: Item Data : 0CRM_PROI
I have done Init upload to this cube from both this ODS.
I am not getting delta option to this.
When I am trying update Delta after init from ODS message is No new deltas in DataStore object 0CRM_PROI for update. No delta option available . It is showing Initial and Full Update option only.
How i can initiate delta option for this Cube ? Please update us.
Thanks in advance.
Regards,

Hi,
you can use DTP's to laod data from ODS to cube .. it will take deltas ..
With a data transfer process, you can transfer data either in full extraction mode or in delta mode. In full mode, the entire dataset of the source is transferred to the target; in delta mode, only the data that was posted to the source since the last data transfer is transferred. The data transfer process controls delta handling and therefore allows you to fill several targets with different deltas from one source. With a data transfer process, you do not need to explicitly initialize the delta method as you do when copying data with an InfoPackage.
or you can create a sepeate Ip for delta apart form full and init .. that will laod delat data in cube ..
Regards,
shikha

BI Query Statistic - Delta Update for 0TCT_C01.

Hi gurus,
I have installed certain Standard content objects (Infoproviders and respective queries). One of such infoprovider is 0TCT_C01. I donot have a process chain for this infoprovider, hence I load data every morning manually into this cube via a delta.
The number of records that come in with first delta run for the day is around 400 - 500. Yesterday, I ran this delta in the afternoon as well And I got 4 records in the update.
Now, this cube would have details as to how many times a particular query has been run, How many queries have been run for the day, what are the users etc.
My question is that when I ran the delta the first time in the morning, i got 450 odd records, but how come the count is so less when I ran it in the afternoon.
One thing I would mention is that there are a lot of users who use a lot many queries very frequently, so its would not be correct to say that only few queries have been run since morning.
Could anyone put some light on this.
Rgds,
Sree.
Edited by: Sree Nair on Oct 15, 2009 7:51 AM

No update,
So closing the thread

Delta Update for ODS

Similar Messages

Maybe you are looking for