Initialize the delta load

Hi BW Experts,
I have question...
1. There is a ODS01 which feeds many data targets.
2. We created a ODS02 which also will be loaded by this ODS01. The update type would be DELTA.
3. We created a INFOCUBE01 which will be loaded by the ODS02. The update method would be FULL UPDATE.
4. The first time (later on i didnt get this msg) when i went to the infosource for the 8ODS02 and tried to create a infopakge to load the full update of the INFOCUBE01, i got a msg that " THERE IS NO ACTIVE DELTA INITIALIZATION FOR THIS DATASOURCE".
The details of the msg is:
Procedure
You have to initialize the delta load for a DataSource before you are able to load the delta data from it.
If you want to load deltas only for the purposes of testing, or you do not require any initialization data (because you have already uploaded it using a full upload, for example) use an initialization simulation.
This way, only the init. entries you require are made in the control tables of the source system, and a 'dummy' entry appears in the Monitor, setting the load status to green.
No data is in fact loaded, however, and the initialization takes only a few seconds to complete.
Does this mean i have initialize the delta load in the ODS02 or the INFOCUBE01.
How do i do that ?
(I actually did few full loads then i was informed that it would be a delta load from the ODS01 to ODS02,
within the infopkg for ODS02, I selected the Delta update next time, and did start immdtly, then check the monitor, it displays no records)
I'm little confused with this initialization, and in what cases would i do it.
Would you please help...
Thank you,
Tia
Message was edited by: Tia Ismail

1. so, you are saying for the ODS02, do a full load first.
2. Then do a "Initialize delta process".
3. Then do a "delta process".
I had partially tried this, I did a full load first in one infopackage, then created another infopackage trying to do a "Initialize delta process". I get a msg as following:
Diagnosis
Deltas have already been loaded for the init. selection of request REQU_3ZEHH34LV68LVHAWT75TJVIF8. A second initialization is therefore not possible with these selection conditions.
Procedure
If you want to carry out a new initialization, you have to choose selections that do not overlap.
If you want to repeat the init. for the same selection, you have to delete the delta queue in the source system, and restart the delta process.
Choose the menu entry 'Init. Selections in the Source System' from the Scheduler.
Any thoughts...
Thank you,
Tia

Similar Messages

COPA Realignment in R/3 -do i need to Re-initialize the Delta Process in BI

Hi frnds,
Im facing an issue related COPA realignment,
1.Once the COPA realignment is done in R/3, Do i need to Re-initialize the Delta Process in BI?
Edited by: MohanDP on May 4, 2011 8:37 AM

But i need historical data too,so how to avoid Re-initialization to get historical data.Can u please help
if you need the changed historical data, you have no choice but to reinit. you can do this at anytime, you don't need any downtime for copa init.
M.

Duplcate records in the delta load

BW experts,
I am getting the following errors when doing a delta load from 2LIS_02_ITM
into OBBP_CON, 0BBP_INV, 0BBP_PO, 0SRCT_DS1, 0SR_VEGUID.
The delta loads show a green light for all the targets except 0SR_VEGUID and
the error message is
3 Duplicate record found. 2295 records used in /BIO/XSR_VEGUID
3 Duplicate record found. 2295 records used in /BIO/PSR_VEGUID
I tried to check the contents of the both /BIO/XSR_VEGUID and
/BIO/PSR_VEGUID but i get a message saying the tables are not active in the
dictionary.
However, i can view the data in the Info object OSR_VEGUID.
How can i resolve this issue ?
Any help will be appreciated.
Many Thanks

Kiran,
Welcome to SDN,
P and X tables are created only if you have 1. Time dependent Navigational Attributes ( X Table)
2. Time Independent Master Data Attributes.. ( P table)
Otherwise the tables will not be created.
Arun
What table do you see in the header when you see the data for the infoobject ? on the creen - do you see something like
/bi0/XX0SR_VEGUID where XX xould be some characters ... Ideally P table should be viewable...

Issue in the Delta load using RDA

Hi All,
I am facing an issue while trying to load delta using RDA from R/3 source system.
Following are the steps followed:
1. Created a realtime Generic Datasource with timestamp as delta specific field and replicated it to BI.
2. First I have created the Infopackage(Initialization with data transfer) and loaded upto PSA.
3. Created a standard DTP to load till DSO and activated the data.
4. Then created a realtime delta infopackage and assigned it to a Daemon.
5. Converted the standard DTP to realtime DTP and assigned the same to the Daemon.
6. Started the Daemon, giving an interval of 5 minutes.
In the first time, Initialization with data transfer is taking the records correctly. But when I run Daemon for taking delta records, its taking all the records again, i.e. both the previously uploaded historical data and the delta records).
Also after the first delta run, the request status in the Daemon monitor, for both Infopackage and DTP changes to red and Daemon stops automatically.
Can anyone please help me to solve these issues.
Thanks & Regards,
Salini.

Salini S wrote:
In the first time, Initialization with data transfer is taking the records correctly. But when I run Daemon for taking delta records, its taking all the records again, i.e. both the previously uploaded historical data and the delta records). .
If I understand you correctly you Initially did a full load. Yes? Well next you need to do intialise & after that delta.
The reason is that if you will select delta initialisation & initialisation without data transfer- it means delta queue is initialised now & next time when you will do delta load it will pick only changed records
If you will select delta initialisation & initialisation with data transfer- It means delta queue is initialised & it will pick records in the same load.
As you know your targets will receive the changed records from the delta queue.
Salini S wrote:
Also after the first delta run, the request status in the Daemon monitor, for both Infopackage and DTP changes to red and Daemon stops automatically.
I take it the infopackage has run successfully? Did you check? If it has and the error is on the DTP then i suggest the following.
At runtime, erroneous data records are written to an error stack if the error handling for the data transfer process is activated. You use the error stack to update the data to the target destination once the error is resolved.
To resolve the error, in the monitor for the data transfer process, you can navigate to the PSA maintenance by choosing Error Stack in the toolbar, and display and edit erroneous records in the
error stack.
I suggest you create an error DTP for an active data transfer process on the Update tab page (If key fields of the error stack for DataStore objects are overwrite On the Extraction tab page under Semantic Groups, define the key fields for the error stack.) The error DTP uses the full update mode to extract data from the error stack (in this case, the source of the DTP) and transfer
it to the target that you have already defined in the data transfer process. Once the data records have been successfully updated, they are deleted from the error stack. If there are any erroneous data records, they are written to the error stack again in a new error DTP request.
As I'm sure you know when a DTP request is deleted, the corresponding data records are also deleted from the error stack.
I hope the above helps you.

Initialization of delta loads possible with process chain?

hello all,
followed situation:
i load data from file and sap extractor to ods 1. from this ods i have an automatic delta load to another ods 2, where the data are filtered and aggregated.
its possible that some of the data change their state from filtered out to in but are not in ods 2 because of the earlier criterias they had have. now i want a weekly load (initial load) from ods 1 to ods 2 and a daily delta load if new data arrived ods 1 to the no 2.
i tried to create a process chain for that but i cant! i cannot use the info package for the initialization of the load from ods 1 to 2 because it is generated info package. and if i use the process "update ods object data" there is always tried to make a delta load! at first step i delete all data of ods 2, so i need an initialization with data as next step.
how can i do what i want?
thanks for any idea
Frank

Hello Tom,
ok, i understand but i dont know how...
The only way i know to create an InfoPackage between ODS is to use "Update ODS Data in Data Target" of the context menu of an ODS. Then i chose between full/delta/init load and the infopackage will be generated. How else can i create it?
Frank

How should I reload the delta load?

Dear all,
An ODS which includes Sales invoice information with daily delta load. The loading is fine but somehow one KF got different logic from April e.g. for same order this KF has correct value after April but incorrect value before April. So I am going to reload data old than April, but all the old load are fine and existed, so how should I do?
Thanks

Hi,
Thanks for you reply, No date for selection. So I found some data in the ODS for a specific comany code and the bill type(I got 16 recordes), then I created a Infopackage then put the selection same with the company code and bill type, set it to full load and run immediatly, but 0 record was loaded. I am sure the corresponding data exist in R3 because I checked the data using VA03. So what's the problem?
Thanks in advance

The delta load for generic machine in CRM doesnt run.

When the machine was dismantled from a location and installed on a different Functional location. The changes didnt download to CRM. Even the request load fails for the same. The machine is a generic Machine.
In R/3, the queue is in STOP status and gives the error Generic stop set on activation.
User had changed the Functional Location for a Generic machine in R/3. The changes didnt upload to CRM. Even the request load failed to upload the changes.
The Idoc is failed on R/3 , it gives the error message - Generic Stop Set.
Thanks in advance

Hello Mohammed,
I have also met with this issue in the past, and I have resolved it by steps described in this link: http://scn.sap.com/docs/DOC-56972
Hope it helps.
Best regards,
Jerry

Doc. for using 'Simulate the Initialization of the Delta Pro'

Hello!
I am trying to find documentation on using the 'Simulate the Initialization of the Delta Procedure' in the SBIW of the SAP R/3 system 3.1i.
If anyone can provide the documentation or a link to the correct source, I woul appreciate it greatly.
Thank you,
Sharon Bomberger
[email protected]

Hello Sharon,
jere is the documentation:
Delta process initialization simulation
Use
If the delta process has not yet been initialized, but you want to test the delta upload, you have the option of simulating the initialization.
This runs the help entries in all the required tables in BW and in the source system, without loading any data from the source system.
In the monitor, you get a message telling you that a record has been loaded. The initialization-simulation request appears in all the data targets in which an update has taken place. However, this request contains only help entries. The simulation does not update any data in the data targets.
Dependencies
After you have tested the delta upload in this way, initialize the delta process.
Note
You are able to simulate the initialization of the delta process for extractors available as of PlugIn 99 (A), that is, BW-BCT 2.0.
Kind reg.
Michael

Delta load problem after Initialization

Hi everyone.........................I need your inputs on the following problem that I ran into:
I have an ODS which gets supplied by regular delta loads.
Accidentlly, I have deleted the Initialization(Info Package->Scheduler->Initialization options for source systems). Because of this the delta loads are broken.
I am now trying to fix this by Initializing it again(but without data transfer as I dont need all the data till this current point again). That worked successfully.
But the deltas after this initialization are causing a problem. The first delta that I loaded failed with an error :
"Delta Request REQU123XYZ is incorrect in the monitor.
A repeat needs to be requested. Data target (ODS) still includes delta request REQU123XYZ. If the repeat is now loaded, then after the load there could be duplicate data in the data target.
Request the repeat?"
I repeat the delta load and this time around it loads correctly.
The next delta that I load after this is again an error. The repeat of this is again a correct one.
This problem continues.
Can anyone throw some light on whats going wrong?
Thanks.

Hi Sat,
I tried your suggestion by turning the failed request manually to green.
However, for the next delta load, the info package just wouldnt allow me to initate a load saying that-
"Last delta update is not yet completed
Therefore, no new delta update is possible.
You can start the request again
if the last delta request is red or green in the monitor".
Although it says not yet completed, I can see that the request has failed.
Any more alternatives will be highly appreciated.
Thanks.

IDoc delta loads using the program RBDMIDOC

Hi ALL,
We are doing some delta loads for ALE-IDOC using the program RBDMIDOC and we are using the message type HRMD_A.Under this message type we have configured two diff distribution models with different infotype data.
So when we execute the program we have only one input parameter that takes the message type.based on our setup will the program send the delta loads for both the distribution models since they are using the same message type which we do not want.
How do we restrict the program to send the delta loads only for the intended distribution models even though they are using the same message type.
Thanks
Bala Duvvuri

Hi Bala,
Assuming that based on IDoc content there is some way to determine which system should be the recipient, you could do the following (requires ABAP development as indicated by Mylène):
Define a new filter object type if required via BD95.
Assign new or existing filter object to E1PLOGI segment field FILTER1 or FILTER2 via BD59
Create BAdI implementation for HRALE00OUTBOUND_IDOC and implement method FILTER_VALUES_SET to set values for FILTER1 or FILTER2
Even without the BAdI implementation you'd see the new filter value appearing in your distribution model for message type HRMD_A. However, you need the ABAP logic for filling the fields with actual values that you can utilize.
Cheers, harald

How to handle the error delta load?

Hi Experts,
We have a InfoCube include three InfoSource: 2LIS_11_VAITM, 2LIS_12_VCITM, 2LIS_13_VDITM.
The delta load of 2LIS_12_VCITM failed on Oct 23,2006. It blocked all of the latter data load, even though 2LIS_11_VATIM and 2LIS_13_VDITM load the data successfully. And 2LIS_12_VCITM didn't do any load step after Oct 23, 2006.
How should I do to fix this problem and make all of the data can be go into InfoCube correctly?
Thanks,
Lena

Hi Jerome,
Thanks so much for you help. Currently, the data loaded successfully.
But I have another issue, because of the failed request status is red, it seems it blocked all of data to go into InfoCube (even though the delta load is successful). I can not see the new data in the InfoCube. And in the InfoCube manage, the "Request for Reporting Available" field for the successful request is null.
How should I do?
Thanks,
Lena

Delta loading of the material classification

Hello,
I use 1CL_OMAT001 datasource on order to extract the material classification from R/3 into BW.
The load works in init/delta.
If I change the characteristic value from its value A to ' ' (re-initialized) in R/3, the delta loading will not take into account the modification in BW and therefore, in BW I will always have the value firstly defined (A). But I would like to see ' ' for that characteristic.
Fortunately, when I modify the characteristic value from A to B, the delta loading will take into account the modification and there will be "B" in BW.
Did you notice the same problem ? What did you do then ?
Anybody have a solution ?
Thanks for your answers.
Vanessa.

Hi,
we are using the same datasource and we planned to go for delta. but could not manage to do so. the data we are loading is in the range of approx 300000, so rather then going for delta we are doing full load daily with the deletion of previous request. when we think the data is getting huge we do a full load for a required period and the change the selection for the next.
eg: in the infopackage selection for last year we had fiscal year period set to 001.2005 to 012.2005 then once the year is over we change the selection to 001.2006 to 012.2006 and through out the year we have a max of 1 mil records so works fine with us. check this with your requirement.
Ravi.

Error while implementing Delta Load

Hello Experts,
I need your help.
I am trying to extract data from SAP R/3 to BI system.
The R/3 system contains data from 1999-2008 fiscal year. I extracted data for fiscal yr 2007,2006 and 2005 successfully and created a delta info package
In the delta info package I didn't specify any fiscal year limit under the Data selection tab.
I started a background job which needs to run daily. Now my issue is the load came up with an error stating time limit exceeded. I believe the number of data packets exceeded. The request showed a warning sign and it got stuck there. I tried to delete that request and consequently delete the whole delta info package and creating a delta package freshly.
But when I tried to start the process of extraction, the following message popped up. Please tell me what I need to next.
Init. select. for field name currently running in request REQU_464F7XQP5TZIEJPIS0MUV32IB
Message no. RSM1070
Diagnosis
Init. selection for field name with the 'From value' and the 'To-value' , is currently running in request REQU_464F7XQP5TZIEJPIS0MUV32IB.
Procedure
Wait until the init. selection is completed; check the load status in the Monitor.
Thank you. Appreciate your help.
Raj

Hello guys,
I tried to delete the delta request by right clicking on the infopack and hitting manage, and then selecting the particular request and hitting delete.
But when I tried to create a new infopack and initialize it it constantly gave me the same error saying that I need to delete the previous request.
There is another place where you need to delete the request from.
You need to double click on the delta infopackage and on the top menu click on
Scheduler > Initialization options for Source System > Now select the particular delta request and delete it.
This solves the problem and helps you to reintialize the delta load using the new delta infopackage

Issues with 0PP_C03 delta loads

Hi,
I loaded the data from 2LIS_04_P_ARBPL & 0PP_WCCP to 0PP_C03. Initialization of the data load went fine. Did the delta loads to BI and observed that I am not getting any of the Key figure data in the cube. All the values are showing as Zero.
When I observed the in the PSA table and in the RSA3 , I observed that for every order 2 entries got created, One is with +ve values and another with u2013ve. So at the end while updating to cube its nullifying the values. Because of this reason I am not able to view the latest data which is updated as Deltas.
I am not sure what settings I missed. Could some one please help me to fix this issue.
Thanks & Regards,
Shanthi.

Thanks Francisco Milan and Shilpa for the links. Itu2019s very useful. But still I didnu2019t able to find the cause of the issue.
My data source 2LIS_04_P_ARBPL is of ABR type and the update mode for KF is Summation. In the data source level, I am getting the values with before & after image (same entries one with +ve & another with u2013ve) and as I am using the u201CSummation as my update type for KF its getting nullified.
Because of this reason I could not able to get the values in my report. Could any one pls help me on this as I am reaching the go-live date. I need to address this issue immediately. Thanks for all your inputs.
Regards,
Shanthi.

DTP Full/Delta loads

I am loading data from one DSO to another. The change log of the source DSO has been deleted for any request before 20 days.
I want to do a full load from active table and then start the delta loads from change log. But the problem is the load is picking up all the previous deltas from change log again, instead of picking deltas after the full load.
Is there a way to do a "init without data transfer", like the option we had before - where it resets the delats so that only the deltas after the full load are picked.
Thanks. Points will be awarded.

Hello Sachin,
In BI7, there's no longer the notion of delta initialization. Just do a delta from your DSO.
Just load the full data in our DSO and launch the delta, then run the deltas for populating your DSO and the corresponding deltas from it.
Hope it helps,

Initialize the delta load

Similar Messages

Maybe you are looking for