-
Add Weight and Volume as data fields to Shipments for wave management
Weight and volume are visible on a shipment - but these are only display fields. In order to prioritise classify shipments according to weight and/or volume during automatic or manual wave creation it would be highly advantageous to add two new data fields to allow filtering/sorting in wave templates and wave filters.
-
Cannot distinguish handling units in inventory without LP management
We cannot see the different "handling units" in inventory without using Licence plates, and that means barcoding when we don't necessarily need/want it. A container type or UoM storage dimension would help immensely.
Examples
- Different vendors deliver in different handling units
- Different customers require different handling units to be delivered. These may therefore require reconditioning before shipping.
- Improve cycle counting and replenishment efficiencies by dealing in handling units
-
Trigger inventory status change after work completion
When a sales/transfer order is released to warehouse and automatically wave processed, any items that are reserved by work cannot be allocated, work will not be generated and the order's shipment will be removed from the wave.
To avoid this situation, the inventory status on putaway work may be set to a value other than that on the sales order, for example, by setting a default inventory status for the vendor.
Once the putaway work has been completed, the inventory status should revert to the default value for sales, or for another value that could be indicated on the work template.
-
Create routing matrix based on item and resource attributes
It is not currently possible to set up a single Route with capacity/resource that varies according to resource and item attribute.
e.g. fill rates per bottle size and per machine.
Ideally: create a new attribute on the item (not Item group - often already owned/defined by finance), and allow the same Operation to be specified for each combination of Route, Item route attribute and resource. The system should be able to determine the optimal Routing line to choose through a bottleneck-type calculation.
Data entry would be possible through a matrix-type form.
-
Location blocking for Inbound/Outbound
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.
-
Batch and Licence plate confirmation during cycle count
Batch and Licence plate confirmations were added as menu item confirmation options.
Unfortunately, these are not available for cycle counting.
These SHOULD be allowed for cycle counting.
This is the same story as for Product confirmation.
-
Improve intercompany direct delivery flows
When creating a direct delivery with an intercompany sales order we cannot block the order across companies. Order holds have been deactivated for these.
When shipping in the warehouse we need to have the originating company's logo, address and contact information appearing on shipping documents such as container contents report.
The SSCC code that is generated for shipping should have the originating trading company prefix and be based on their own number sequence (quick "change company" required).
The SSCC code/LP should be copied across to the trading company so they can be tracked more easily, and appear on any forms or EDI flows requiring this information. Note that direct delivery will soon be enabled for advanced warehousing warehouse - this is the next step forward. https://ideas.dynamics.com/ideas/dynamics-operations/ID0001593#comments
-
Enable work templates on cycle counting work to assign work to users per zone
Allow a work template to be entered for cycle count plans when "Include empty locations" is selected (currently not available for that strategy). NB: "Include empty locations" is the most frequently used strategy for daily cycle counting, as it means "check all locations regardless of if they are full or not". This modification would allow a warehouse supervisor to choose different work templates and therefore different work classes per cycle counting plan (generally per zone). Menu items with different work class assignments could then be setup according to zones that must be counted. A user can thus be assigned a specific counting menu item for the zone they must count. Instead of this, supervisors must ask users to select the correct work pool in "Cycle count grouping" which inevitably leads to manual errors and/or system abuse. -
Efficiently identify all tables with data and associated entities in a gold data environment
Currently there is no way of listing all tables with data in them through the D365 front-end. This is needed in gold data environments as a critical checklist, and to identify missing entities. This would take the form of a listing (form, report) that shows all tables with records as follows: - table name - shared or per company table - number of records per table (and per company where appropriate) - associated data entities, or "None" if a data entity is missing - companies where the table is filled - any templates where the data entity is present. - other relevant information such as table type, category, model The tool would ideally allow a user to efficiently: - identify tables with missing data entities (form filter) - add data entities to templates directly... - ...with intelligent auto-sequencing - that's nice-to-have :) -
Allow pick/put override but prevent user entering location ID
When a user has override permission for pick or put nothing prevents them from entering the location ID instead of asking the system to determine the next-best location. A new parameter "Allow location ID entry" will supplement the current "Allow override for pick/for put" options in the warehouse user options.
