WMS-INT01-EN-5.8.0.0
Entersoft Business Suite® | Entersoft CRM® | Entersoft WMS®
New features and extensions
Brief description of version contents
A summary of the main version features. Next up, the full new features & improvements catalog is broken down per category, along with the use of instructions & examples, as appropriate.
Entersoft WMS Back Office
- Container management as stock
- Splitting stock movement requests
Entersoft WMS Mobile
- Specify container in sorting
- 3PL stock movement receipt
- Check of expired real time picking lots
- Extension of the repackaging menu
- Specify target SSCC of ad hoc replenishment
Entersoft WMS Touch
- Product station: Reverse production
- Product station: Master Package in new container
- Packing station: Creating loading requests with parameters
- Receipt station: Focus on the SSCC field
- Receipt station: Ad hoc item receipt
- General implementations: Dialog translations
- General implementations: Automatic weighing
Περιεχόμενα
WMS Back Office extensions
Container management as stock
In this version it is possible to monitor the stock of empty pallets in WMS, in order to improve pallet management in the installation. In particular, the following parameter was added to the container type:
<Monitor container type as item>
When enabling it, in the action of a container that changes position, a corresponding stock movement action is created. In the configuration (of the application) and then, in the containers types, the user selects the relevant type and can set it to be monitored.
Splitting stock movement requests
Respective to the picking and receipt parameters, parameters were added that define the fields by which stock movement requests are grouped per item line.
Fields list for Grouping Stock Movement Requests >WMS_StockMoveRequestGroupingFields
WMS Mobile Extensions
Specify container in sorting
This extension optimizes customer workflows in the sorting part, as sorting in a container allows the option of “on-site” packaging.
In particular, from now on, during picking, whether that happens in picking, or from the separate sorting menu, it will be possible to specify a container (of all types).
• If packing will follow the sorting, then the container will be a sorting container.
• If after loading will follow the sorting, the container can be a pallet or a package.
From the Picking: In RF from menu 3.ORDERS>8.REAL TIME PICKING
From the Sorting menu: In RF, 3.ORDERS > 8.SORTING
By pressing Enter in the SSCC field, we have:
3PL stock movement receipt
In essence, this is an extension of the already existing functionality that has been available for trade documents. In this version, the use of document line SSCC will be supported in the receipt request and for stock documents (ITN, IWB, etc.).
With this optimization, if the SSCC, declared as stated in the receipt document, is scanned by the user, all its contents will be automatically received and there will be no need to scan all line items one by one.
For example, a need to be met with this extension and functionality is the stock movement receipt by Third Party Logistics packages without scanning the items. Intra-branch stock movements are also covered.
Check of expired real time picking lots
In this version, a new check on the lot expiry date was added to the real time picking process.
The aim is to improve the whole process, during which if the user now accidentally tries to pick expired lots, then this warning will be displayed on the RF, informing the user that the selected lot has expired.
Then, the user can choose to proceed with picking or not. In other words, any errors that users may have been making so far will be eliminated, if they hadn't noticed that the lots have expired.
Detailed example as follows:
From RF in menu: 3.ORDERS => 3.REAL TIME PICKING
This feature is also available in hotfix of versions 5.6.0.0 and 5.7.0.0.
A new menu has been added to the RF, named Per package By relationship, through which the per package process will be implemented and only the stock that can be repackaged will be, based on the relationship and the rest will remain as it is.
In short, the entire implementation will work like stock repackaging and the Back Office. With this optimization it will be possible to better update stock in a warehouse, with all the advantages that this entails for its proper functioning.
More specifically, here's an indicative example to illustrate the above improvement.
We have stock:
In RF from menu: 2.STOCK > ON THE SECOND PAGE 2. REPACKAGE BY RELATIONSHIP
The stock is now as follows:
This feature is also available in the hotfix of version 5.7.0.0.
Specify target SSCC of ad hoc replenishment
A new functionality was added to this version with regard to Ad Hoc Replenishment based on demand. More specifically, it is now possible, during execution of the RF flow, to specify a pallet after the target location.
In installations where the items are in a pallet container and package (i.e. nested) this is an implementation that gives great potential.
In, RF from menu:
3.ORDERS > 6. REPLENISHMENT > 3. ADHOC BASED ON DEMAND >
WMS Touch applications extensions
Product station
Production reversal
Basically, when the ‘’Reverse pallet production- consumption’’ button is pressed, the production date will not be pre-filled, but will take into account the period of days set.
More specifically, the user experience in Product Station was optimized, particularly for customers who have production orders with dates prior to the production execution.
This feature is also available in hotfix of versions 5.4.0.0, 5.5.0.0 and 5.6.0.0.
Master Package in new container
In this version, the Master Package (main Package) is supported when creating a new container in the Product Station.
Specifically, until today it was possible to create a pallet container type, so now the existing functionality was extended to offer the user more capabilities when closing the actions they're implementing.
This will result better quality in the user’s work. Below is a typical example of Production in the Product Station, where the default palletization has been selected and then the final step to create a new Master Package container.
This feature is also available in the hotfix of version 5.7.0.0.
Packing station – Creating loading requests with parameters
This feature was implemented in packing through the Packing Station, so that the creation of loading requests is done with parameters, when a target location with a shipment zone is specified.
That means, user is able to easily specify using a parameter if they want to create a loading request or not.
The parameter is: GENERATE_LOADING_REQUEST,
when this parameter is >> True
a loading request is then created,
while when it's>> False, it is not created.
For example, we have the following: the packing action is implemented through the packing station.
With the True parameter we can see that the loading request was created as it should.
The the False parameter we can see that a loading request has been created, as it should.
Receipt Station
Focus on the SSCC field
A new parameter was added to the Receipt Station:
INPUT_SSCC_FOCUS with default value False.
Enabling it will keep the cursor focus on the SSCC field after closing the package. (and not in the item field, as it happens when the parameter is False).
This functionality will be useful in facilities where receipts are implemented in SSCC in the document line (the receipt station is configured for receipt in a request container).
This optimization will eliminate any errors that may have been caused, in cases where the user forgets to put a new SSCC after closing the package during the receipt, which would have risked continuing to digitally receive items in the already closed package.
All this is simplified with the above parameter (cursor focus on the SSCC field) that facilitates user processes.
In the following images, there’s a simple example depicting the full optimization.
The following image shows that the focus is found on the SSCC field.
This feature is also available in hotfix of versions 5.6.0.0 and 5.7.0.0.
Ad hoc item receipt
This implementation is an extension of the already existing Product Station functionality. Now, this idea has been transferred to the Receipt as well. Basically, a new control has been added, so that by pressing it the user can select the item they want to receive ad hoc.
This implementation is considered extremely important, in cases where users don't have a barcode to scan and don't remember the code of the item that needs to be received ad hoc, in order to enter it in the field “Item (to be received)”.
Added a new parameter: AD_HOC_ITEM_SEARCH ---> False
With default value False.
When the parameter is enabled, a new field will appear on the Station.
Ad Hoc Item Search
Below is a typical example to make the extension easier to understand.
Then, by clicking on the control of AdHoc Item Search, we get:
General touch application implementations
Dialog translations
More specifically, this version will now display Kiosk applications dialogs translated. Users will be able to login with a language other than Greek in all kiosk applications, in order to be able to work and utilize all the existing functionalities and features.
This extension is added to the already existing improvements on this part (of translations) from previous versions, so that there is now a fully optimized and full user experience, in all areas of a modern application even for those who log in with another language.
Product Station
Receipt Station
Packing Station
Automatic weighing
It’s an implementation of utmost importance, concerning the Product and Receipt Station. A lot of changes and improvements have been realized in both the Stations, concerning weighing.
The following parameters were added:
<ES00KioskParam>
<Code>AUTOMATIC_WEIGHING_SCALE_MODE</Code>
<Value>False</Value>
</ES00KioskParam>
This parameter has False as default value. By enabling it, the Auto Weigh field of the Receipt and Product Stations appears. Basically, it's the parameter that activates the whole implementation and starts the process of automatic weighing.
<ES00KioskParam>
<Code>WEIGHING_SCALE_TIME_SECONDS_GET_MEASUREMENT</Code>
<Value>0,5</Value>
</ES00KioskParam>
With the above parameter, the user can specify the time limit, meaning when weighing will be “called” by the weighing scale. For example, every half second (0.5 as specified above), it’s required to run a weighing, or depending any kind of time limit that has been specified in an installation.
<ES00KioskParam>
<Code>AUTOMATIC_WEIGHING_SCALE_MODE_WEIGHT_LIMIT</Code>
<Value>0,5<Value>
</ES00KioskParam>
With this parameter, the user will be able to specify the kg limit. After that, the automatic weighing mode - implementation will start running. The limit specified is the max tare of the installation, for example the crate tare.
More specifically, the limit in our case is “0.5”, which means that the weighing scale will start weighing when this limit is exceeded. This parameter is used to specify the maximum weight for the tare.
Receipt Station
Product Station
