Traceability App Additional information related to the BOM consumption level in table view format
It would be nice to have a numeric identifier which let you understand, once you download data in excel from Table view composition, the bom level consumption related to the given line. Actually you only have list of codes with batch without differentiation related to the BOM layer of the give...
Table view composition
In the table view composition of the Traceability app would be nice to have more information displayed such as Quantity and Item description.
In this way you can easily make the difference between input quantity (component) & output quantity (product).
You can also download it in ...
Thank you for the suggestion—this is a valuable enhancement.
We’re currently working on the design for integrating the Traceability app with Inventory Visibility, which will allow us to retrieve on-hand quantity and item master data, including item descriptions.
This feature is already on our roadmap, and we’ll share an update once it’s officially planned for implementation.
Traceability App consolidation quantity bug
We have found a bug concerning multiple report as finished journal and multiple picking slip journal for same batch and item. E.g.
Finished product à item: x batch y
Semifinished à item a batch b
Journals (listed accordingly ...
Since this quantity is at the activity event level, representing a single fact, we will remove the incorrect consolidated value. The consolidation request will be evaluated to be applied in table format at the genealogy node level - Microsoft Idea.
Traceability solution for siloed materials
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 creat...
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).
Vendor traceability references beyond batch and serial number
In many cases, the traceability to a vendor related material is not done with Batch or serial references, but basically by using other Vendor references for traceability:
- Purchase order number
- Delivery note number (Receipt ID in Dynamics)
- Shipment ID
Search on 'Product'
From the genealogy tree, it doesn't seem to be possible to search on the 'Product' or 'Item', We can only search on Serial, batch, asset or lot. Even when I try te search on an product/item, the system doesn't return any entry...I'd like to be able to pull an overview for a specific item...
The “Find Item” function is currently a work in progress. It enables users to retrieve a list of serial or batch numbers based on the item number and either an activity code or data collection reference.
Administrator
This requirement is already on our roadmap. However, due to the current lack of UoM (Unit of Measure) conversion capability, consolidation across BOM levels is not yet supported in the current Traceability solution.
We’ll keep this item on our roadmap and will provide an update once it’s officially planned for implementation.