-
Make cells in exported Excel files "Text" formatted
When Excel files are exported using data management, cells are in General format, which mean when we click into them, and they contain a number, they loose their formatting. This is particularly troublesome for strings with mandatory leading zeros, such as for GTIN14 barcodes, or for any text that looks like a number or a date. If all cells in data management generated Excel files were formatted as "Text" then this issue would not arise. -
Improved support for unit of measure conversions for trade agreements
Companies often setup general pricing in "ea", but may also sell to some customers in "cartons", "pallets", or other units of measure. If sales orders are entered in both "ea" and "cartons" then prices (trade agremements) needs to be duplicated to hold the unit price in both "ea" and "cartons". I suggest that a function to automate conversion of trade agreements. The system will auto-generate "child" trade agreements for different units of measure, for any qualifying trade agreement. Any updates to the trade agreement will automatically filter through the child agreements.
-
Add shelf life and direct delivery to Retail category hierarchy defaulting
There are a few important fields missing from Retail product category hierarchy defaulting. - Shelf life dates (all 3 of them), which are mandatory - Direct delivery option + Direct delivery warehouse These must currently be filled manually after product release, which defeats the whole purpose of this feature!
-
Allow check digit check during cycle counting for empty locations
Currently check digit control only appears when a location is cycle counted and has items in it. If the location of blank the operator can simply validate the location without scanning or entering the check digit. This is likely to lead to mistakes, that the check digit would otherwise eliminate. Perversely this will lead to a tool which is meant to improve inventory accuracy actually introducing new ones. Please include a check digit control the first time the user arrives in front of a location, instead of during item scanning, for cycle counting work. -
Improve labour standards - introduce warehouse workload calculations and reporting
Labour standards are crucial to allow measurement of warehouse performances against a target. Currently no reporting is available in either Power BI or SSRS. There is no way of calculating and visioning capacity vs. future workload - ideally a similar system as for "Inventory management > Periodic tasks > Schedule workload" leveraging Master planning should allow a warehouse supervisor to plan their workloads better. -
Improve labour standards - add cycle counting to labour standard time capture and setup
Cycle counting time is not currently captured on work in the labour standards area. - cannot define a labour standard for a cycle counting work line type - cycle counting actual time not captured on work lines -
Add location to work header for cycle counting and other work order types
Once cycle counting had been generated, there is no way of seeing a list of locations with open cycle counting, or of sorting on the work. There is no way to sort on sort codes to ensure that counting is performed in the logical physical route. I would like to see "from" and "to" location, and from/to zone, to be added to the work header. This would then allow ALL mono-line work to be sorted correctly e.g Relenishment work: to allow a user to see all replenishment work from the same location to be performed at the same time (avoid multiple pallet lifts), allow put replenishment work to be done in the correct sorting order. Individual sales/production picks: to sort by location order Putaway: Allow individual receipts to be made, and then grouped by putaway zone. -
Split work for staged license plate
Once work has been picked, a user may wish to split the licence plate into multiple separate licence plates, e.g. if a product need to be sent urgently via a separate carrier, or if part of the picked quantity needs to be cancelled, e.g. customer postpones shipment or quality issue is discovered. Currently work can only be split before the first pick line has been processed, and a pick line cannot easily be split in any case (separate issue, see idea https://experience.dynamics.com/ideas/idea/?ideaid=6a4c7517-b7e8-e811-a140-0003ff68bbbf) -
Enforce zero days batch mixing to ensure only batches with same expiry date are stored on the same location
What I am trying to achieve is to avoid mixing items with different expiry dates in a location. Same item, different batch, same expiry date OK Same item, different batch, different expiry date NOK. The Parameter "Number of days to mix batches" accepts any numeric value, including zero. When a value greater than zero is entered the system will ensure that the difference between the expiry dates for all batches on the location are not more than the number indicated in the "Number of days to mix batches" field. When zero is entered, the system ignores this control and allows any batches to be stored at the location, regardless of the expiry dates. I suggest that the value "0" (zero) means that only batches with the same expiry date can be put at this location. The "Override rules for batch days" on location profiles allows this to be overridden if required. -
Catch weight in ATP calculation
The ATP calculation should use CW units in conjunction with the minimum quantity for catch weight. for CW items. e.g. A customer orders 20 pallets of a product having nominal CW = 1000 kg, min CW = 800 kg. 20 pallets are available in inventory with a combined weight of 19,450 kg. ATP should check for both 16,000 kg (20 x min quantity) and 20 pallets (20 x CW units), and thus assume inventory is available.
You’re offline. This is a read only version of the page.
