Microsoft Dynamics 365
Agree with all previous comments, especially the functionality being available in all kinds of picking scenarios.
Experiencing a challenge in a scenario where containers are filled during production RAF to individual license plates, then parent license plate building would be completed, then transfer order is needed from one warehouse to another. Being unable to pick to the transfer and then receive the transfer from the parent license plate is creating a large volume of non value added scans in the process.
Pick whole quantity of parent licence plate have to be possible in all related proceses like salespick, transfer issue, raw mat pick etc..
Very important and critical feature!
My customer uses a third-party WMS, it isn’t possible to switch to D365. There is an important work scenario, which so far, we haven't been able to integrate to D365. In this WMS the smallest tracking UoM is a box,(in our understanding License Pallet) with a unique serial number (for each box) and each box has a fixed quantity in pieces. The next UoM is pallet - number of boxes are stacked on pallets - also with a unique pallet serial number. The production process is built in such a way - at the end of each line there is a packing station, after RAF FG comes to the packing st.. Here, serial numbers for boxes (& for pallets) are pre-generated and printed on special labels and glued onto the boxes. And already in the labeled empty boxes, each piece is scanned piece by piece, on which there is a basic barcode of the product and the barcode of the box is scanned - they determine in which box the scanned-read product is added and as the box is replenished (there is a box/pcs capacity/unit conversions exmp: 1box = 24 pcs, ) the box is closed and the next empty new box is scanned and goods are scanned and placed on it, and so on until the last multiple of a piece, the goods replenish the boxes. Next, brings pallets - also with pre-generated pallet serial numbers and glued labels, at first scans the pallet LP, then scans each box and puts on pallet until this pallet is full(exmp:palet box capacity-1 PL= 64box). This completes the containerisation and packaging process then all pallets are transferred to the FG WH.
In this WMS, all products are further tracked at the unique pallet level and below at the box level. Any movement or on-hand can be tracked/detailed - which box/which production order/which resource/shift and sold to which customer.
We need a full-fledged nested LP with a RAF/Internal containerization process, with boxes and pallets and the ability to transact products with nested LP.
Very much needed feature. Not all companies require or can utilize the container process, can afford to scan 50 LP's at time of sales pick or logistics dictate they pre-stack pallets with boxes for large future orders where a single scan can facilitate sales pick at time of order fulfillment. Too much good utility baked into this potential feature.
This is required as the movement per parent license plate saves time and money
bu gerekli transfer emri çekme, Hammadde Toplama, satış siparişi toplama vb.
Önceki yorumları açıklamak gibi aynı senaryolara sahibim.
Definitely I agree,
this is needed transfer order picking, Raw material Picking, sales order picking etc. this function should be possible to all wave types.
I have same scenarios like explained previous comments.
Yes, this is needed not only at sales picking, but at RAF too.
Today's warehouses are getting automated and following industry 4.0. Need a plenty of support from MS to sync with advanced warehouse automation.
I have a scenario that I am trying to achieve:
At manufacturing, each box needs to have a unique ID (LP)
64 boxes get wrapped on one Pallet, which should have a unique pallet ID (Parent LP).
Items are batch enabled.
I am looking to build a nested LP at the time of RAF. (For now, am using build License plate after RAF)
At the time of transfer, I am trying to scan the parent LP instead of child LP's which the system is not allowing me to do for the Transfer issue.
I agree, because the nested license plate could be used to manage a container hierarchy.
For example: an item with Each as unit can be stored as boxes and as pallets. Today the only way to do this is using the nested license plate.
Boxes would be a simple license plate and a pallet would be the parent license plate.
In case of sales picking, having the ability to scan the parent license plate would be useful to avoid scanning each license plate. It is time consuming if you have for example 50 boxes (license plates) inside a parent license plate.