What is a repair request?

Refer.
Repair full request
Re: Repair full request
Steps to perform repair full request
full repair request
Thanks...
Shambhu

Similar Messages

What is the use of marking repair request in the scheduler?

Hi !
what is the use of the option repair full request in the scheduler menu item?

Hi Durai,
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.
Nice post by Roberto:
Bye
Dinesh

What is repair request? when we use this?

Hi all,
what is repair request?
when actually we use this?
Thanks& Regards,
Ravi Alakuntla.

Hi Ravi,
When you find some records missing when deltas are running then instead of going for re-init and again deltas you can go for repair full request giving selection conditions for those missing records, without affecting your delta laods.
Hope it helps,
Sunil.

I cancelled my repair request, but i still received my box..what should ido

I cancelled my repair request, but i still received my box..what should i do?

Chances are, they shipped the box before you cancelled. To be safe, I'd call them and make sure the cancelation actually went through.
http://www.apple.com/contact/phone_contacts.html
Cheers!
-Bryan

What is my replacement/repair bill Re: Re: Update on your repair request (D132652385). I wouldn't expect the Community to know this answer but this is where the non reply letter directed me to.

What is my repair bill reference D132652385, anyone?

You'll need to contact whoever sent you the letter. Or call AppleCare directly. Use the Contact Us link at the bottom right of every page of these forums.

Credit and Debit notes in reference to Repairing invoice or Repair request

Hi Experts!
I create a Sales order ("RA") for repairing. My flow is complete and also billing documents are generated.
The fixed price defined in the Repair request is copied into the invoice, and can not be modified (we block the change).
If the price is lower or upper than the real costs. It would like to create a credit or a debit note in reference to the billing document.
Is it a standard way to work because SAP blocks it in Standard.
Or there is no link between a billing document and a credit memo?
I have an alternative, to use "Purchase order N°" with Sales order, but this field is a free text.
Thanks for your help.
Stéphane

Who/what is "it" in "it would like to create"? What does SAP "block"? What exactly is an issue?

Repair Request Help

Hi, We are in BI 7.x SP15.
I have a DSO to DSO Data flow and I'm going to delete some data from our Top DSO via selective delete. I then want to reload this data from the lower DSO.
After a selective delete will just a full load of the deleted data replace it correctly and the deltas will continue?
The reason I ask is that I see a reference to "Repair Request" in the selective deletion documentation. Is this just a full with the same selections or something special I have to do in the DTP?
Thanks for any help

Great. This is what I thought. When I do a separate full the delta should continue just fine.
Also, like said earlier if I'm going to reload a full with selections I do not need to do selective delete because they will just overwrite. correct?
Thanks all!

A full repair request

Hello Gurus,
what is a full repair request?
Many thanks,

Hai ,
Q. Repair Full Request
Ans: You can find the option in the InfoPackage. Open up the InfoPackage and press ShiftCtrlF1 or from the menu Scheduler > Repair Full request. You need to check in the box and it will be done.
You can go in for a repair full request when you have missed any delta loads or there are data corruption issues. By doing a full repair load, you can ensure that your data is correct and has good integrity.
With this option you can continue to use your existing delta and not worry about resetting the delta.
But make sure that the ODS is in overwrite mode and not additive. If its additive then you will face the problem of having duplicate data. If this is the case then you have to delete all the contents and then do the full repair request.
Say if your current scenario has init/delta setup to your ODS.
And for some reason you have to do a full load because you missed some data or you have to load some historic data.
Then if you do a full load to ODS then the request will be loaded but do not get activated as full load to ODS once the delta/ init is setup.
So in these scenarios you'll have to go for repair full request option when loading to ODS.
You'll have the same option when loading to CUBE but in cube it doesn't matter as it is possible to do a full load even we had delta/init.
So doing repair full will not disturb your Delta mechanism in your ODS.
OSS Note on Repair Full Request.
Some data is incorrect or missing in the PSA table or in the ODS object (Enterprise Data Warehouse layer).
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."
Another Scenario where we use Repair Full Request
If your data load is delta and now if you are planning to run Full load, then you can go for Repair full request.
Eg: If you have missed data for 3 days and next delta loads are running successfully, in this case if you want to fill data for only particular 3 days, than you can run the statistical setup for that particular data source for 3 days and load it as a full load through repair request.
It is particularly used in the upload of data into the ODS ,if the ODS has already Delta loads.
This is required if want to upload any full uploads(with selection at infopackage or without) to be done to ODS, because ODS does not allow to activate the simple Full uploads if there are delta loads to it.
But make sure that check the option "indicate request as repair" in the Scheduler before you start the IP.
Thanks,
Kiran Manyam

Repeat Delta Vs Repair request

Hi Gurus,
What is difference betwenn Repeat Delta and Repair request? May i know the in which scenario we go for these options?
Thanks & Regards,
Prabha.

hai Prabha,
Delta Update
A delta update only requests data which has appeared since the last delta.
Before you can request a delta update, you must first initialize the delta process.
A delta update is only possible for loading from SAP source systems.
If a delta fails (status red in the monitor) or the overall status of the delta request has been set to red manually, the next data request will be performed in repeat mode. A repeat request extracts the incorrect or incompletely loaded data from the failed delta request, along with any new data since the original request. A repeat can only be requested in the dialog. If data from the failed delta request has already been updated to the data targets, delete the data from the data targets affected. If you cannot delete the data from the data targets, duplicate data records may be produced when the repeat request is performed.
The concept of Full repair request is " when we r loading data bydelta update from a data source then it will not allow the Full update from the data source. When we r using this option we can extract the data on repair request then the deltas of the data source is not disturb.
Data will come from the data source only.
repaire request is used to get the missing delta records.
In the info pack menu bar scheduler you will get this option Repair Full Request. generally we use this option for ODS. pls read this OSS note :739863
hope this helps
regards
KP

Can I reprint a repair dispatch label for a repair request?

I submitted a repair request and when it came to the page where I needed to print the dispatch label so that I can post my ipod back to Apple but the page didn't load properly and so I couldn't print the label. When the email arrived from Apple it said that I could click on a link for "print dispatch label" but when I clicked on the "link" nothing happened. Does anyone know if you can enter your repair id somewhere and reprint the dispatch label?
thanks!!

I would try contacting Apple directly and see what they say...
Patrick

How to setup a variant to do full repair request for 0Material?

How to setup a variant to do full repair request for 0Material?
Thanks
York

Hi,
Do you mean to set up a varinat in process chain?
Regards
Srini

I sent my iphone in for repair and the status was canceled repair request.

I sent my iphone 3GS in for repair and when I checked on the status of the repair, it said repair request canceled. Does this mean it has been fixed and on its way back or they are sending a new one back? I am confused.

Ah ,so you are in Europe ( helps to tell upfront as this is a WW forum )
They will not repair your iPhone they will check it and assuming no user induced damage will send back a replacement refurbished unit to you ( reason for no accessories )
There must be a contact number where you arranged the return
It is possibly going to Eire where Apple seems to ship most EU shipments from

How to do Repair Request in BI 7.0

Hi All,
I'm doing some testing in BI 7.0 system, would like to know how do I go about in doing repair request via BI 7.0 without Infopackage.
Is there any other option.
Please advise
TQ

Hi,
Pls chk this link;
http://help.sap.com/saphelp_nw70/helpdata/en/80/1a65dce07211d2acb80000e829fbfe/frameset.htm
Steps to perform repair full request
Repair Full Request with BW 7.0
Hope this helps,
Regards
CSM Reddy

Can i transport the repair Request?

hi,
We have a data osurce enhance with Two fields and is tranported to Production.
Now again we enhanced the same data source for the Third Field and wriitemn code for tit in Cmod.
When enhanceing , it is asking a request and we have given it .
Now if see this request in SE03.
We find that (the newly created request for the third field ) as task request under the main request which is already tranported .
and
This request is REPAIR Type.
Now my Question is ,
Can we tranport only this request(repair request ) directly to production. or not.?
Do we need merge this request to the already tranported request and then tranport?if yes please tell me steps.
OR
Pleae tell me a solution to get third field also into my production system.
Regards,
Naresh.

Little deviation in above question: simply
Datat source 2lis_03_bf with 2 enanced fields(via append str) wtih CMOD code transported to production.It's ok in prod.
Now i added new field to above append str and again wrote new piece of code in CMOD. I created one req for datasource at RSA6 level, with a task request as repair at append str level. Now hierarchy of change req is
Req1-task1(rsa6 changes) :
Req1-task2(appnd str changes) - (i have seen task2 description as repair in se09, Is it causes any problem if transport repair task to prod..ie. can i get new field to production sys append str). can anyway turn task descripton of repair to dev/correction. Usually first time task we get description as dev/correction, but second time task onwards for particular objects we get repair.

What is change order request ?

hi
what is change order request ,is it change management in that case what is change management .
can we change sales order information also ...
thanks in advances ...

Check versioning functionality.

What is a repair request?

Similar Messages

Maybe you are looking for