Delta load related

Hi experts,
I have changed the data source for 0CRM_SRV_PROCESS_H and now I want to move it to production, but in production already we have delta pull for 0CRM_PROH ODS.
When this change will take place how do I restore delta pull??
Regards,
Priyanka Joshi

to fill the new field you will have to do init with data transfer or init without data transfer and full repair requests.
If you want to load all the history again then after transports do a new init with data transfer..If the amount of data is not huge or do init without data transfer and do full repair loads so that you can manage the data loads.
Since the loading is going to be for the whole history again therefore I dont think you need to lock the system.The only problem could be the records getting created at the time of init.
So you amy need to lock the system only for the time you do an init without data transfer.

Similar Messages

Generic Extraction Delta Loads

Hi Experts,
I am facing problem is I want to extract the data in Generic Extraction in View, Suppose my requirement is I want to delta loads every 1 hour per day, how can i do, Generic Extraction possible are not delta records.
Note:- LO Extraction is possible like we have update mode we can scheduled hours in everyday, But Generice Extraction possible are not.
Please provide me solutions ASAP.
Thanks in Advance......
Regards,
Bharathi.

There are various delta method
1.calday.
2.time stamp.
3.Numeric pointer.
For youe requirement Time stamp will work.
Please check weather you have any field related to time.
Thanks,
Saveen kumar

Problem with delta load urgent!!

Hi,
I have a problem with delta load
We have an IP, which loads data from R/3 system daily, its a delta load to the ODS and it updates to the cube with the selection on Company Codes and 0FISCPER
we are in 3.5 system
For a couple of company codes A & B, the init was done for the period 07.2010 to 12.2099 and after tht the deltas are loaded from 07.2010 till 12.2099 and there's no pblm with tht
Now, there was some updation in R/3 system and the data was maintained for the company codes in A& B for the FISCPER 001.2010 to 006.2010, for which init wasnt maintained...
now how shall we need to load the init in this case? dnt ask me how the postings was done in R/3, but my pblm is purely related to the loading data in BW from R/3, as its very imp for the customer to see the data from 01.2010 to 12.2010 in reports, but the data was only available in reports from 07.2010 onwards
do i need to create another IP and maintain the init for 01.2010 to 06.2010? so tht this selection will automatically appear in the ODS delta loading infopackage
pls throw ur inputs ASAP
thank you

Hi Prince,
No need to maintain any Init for this data, It will be enough if you can load the data from jan 2010 to jun 2010 into your Info Cube.
Follow the below steps:
1)create full load IP for this data source.
2) give the selection as A and B company codes and 0FISCPER as 001.2010 to 006.2010
3) in menu bar, click on scheduler --> select full repair request
4) In the next screen check the check box and save
5) Now execute the IP, it will the data with out disturbing your daily delta.
follow the same procedure to load data till to your Info Cube.
Please revert if you have any questions
Regards,
Venkatesh

Invoice/payment delta loads

We have a web application that displays project/WBS related invoices and payments. We have found that different clearing document types, payment types, credit memos, etc. cause issues with delta loads to this application.
Has anyone addressed this topic before? In the web app, the user wants to see invoices (revenue) by WBS and the corresponding payment(s) - sounds easy but the way data is stored in BSEG, BSAD, BSID, etc., we have found that it is not so easy to do it by WBS.
Any help is appreciated.

Matt,
We are currently using a function module that the ABAPer wrote. This is not SAP BW but it is a case of sending data to an external system so if you think there is another forum that is more appropriate, please move it.
Thank you,
bak

Delta Load - BI Statictics 0 records

Hi All,
I have loaded Init successfully for all the infoprovider related to BI Statistics. But the delta loads are bringing 0 records then I checked in RSA7 and found no records.
Please help me how to resolve this issue.
Regards,

Hi Vikas,
I will tell you how I did the setting for the statistics -
1. Allowed all the Infoprovider for statistics collection (RSA1-Tools-Setting BI Statistics---Selected Infoprovider changed Defalt setting to X mode).
2. Init load for all Statistics cubes.
While running Delta No records are updated.

Error in activating init flag for delta load

Hi everybody, I am trying to activate the init flag for delta load, when I schedule the infopak it is taking too long to execute and the status is remaining in yellow for a week. I checked in details tab the error message is u201C no data available in source system u201C Please helpu2026

Hi Vinod,
When there is no data available in the source system, you will have yellow flag for the delta init request. Check for the delta queue entry (RSA7) on the source system. Delta mechanism starts working once this flag is created. After that schedule the delta infopackage.
Also check on the source system whether there is any data avilable in the application tables related to this datasource. Take the help of functional consultants if required.
Regards,
Sreenivas.

Missing Data in 0FI_GL_4 delta loads.

Hello All,
We successfully loaded the 0FI_GL_4 related ODS upto 02/06. We turned on delta loads for the same from 03/06. The data validation team has discoved that there is missing data in 03 and 04. I plan on resetting the delta queue in R3 and reinitialize a full load until april. Here are my questions
1) Are there any specific steps i would need to follow?
2) Are their any other better alternatives then reinitializing with the full load.
Thanks in advance.
Kiran

Initialization Concept :
I will explain this with an example.
You have 5 company codes (CCs) (1000, 2000, 3000, 4000, 5000) in your R/3 source system.
But your client wants reporting in BW only for 3 Company codes (CCs) (1000, 2000, 3000).
In that case, there is no point in bringing the data for other 2 CCs.
So during Initialization, you give the inputs as,
CC = 1000, 2000, 3000 and do a Initialization (With or Without Data transfer)
So henceforth, when Delta is pulled, any changes corresponding to CCs 1000, 2000, 3000 only will be captured.
Eventhough there are changes in 4000 & 5000, they will not be captured in the Delta.
Hope I answered your Question.
Regards,
Balaji V

Delta loading to BW and archiving

Hi Expert
We have ERP2004 and BW. For loading data from ERP2004, we use both full and delta upload. We are currently planning to implement archiving in ERP2004.
Especially MM PO (purchasing order) documents is the target for archiving. I have question here.
If we archiving tables which are loaded to BW with delta upload, is data in BW also deleted?
We do full loading to BW for PO document table, but related tables like STXH, STXL, ADR2, ADRCT, we do delta upload. I am afraid that data inconsistency will occur.
Thank for your advice in advance.

In my opinion, if you are using standard data sources for loading in delta mode, it will delete archived documents from BW tables also unless you write a specific routine for field ROCANCEL and value R (used for deleted records).
In case of full load, data will not be deleted from BW system unless you are doing a delete and full.
If you are doing a delta load using generic data sources, it will not bring any deletion to BW system unless you have specifically written some code to find the deleted records and send those to BW.
I hope it helps.
Regards,
Gaurav

Question for delta loading

Hi, Gurus,
I load data from a flat file into one infocube with delta loading option, and in the related datasource, i chose 'additive delta' option.
However after delta initial and delta update, when I checked cube content, I found that there are 2 records with the same characteristic value (just like duplicated key), and my expectation is to sum key figure with the same characteristic. Who can help me on that?
BTW: when I check delta queue, why there is not any queue?

Ls,
Please do not post same question in both forums - please refer the answers in the other post in the other forum.
Arun

Question for delta loading, why can not update existing record in cube

Hi, Gurus,
I load data from a flat file into one infocube with delta loading option, and in the related datasource, i chose 'additive delta' option.
However after delta initial and delta update, when I checked cube content, I found that there are 2 records with the same characteristic value (just like duplicated key), and my expectation is to sum key figure with the same characteristic. Who can help me on that?
BTW: when I check delta queue, why there is not any queue?

Hi,
In uploading of flat file , If you are able to capture the changes to the previously loaded records, Then you can follow the additve delta. So it decreases the time of uploading .Only changed or new records will be uploaded every time.
If you are not able capture the changes in flat file ,Every time you have to do full upload ,Before this delete the contents of Infocube. (Assuming there is no ODS B/W Infocube and Flat file).
With rgds,
Anil Kumar Sharma. P

Populate setup table impact on delta loading

Hi Expert,
For a ECC standard data source supporting delta mode; Taking 2lis_03_bf for example, now DSO A is loading data from 2lis_03_bf; but there are new requirement need to load the history data from this data source. So i want to populate the setup table of 2lis_03_bf and then make a full upload to another DSO B. If i do this, any impact on delta loading to DSO A ?
In my opinion, populating the setup table is not impact on the delta loading data to DSO A ! Because delta loading is related to Delta Queue and full upload is related to setup table.
Thanks,
Dragon

Hi Draco,
Are you in 3.x or 7.0 version?
This scenario needs to be addressed diffferently based on the version.
If its 3.x version, then you need to create a full repair request (Overwrite mode in DSO A) and load the data into two targets
or
Create a full update infopack, remove tick from data target tab for DSO A and load to DSO B.
If 7.x version.
Create a full upload info pack and extract the data into PSA and using the new DTP from PSA to DSO B.
Create another DTP on PSA to DSO A and do the inti without data transfer and run regular deltas. If you dont do this, then the DTP for DSO a will pick up the full update request from PSA in delta run.
Gurus: what are your comments on this approach?
thanks
Srikanth

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.

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.

Delta Loads are not working: 0FI_GL_10 With enhancement : HR Data in source

Hello Friends. Thanks for your answer on theory which I know, Please help me with this situation. I read all the sdn response to my message and have below for your suggestion
QUES1: Why the 0RECORDMODE is not coming in Standard DSO and hence it is not there in Transformation in between Infosource and DSO. What do I need to include 0RECORDMODE in standard DSO. What is the correct OSS to Implement on SP 10 to solve this.
Ques2. As suggested by you If I run the Delta loads after waiting for 1 hour of Init load. say init load was done at 11 am . i will do the delta at 12:10 am to psa via Infopack and then wait for an hour to run the DTP from PSA to DSO. Delta Records come in but it also bring in the records in DSO that are not changed from about 7 hours in ECC. and make our total Balance incorrect.
Ques3: We have this Cocatenation of Keys in DSO since we exceeded the total number of 13 key in DSO.
Cocatenation#1 GL ACCT and CHRT OF ACCTS
Cocatenation#1 SEGMENT AND CONT AREA
Cocatenation#1 Version, Value Typem, Valuation view, Currency Type.
<b>
Since business want to include HR Data in Keys Like Employee Number, Emp Code, EMPSPIMCODE. Payroll ID and I can not remove these fields from Key in DSO as per the business.</b>
Also the above fields GL ACCT , CHRT OF ACCTS, SEGMENT, CONT AREA
exist in Data FIELDS OF DSO. so what are the steps to modify the design to fix this asap.
Please email me at [email protected] if you have any docs to resolve the above
Thanks
Soniya
null

Did the full load bring all records from sourcesystem to PSA?
Was this an issue with the first delta you have tested ?
Concatentaion of multiple keys into one should not be an issue here as that must have been happening in DSO and delta brings incorrect records to PSA itself.
Are you validating delta records against FAGLFLEXT inputing the timestamp value or RSA3 ..how ?
<b>Check if this note helps</b>
Note 1002272 - NewGL-DataSource 0FI_GL_10, 3FI_GL_*: Missing record.
Is delta bringing incorrect records to PSA or DTP brings incorrect records to DSO from PSA ?
May be you should revisit the logic behind for the enhancement of 0FI_GL_10.
I am facing a similar issue as well but here delta doesnot even bring a single record ( ODS has 20 keys )...will update if resolves and you do the same.
Message was edited by:
Jr Roberto

Delta load related

Similar Messages

Maybe you are looking for