Traceability solution for siloed materials

I met recently this kind of customer requirement.

I do like Conrad's proposal : it looks smart and relevant.

Hi Matthieu and Conrad,

Could you please share any business flow details or integration/trigger points related to the Mix Batch scenario?

From a technical perspective, the Traceability genealogy tree supports two approaches:

• Creating a new batch that links to multiple source batches.
• Directly associating a finished product with multiple batches.

Both approaches can be demonstrated using public APIs.

If you could provide more detailed requirements and execution steps, we’d be better positioned to evaluate how Traceability can align with and support the business flow effectively.

Best regards,

Ban

Your practical question is interesting.

From a business perspective, I would prefer second option : 1 finished products to n batches. But how to implement it ? Looks tricky.

So : from a functional perspective, the new batch creation with links to source batches looks easier to implement. It could be automatically triggered when a second source batch is added in the silo. Some business rules would have to be defined in relation with location profile ID. And the "silo batch" could stay alive as long the silo is not completely empty. Only this "silo batch" would be used to populate downstream transactions (InventTrans.InventDim...).

When the silo is empty, the "silo batch" would be cleared, and next number sequence would be ready for future next batch mix.

Let's see Conrad's mind about it.

The scenario is the following:

• You have a production location (a silo, or a location where bulk material for a machine or production line is staged.
• Products are staged on demand with different lot or batch tracking Information
• Production / batch orders are reported that consume the material from the staging location. Because it cannot be identified which batch is has been used, the traceability should be established to BOTH batches (all staged batches).

When you say this can be demonstrated using the API - would that be supported using the standard API from Dynamics or would it require a specific implementation of the API ?

About the new batch linked to multiple source batches :

A solution could be to just automatize this already existing feature : Inventory mgmt / Periodic / Batches / All batch merges.

And of course, consider all specific situation around. I suppose it won't be that obvious.

Is this batch merge feature already considered on Traceability app ?

(Thanks to Patrick LACOUR for the tip).

Hi Matthieu, yes, we are working on the design of Inventory Transfer journal integration for tracking the batch merge.

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).