Depot Repair Engineer issue(High VolumeRepair)

hi,
In High Volume Repair page when enter a item name and go we will get the repair orders available for that item if we click a repair number and navigate to the further page we get 3 sub-tabs(Evaluation /Repair Execution/Debrief) in the Evaluation tab we have Service Codes Advance Table if select a check box in the Region and click Generate Jobs Button a job is generated in Repair execution tab's Repair Operations Advance table RN a job is created , materials created in materials AdvTbl Rn, Resources in Resources AdvTbl Rn in all the 3 advance table Rn's the select check boxes and dropdownbox(poplist) are disabled what is the process for making that check box enable can anyone please help me .........................and in some repairnumbers the repair execution tabs advanceTbl Rn's does not have addanotherrow button ............... can any one help me please

What you're describing doesn't sound like fan noise to me.  At 3597 RPM, your fan is spinning at about 60 Hz.  Typically a fan noise will sound like a low hum or buzz, and a failing fan, in my experience, sounds kind of high-pitched, but not what I'd describe as very high pitched.
If, on the other hand, what you're hearing is a very high pitch whine, then you might be experiencing something similar to what's described in this thread:
terrible whine noise!

Similar Messages

  • Error in Depot Repair when creating repair order for SR

    Hi,
    I am getting the following error in Depot repair when creating a repair order for a Service Request :
    "The Service Request Customer (GEJ Service Provider) does not own this item instance (&ITEM_INSTANCE). Please choose another instance. (IB_INSTANCE=21777)"
    An Item Instance was created for customer A (Owner), then party relationship was created in IB with another customer (GEJ Service Provider).
    Now a SR is created with customer as GEJ Service Provider and this item instance is selected.
    The error is coming up when trying to create repair order for this SR.
    Any idea how to resolve this issue?
    Regards,
    Mohammed

    Mohammed
    Please refer to this in Metalink note that says Deport Repair 11.5.10 enhancements and search for this ER number.
    ER: 4723163
    Service Request and Repair Order blocks of Depot repair do not allow ability to change Installed Base ownership of an item or creation of TCA relationships between existing TCA parties before creating a service request or repair order.
    Ability to automatically change ownership for an install base tracked item when returned for repair.
    ER 4723163
    Patch 4910836
    Look like you have applied this patch.
    Coming to the issue you cannot achieve what you are trying. The only option is to add this subfunction Depot: Allow Change of IB Ownership to your menu of the resp you are trying to use and the message will be different:
    This allows you change the ownership and create a repair order.
    Unfortunately customer relationship is not going to help at this time. YOu may want to log an SR and see if that is intended in the future. I checked R12.06 but the same behavior is exhibited there as well.
    Good luck!
    Thanks
    Nagamohan

  • Depot Repair Implementation in 11.5.10

    Hi All,
    Need advise regarding the Depot Repair Implementation. We are currently implementing Depot Repair module in 11.5.8 (Upgraded from 10.7) but observed that there are lot of bugs.
    Did anybody successfully implemented Depot Repair in 11.5.8?
    We wanted to evaulate upgrading from 11.5.8 to 11.5.10 if Depot Repair module is stabilzed in 11.5.10. Could anyone advise if Depot Repair functionality is working good in 11.5.10?
    We are currently on 11.5.8 with GL, AP, AR, PO, INV, OM, BOM, WIP, MRP modules.
    Thanks in advance for the help.
    Regards,

    I am implementing Depot Repair 11.5.10 and so far so good. It is very tightly integrated with OM, INV, CRM Foundation, FS Debrief, Install Base and Service. Not actually using any Service Contracts functionality or KB but we are going live in 6 weeks and not really had too many serious issues.
    Hi All,
    Need advise regarding the Depot Repair
    Implementation. We are currently implementing Depot
    Repair module in 11.5.8 (Upgraded from 10.7) but
    observed that there are lot of bugs.
    Did anybody successfully implemented Depot Repair in
    11.5.8?
    We wanted to evaulate upgrading from 11.5.8 to
    11.5.10 if Depot Repair module is stabilzed in
    11.5.10. Could anyone advise if Depot Repair
    functionality is working good in 11.5.10?
    We are currently on 11.5.8 with GL, AP, AR, PO, INV,
    OM, BOM, WIP, MRP modules.
    Thanks in advance for the help.
    Regards,

  • Internal Refurbishment in Depot Repair & Spares Management

    Hi,
    We have a requirement of Intercompany Transfer for Depot Repair. I want to receive the goods in Org 1, work on it and then internally transfer it to Org 2 and then again work on it and then send the same to customer.
    Please let us know how this scenario can be handled. We are using the following modules for the same:
    1. Depot Repair
    2. Spares Management
    Please let us know....Its Veryyyyy Urgent
    Thanks and Regards.,
    Akesh

    Hi
    Please check follwoing link it may helpful to you
    [Repair and Return;
    [Issue Return stock to other plant for repair;
    Regards
    Kailas Ugale

  • TS1440 I followed all of the directions after seeing that my laptop flashed the folder with the question mark. But when I went to disk utility to repair/ verify issues w/ start up disk it would not allow me to.button to repair/verify is there but cant be

    I followed all of the directions after seeing that my laptop flashed the folder with the question mark. But when I went to disk utility to repair/ verify issues w/ start up disk it would not allow me to. The buttons to repair and modify we're there but they were grey and couldn't be pressed.

    Were you trying to repair the disk you were booted from? You can't do that - you need to boot from your install disk, and choose 'Disk Utility' from the 'install' menu.

  • Depot Repair Order Flexibility after SO created

    Hi everyone,
    I have a client who's looking into using the Depot Repair functionality to handle all returns.  What we're finding so far is that everything works well so long as you know what you're going to do with the material before you create the service notification.  We need to be able to receive the material back in before we decide if we're going to repair it, replace it, or just credit the customer.  The Notification type creates and drives the SO processing.  W/in the SO, the item categories seem to be driving the returns subline, the repair subline, and the outboud delivery subline.  I thought perhaps we could change the item cateogories in order to control subsequent processing (ie, before the return is actually processed in VL01n, update the item category on the return to reflect an item category for return for replacement vs return for repair, etc. but the item categories are protected in the SO. 
    Does anybody have a better way of being able to provide the flexibility of determining the type of processing after the Service notification has been created?  If not, does anybody know how to "unprotect" the item category fields so we can update them manually?
    thanks for the assistance,
    Christie
    Edited by: Christie Monacos on Aug 4, 2010 3:53 AM

    Hello Christie
    I am not a CS specialist, but my current  role affords me the opportunity to provide some thoughts. Here the repair process has been automated to 2 distinct stages: a) Receipt and b) Inspection and repair,  to  create multiple documents  and even objects ( Equipment if required) from Service, Sales, Logistics, and Inventory Management perspectives.
    1) For one you can divide the service notifications into 2 types: a) Customer facing, and b) Internal (fault) Notification.
    2) When you receive you can have 3 types of dispositions: a) Review receipt, b) Return for Repair and c) Exchange at Receipt. If all information is available, in case of the last  2 dispositions, the following documents are created:
    a) Equipment if serialized
    b) Customer facing notification
    c) repair order
    d Inbound delivery
    e) Material  document for movement into stock
    f)  service order/s
    g) Internal Fault Service notification
    3) The first one, Review receipt is used when there is not enough information to create a Repair order. At that time the documents created are: a) Customer facing notification, b) Equipment u2013 if serialized, c) Goods receipt material document.  A task is added automatically to the notification for administration action and/or follow up with the customer.Once all info is available, the remaining documents are created using the reference of  Customer facing notification.
    4) Thus the repair order created will have requisite sub-lines, e.g. Return, Exchange, Repair etc.
    So I believe you need to follow the business  process as it happens in SAP.
    Hope this helps. Let me know.
    4)
    4) Once information becomes available, all other documents created.

  • Depot Repair

    Does the addition of the depot repair module in addition to the customer service module improve the ability to get detailed reports on repairs. Also if you have a repair depot and you bring in a product where you have to fix more than one component, how does depot repair track this and how will it report this? Are the reports searchable?

    Failed and replaced component data is captured in a note field along with mode of failure and failure symptom information. This prevents one from validating the data to ensure consistency and integrity. Consequently, it is unlikely one could perform operations required for analysis of this data. For instance: Assume we are repairing an item and the problem is Low Signal Output. Utilizing a dropdown (or pop-up, your preference) box, one can limit the data entered into a field allowing only the approved values. In this case the repair technician would select Low Signal Output. One could then use this information to determine the most frequently observed mode of failure for a given product or range of products. Conversely, allowing entry of this data into a "free-text" field frequently causes a loss of integrity when, for instance, individuals choose to abbrievate. The problem listed above may be entered as Low Out, Low Signal, Low Output, or even Output low. This eliminates the ability to aggregate this data by mode of failure. One could dump the data to Excel. That seems to defeat the purpose of automating the repair process and collecting data using a sophisticated system such as Oracle.
    Hope this helps

  • Depot Repair interractions question

    At our site, we have two business units running one instance of Oracle. One of the units is going to be turning on the Depot Repair module and our business unit is not.
    We've been asked to participate in the pre-release testing and I'm not sure we're actually needed but I'm seeking some general information to confirm my suspicion.
    Question 1: If we don't use the module in our business unit, is there any way the module could cause changes to either the way other modules we use work or to the underlying data in those modules?
    Question 2: If the data in Oracle is segregated by business unit, is there any way that the module when used by the other business unit could drive changes to data in our unit?
    I'm not an Oracle person; I've been tasked to do a risk assessment/mitigation for our business unit and an trying to figure out how a module we don't intend to use could muck up anything we do use.
    Thank you for any information you can share.
    Doug

    Failed and replaced component data is captured in a note field along with mode of failure and failure symptom information. This prevents one from validating the data to ensure consistency and integrity. Consequently, it is unlikely one could perform operations required for analysis of this data. For instance: Assume we are repairing an item and the problem is Low Signal Output. Utilizing a dropdown (or pop-up, your preference) box, one can limit the data entered into a field allowing only the approved values. In this case the repair technician would select Low Signal Output. One could then use this information to determine the most frequently observed mode of failure for a given product or range of products. Conversely, allowing entry of this data into a "free-text" field frequently causes a loss of integrity when, for instance, individuals choose to abbrievate. The problem listed above may be entered as Low Out, Low Signal, Low Output, or even Output low. This eliminates the ability to aggregate this data by mode of failure. One could dump the data to Excel. That seems to defeat the purpose of automating the repair process and collecting data using a sophisticated system such as Oracle.
    Hope this helps

  • Depot Repair APIs

    Does anyone know where I can find good resources and examples of using the depot repair APIs?

    Failed and replaced component data is captured in a note field along with mode of failure and failure symptom information. This prevents one from validating the data to ensure consistency and integrity. Consequently, it is unlikely one could perform operations required for analysis of this data. For instance: Assume we are repairing an item and the problem is Low Signal Output. Utilizing a dropdown (or pop-up, your preference) box, one can limit the data entered into a field allowing only the approved values. In this case the repair technician would select Low Signal Output. One could then use this information to determine the most frequently observed mode of failure for a given product or range of products. Conversely, allowing entry of this data into a "free-text" field frequently causes a loss of integrity when, for instance, individuals choose to abbrievate. The problem listed above may be entered as Low Out, Low Signal, Low Output, or even Output low. This eliminates the ability to aggregate this data by mode of failure. One could dump the data to Excel. That seems to defeat the purpose of automating the repair process and collecting data using a sophisticated system such as Oracle.
    Hope this helps

  • Depot Repair setups and flows..

    Gurus,
    Can some one please help in forwarding the Setups for Depot Repair and any flows like BFN.
    Thanks in Advance........

    Failed and replaced component data is captured in a note field along with mode of failure and failure symptom information. This prevents one from validating the data to ensure consistency and integrity. Consequently, it is unlikely one could perform operations required for analysis of this data. For instance: Assume we are repairing an item and the problem is Low Signal Output. Utilizing a dropdown (or pop-up, your preference) box, one can limit the data entered into a field allowing only the approved values. In this case the repair technician would select Low Signal Output. One could then use this information to determine the most frequently observed mode of failure for a given product or range of products. Conversely, allowing entry of this data into a "free-text" field frequently causes a loss of integrity when, for instance, individuals choose to abbrievate. The problem listed above may be entered as Low Out, Low Signal, Low Output, or even Output low. This eliminates the ability to aggregate this data by mode of failure. One could dump the data to Excel. That seems to defeat the purpose of automating the repair process and collecting data using a sophisticated system such as Oracle.
    Hope this helps

  • Depot Repair Actual (API)

    Hi,
    I am going to create Depot Repair Actual Lines using CSD_REPAIR_ACTUAL_LINES_PVT.CREATE_REPAIR_ACTUAL_LINES API, For that i need a document to find the mandatory and optional parameters, If any one have the document please put is over here.

    Hi,
    Please see eTRM and IREP websites.
    eTRM
    http://etrm.oracle.com
    Oracle Integration Repository
    http://irep.oracle.com/index.html
    Thanks,
    Hussein

  • Depot repair erroe while receving !

    Dear all,
    Iam working in depot repair, i had choosen the repair type as repair & return hence automatically return & shipped line is created..when i am trying to receive the item in to subinventory by specifying the sub inventory the following errors occurs..
    CSD_AUTO_RECV_NOT_POSSIBLE
    Regards
    varma

    hi..
    i think u can get all docs in metalink below is the link ...
    https://metalink.oracle.com/metalink/plsql/f?p=130:14:10044972268291132669::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,267828.1,1,0,0,helvetica
    Home > Support Categories > Depot Repair > Depot Repair
    hope u can browse thru the docs...
    pl check & revert me..
    thnks

  • How to enable Tasks mode tab in Oralce Depot Repair

    Want to create repair by using tasks.
    Please let me know how to enable Tasks mode tab in Oralce Depot Repair
    Ashish

    Look for a System Profile under CSD... there you should be able to setup the TASK mode for Depot Repair.
    Hope it helps.
    Jose

  • Approval date in Depot repair

    Hi All,
    In the depot repair orders if the approval_flag='N' where can we get the "approval date/rejected_date" and "date sent for approval"
    Regards,
    Sandeep V

    Lets start with the obvious question, is there anything that's saying having workflow created versioning is a bad thing? If you've got document checking and versioning turned on, you're clearly in an environment where auditing it needed.
    SPD has steps for checking in and checking out.  If you use these, than you can also use the "log item to history" or something similar to log the history.
    Other than that, try using calculated columns to look up both the Approver and the Approver Date.  Return these as single lines of text and they should work fine with Quick Parts.
    Steven Andrews
    SharePoint Business Analyst: LiveNation Entertainment
    Blog: baron72.wordpress.com
    Twitter: Follow @backpackerd00d
    My Wiki Articles:
    CodePlex Corner Series
    Please remember to mark your question as "answered" if this solves (or helps) your problem.

  • Automatic RMA creation in Depot Repair Orders

    Hi
    We are implementing the Oracle Depot Repair Module in 11.5.10.2.
    The logistics tab is empty and, the RMA is not created automatically for my repair orders. I am using the Repair Type 'Repair and Return' and followed the oracle Metalink note 412088.1. It still doesn't create the RMA.
    Can some one provide the steps in acheiving this thing?
    Also, the sequence numbers for SR number is starting from 1 and incremented by 2. I couldn't see any sequence numbers/profiles set from the applications for this. But, could see some sequence from the back end, CS_Incident_types_s. Is this the one which is getting populated inti the sr number in the Service Requests form?
    In order to start the number from lets say 1000, do I need to change the sequence?
    Thanks
    Radhika

    Go to Logistics General --> Tax on Goods Movement --> India --> Basic Settings --> Maintain Excise Group
    There select the Excise Group for Depot and tick the boxes "Create EI" and "Depot Excise Invoice"
    thanks
    G. Lakshmipathi

Maybe you are looking for