Diff between init with data transfer and repair full request

hi,
i have observed that even in the new flow we are doing init without data transfer and then repair full request
if i do init with data transfer also i can achieve the same?
i want to know why we need to do this ,do we have any advantage of doing init without transfer and repair full request?
please suggest me

Hi Venkat,
A repair full request is loaded in cases where you get erroneous records or where there are missing records which you want to load. In such cases, a repair full request for the selective records can be loaded and is the most efficient way to correct the data, since you won't be required to load the entire data once again. Also you acheive the desired result without disturbing the delta. (You are not required to do an init w/o data transfer after a repair full, people just do it a a precaution)
However, repair full requests should only be loaded to infoproviders with update mode 'overwrite'. Otherwise, if the InfoProvider, its very probable that you might double the value of the key-figures due to rows being added twice - in case of an InfoProvider with update mode 'Additive'. So, if your InfoProvider is additive, you will need to delete the entire data and do an 'init with data transfer' to avoid corrupting the data. (Note: you can do a repair full request for an additive infoprovider in case of lost records or if you can delete erroneous records with selective deletion.But you have to be careful with the selections lest you inadvertently load other records than required and corrupt the data)

Similar Messages

Source for Init with data transfer and full load

Hi Experts,
1. Please tell me where the data comes when we do the
    following actions :-
    a) Init with data transfer
    b) Full load
i want to know the source of data i.e (setup table or main table or any other table)
Helpful if you can provide the data-flow.
kindly tell which is prefrable and why?
Regards,
RG

Hi.......
When you do init with data transfer it will read data from the set up table only..........but beside this it will also set the init flag..........due to this from next time any new records will go to the delta queue...........and next time when you run delta load it will pick records from delta queue...........
Now suppose data are alrady available in the BW side...........then you can run init without data transfer.......this will only set the init flag.........it will not pick any records.........
Extraction structure gets data from set up table in case of full upload ............and in case of delta load from delta queue.......
Regards,
Debjani...........
Edited by: Debjani Mukherjee on Sep 20, 2008 11:45 AM

Difference between initialization with data transfer?

Dear Ones,
What is the Difference between initialization with data transfer,initialization without data transfer and early delta initialization?
Please explain me in senario basis..
Thanks
Shiva

Hello Shivananda,
See oss note 505700 :
The early delta initialization is used to admit document postings
in the OLTP system as early as possible during the initialization
procedure.
Regards,
Fred

What is full request? and repair full request?

Hi experts,
please let me know what is full request? and repair full request?

Hi Suman,
Delta loading not possible if FULL requests already available in ODS from same datasource & souce system combination, In order to delta's FULL requests should be changed to Repair FULL full requests. Then system allows Deltas.
<a href="http://sapbwneelam.blogspot.com/2007/09/how-to-do-delta-loads-after-full-loads.html">Repair Full Request</a>
Hope it Helps
Srini

Add new key figs or characteristics and "Repair full request"

Hi Gurus, here are my questions
1.If I add new key figs or characteristics(which are not Key fields) to ODS and Cube containing tons of data, Will the transport for structure changes fail due to presence of data?
2.The extractor to the ODS which inturn is feeding the cube, is delta enabled. So the newly added objects wont have entries for historical records. If I change this extractor to "Repair full request" after adding the new fields, will the new fields then get populated?
3. After the "Repair Full Request" activity, Can I change the Infopackage setting back to delta update mode?
Thanks for the help in advance!!
Simmi

Hello Simmi,
1. Transport should go fine. As you are not changing the key fields, it should not cause any problem even if data is present.
2. Yes. But make sure what data you want to laod. As with full repair, system is not going to check for duplicate data. The responsibility lies with you.
3. Sure. if you mark the full load as repair, the delta settings will be unaffected.
Hope it helps.
Regards,
Praveen

Selective deletion and repair full request!!!

Hi,
I have one DSO which is receiving deltas from Std extractor and is also serving deltas to many data targets (Both DSO and Infocubes)
Now there comes the need of deleting data in DSO by means of year ( selective deletion )
I know that i need to adjust the data flow from DSO to other data targets myself!!
So after doing selective deletion in DSO, can i update datatargets ( of 3.5 version ) with full update so that data is adjusted in correct format for the subsequnet data targets?
or is there any better option??

Hi Sujith,
Difference between Repair Full and Full Load ;
1. When we want to pull the history data from the source system(SAP R/3) for the first time till yesterday and trigger / enable the Delta load.
For Eg; for your client,when the implantation was done ,when the GO Live started, all the history data(sales,Material,Finance etc) would have pulled from the source systems into BW system and enabled the delta load from next day.
Note: In this scenario ,We use Full Load only for the one time.
2. In most of the scenarios we will use Full Load for the master data (Daily Load). In few scenarios we will use Full Load for the transaction Data Loads. For Eg: in case if there are no changes happening in transaction data daily (like sales data) ,then we go for Full Load for transaction Data Load also.
3. If someone has deleted the data in the data target by mistake which was loaded using 'Full Load' ,then we can go for re-loading the lost data using the same normal 'Full Load' option. In this case if you are using a DSO in between PSA and Infocube then if you don't use the selection parameters(Company Code,Profit Center, Sales Organization etc) for the lost data ,then also it's fine. Because DSO has overwrite option. In case ,if you don't have DSO,then you have to use the selection parameters on infopackage/DTP level depending on from which level you are trying to get the data back. i.e Source System or PSA.
4. We have scenario where the data which was loaded using DELTA load has been deleted from the data target, OR due to DELTA load failure the data didn't get loaded into the data target. Now,we want to get the lost DELTA data back into the target. In this case we can go for using both 'Repair Full' and also 'Full Load'. but depends on the below conditions;
If we want to use 'Full Load' to get the lost DELTA data,then we should block the users in source system(SAP R/3) from posting the data,and clean up the delta queue . Then stopping the daily process chain in BW system which will bring the DELTA data. Then we can use' Full Load' option.
But, If we don't want to disturb the daily DELTA load and if we don't want to block the users in source system, then we should use 'Repiar Full Request". Using this option, the daily DELTA load will not get affected.
Please let me know you are clear with my points.
Regards,
Asha

Record count is different for Full load and Init with data transfer

Hi all,
We have a data source for which delta is enabled on Calendar Day.
If I run the full load record count is 2670.But If I run the delta record count is 2665.5 records are missing.
Would you please help on this.Why those records are missing.

Hi,
Actually for Full Load say you have 50 records. When you run it will upload 50 records.
Now if you run delta if there is no records changes it wouldnt update because there is no update in the existing records.
only delta is done when there is changes in the records.

Init with out data transfer and DELTAS

Dear Gurus,
I created Generic data source using Function module on FAGLFLEXT table. Here i used TimeStamp for capturing DELTAS. In the first run while loading into PSA i selected INIT WITH DATA TRANSFER then it got failed. Again i deleted INIT Request in Schedular and RUN INIT WITH OUT DATA TRANSFER then it got Sucess. Again i run Delta then it also it got failed. Again i deleted the INIT Request and out FULL LOAD. IT got success. May i know why MY Deltas are getting Failed.even in R/3 side when i checked in RSA7 then in status column and in Current Status Tab it showing time stamp field like this . . : :.
I got Stuck up I dont know what to do............
Can one kindly give solution for this.
Thanks,
Sony

Debug your generic DataSource, using RSA3, to determine why the delta failures are occurring. It's most likely in the delta logic portion of your custom Function Module.

Error while executing Initialize with Data Transfer for 0FI_GL_10

Hello All,
Post Pre prod refresh, our timestamp for the datasource 0FI_GL_10 got reset. Due to which our deltas did not bring any records to the BW system.
First we did an Initialize without data transfer for all the BW related datasources. The deltas were then set properly for all datasources except 0FI_GL_10.
We then raised a message to SAP and they suggested to run the 'Initialize with data transfer' for 0FI_GL_10 so that the timestamp is set and accordingly the deltas are fixed.
The issue now is we are getting the following error message while running INIT with data transfer.
Job terminated in source system --> Request set to red
Message no. RSM078
We have copied the data till July 1st week of 2011.
Please advice. The issue is very critical.
Thanks & Regards
Sneha

Hi Arvind
Thanks for your inputs.
Please find below the details of the short dump.
Runtime Errors         DBIF_RSQL_SQL_ERROR
Exception              CX_SY_OPEN_SQL_DB
Date and Time          09/07/2011 11:25:32
Short text
     SQL error in the database when accessing a table.
What can you do?
     Note which actions and input led to the error.
     For further help in handling the problem, contact your SAP administrator
     You can use the ABAP dump analysis transaction ST22 to view and manage
     termination messages, in particular for long term reference.
How to correct the error
     Database error text........: "ORA-01652: unable to extend temp segment by 128
      in tablespace PSAPTEMP"
     Internal call code.........: "[RSQL/FTCH/FAGLFLEXT ]"
     Please check the entries in the system log (Transaction SM21).
     If the error occures in a non-modified SAP program, you may be able to
     find an interim solution in an SAP Note.
     If you have access to SAP Notes, carry out a search with the following
     keywords:
     "DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
Information on where terminated
    Termination occurred in the ABAP program "GP_GLX_FAGLFLEXT" - in
     "FETCH_TO_ISTRUCTURE".
    The main program was "SBIE0001 ".
    In the source code you have the termination point in line 903
    of the (Include) program "GP_GLX_FAGLFLEXT".
    The program "GP_GLX_FAGLFLEXT" was started as a background job.
    Job Name....... "BIREQU_4N3PZQ12IA0X0PYGEA85IG39S"
    Job Initiator.. "BIWREMOTE"
    Job Number..... 11203300
    The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
    procedure "FETCH_TO_ISTRUCTURE" "(FORM)", but it was neither handled locally
     nor declared
    in the RAISING clause of its signature.
    The procedure is in program "GP_GLX_FAGLFLEXT "; its source code begins in line
    840 of the (Include program "GP_GLX_FAGLFLEXT ".

I have problem with data transfer between Windows Server 2012RT and Windows7 (no more than 14kbps) while between Windows Sever 2012RT and Windows8.1 speed is ok.

I have problem with data transfer between Windows Server 2012RT and Windows7 (no more than 14kbps) while between Windows Sever 2012RT and Windows8.1 speed is ok.

Hi,
Regarding the issue here, please take a look at the below links to see if they could help:
Slow data transfer speed in Windows 7 or in Windows Server 2008 R2
And a blog here:
Windows Server 2012 slow network/SMB/CIFS problem
Hope this may help
Best regards
Michael
If you have any feedback on our support, please click
here.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Re: difference between data transfer and data upload

Hi,
I want to know the difference between data transfer and data upload.
Regards
Sasi

Hi,
Data Transfer: It means data tranfer from SAP System to Non SAP System
Data Upload:It means data transfer from Non SAP system to SAP system.
Regards,
kavitha....

Full Load" and "Full load with Repair full request"

Hello Experts,
Can any body share with me what is the difference between a "Full Load" and "Full load with Repair full request"?
Regards.

Hi......
What is function of full repair?? what it does?
How to delete init from scheduler?? I dont see any option like that in infopackage
For both of you question there is a oss note 739863-Repairing data in BW ..........Read the following.....
Symptom
Some data is incorrect or missing in the PSA table or in the ODS object (Enterprise Data Warehouse layer).
Other terms
Restore data, repair data
Reason and Prerequisites
There may be a number of reasons for this problem: Errors in the relevant application, errors in the user exit, errors in the DeltaQueue, handling errors in the customers posting procedure (for example, a change in the extract structure during production operation if the DeltaQueue was not yet empty; postings before the Delta Init was completed, and so on), extractor errors, unplanned system terminations in BW and in R/3, and so on.
Solution
Read this note in full BEFORE you start actions that may repair your data in BW. Contact SAP Support for help with troubleshooting before you start to repair data.
BW offers you the option of a full upload in the form of a repair request (as of BW 3.0B). If you want to use this function, we recommend that you use the ODS object layer.
Note that you should only use this procedure if you have a small number of incorrect or missing records. Otherwise, we always recommend a reinitialization (possibly after a previous selective deletion, followed by a restriction of the Delta-Init selection to exclude areas that were not changed in the meantime).
1. Repair request: Definition
If you flag a request as a repair request with full update as the update mode, it can be updated to all data targets, even if these already contain data from delta initialization runs for this DataSource/source system combination. This means that a repair request can be updated into all ODS objects at any time without a check being performed. The system supports loading by repair request into an ODS object without a check being performed for overlapping data or for the sequence of the requests. This action may therefore result in duplicate data and must thus be prepared very carefully.
The repair request (of the "Full Upload" type) can be loaded into the same ODS object in which the 'normal' delta requests run. You will find this request under the "Repair Request" option in the InfoPackage (Maintenance) menu.
2. Prerequisites for using the "Repair Request" function
2.1. Troubleshooting
Before you start the repair action, you should carry out a thorough analysis of the possible cause of the error to make sure that the error cannot recur when you execute the repair action. For example, if a key figure has already been updated incorrectly in the OLTP system, it will not change after a reload into BW. Use transaction RSA3 (Extractor Checker) in the source system for help with troubleshooting. Another possible source of the problem may be your user exit. To ensure that the user exit is correct, first load a user exit with a Probe-Full request into the PSA table and check whether the data is correct. If it is not correct: Search for the error in the exit user. If you do not find it, we recommend that you deactivate the user exit for testing purposes and request a new Full Upload. It If the data arrives correctly, it is highly probable that the error is indeed in the user exit.
We always recommend that you load the data into the PSA table in the first step and check the result there.
2.2. Analyze the effects on the downstream targets
Before you start the Repair request into the ODS object, make sure that the incorrect data records are selectively deleted from the ODS object. However, before you decide on selective deletion, you should read the Info Help for the "Selective Deletion" function, which you can access by pressing the extra button on the relevant dialog box. The activation queue and the ChangeLog remain unchanged during the selective deletion of the data from the ODS object, which means that the incorrect data is still in the change log afterwards. After the selective deletion, you therefore must not reconstruct the ODS object if it is reconstructed from the ChangeLog. (Reconstruction is usually from the PSA table but, if the data source is the ODS object itself, the ODS object is reconstructed from its ChangeLog). You MUST read the recommendations and warnings about this (press the "Info" button).
You MUST also take into account the fact that the delta for the downstream data targets is created from the changelog. If you perform selective deletion and then reload data into the deleted area, this may result in data inconsistencies in the downstream data targets.
If you only use MOVE and do not use ADD for updates in the ODS object, selective deletion may not be required in some cases (for example, if incorrect records only have to be changed, rather than deleted). In this case, the DataMart delta also remains intact.
2.3. Analysis of the selections
You must be very precise when you perform selective deletion: Some applications do not provide the option of selecting individual documents for the load process. Therefore, you must first ensure that you can load the same range of documents into BW as you would delete from the ODS object. This note provides some application-specific recommendations to help you "repair" the incorrect data records.
If you updated the data from the ODS object into the InfoCube, you can also delete it there using the "Selective deletion" function. However, if it is compressed at document level there and deletion is no longer possible, you must delete the InfoCube content and fill the data in the ODS object again after repair.
You can only perform this action after a thorough analysis of all effects of selective data deletion. We naturally recommend that you test this first in the test system.
The procedure generally applies for all SAP applications/extractors. The application determines the selections. For example, if you cannot use the document number for selection but you can select documents for an entire period, then you are forced to delete and then update documents for the entire period in the data target. Therefore, it is important to look first at the selections in the InfoPackage exactly before you delete data from the data target.
Some applications have additional special features:
Logistics cockpit: As preparation for the repair request, delete the SetUp table (if you have not already done so) and fill it selectively with concrete document numbers (or other possible groups of documents determined by the selection). Execute the Repair request.
Caution: You can currently use the transactions that fill SetUp tables with reconstruction data to select individual documents or entire ranges of documents (at present, it is not possible to select several individual documents if they are not numbered in sequence).
FI: The Repair request for the Full Upload is not required here. The following efficient alternatives are provided: In the FI area, you can select documents that must be reloaded into BW again, make a small change to them (for example, insert a period into the assignment text) and save them -> as a result, the document is placed in the delta queue again and the previously loaded document under the same number in the BW ODS object is overwritten. FI also has an option for sending the documents selectively from the OLTP system to the BW system using correction programs (see note 616331).
3. Repair request execution
How do you proceed if you want to load a repair request into the data target? Go to the maintenance screen of the InfoPackage (Scheduler), set the type of data upload to "Full", and select the "Scheduler" option in the menu -> Full Request Repair -> Flag request as repair request -> Confirm. Update the data into the PSA and then check that it is correct. If the data is correct, continue to update into the data targets.
And also search in forum, will get discussions on this
Full repair loads
Regarding Repair Full Request
Instead of doing of all these all steps.. cant I reload that failed request again??
If some goes wrong with delta loads...it is always better to do re-init...I mean dlete init flag...full repair..all those steps....If it is an infocube you can go for full update also instead of full repair...
Full Upload:
In full upload all the data records are fetched....It is similar to full repair..Incase of infocube to recover missed delta records..we can run full upload.....but in case of ODS does'nt support full upload and delta upload parallely...so inthis case you have to go for full repair...otherwise delta mechanism will get corrupted...
Suppose your ODS activation is failing since there is a Full upload request in the target.......then you can convert full upload to full repair using the program : RSSM_SET_REPAIR _ FULL_FLAG
Hope this helps.......
Thanks==points as per SDN.
Regards,
Debjani.....
Edited by: Debjani Mukherjee on Oct 23, 2008 8:32 PM

Init without data transfer

Hi sdn
my data is going form ods to cube and i already done full update from Source system now we want to do init without data transfer but when I'm seeing in monitor then requst is running for 5 hrs still yellow and when i cancell that request then run it again the when I press start load button then it ask me for ods activation for all request and for one request i had tried either way but didn't got successful, what to do we are using generic datasource
rubane

Hi,
I think you are doing data upload to ODS .
In the seetings of ODS Select Automatic Activation.
Since you have cancelled the data upload,So delete the Data from the ODS . And then Do Delta init with out data transfer .and then do full upload. But when you are doing full upload you have to make it as Repair request. And then continue Delta loads.
Once Delta init (with out data transfer) and Full upload is over to ODS ,you can start Delta init upload to Cube.
With rgds,
Anil Kumar Sharma .P

MyRIO memory, data transfer and clock rate

Hi
I am trying to do some computations on a previously obtained file sampled at 100Msps using myRIO module. I have some doubts regarding the same. There are mainly two doubts, one regarding data transfer and other regarding clock rate.
1. Currently, I access my file (size 50 MB) from my development computer hard drive in FPGA through DMA FIFO, taking one block consisting of around 5500 points at a time. I have been running the VI in emulation mode for the time being. I was able to transfer through DMA from host, but it is very slow (i can see each point being transferred!!). The timer connected in while loop in FPGA says 2 ticks for each loop, but the data transfer is taking long. There could be two reasons for this, one being that the serial cable used is the problem, the DMA happens fast but the update as seen to the user is slower, the second being that the timer is not recording the time for data trasfer. Which one could be the reason?
If I put the file in the myRIO module, I will have to compile it each and every time, but does it behave the same way as I did before with dev PC(will the DMA transfer be faster)? And here too, do I need to put the file in the USB stick? My MAX says that there is 293 MB of primary disk free space in the module. I am not able to see this space at all. If I put my file in this memory, will the data transfer be faster? That is, can I use any static memory in the board (>50MB) to put my file? or can I use any data transfer method other than FIFO? This forum (http://forums.ni.com/t5/Academic-Hardware-Products-ELVIS/myRIO-Compile-Error/td-p/2709721/highlight/... discusses this issue, but I would like to know the speed of the transfer too.
2. The data in the file is sampled at 100Msps. The filter blocks inside FPGA ask to specify the FPGA clock rate and sampling rate, i created a 200MHz derived clock and mentioned the same, gave sampling rate as 100Msps, but the filter is giving zero results. Do these blocks work with derived clock rates? or is it the property of SCTL alone?
Thanks a lot
Arya

Hi Sam
Thanks for the quick reply. I will keep the terminology in mind. I am trying analyse the data file (each of the 5500 samples corresponds to a single frame of data) by doing some intensive signal processing algorithms on each frame, then average the results and disply it.
I tried putting the file on the RT target, both using a USB stick and using the RT target internal memory. I thought I will write back the delay time for each loop after the transfer has occured completely, to a text tile in the system. I ran the code my making an exe for both the USB stick and RT target internal memory methods; and compiling using the FPGA emulater in the dev PC VI. (A screenshot of the last method is attached, the same is used for both the other methods with minor modifications. )To my surprise, all three of them gave 13 ms as the delay. I certainly expect the transfer from RT internal memory faster than USB and the one from the dev PC to be the slowest. I will work more on the same and try to figure out why this is happening so.
When I transferred the data file (50MB) into the RT flash memory, the MAX shows 50MB decrease in the free physical memory but only 20MB decrease in the primary disk free space. Why is this so? Could you please tell me the differences between them? I did not get any useful online resources when I searched.
Meanwhile, the other doubt still persists, is it possible to run filter blocks with the derived clock rates? Can we specify clock rates like 200MHz and sampling rates like 100Msps in the filter configuration window? I tried, but obtained zero results.
Thanks and regards
Arya
Attachments:
Dev PC VI.PNG ‏33 KB
FPGA VI.PNG ‏16 KB
Delay text file.PNG ‏4 KB

Init without data transfer is not working in the Production box for FICA extractors

Hi Guys,
We are unable to do Init without data transfer for FICA Extractors(0FC_INVDOC_XX) from BODS system. And the job is successfully completed from the BODS end but it is not hitting the source system.. Can any one please let me know how to resolve this issue.
Thanks,
Kovur

Hi,
After triggering your info pack with init without data transfer, are you able to see delta pointer at info pack-->scheduler--> init options source system.
Are getting any error message? if yes then please share here.
Thanks

Diff between init with data transfer and repair full request

Similar Messages

Maybe you are looking for