Many AX / D365 customers have supply chain requirements that include scanning barcodes that are formatted to the GS1-128 standard. This includes barcodes that have multiple data elements where each element starts with an Application identifier and can either be fixed or variable length.
- For use with the D365 Warehouse App and WHSWorkExecute
- Parameters to signify special characters for "start of barcode", "end of barcode" and "end of variable length barcode segment"
- New table for GS1-128 Application identifiers e.g. 00 = SSCC (Licence plate), 10 = Batch etc.
- New table to map the Warehouse App fields to individual barcode segments e.g. 00 = Licence plate, 10 = Batch
- A single scan of a barcode that includes multiple data elements, each with its own GS1-128 Application identifier, will populate all associated fields, e.g. during Purchase receive, one scan will populate Batch + Batch date + Expiry date
- Scanning will include the removal of the Application identifier e.g. 00012345678012345678 will be processed as Licence plate = 012345678012345678
- Applies to all Warehouse App activities that involve the scan of a barcode
Suggested by Microsoft – Planned – 8
Category: Warehouse management
The purchase receiving process has an issue. Mobile client brings the PO line to 'registered' - Nobody in warehouse or office is willing to go to each PO and individually click a "Product receipt" for the registered lines - Batch program in advanced warehousing exists to bring PO lines to "received" status using a LOAD number - So we can auto-create Loads for each PO via a parameter in Transportation - then the batch program , filtering on "inbound" and "open" load status could theoretically handle this.. all PO lines become "received" after being "registered" within a few minutes. But then we still have a Load in status 'received' which is not the final status. somebody will have to manually go to each Load (and we have one load per PO) and say "confirm inbound shipment".. and only then will the load be 'shipped' and disappear from the radar screen. No batch exists to "auto confirm inbound shipments". What can be done to streamline the PO receiving process in advanced warehousing? We would like to request a batch program that processes "registered" PO lines to "received" and also confirms the inbound shipment. There is no business added value to have that last step as a manual step
Although there are third party solution for this, they come with a larger suite of code that over-layers the standard code. They are also expensive for what new customer sees that should come as standard.
Customers that need to use catch weight cannot use WHS, and the change required is very hard to write without over-layering the standard product.
If the supplier delivers a pallet with mixed items, D365 for Operations assigns one license plate to this pallet. When you do the put away process, the warehouse app proposes the items which you have to scan. This is not handy in case of different items. Actually you would have the option to scan a random item of the pallet.
Currently the direct delivery functionality is blocked on a warehouse that implements the Advanced Warehousing functionality. Please remove this restriction and allow this functionality to work across all warehouses.
Could we have some sort of automation for configuration so we don't have to add extra lines to the Location directive action queries just to filter out locations that are blocked for inbound/outbound? e.g. a tick-box on Location directive actions "Use location blocking codes". Would just add a line to the query. Or alternatively a global parameter (or per warehouse) which enforces this.
Simple but would save precious setup hours as we currently need to do this manually on ALL put actions.
The FEFO batch reservation strategy for replenishment is missing. It should be implemented in the same way as the FEFO batch reservation for the sales order work order type in the location directive actions.
If one turns to the Android system in English, some labels in English are displayed and some continue in German.
The language setting in the AX user does not matter.
For example there is English/German mix at logon screen and also when you click on Replenishment menu.
Application version: 7.2.11792.56024
Platform version: 7.0.4565.16212
The current WHS functionality doesn't have functionality to cross dock production requirements.
- A production order for assembly of a finished product with 100 parts
- 90 parts are on-stock
- 10 parts are not on-stock
- Production order is released to the warehouse (allow partial release)
- Wave is created, but not fully processed due 10 parts are not on stock
- Pick & Put work is created for 90 parts
- Supplier delivers the 10 remaining parts
- 10 remaining parts will be registered on the inbound location
- An automatic put away proposal of the 10 parts from inbound to the input location of the production order.
- D365 should consider the open production wave lines for the put away from inbound to the input location
- An automatic split up of put away work to central warehouse location and input location in case when more parts arrives then required.
A vendor return is created (purchase order with negative lines) for an intercompany vendor in company A. This generates an intercompany sales return order in company B.
Now it's required to ship to goods from company A using WHS processes, but in the purchase order there is no way to "Release to warehouse". Therefore all the capabilities of the warehouse processed cannot be used for shipping returned godos to vendors.