Frans Hoogenraad

MDMI - handle by LP challenges:

User directed process: the worker can scan the license plate and confirm (by pressing OK, not through scanning!) that he puts the LP on the baydoor.

But how does the user know which location to start?

System directed process: the worker is guided to an LP, but does not have to scan the LP to validate.

Put location confirmation by scanning is not enforced (the setting is there, but is not respected.

It should possible to use Handle LP also when putting to a staging location.

Current error message: Invalid license plate when putting to the staging location.

Note that it should work for Sales order picking, Transfer issue picking, Crossdock work, Raw material work.

Ideally there should be an option to enforce specific LPs on salesline and transfer order line and raw mat line in a more logical way than the current solution which is only available for sales lines through the open in excel.

Photo capture option on the warehouse management app

Purpose:

With the mobile device, take a photo of a work exception (damaged product, location blocked etc.) or any other phenomena in the warehouse and attach this photo as a file to the work exception, work line or the current source order line.

Proposed solution:

In the Warehouse management app, add a new button that can be used for uploading a photo taken by this mobile device.

This option could be configurable in the mobile device menu item.

I suggested this some years ago in Yammer, but can not find an idea.

Also refer to the Yammer post of Luca Ganz.

https://www.yammer.com/dynamicsaxfeedbackprograms/threads/2533552878583808

When vendor collaboration is used and the purchase order has status In external review, when trying to receive a purchase order line on the mobile device, the message is unclear.

Product can not be received. Contact your supervisor.

Proposed change:

Purchase order %1 is in external review and can not be received.

Enable Automatically process of work that is not created through a wave.

Purpose:

In some situations it should be efficient when RAF put away work or purchase put away work or transfer put away work or replenishment put away work would be auto finished. E.g. for quality order processing or crossdock work, or when the production machine has an automatic output location selection etc.

Currently it is possible to auto-execute sales picking work and transfre picking work when the wave is being processed, through selecting the checkmark Automatically process on the work template header.

Pls. enable the same setting when work is creaed in a mobile work creation process.

https://www.yammer.com/dynamicsaxfeedbackprograms/threads/2565657701924864

In the form Container types, the field sequence in teh group Container dimensions and Maximums is different ad therefor confusing/error prone:

Current unlogical sequence

CONTAINER DIMENSIONS MAXIMUMS

Container length Volume

Container width Length

Container height Width

Container volume Height

Proposed solution is to sort the fields in the group MAXIMUMS as Length, Width, Height, Volume

In the inventory visibility app, the user should be able to scan or enter a barcode instead of the item ID.

Similar functionality that exists in D365FO WHS Item inquiry.

In the inventory visibility app, the first expected receipts for the current warehouse should be visible incl. date and qty.

Scenario: in the warehouse or I need to check for a customer if there is e.g. 10 pcs on stock. If I see only 7 pcs on stock, I would like to see that next expected receipt is coming Tuesday.

The determination of the ATP time fence does not support working days. When the ATP time fences are typically around 2 to 4 working days, there is no correct way of entering an ATP time fence. It makes a big difference if there is a weekend in between.

Proposed solution is to add in the default order settings (initialized from the accounts receivable parameters, tab Shipments) a checkmark Working days.

Working days should depend on 7 new "ATP working day" parameters Mo, Tu, We, Th, Fr, Sa, Su.

In the ATP calculation (class SalesATPCalulcation), if the ATP time fence is in working days, the non-working days must be added to the ATP time fence (salesATPSettingsMap.atpTimeFence).

Cross docking to specific location per transfer-to-warehouse.

The cross dock template header query is only on items, not on demand.

If the supplied item fits in query of the cross dock template header, the logic checks if the supplying order fits the supply source query.

If not, there is no further validation for the next cross dock template (although there is a sequence number which suggests that it behaves like location directives).

The work template for cross dock can filter on the To warehouse in the temp work transactions, but unfortunately it does not support a directive code to determine the to location directive. The directive code comes from the cross dock template which is the wrong place because the logic does not traverse multiple cross dock templates.

As far as I remember, the to-warehouse was not even filled in the temp work transactions for cross docking.

I raised a case, but it was declined. The advice from MS:

when you want to cross dock to multiple warehouses, use the commerce cross docking.

But this would require a totally different setup and will create transfer orders through a push mechanism instead of using a pull mechanism.

My suggestion is to enable a directive code on the work template (to be filtered on the temp work transactions to-warehouse which should be filled for cross docking as well).

And align the sequence numbering for cross dock templates with the traversing sequence numbering logic on location directives, work templates etc.

In the mobile device menu item indirect activity Register material consumption, there is currently no way to define Default data. E.g. it would be logical to set the machine location as a default location to consume from, or to set qty = 1 when you typically scan serial number items.