Doubt in Delta Loading !

Hi,
I have a Doubt in Delta Data Loading
Please check the following Procedere is Right / wrong ?
I did Full Load it is successful.
I am doing Delta Loading.
For the Business Content Info Cube 0COPA_C01 --
CO-PA: Published Key Figures I am Loading the Data.
I am doing INIT & Delta Load.
This cube has the Data source 1_CO_PA_110_BILDA
I had checked in RSA6 : 1_CO_PA_110_BILDA
ExtractStruct : ZOXGDV0108
Direct Access : D
Delta Update is check -
First I Created a info package --
In Update Tab
Update Mode
Full Update
Delta Update
Initialize Delta Process
Initialization with Data Transfer
Initialize without Data Transfer
I have choosen Initialize Delta Process -- Initialization with Data Transfer
Then For the DTP --
In DTP -- Extraction tab -- Extraction mode is set to Delta.
There is no difference in Records when I loaded Full/Delta.
showing same records.
is the Right Procedure I followed !
When Next time I load Delta then I need to follow the Same procedure ?
Thanks
prasanna

Hi Prasanna
I thought that u r in to Bw 3.x
Ny ways in this case u should create a proces chain..
and schedule it in the start process it self .
Still there is one ancient option like define the subsequent process in the in fo pak
schedule once the PSA request is sucessfull then put a Event and then place the
same event in the start process or scedule process of DTP.
But as per Expert Suggestion U should Go for Process chain.
Thanks & Regards
R M K
**Winners dont do different things,they do things differently**
> Hi R M K thank you,
>
> if we do Info Pack -- schedule Tab
>
> In the option Start Later in background-- set
> periodic values
>
> Then it will update only in PSA.
>
> But if we want to get these Records in info cube
> we need to Execute the DTP.
>
> That is not doing.
> (selecting the option start later in background and
> set the periodic values is sufficiant)
> here you are not discussed for DTP.
>
> cause i don't want to load manually.
>
> How do we Execute DTP automatically ?
>
> thanks
> prasanna

Similar Messages

SAP Mobile Sales 2.0 delta load issue for Sales Orders

Hello,
we have used Mobile Sales 2.0 with a Windows app for a while now. Our current issue is that sales reps won't see any historical sales order data on their devices.
Background
Due customer requirements, we need to make small changes to customer master data attributes and reload all customers from ERP to CRM. Then we ran delta loads (MAS_PARTNER followed by all other objects) to DOE, in which virtually all 5000+ customer accounts were compared. The delta load ran for about 3 days (some performance bottleneck we haven't located yet).
During the delta load, data on devices was inconsistent. Accounts were missing and all transaction data disappeared. After the delta loads, all accounts and contacts are OK, save for a few. Data from activities (appointments, tasks) have reappeared, as they should. Only sales orders won't reappear. The sales orders exist in the backend and belong to active accounts and sales reps.
Settings and troubleshooting so far
We don't have any limitations for sales orders in CRM Sales Mobile configuration.
We've run delta loads for all objects in transaction SDOE_LOAD.
MAS_CUSTOMIZATION etc seem fine.
We've re-run initial load for sales orders from CRM.
In the test system, we've even reinitialized the whole CDS database on DOE and on the devices, then re-ran the loads.
Checked steps suggested in discussion
SAP CRM 2.0 initial load issue
Historical sales orders (those created before the master data reload) exist in the backend, but don't show up on the device.
If I change one of those historical sales orders in the backend, it gets sent to the device.
If I create a new sales order in the backend or on the device, it is saved and replicated just fine.
To sum it up, it seems DOE is unable to identify the sales orders relevant for replication.

First Doubt i got clarify by my self as we can go with Unwired Runtime option .
But i still have doubt in :
2. How can i Modifying the Main Menu for iOS.
i am able to customize the same for windows using files SybaseCRM.Configuration.xml file.
Same how can i do for iphone/ipad.

In BI 7 how do we handle if any delta load gets fails

Hello All
Iam having a doubt like,in BW 3.5 if we are loading delta data from one source ODS to 2 targets(either cube or ODS),and if for one target if the load gets failed we will delete the bad request from the 2 target ods , reomve datamart flag from source ods and then relaod the delta load again.
But in BI 7 how do we handle this type of scenarios.
Many Thanks
Swami

In 7.0 we have DTP between one source and one target right?
If a load fails then delete the concerned request and reload.
It is independent of the other load.

Problem in delta load with Z field

Hello Experts,
We have CRM 5.0 system and as per the requirement we have
added ZFIELD to BUT000 table. This field is added to BUT000 via EEWB – Easy
Enhancement Workbench. This field is also BW enabled.
BW enabled means – this field is used / available to BW
extractor for further analysis.
We update this ZFIELD with custom program – FM BUPA_CENTRAL_CI_CHANGE.
When full load is done – data flows to BW correctly, ZFIELD
values are reflecting correctly. But when we are doing delta load it is not
working.
If we use BP t-code delta works perfectly. So issue from BW
side is ruled out. The FM BUPA_CENTRAL_CI_CHANGE is not triggering the change
record for this BP. But then I don’t see any other FM / BAPI to use so that
change record is also created.
Could you please provide any pointers or any checks to
overcome this problem?
Thanks in advance.

Hi Ashtankar,
When you are changing the attributes(say ZFIELD) and save the transaction in BP, Is this updating the CHDAT(Change date) in BUT000?
If the change date is being applied, then Delta shouldnt be a problem - if you are using datasource 0BPARTNER_ATTR.
In order to check if the delta is being captured or not, you could use TCODE RSA7. Also, this brings the Doubt when you say Full load works while delta doesnt, try Re-initializing the datasource from BW after Datasource replication - because there have been some changes effective in Source system which the BW system/Delta queue might take into consideration.
Regards,
Thejas K

Doubts reg Delta

GM All,
I've seen several posts regarding delta's in the forum but coulnt get a clear picture..my doubt is:
With respect to V3:
1.Once initialization is done does delts gets into delta queue automatically or does we need to run an IP?
2.when we run an IP for delta does the data be fetched from delta queue i.e RSA7 in R/3?
3.Is there any queued delta which comesinto picture before deltaqueue(RSA7) if so what's the use?
Plzzzzz clarify..
Madhavi

Hi Madhavi,
1Ans:
When ever you done the initial Load then delta will enable automatically at BW side and also you can check at RSA7. then we can do delta loads
2Ans:
Yes, delta record come from RSA7
3Ans:
Yes,
in LO Cockpit here delta methods are 3 types
1 Direct delta : delta records directly comes into RSA7.
2 serialized delta : delta records comes into SM13 and than thru V3 Job, records come into RSA7.
3 queued delta : Delta records comes into LBWQ than into RSA7 thru V3 Job
I think u may get an idea about your questions.
Let me know if you have any doubts.
Thanks,
Raju
Edited by: Raju Eegu on May 15, 2008 8:00 AM
Edited by: Raju Eegu on May 15, 2008 8:02 AM
Edited by: Raju Eegu on May 15, 2008 8:18 AM

Delta load from r3 to bw ?

i have one question on the mechanism of data transfer from r3 to bi 7.0. the followings is my concerns:
scenario:
The total numer of data is 1000 rows and these rows are seperated into 10 data package , each package contains 100 rows.
Now bw is trying to recieve these 10 packages from r3 in sequence.
When 5 data packages have been transfer to bi psa. the network is broken and the tranfer is canceled at the 6th data package.
What i want to know is when the network is reconnected ,Does the transfer start from the 6th data package?
How to find out whether its a delta load or a full load if a transfer is scheduled from r3 to bw ? For both CUBE & ODS.
How to find out how many records have been transfered from r3 to bw while the transfer has ended in
the middle ? I mean how to check how many records have been successfully transfered from r3 to cube/ods .Please tell me for ods as well as cube.
Is the continuation of transfer process is same for both ODS & INFOCUBE, if it ends in the middle ?
What is the procedure for full load & Delta load in case of CUBE & ODS ? I mean how to reschedule the transfer.
And if the whole scenario is is in the support, SO I will be handling these issues on the live production server. Am I right ? So in this case my user id should have access to all the production r3 and production bw to do these change status to red and delete the request and reload the request etc., So I should be logging on to the production server and do all the manipulation, Am I right ?
Last doubt, what is repair request and so if the transfer stops in the middle we change the status to red and reload the request again , Is it called repair request ?
What is the difference between repeat delta & repair request & repair delta ? When do we choose these options, In which scenarios ?
How do we schedule a daily load job from r3 to bw without the use of process chains ? I mean daily it should fetch the records from r3 to bw from the SD datasources at 10.00 PM ,how do we do that ?
Please I am having all these doubts and I want you SAP experts to answer them please so that I can clear my doubts in production support . I really appreciate if someone explain me the scenarios here. It will be a really great help if someonce clears these doubts.

Hi......
What i want to know is when the network is reconnected ,Does the transfer start from the 6th data package?
If your connection is broken in between......inspite your load is through PSA...........you have to delete the request from the target(after making the QM status red)............then you have to reload it again............But before repeating the load check the connection is ok or not in SM59........
How to find out whether its a delta load or a full load if a transfer is scheduled from r3 to bw ? For both CUBE & ODS
This you can check in IP scheduler in the Update tab...........whether it is delta or full load.......
or you can also check in IP monitor(You can go here through RSMO..........IP monitor screen will open directly here............or you can also go through RSA1>> Find your IP >> Double click on it >> Click on the monitor icon in the top >> From the you will go to the IP monitor>> the under the Header Tab you can see whether it is a delta or Full update...........
Or you can check the datasource also..........
If it is a generic datasource go to RSO2..........and check...........If it is a standard datasource check it in RSA5...........
How to find out how many records have been transfered from r3 to bw while the transfer has ended in the middle ? I mean how to check how many records have been successfully transfered from r3 to cube/ods .Please tell me for ods as well as cube
Your load cannot be ebded in the middle.........it can failed.............if it fails then you have to delete the request from the target..........and then repeat the load.......
Is the continuation of transfer process is same for both ODS & INFOCUBE, if it ends in the middle
Yes.........
What is the procedure for full load & Delta load in case of CUBE & ODS ? I mean how to reschedule the transfer
If a full or delta load fails after extraction got completed due lock issue or SID issue.....etc..........and if you load is through PSA.............then just delete the request from the target without making the QM status red.......and reconstruct the request.........no need to repeat the whole load again........
But if you r load is not through PSA..........then make the QM status red........delete the request from the target........and repeat the load...........
And if the whole scenario is is in the support, SO I will be handling these issues on the live production server. Am I right ? So in this case my user id should have access to all the production r3 and production bw to do these change status to red and delete the request and reload the request etc., So I should be logging on to the production server and do all the manipulation, Am I right ?
Yes.......
What is repair request and so if the transfer stops in the middle we change the status to red and reload the request again , Is it called repair request or reload request?
Suppose you delta load has failed ............and you have deleted the request from the target without making the QM status red............In this case your data will be lost and your delta mechanism will get corrupted............In this situation.............
1) Delete the init flag........
2) You have to do Full repair..........(After filling the set up table)
3) Init without data transfer to set back the init flag
4) Then Delta upload.............
In case of an ODS............you cannot load Full update and delta upload parrallely..............Your ODS activation will fail...........suppose you want full upload in the ODS..............then you have to go for Full repair............
What is the difference between repeat delta & repair request & repair delta ? When do we choose these options, In which scenarios ?
I think Full repair concept is now clear............
Suppose your delta load fails...........After that you delete the request after making the QM status red............Then system will ask for a repeat delta when you will try to repeat the load...........which means it will pick the same delta records of the failed load..........
How do we schedule a daily load job from r3 to bw without the use of process chains ? I mean daily it should fetch the records from r3 to bw from the SD datasources at 10.00 PM ,how do we do that ?
This you can do via infopackage or infopackage group...........schedule it at the specific time.....
Check these links :
http://help.sap.com/saphelp_nw04/helpdata/en/20/ad673844a7114be10000009b38f842/frameset.htm
Re: Schedule Infopackage for last day of a fiscal period
Hope this helps you.........
Regards,
Debjani...........

BPC 7.5: Delta Load when loading from BI InfoProvider

Hi,
in BPC 7.5 running a package based on Process Chain "CPMB/LOAD_INFOPROVIDER" loads data directly from an SAP BI Infoprovider into an BPC-Cube. According to the options you can choose "Merge Data Values" or "Replace & Clear DataValues"
According to the description the first one "Imports all records, leaving all remaining records in the destination intact", the second one "Clears the data values for any existing records that mirror each entity/category/time combination defined in the source, then imports the source records".
I tried both and both (!!) result in what you would expect of "Replace & Clear". Both firstly create storno-records in the cube and then add the new values.
Is this an error or wanted behaviour? I didn't find any SAP Notes on this topic, but doubt it's right....
Is there any way to achieve an Merge or - even better - a delta load?
Thanks a lot for any input given.
bate

Hi Bate,
It is indeed a bit confusing. I'll translate the BPC-speak for you
Replace & Clear:
1. Look up all CATEGORY/ENTITY/TIME combinations in the incoming data
2. Clear all records in application with the same CATEGORY/ENTITY/TIME combinations that exist in the incoming data records
3. Load incoming data to the cube
Merge:
1. Load incoming data to the cube record-by-record, overwriting existing data.
This means that "Replace & Clear" might clear out existing records in the cube that do not share the full key of incoming records but do share the CATEGORY/ENTITY/TIME dimension values. For example, a records with CATEGORY/ENTITY/TIME/ACCOUNT values of ACTUAL/1000/2010.JAN/ACCT1 would be deleted when loading an incoming record with values ACTUAL/1000/2010.JAN/ACCT2, if you use the "Replace & Clear" method, but would not be deleted if you use the "Merge" method.
There is no option to load data additively, like it is loaded to a BW InfoCube.
Cheers,
Ethan

Does APD support delta load?

Hello experts,
does the APD support delta load of data in case the data target is
1. a DSO?
2. an InfoCube?
Many thanks in advance,
Marco

Hello Marco,
As far as APD is concern with data source DSO's, it supports only Direct update DSO..& Direct update DSO not support Delta ,hence have an intermediate standard DSO before the Cube which will capture the Deltas....
The flow should be like,
Direct DSO-->Standard DSO --->Cube
Hope it clears your doubt scenariowise.
Thanks,
Santosh

Delta load Error in LO Cockpt

Hi
If I get Error while Delta Load using V3 unserialized update in LO Cockpit....How can I rectify the problem ?
Thanks,
Abhi

Hi Pradeep,
This is the interview Question what I have.
In General, When we extract data from R3 LO Cockpit to BW ( Deltas )every load won't be success.
1. If I get an error in Scheduling the Job Control .. what I have to do ? Where I have to look ?
Is there any place to look otherthan SM37,Delta Queue(RSA7) and Update Tables(SM13)
2.While Delta loading...I have the data in Update tables but I didn't find in Delta Queue. How can I sove this problem ?
Please Clear my Doubts. Points will be awarded.
Regards,
Abhi.

Delta load after upgrade to 2004s - Functional changes

Hi All,
I have some doubts about Delta using DTP.
Our BI landscape has been upgraded to 2004s from 3.1 (technical upgrade). There are many existing delta loads and we cannot afford to mess anything at all. So my question to you all
When we do a functional upgrade...
1. The existing delta from 0FIL_GL_4, AP_4, AR_4, WBS_6, NWA_2 etc all having delta loads right now and go to DSO. The records are in many millions. It is highly unlikely they will allow me to delete the PSA and reload all, because it will take couple of months. So that is out of the question.
We have 3 situations.
1. Delta from Data Source into DSO.
2. Delta from DSO to Cubes
3. Delete from few Cube to Cube.
Questions
1. After converting from Info Package to DTP I will still load the delta from Data Source to PSA, but the data source need to migrated to 2004s. WIll it cause any issues in loading delta data?.
2. The DSO to further targets are using delta info package, I believe I change the info package to DTP with load mode selected as DELTA. Is this correct?
Thanks in advance.
Alex.

DTP is used to load data only from PSA to Datatargets and DELTA DTP Loads the last PSA request which was transferred to PSA from source.
So 2 plausible ways could be -
1)Delete all PSA data and so your DELTA DTP will get the DELTA load only or new changed posted to PSA only and not all the previous requests ..but you may not want to delete the PSA now.
2)Fake the DTP using some infoobject FILTER selection criteria as blank which acts like INIT w/t data transfer and then do DELTA DTP as mentioned below -
https://forums.sdn.sap.com/click.jspa?searchID=10026965&messageID=4743634
1. After converting from Info Package to DTP I will still load the delta from Data Source to PSA, but the data source need to migrated to 2004s. WIll it cause any issues in loading delta data?.
NO
2. The DSO to further targets are using delta info package, I believe I change the info package to DTP with load mode selected as DELTA. Is this correct?
YES
Hope it Helps
Chetan
@CP..

Re: Delta Load for master attribute CUSTOMER

Dear All,
I have got the delta loading into 0customer_attr and 0 material_attr in production. Yesterday the load failed because the previous change run run has been terminated and locked the attributes of characterstics 0 material and 0customer.
To solve this i went back and ran the attribute change run and all the locks got released.
Now i know that i need to repaeat the delta load.
If we go to the RSMO for the failed load i see that under details tab in processin option we have as follows
Transfer rules(67-->67 records):No errors(This is Green)
   Master data received:Processing being started(Green)
   Transfer 67 data records in communication structure(Green)
This is where the processing stopped.
Update(0new/0changed)(in red): Errors occured
My doubt is if i now repeat the load in process chain will the 67 records come into the0customer infoobject.
Will this have any impact on the next day delta load.
Kindly advice.
Regards
Madhuri

Hi abhijit,
When i tried to do a repeat delta the load failed again and when i check for the error message i get the following
Diagnosis
    The application program for the extraction of the data was called using
    update mode R . However, this is not supported by the InfoSource.
System Response
    The data extraction is terminated.
Procedure
    Check for relevant OSS Notes, or send a problem message of your own.
Procedure for System Administration
How do i proceed further.
Regards
Madhuri

Delta load after full load

Hi gurus
We are doing delta loads to a cube which is initialized in 2007.
Now we have some problem with the data cause 2 deltas are missing for Aug
so I just want to selective deletion for aug and i want to do a full load for aug
my doubt is
after that full load daily delta will be sucessfull?
Thanks in advance
Regards
a

Hi,
Before going on with the load, check the following points:
1. Check if all the delta has been moved up to the cube and all the data request in lower level has datamart status set.
2. If there are some request without data mart status move those reqeust to cube before doing the full load.
Then go for the selective deletion from the cube and reload as full update. You should be able to load delta further. There wont be any problem. Even if you have problem, since you have made sure that all the request has gone up and delta mart has been set in lower level you can break the init and reinit from lower level to current cube.
Hope this is clear.
Regards
akhan

Delta load to Full load

Hello Gurus,
As per my knowledge while creating delta load form R/3 to BW we need to declare the type of load in R/3 and in the infopackage ....
Where my doubt come on,
i need to convert delta load to full load for one info object ,is their any steps to do in R/3 for changing the type of load .
where i had just changed the load type in only Info package ...is it runs fine.
Plz assist me
Thanks in advance
SAP

Hi,
There is nothing specific needs to be done in R/3.
A data source is delta enabled but still you can load it through full load and in that case you need not do an initialization just schedule a full load package.
i need to convert delta load to full load for one info object ,is their any steps to do in R/3 for changing the type of load .
For this just delete the init which is present there and create the new package with option full update.Just make sure that the last delta is loaded for precaution.
Since infoobject is overwrite so no need to delete the data also every day there will be full load and it will bring the new data along with.
This wil start loading the full load into your object.
Hope it clears
Thanks
Message was edited by:
Ajeet Singh

About delta loading for master data attribute

Hi all,
We have a master data attribute loading failed which is a delta loading. I have to fix this problem but I have two questions:
1. how can I find the those delta requests because I need to delete all these failed requests first, am I right ? Master data is not like cube or ods that we can find the requests in Manage, for master data how can we find them ?
2. Could you please let me know the detailed procedures to perform this delta loading again ?
Thanks a lot

Hi...
1. how can I find the those delta requests because I need to delete all these failed requests first, am I right ? Master data is not like cube or ods that we can find the requests in Manage, for master data how can we find them ?
Look.....for master data.....no need to delete request from the target..........just make the status red.......and repeat the load.....But problem is that master data sometimes does'nt support Repeat delta..........if u repeat......then load will again fail with Update mode R.........in that case u hav to do re-init.......
1) delete the init flag.......(In the IP scheduler >> in the top Scheduler tab >> Initialization option for source system)
2) Init with data transfer(if failed load picks some records)..........otherwise .....init without data transfer.....if the last delta failed picking 0 records.......
3) then Delta.......
2. Could you please let me know the detailed procedures to perform this delta loading again ?
1) Make the QM status red.........to set back the init pointer.......
2) Repeat the load.....
After that.........if again load failed with Update mode R.....
1) delete the init flag.......
2) Init with data transfer(if failed load picks some records)..........otherwise init without data transfer.....
3) then Delta.......
Regards,
Debjani.....

Compare data in R/3 with data in a BW Cube after the daily delta loads

Hi Friends,
How can I compare data in R/3 with data in a BW Cube after the daily delta loads? Are there any standard procedures for checking them or matching the number of records?

Hi Sunil,
If you want to check the records daily instead of checking the data in R/3 manually ......
You can try this...
If you have staging DSO(level 1) that means whatever data is in source system load it to Staging DSO without any routines or any modifications.
Now load this DSO data to Cube or DSO(level 2) as per your requirement with routines etc.
Now Staging DSO contains Source system data.
Now the level 2 Cube or DSO contains BW data with some modifications.
Now create a Multiprovider based on level 1 and level 2 data targets.
Now create a report on which keyfigures you want to test the data.
In Multiprovider there is a field called 0infoprovider in data packet dimension.
you can drag this infoprovider to the columns and restict your keyfigures with level 1 and level 2 data targets.
In the first column you can see the level 1 DSO data ( source system data),in the 2nd column you can see the BW data.
Now create a formula which gives the diffrence b/n level 1 and level2.
that is R/3 data - BW data.
If the diffrence is zero both R/3 and BW data are same.
if the diffrence is not eqaul to zero check whether any routine is there or not.

Doubt in Delta Loading !

Similar Messages

Maybe you are looking for