Good Afternoon,
We are getting more familiar with DMR processing as we have some new quality personnel interested in ensuring that it gets done properly, all the time. Apparently an RMA fail goes to DMR and then needs to get rejected again to go away. We use RMAs to manage repair of customer owned parts and sometimes the customer tells us they don’t want us to do the work and we disposition to RMA to fail so we can either scrap it or return to customer, as they prefer.
Our quality personnel stated concern “I am now questioning the whole process of generating a DMR for an RMA that fails/ we cannot repair. Material returned under an RMA is customer property. DMR process is to handle our company parts generated during its manufacturing process. Why is the Epicor system even generating a phantom DMR for something we do not own. It seems to me this is an unnecessary step that we have to maintain. Can Epicor workflow be modified to stop generating these type of DMRs.”
So…I think that the quickest way to do this would be a BPM that closes a new DMR created for our Repair Part numbers right after the system automatically creates it. This isn’t a DMR reject, but I am thinking maybe a DMR reject isn’t really necessary. It would be more difficult to ‘backdoor’ a DMR reject than merely closing the unnecessary DMR. The value of the part will always be $0.
Does this sound like a reasonable way to handle this? Any gotchas I might not be thinking of? I tested in another database and it looks good to me…
Thanks,
Nancy