Hi all,
I have a question on how to handle a rebuild scenario in D365.
Scenario: A customer sends back a finished good (FG) to us — this isn't necessarily tied to a sales order at all, it's just a physical return/exchange arrangement: they send the old unit back, we send them a new one. We then take that returned FG, fix/swap some parts on it, and put it back into inventory as good stock.
Question 1 — Receiving the return: Since there's no sales order behind this, how do we bring the FG back into inventory? What's the right document/process to use for the receipt?
Question 2 — The inventory offset problem: Once the FG is received back into inventory, the on-hand quantity goes up by 1. A few days later, we need to rebuild it — swapping RM01 and RM02 out for RM03 and RM04. The problem: a production order for the FG will output +1 FG when reported as finished. But the FG is already sitting in inventory at +1 from the return. If we run the production order as-is, we'd end up with +2 — which is wrong, since we're not creating a new unit, we're rebuilding the one already there.
So do we need to first reduce the FG inventory by -1 (e.g., via a movement journal) to "consume" the returned unit before running the production order, so the production order's +1 output nets back to a correct on-hand of 1? Or is there a better standard way to model this without artificially zeroing out and re-creating the FG?
Question 3 — Capturing the rebuild itself: For the actual swap (removing RM01/RM02, adding RM03/RM04), is a production order the right tool, or is there a better standard option? We need to capture:
- Labor hours spent on the rebuild
- Material consumption (the new RM03/RM04 going in)
- Scrap (the old RM01/RM02 coming out)
Is there a standard D365 pattern for this kind of "rework/rebuild" scenario that handles the swap and captures time/material/scrap without causing a duplicate FG in inventory? Or is the production-order-plus-movement-journal combination really the only way?
Thanks!

Report
All responses (
Answers (