19.1 Release [2019.02]
The full release notes and download links can be found here:
Picking (Sales flow)
- Alternate picking:
Added possibility to force the user to use the first available batch (Ordered on FEFO). If the batch is stored on several locations/SSCC/… the user can still choose from where he wants to pick the stock.
Configurable on the Picklist
This option cannot be combined with 'Ad hoc alternate picking'.
Please see section All, except Ad hoc picking / Force first available batch on selecting alternate item? (Y/N) in Configuration guide / 220.127.116.11.Picklist controller.
- Prepare carts:
The Prepare carts flow can be used for orders where items can be picked into one or more carton boxes in which the items will be shipped.
The flow is based on a wave and makes it possible to assign more than one carton box and more than one movable location to each pick list in the selected wave. Besides, during the flow, an SSCC number is added to each carton box. With the end of the Prepare carts flow the operator needs to start a Multi-picking flow to pick the items into the carton boxes.
- Prepare carts flow documentation:
(1) Configuration: please see section Prepare carts in Configuration guide / 18.104.22.168.Picklist controller
(2) Steps in the Prepare carts flow: please see Functional guide / 19.3. Prepare carts flow
(3) Print event: 203 - Picking: Prepare cart: New SSCC created - please see List of print events
- Adjusted flow to support multiple 'picking logistic units'.
- Packing: As the carton boxes are the final destinations of the items, no packing process is needed. When the operator finishes the multi-picking flow, the stock can go through the necessary shipping flow. If a packing step is needed to double check the content of the box, the operator can start a Consolidated packing flow.
When a pick list has been prepared using the 'Prepare carts' flow, the SSCC that was used during picking is kept. This also means that the packing step needs to pack all goods for this SSCC at once.
Please see Functional Guide / 9.2.2. Consolidated packing flow (keeping SSCC number)
- Limit Wave selection:
Powerful customisation option that allows a query to be used to limit/filter the waves displayed at the terminal. This adds the possibility to limit the waves that can be selected on the scanner.
Available in the Picking and Multi-picking flows.
This can be configured on the Picklist
Please see section Picking/Multi-picking in Configuration guide /22.214.171.124.Picklist controller
Packing (Sales flow)
- new hook flow: AfterLogisticUnitFinishedPacking
This flow is executed after the logistic label is printed.
This new hook flow is similar to the existing hook flow AfterLUIDPacked, which is executed before the labels are printed.
- new hook flow: BeforeFinishLUIDPacking
This new hook flow is executed before performing the tasks to finish a logistic unit.
ASN (Purchase flow)
- ASN import module
This adds a default ASN import, plus a customisation option for the header (to easier integrate into multiple ASN csv layouts)
Please see: Configuration guide /126.96.36.199. Interface for PMX Advance Shipping Notice im-/export and Functional guide /18.3.2. ASN template for importing
- New field 'Verification Code'
Bin locations now have a field for verification.
The verification code is a unique code which can be used for verifying bin locations in the different flows. It has the same function as a bin location code, and its use is optional, that is, you can either use the verification code or the bin location code for verifying the correct bin location in the different flows.
By proving this extra field customers can now use the Bin Location Code to provide human-readable information of the location (or any other type of information) of the bin (e.g. Area 51 Row X) that is displayed in the Mobile Client and they can still validate a correct pick location by scanning a hard-to-read verification code.
On the Mobile Client (AKA FAT client) it will be possible to scan either the 'Location Code' or the 'Verification Code'.
The Verification Code will not be visible on the Mobile Client (AKA FAT client).
Please see Configuration guide/5.2.6. Bin settings
Optimization and Performance
- Manual Archiving of Produmex WMS data
Produmex offers the option to manually archive data from closed documents to decrease database size and improve system performance.
The archiving process moves the selected data from closed documents into other tables in the same database or a separate database, based on the configuration Archive databases and tables can be distinguished by the ‘_AR’ suffix in their name.
Please see: Configuration Guide / 5.1.15. Archiving
- Continuing Adding more WITH(NOLOCK) hints
Produmex WMS continues its large scale approach to performance improvements, and further NOLOCKs hint have been added in:
- PMX_OITM_MEASUREMENTS view
- New version of the tool to create 64 bit Crystal reports for HANA.
This new version supports the new Crystal reports version.
Please see: Tools guide / Hana Report Setting Tool
- Google Route maps
Due to changes in Google Maps API, a new API key is needed to run the Google maps functionality.
Each customer needs to get his own API key.
This API key needs to be entered on the Organizational structure → Select company → Tabpage 'Config'→ Google API key.