The current RMA process in Epicor is far too involved for one of my customers warranty repair department.
Also, disposing each repair to a job plays havoc with part costs.
We got the RMA process working in Epicor involving BPM’s and posting rules, but it was did not scale up.
The only thing that is required is a record of the time logged/ cost incurred and any parts logged out to the repair.
At the moment a custom solution using the UD tables is been used, which handles the process of receiving a repair and completing it, but the time logging only allows a single engineer on the repair…
Can anyone see any issues with creating a expense code (e.g. Warranty Repair) and getting the users to log in using MES and indirect labor?
The only thing I can think of is if they want actual costs for each repair. A separate code would have to be created for each repair for the labor to be entered.
Not in my experience. Maybe there is an issue with the setup? All of the repairs at my old company did not factor into cost. Although, we were using Field Service, so that might be the difference.
Sorry, it was a few years ago that I looked at this - I meant dispose to job.
The config was done by Epicor and I seem to remember that the job still needed put into stock when the job was completed and this was messing up the cost of goods sold account.
We did eventually get some kind of solution working, but ultimately it was not able to cope with. large volumes where a large number of units were returned, on a sale or return and each needed an inspection job before going back into stock.
I have to admit, while we got Field Service to work, I had to figure it out all by myself. We had multiple consultants from Epicor and 3rd parties try and help us implement it to our process, and none of them could. It was after I was able to put in some dedicated time before I was able to determine that it would work for our process. I literally got no help from anyone else, all the info and recommendations that consultants had given I threw away and started from scratch. It ended up working, but it was not the smoothest process to follow.