WMS-INT01-EN-5.11.0.0
Entersoft Business Suite® | Entersoft CRM® | Entersoft WMS®
New features and extensions
Περιεχόμενα
Brief description of version contents
See below for a summary of the main version extensions. The full new features & improvements catalog is broken down per category, along with user instructions & examples.
Entersoft WMS Back Office
- Optimization of the duration tracking process
- Resource assignment to item movement orders
- Extension of the receipt activation automation
- Support of Standalone Mode
- SoftOne Interface
Entersoft WMS Mobile
- Improvements in item weighing in various RF flows
- Receipt of Pack pallet from branch item movement
- Nested container extensions
- Check for pallet transfer in gross pallet item movement
WMS Back Office extensions
Optimization of the duration tracking process
This version includes an improvement of the whole process concerning the cases where the duration tracking led has been activated in the application.
More specifically, this functionality concerns cases such as consumption stations, where a lot of customers need the entry dates of weighing entries as information – data.
By selecting an action type, such as “Consumption” and by selecting, from within the action type the option “Enable duration tracking” the information that is ultimately required by the user is obtained in a typical installation where, for example, touch screens are used.
As shown in the following image, at Configuration > Warehouse Management, the user selects all action types to display.
In case the user has activated a consumption action type, the duration tracking led will automatically be able to receive the desired data as mentioned above. For example, in case the entry date data of the weighing entry are required.
Resource assignment to item movement orders
A number of improvements – extensions have been implemented, regarding the new activation automation for item movement orders. In particular, the activation automation was modified in order to have the capacity to assign a resource the exact same way as in the other sub-systems (receipts and shipments).
As shown below, by going to the expected item movements menu and selecting the option to enable management in WMS (new), a pop up window is opens where it is possible to select the assignment to a resource and then enable.
This means we can now prevent too many users being involved when implementing processes in an installation.
Extension of the receipt activation automation
In this version, extensions were made to the new automation of receipt activation, so that the user can group PPIs. This results in the creation of a common WP which is expected, instead of two different ones.
In more detail, the following images accurately illustrate an example of the complete process of activation from the new automation to the final stage of creating a common WP.
This implementation will especially assist customers who have large orders to manage and will now optimize the speed of processing their tasks without any unnecessary cyclical waiting times.
Support of Standalone Mode
The new version of WMS (.exe) supports a standalone mode, without the need to install ERP.
WMS can now:
- Update the database itself
- Function as a fully autonomous application (standalone)
Enable Standalone Mode:
To enable the standalone mode, the WMS service must be run with variable Standalone=True.
SoftOne Interface
In this version, a new integration was implemented with SoftOne, providing a single environment for monitoring and managing the synchronization processes between the two systems.
The functionality is explained in detail in the relevant documentation titled “SoftOne Interface”.
WMS Mobile Extensions
Improvements in item weighing in various RF flows
In this version, improvements were implemented in the RF regarding item weighing in various flows. More specifically, the changes will optimize the whole process in the following flows:
- Item movement with orders.
- Ad hoc item movement
- Inventory (counting) with plan.
- Inventory (counting) without plan.
This means that all items that only have kg in the hierarchy, from now on will display the F5 option in the RF, in the corresponding flow menus for weighing. This is an improvement that concerns customers with the specific set-up of items and was deemed necessary that it can be implemented in these cases as well.
Changes have been made to implement the above in specific application (RF) files. More specifically, updates were made to:
- The StockTransferRequests.xaml file for the flow of item movement with orders.
- The StockTransfer.xaml file for the flow of Ad hoc item movement.
- The StockImport.xaml file for the flow of inventory (counting) with a plan.
- The Stockimport.xaml file for the flow of inventory (counting) without a plan.
Regarding item movement with orders, go to RF:
menu 5. ITEM MOVEMENT -> 1. WITH ORDERS and after the steps of this flow are taken as they were being implemented so far, in the final step and after the item is confirmed, it is immediately possible to select with F5 the item weighing. This is something that did not exist before, namely the optimization that was implemented as explained in detail above.
With regard to Ad hoc RF item movement:
In menu 5.ITEM MOVEMENT -> 2. AD HOC and after the steps of this flow are taken as they were being implemented so far, in the final step and after the item is confirmed, it is immediately possible to select with F5 the item weighing.
In the case of inventory (counting) with plan in RF:
In menu 8.INVENTORY-> 1.BASED ON PLAN -> 2.ITEM and after the steps of this specific flow are taken as they were being implemented so far, in the final step and after the item has been confirmed, it is immediately possible to select with F5 the item weighing.
In the latter case of inventory (counting) without plan in the RF:
In menu 8.INVENTORY -> 2.NO PLAN and after the steps of this specific flow are taken as they were being implemented so far, in the final step and after the item has been confirmed, it is immediately possible to select with F5 the item weighing.
Receipt of Pack pallet from branch item movement
An extension was made to the RF concerning the ability to receive SSCC pallet with Pack SSCCs from branch item movement was implemented by scanning the SSCC pallet without confirmation – detailed counting of the SSCCs Pack contents.
The user will now be able to proceed via RF scanner to the actual receipt against the item movement note of the pallets and Pack SSCCs in another branch, receiving – confirming only the SSCCs of the pallets and not all.
The above extension will cover the needs of customers who have regular item movements between branches i.e. export from one warehouse and import to the other with two notes and not with one. Until today, when the stocks reached the opposite branch, the warehouse worker was asked to receive the pallets as well as the packs on the pallets.
However, manually receiving all the Pack SSCCs on the pallets one-by-one takes an incredible amount of time for the warehouse worker and does not ensure reliable receipt of the total stock. So, this is not an acceptable choice.
With the new implementation this no longer exists and the processes are carried out in the most modern way.
Nested containers extensions
This version supports the item movement and immediate import of 3-level (nested) Pack SSCC containers within Master Package SSCC nested in an SSCC Pallet in order to meet the needs of customers using nested containers.
Check for pallet transfer in gross pallet item movement
This functionality covers the need to carry out a container transfer check in the case of gross containers. To date, the container transfer rule (CCP) is not applicable when gross containers are involved, so the user is not asked if they want to also transfer the container.
For example:
If a gross pallet item is collected, then a message dialog will appear to confirm the pallet transfer.
In RF 5.ITEM MOVEMENT -> 1.WITH ORDERS
If an ad hoc item movement is carried out, a message dialog will appear in this case to confirm the pallet transfer.
In RF 5.ITEM MOVEMENT -> 2.AD HOC
