Diff b/n Repair full and Full load

Experts
Please explain diff b/n Repair full request and Full load.
If I do Repair full request instead of Full load ,is there any problem in the data ?
Many thanks
Manoj

Hi Manoj,
You can use a request that was selected as a repair request via Scheduler ® Repair Full Request to carry out a full update in any data target. This also applies to data requests that already contain data from an initialization run or deltas for this DataSource/source system combination, and that have overlapping selection criteria.
The difference between a Full Load and a Full Repair load is only evident in the case of loading to an ODS (to which you are also loading Init and Delta from the same datasource). If you ODS has the Init request active and you load a Full request, the data will not be activated. You should always use a Full Repair request when you want to load a full load to the ODS. For a cube it does not make a difference as the sequence of data loads is in important in a cube.
If you have accidentally not marked the request as a repair request, you can convert is using SE38 > RSSM_SET_REPAIR_FULL_FLAG
Hope this helps...

Similar Messages

Is there any repair full load option in DTP?

Hi Experts,
I have run delta DTP from Cube A to Cube B with selection less than or equal to 31.03.2004 and I want to run grater than 31.03.2004. Now the problem is this load is not bringing the required records because data mart symbol is already set in Cube A.
How do I extract grater than 01.04.2009?
Is there any repair full load option in DTP?

Hi,
I am afraid that we have only full and delta options available in DTP, but the several other options available on extraction tab will enable us to do something similar to it.
If you looking to get data after 31.03.2004, in you selction condition change the from date to 01.04.2004 and try extracting, I am sure it will give you the desired records.
Please follow info on this link and decide which would suit to your requirement, if you get stuck, post back and I'll try to assist you.
http://help.sap.com/saphelp_nw70/helpdata/en/42/fa50e40f501a77e10000000a422035/frameset.htm
Regards,
Ray
Edited by: Rayapa on Apr 4, 2009 9:04 AM

Repair full load

Hi,
I have "Billing document" number( 9000182) in ODS .
For the debugging purpose I want to do " REPAIR FULL LOAD' only for this document .
can i do repiar FULL LOAD" for this documetn in Production system?. Is there any problem if i do repair full load. any data mismatch occurs.
I can do selective deletion and i can do " REPAIR FULL LOAD' but my doubt is any problem will come as it is ' PRODUCTION System".
Please confirm .U r suggestions will be helpful.
i tried in Q system but that document was not there in R/3.

Hi Kotha,
If you are doing this for debugging purpose,Then no need to delete the data from ODS.
Follow the below steps.
1) Run IP with options "load till PSA" and selections for Billing no 9000182(If you think it will run for longtime,do full repair or run it as full load)
2)If you want to check thi data in CUBE's as well then run in simulation mode using Update rules with respect to each target.
Hope this helps.
Regards,
Venkatesh

Give difference between full load, delta load, repair full load

Can i run full update after delta load?? if yes tell me a scenario??Can anyone tell me the difference between all three & when to use these??
Regards,
Asish

Hi,
For Repair full load please check OSS note 689964 which is about repairing the full load by executing the program RSSM_SET_REPAIR_FULL_FLAG.
Basically in this you provide your ODS, Data Source and Source System name and execute the program RSSM_SET_REPAIR_FULL_FLAG and hit Repair full load.
It will repair the full load.
But after this you cannot go directly for delta load which is for new added records or changed records. Before delta load do initialization without data loading and then go for delta load.
So delta load will run after init run (without data transfer) and add new added record or changed records to exisitng full upload records.
Technically you cannot go for delta load with out init load.
So, If you have already done full load, you can go for delta load after doing initializing (init load) without data loading.
Hope it helps.
Regards,
Mona

1_CO_PA_RHPA03_03 repair full load

Hi Friends,
What are the steps to load 1_CO_PA_RHPA03_03 datasource. It is a COPA extractor.
Thanks and regards,
Balaraj

COPA is not a Logistics datasource, so there is no concept of filling set up tables.
Below link gives you all details
Re: How COPA datasource is loaded with data?

BW Delta and Full load

Hi !
This is a simple question with BW 3.5 :
A standard extractor with Delta is extracting everyday delta to 1st level ODS -> 2nd level ODS -> Cube.
Now i want to add 2 ODSes in same flow and they should also catch all these delta. Along with that I want to load for remaining period of this month (ex. Full load from 1st to today of the month and then onwards delta)
So new structure would be
0CRM_SALES_ACT_1 -> Level 1 existing ODS delta -> Level 2 existing ODS Delta
-> New level 1 ODS with delta -> New Level 2 ODS with delta
Can you please let me know how to do that ?
Full , delta info package ?
(FYI - i loaded full load for history and then tried delta, but delta failed saying Full load is already there in system)
Please do not post duplicate threads
Edited by: Pravender on Apr 12, 2011 7:08 PM

Partik,
My suggestion is load data from exiting Level 1 DSO to 2 New DSO's instead of loading directly from source to New DSO's.
To do that... removed initialization from Level1 DSO to 2nd level DSO and Re-Initialize WITHOUT data transfer by considering new DSO's also and continue delta's.
Use full load infopackages to load historic data from Level 1 DSO to 2 new DSO's.
Flow now should be:
0CRM_SALES_ACT_1 -> Level 1 existing ODS delta -> Level 2 existing ODS Delta
Level 1 existing ODS delta -> New DSO's
If FULL loads already there in DSO's further delta's wont work. Convert FULL loads to repair full load using Program: RSSM_SET_REPAIR_FULL_FLAG.
Then continue delta's.
Hope it Helps
Srini

How to delete repair full request

Hi,
There was a delta load scheduled in background. By mistake before the delta load a repair full load with particular company code selection was run. So after the delta load, data is duplicated in the system. Now the request is compressed. I want to delete this repair full load request from the ODS. Please let me know step by step solution for this.
Thanks.

Hi,
from where u r loading data into cube from ODS or R/3. if u run a repair full load then it will not check the data mart symbol although it is successfull so the next delta will brings data again, so u have to run init with out data transfer to make deltas 0 in source. this happened in ur case .
but the cube is compressed so u cant delete data request based
is there any PSA there if there is PSA then u can use REVERSE POSTING from PSA this will brings key figure values with - values so the records will be nullified
in manage of the cube -> select that repair full request -> click on monitor button -> u can find an icon in the top(psa request symbol with red mark) click on that and execute.
if there is no PSA then u have to do selective deletion.
assign points if it helps,
thanks,
pavan.

Change from Full load to delta load.

Hi Gurus,
I have one ODS object which is extracting data from r/3 system.this ODS object is getting loaded on a daily basis,& it's having heavy volume data (takes almost 8 hours to load).
Now I want to change the load mode of that ODS from FULL load to Delta Load
How can I do that ?
I tried to do* Init without data transfer* from source to this ODS obejct , but while activation it's saying Full load is already loaded so no init
I want to change the load mode of that ODS object without deleting the data,as it takes lot of time to load the total data.
Is there any way to that??
Plz help.Thanks in advance.
Regards,
Kironmoy Banerjee.

RSSM_SET_REPAIR_FULL_FLAG.
1 more question,if run that function module,will it change the existing loads in Repair full mode?
or it will load the total data again.
If you run RSSM_SET_REPAIR_FULL_FLAG Program and give ODS name etc.. it will turn all Full loads to Repair full mode.
Steps:
1. Run that function module.
Run Program RSSM_SET_REPAIR_FULL_FLAG
2. give ODS,data source name.
Yes
3 it will change the existing load to repair full load,
Yes
4.Init without data transfer. (i am not sure if this step is required or not.)
Yes
5.delta load.
Yes
Thanks
Reddy

Regarding Repair Full Request

Hai
Can anyone explain in detail "when and in which scenarios and how REPAIR FULL REQUEST funcationality is used ....
Please tell me with example urgently...
I Will assign the points
Thanks \
BYe
MOHAMMED

HI,
FULL REPAIR.................
Full repair load is only relevant for ODS objects when you need to do a full load from a datasource which has been initialised. If you have done an Init, and then do a simple full load, the request will not activate, that's why the repair full load option works here.
For the cube also you can mark the request as repair, but in any case it will load to the cube. The only thing you need remember is that this will not do the job of removing some records and replacing them with the repaired data.
You can selectively delete from the cube, and then do a full load with the reqd selections.
Please go through the following thread where a similar problem has been discussed.
Re: Repair Full Request
Nice post by Roberto:
full repair request
repair full request
-Shreya

FULL LOAD FOR A SINGLE INFOBJECTS IN ODS

Hi,
I am in a scenario, where I need to do a repair full load for one of my ODS object which is extracting data from R/3 system.
But the problems lies in extraction time, the estimated time to complete the full load is 90hour....which quite impossible to afford in production environment. Hence looking for a solution through which I can load only the modified info object of the ODS.
Can anybody share some thoughts on this please?
Regards,
Kironmoy Banerjee.

It seems in our case, modifying the transfer structure is troublesome as it involves lot of routines in many info object..
Can someone suggest me what method I should proceed with to bypass this too long running full load, but need to have a data refresh to that particular infobjects (at least) to make the changes available on old data.
Any suggestion will be highly appreciated.
B.R,
Kironmoy Banerjee

Delta load is done,now need to have full load

Hi,
Delta load is done,now need to have full load.
Here for DTP we dont have full repair,what is the process.

Hi,
You will have to use repair full load at infopackage level.
But repair full load should be done only if their is any problem
in the load.
Process
1)selectively delete the data where problem had occured
2)Repiar full load in the infopackage for that selection.
You cant do a direct full load on the same selection as that of delta.
Please assign points if it helped you
Regards,
Senoy

Diffrance between full repair and Full load .

hello ,
could you please let me know , what is the diffrance between full repair and Full load .
Regards

Hi,
Full Repair :
If you indicate a request in full update mode as a repair request, then it is able to update that request in data targets even if they already contain data from initial runs or deltas for this DataSource / source system combination and with overlapping selections.
Consequently, a repair request can be updated to ODS without checking the sequence of delta requests. The system supports loading in an ODS object by using the repair request without having to check the data for overlapping or request sequencing.
Full load :
Pulls the entire data from the source system to the BI system
Assign points if it helps
Thanks & Regards
santo

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

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)

Using Repair Full to load Data

Hi Guys
I have to load several years of data. Being loaded into ODS and Cubes in delta mode. I want to break the load into small chunks to load in a controlled fashion. That's what I have planned to do
1- Initialize without data transfer
2-Run Repair full for each year from 2001 to 2006
3-Then start running the deltas.
I am just curious if u know if this method is going to work. Does the delta that i m going to run after running the last repair full will bring all the data again or just the changed records.
I also want to go back historically with repair fulls to make the current data available. Is this going to work or not. If not what should I do to load the data periodically.

Hi,
If you want to do this year load to cube then you can full load sepcifying the year in the infopacakge.
You need not run the program which i specified earlier for cube, but in case you want to do this load year full to ODS and in case delta load is going on in the ODS then you will have to first do the full loads for the years u want to and then excute the program and then carry on with delta loads.
I hope I'm clear.
In case you are not able to see the radio buttons then you can drop a mail to [email protected] and tell them that you are not able to give points for this post.
Regards,
Rohini

Diff b/n Repair full and Full load

Similar Messages

Maybe you are looking for