5
When raw materials are stored in silos, often a new batch is filled into a silo without the silo completely empty. For traceability, this results in a mix of batches (what may be one solution to solve the scenario: create a new merged batch.
The other solution would be to allow to create tracking references on consumption for more than one Batch at a time.
This also applies to scenarios where a production line may be provisioned with material from multiple batches at the same time.
In a way, this could be solved with a concept of "staged batches" on a specific location, that create more than one traceability reference on consumption.
STATUS DETAILS
Needs Votes
Administrator on 7/24/2025 8:12:07 AM
Hi Conrad,
For your case, you still need determine the batch in picking list for system posting, although you have no idea which batch are used physically, right? (Please correct me, if I'm wrong.)
Please let me know if below flow works to your case:
1. Create a batch number for batch merge purpose.
2. Use Inventory Transfer journal to merge multiple batch to the merged batch number created in step 1.
3. Stage the single merged batch number to the silo location.
4. Do manufacturing and post picking list with the single merged batch number.
5. In Traceability, we have 3 layers genealogy structure (for this case). Top is finished goods, 2nd level is merged batch number, 3rd level are the bulk of batch numbers staged into silo.
On the other hand, the public API belongs to Traceability, you need do customization in D365 SCM to post the batches information to Traceability. (Just insert record into D365 SCM table SCTTracingActivity).