RMA processing on IFS - from customer return to reconditionning for resale or manufacturing

Hi Baptiste, for what it’s worth, I thought I still like to give a short and late answer for this topic. 

1) RMA flow in IFS does not seem to cover the need (RMA process in IFS is quite “light”).

The Return Process in IFS is a bit basic, I agree. The RMA can also only return Company Owned stock. All of my customer also require “Customer Owned” for Repairs. So the RMA usually is only used for Returns and nothing else.

2) RMA advance replacement : in standard RMA flow you can only send a new part against the previous one reception.

True, the Repair Work Order offers also a similar functionality, where you can decide to send a replacement part or the original part. However, working with Work Orders is usually unhandy, since no clear flow is given to the user.

3) No shipment is triggered for point 2) juste above - new part sending against previous one reception.

I don’t know anything else than manual work around.

4) I did not find a way to automatically trigger an inspection (quite like at PO arrval) for RMAs reception.
This is not supported.

5) The client does not work with serials or lot batch : how to properly identify parts to be reconditionned (we thought about a dedicated inventory location, “isolated” from operation with part avalability controls, I guess it won’t be enough).

SInce the parts are not serialized, the only other option I see is using new Part Numbers for the Refurbished parts, as described below. That seems a standard in the industry to me.

6) Same point as 5) for parts once reconditionned - client wants a new part_no to be created (initial part_no + “RC” for “reconditionned”. From my point of view it may cause problems in terms of master data maintenance : day to day part creation, confusion for resale activities as well.

I experienced quite a few customers doing that and it seems to work for them.

If the customer would use the Serial Part, he even could use the function “rename Serial” for this.

7) Client works with weigthted average stock valuation (and no serial / lot batch as a reminder) : how to flag a reconditionned part with a lower valuation in stock vs a brand new one ? (i guess the only way is to create a new part no, not recommended from our side, other points of view are welcomed)
Same here, without a lot batch, condition code or serial part, I do not know any way to do that. I know that some customers refrain from the serializing because of handling reasons, but then it’s not possible cater these requirements as well.

8) How to manage reconditionning flow ? we are thinking about the following objects : 
- Work order
- CRO (normally used for external client repair actions)
- Shop order

Two customer stringed everything together via Call Center Cases, but not all objects are supported in that one.

Currently I am implementing a workflow with the Novacura flow, where the user doesn’t  see the borders of IFS functions. But otherwise, you need quite competent end users to make this work.

9) How to follow supplier return - point 2) C) 
- 2 options are possibile :
      - A new part is sent by the supplier to the company (not directlly to the client who already has its new part through previous advance replacement)
      - Credit note

10) How to keep an audit trail between the inital RMA, the new part sent in advance, potential supplier return (and finance associated impacts),the part in stock to be repairded and repair actions performed on the part. Work order allows to perform actions with differents steps and link objects together, but i’m afraid it won’t be “powerful enough” for company traceability needs.

That sounds like a typical case for a non conformance report to me, it can even be connected to an audit. or the mentioned Call Center Case. It doesn’t give a nice flow, but can be used to document everything and corrective actions.

In General, this process is not catered userfriendly in IFS, although possible.