WMS-INT01-EN-5.4.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

• ESRF Configuration (ESRF Config.xaml) by the back office
• Configure ESRF Config.json file with new a exe
• New reports configuration process
• New correction Use cases for packing/sorting actions from the back office
• Extensions to shipment tracking with new use cases of canceling/correction/recall
• Extensions to current stock view and new use cases
• Extensions to the Differences based on plan view, for items with a volume/weight MU
• Extensions to the Loading screen
• New shipment KPIs
• New lot traceability dashboard
• Extensions to item and stock EMIS
• Integration with the CAS weighing scale

Entersoft WMS Mobile

• New Android UI Version 2.0
• Simplified inventory menu
• Real time picking: the lot qualifier is considered

• Extensions to unpacking (automatic or not) in the picking process
• Unpacking feature in the Item movements and Putaway menu
• Ability to state and change lot in the Picking menu
• New “Pre-picking” process

Entersoft WMS Touch

• Receipt Station: zero tare check and the ability to set a fixed tare during weighing
• Receipt Station: various extensions to minimize user movement and errors

Entersoft MES

• ES Touch Product Receipts Station: receipt from production in nested containers is possible, along with display of lot details in a dialog upon production completion.
• ESRF Production menu: production and putaway of multiple containers

WMS Back Office extensions

ESRF Configuration (Config.xaml)

In the Configuration menu, at the General category a new "RF Configuration" option has been added, in order for users to configure the parameters contained in the Config.xaml file.

In case the file is being configured for the first time, you must first create the following path: CSRF\WMS\Modules\MyConfig. The file will be automatically saved to that path. If you want a name other than the default MyConfig, you must first copy the Config.xaml product file to that path and then select it from the File selection.

In addition, you can maintain more than one Config.xaml files as long as they are stored in separate AppIDs. The default AppID is "WMS", in case of differentiation you must select the file (and hence the AppID) from the Select File button. The AppID appears at the top right of the screen.

If case you wish to load an existing Config.xaml file from the installation's CSRF folder, then select the file from the Select File button.

Each time you the default value of a parameter is modified, it is displayed in bold font. In addition, for parameters that accept true/false (Boolean) values, a relevant option is available. In an upcoming release, the values of the parameters that accept discrete values (enum) will be displayed in a drop-down list.

The parameters of the ESRF application were grouped into 25 categories (depending on their reference point). In addition, for each of them there is a description of its functionality and the flows to which it applies.

New ESRFJSONConfig exe

The new ESRFJSONConfig exe is available in the application installation folder. It helps configure Config.json files of the ESRF application.

At least one empty Config.json file must have already been created and then selected from Select file. In order to create a new entry, you must at least type the Subscription ID at the top empty space of the grid. The information necessary for successful saving is checked by the process and the user is informed with a relevant message if they are not entered.

New reports configuration process

In the application menu:

Configuration > Organization Parameters > Printers and reports > Reports per WMS resource/location

A new scroller has been added, that returns the Reports, as well as the associated types of actions involved. If a report participates in more than one action type, then the corresponding amount of records is displayed.

On this scroller, you can either configure a report for the first time by selecting "WMS report configuration" from the scroller’s Actions. A screen then appears, where, by selecting the report file and typing the Report code (optionally you can also provide the Description), a new entry is created in the Reports. The process automatically populates all other fields required to generate a report, except for the scroller Parameters and the Printing property set (see below paragraphs).

In the second part of the screen, you can choose upon what type of action the printing, context, operation type, the relevant application and the printing order will be called. By selecting the context, application, and operation type, the process automatically populates the parameters required for proper printing in the scroller’s Parameters field. At this point you should check whether these parameters (the parameter codes) are present on the selected view. A button to check for the parameter validity will be added in an upcoming release.

On the third part of the screen, select the location and/or resource to which the report applies. At this time, you can only set one location and / or resource via the screen. In an upcoming release, multiple options will be available.

If a printer is already connected to the location or selected resource, it is automatically assigned to the Printer field. Otherwise, you must select a printer from the list. By selecting the printer:

• A new printer location (or printer resources) entry is created, if one does not exist
• The Printing property set is automatically populated in the Report, based on the selected printer.

The configuration of an existing report can be modified by double-clicking on the view.

The prerequisite for all the above, is that the printers in the DB are properly configured:

Configuration > Organization parameters > Printers and reports > Printers

The correct printing files must have also been created.

New use cases for correcting shipment actions

In the application menu:

Menu > Shipments > Shipments monitoring

Two new Correct packing and sorting actions processes were added.

These processes are similar to the existing Picking correction. It is possible to transfer the stock to the initial packing or sorting location, by activating the relevant parameter. Similarly, it is possible to cancel the packing or sorting request (if such a request exists) and, correspondingly, the Shipment order request, by activating the relevant parameter.

Additionally, the container, master box and pallet SSCCs have been added to the criteria of both of the new views, for the user's convenience.

Finally, just like in the Picking correction process, it is possible to correct part of the container's content.

Extensions to Shipments Monitoring

In the current release, extensions were made to the view and automation of the Shipments Monitoring, aiming to facilitate the user and perform context processes on shipment orders previously executed through other views and processes.

Essential are the technical changes to be taken into account when updating a custom view in case of an upgrade. The view now has a Scroller menu that includes all automations (new and old ones). Furthermore, a new level of Requests by item has been added below the Work packages & Requests level. This level has been extended in order to return all requests related to the SO and not just picking (as was the case until now).

Finally, a Selector has been added to the following levels:

• Actions
• Ad hoc Actions
• Requests by item
• Document lines

in order to select the correct entries to execute new and old use cases.

In particular, the following functionalities have been added:

Cancellations and corrections

These are 3 automations under the corresponding scroller item menu

Cancel shipping orders requires the selection of at least one Document line (or the entire document). Runs the Cancel Shipping Orders process for all open quantity of the selected document lines.

Cancel open requests is a new use case for the back office, as until now it was possible to cancel a selected (item) request only via the ESRF application. At least one Item request must be selected from the new level. By selecting the document, automatically selecting all the lines of the item request. The process cancels the open (outstanding) quantity of the selected item request as well as the corresponding quantity from the line of the document being fulfilled.

Correct actions is a new use case that calls all known processes for correcting shipping actions (picking, packing, sorting and loading), while also deleting any replenishment actions, as long as these fulfill the selected document(s). It is necessary to select at least one item action line, either on the actions level or the ad hoc actions level. This use case does not allow the user to select quantity on the selected item actions. This is particularly useful when we want to bulk delete actions for one or more SOs, to carry out the Recall process. For this reason, the default values given in the Cancel and Transfer parameters in the initial location are contrary to those applicable in the correction Use cases. It is recommended that the document is not canceled after correction and that the stock always returns to the initial location (in other words, delete the item action).

If documents with actions in more than one type of action are selected, then the process sequentially corrects the actions in the following order:

Loading, sorting, packing, picking, replenishment.

The picking also includes cross docking actions (the existing Picking correction use case has also been extended to take these into account).

Note that all the correction Use cases need to be updated in case of upgrade, as a new parameter has been added to corrections views, to be able to call them from Shipments monitoring.

Finally, no correction option is not by default enabled intentionally, in order for the user to have control exactly over what they wish to delete. Keep in mind that this process is particularly critical in the event of an operating error, as recovery is not possible. Depending on the action type selection, the parameters screen of the corresponding correction process also opens.

Recall shipping orders

This process allows you to Recall shipping orders for multiple selected entries, while it also replaces the existing Delete Shipping order. In addition, it is possible to select the relevant automatic Assignment parameter of a delivery oder (Shipment Order Document) in order to re-route it, without having the user having to do it.

Otherwise, if no automatic re-routing is selected, the order document will return to its Initial status (just like in the Recall shipping order process from the SO form).

The relevant shipping order documents (initial orders) appear in the corresponding field of the view. However, note the system will display the first random document from the potential many who have formed the final SO.

The basic requirement for a Recall that no actions exist on the document being recalled still applies, for that reason it is possible to bulk correct actions through the corresponding use case described in the previous paragraph.

Extensions to Current stock

In this release, extensions have been made to the view and automations of the Current stock for improved reporting to the user.

Keep in mind the technical changes made to the view to be taken into account when updating a custom view in case of an upgrade.

• The view now has a Scroller menu that includes all automations (new and old ones).
• The view parameters were categorized to, on one hand, give more room to the view results and, on the other hand, to make the selection of criteria manageable, as the number is quite large.

Four categories have been created to include the current parameters:

• Warehouse type (including stock dimensions)
• Storage location
• Containers
• Company dimensions

Two new options have been added in the scroller menu:

Current balance in Service MU

This option opens the Balance in a Base/Alternative measurement unit, based on the selected entries of the detailed current balance. Calling the view with balances in Base/Alternative MU is possible with all the details of the selected locations/items and stock dimensions. In the case of Eliminate dimensions, calling the view with balances in Base/Alternative MU should exclude the stock dimensions to return results. For this reason, a new column has been added to the view (with elimination of dimensions) to help the user select, as well as a parameter to the automation of calling the rest in Base/Alternate, so that if the user selects a location with elimination and activates the corresponding option in the automation, then the available balance will be returned based on the item and location. In this case the location, other than the storage location. Is also the Warehouse and the Site.

If the user selects With elimination of dimensions on locations with elimination, then the Balances view will simply be executed in a Base/Alternative without the dimensions.

Manage locations

This option executes the Manage locations view based on the selected current balance entries. Double-clicking the entry of the current balance opens the item form. However, it is often necessary to view the details on storage locations, not on the item. This option has therefore been added.

As regards to the other options in the scroller menu, they essentially include all the existing ones, with a different arranging.

Menu item Stock qualifier includes automations:

• Change reservation reason
• Change disposition reason

Menu item Manage packing includes automations:

• Unpack stock
• Repack stock

Menu item Manage containers includes automations:

• Stock paletization
• Clear containers

Item menu Changes in stock includes automations:

• Change dimensions
• Change item and dimensions

Finally, some of the view’s columns that were found to be frequently used, have been added as always visible, while the ones that were found to be less frequently used have been removed (still available for display).

Extensions to Differences views in Inventory by plan

In this release and in the 5.3.0.0 hotfix, a number of product-related changes have been integrated, concerning the management of item differences that, on one hand, monitor weight/volume MUs, but, on the other hand, are not items with variable weight/volume. The reason is that weight/volume differences in the detailed balance confuse users who are checking inventory differences, although, when it comes to data-processing, weight corrections are required at an action level.

More specifically, the following extensions have been implemented:

• in the Differences view, at the stock counting Work Package - ESWMBalanceComparison - the differences have been removed at a Weight/Volume MU level. The following columns have also been added: Counted/Data-processing.
• in the Differences view, at container level in the stock counting Work Package - ESWMBalanceComparison_Containers - the differences have been removed at a Weight/Volume MU level.
• A new view has been added, ESWMBalanceComparisonWV, which also contains the differences, at a Weight/Volume MU level. This view is now called from the ESWMWorkPackage_StockCountFinalization_DEF form, i.e. from the finalization Work Package. The form has also been expanded.

Finally, the 5.3.0.0 release and hotfix also include a significant correction regarding locations with an Input sequence, during the process of Creating the inventory finalization plan – Counting per Location to finalize: auto-select final locations

Extensions to the Loading screen

A series of extensions were made to the Loading screen, both to increase its functionalities and to facilitate its use, as well as remove all other loading processes from the menu. Note that the old loading processes remain available in the application, they simply do not appear in the application menu.

Keep in mind that the Loading screen consists of 2 parts. The top part displays the item requests To load or item actions with a loading ramp as the target location (for SO without requests).

The bottom part displays the (loading) Stock, based on the results returned by the top of the screen. The extensions primarily concern the ability to select entries To load.

With the Allocate loading option, the process calculates in the Loading quantity column how much stock can be loaded, based on the requested quantity and the actual balance. The Loading stock can now be modified (downwards or with 0), before the Load key is pressed. Allocate loading is always performed when Loading from the application, even if not selected by the user.

The Allocation and Loading processes have not changed in this release. The only thing that has changed is that it is no longer necessary to select all stock entries with Ctrl+A. The application does this automatically.

Select a grouping level

It is now possible to select a grouping level for the data to be loaded. There are 4 grouping levels available, in addition to the default, which is the detailed, by loading request or action item with a loading location as its target location:

• SSCC
• Shipment (Shipment Code)
• SO
• Work Package

The below figure shows the detailed result of the default option.

And the corresponding result based on the same criteria, but with the Grouping option Work Package:

Selectable entries to Load

It is now possible to select entries To load with a Selector. The loading stock allocation at the bottom part of the grid is now carried out based on the selected entries To load. If no entry is selected, then all stock to load is returned.

If you select even one entry, then you must select Allocation for the process to filter the correct stock to load. If you change the selection of the entries to Load, it is necessary that you run Accept and select again, to be able to filter the stock properly.

In addition, some key features have been added to the right-click menu of the selected entries, such as Copy or add/remove columns, filter with selection. Finally, a loading successful or loading failed message is displayed, as long as the loading is performed.

Shipment KPIs

In the application menu:

Menu > shipments > Shipment KPIs > Picking dashboard

The KPIs dashboard related to the picking process, as well as some indicators generally related to Shipments have been incorporated.

In particular, the Picking productivity (number of hours, resources, tasks, packages, weight, volume) takes into account both picking tasks and replenishment processes (in the context of shipments). The same applies for picking indicators of participation in the total tasks (per customer and per resource).

Regarding on-time shipments, the indicator is calculated based on the Agreed delivery date of the Shipping Order and the Issue Date of the final Delivery Note (or Invoice), from the Shipping order invoicing process.

Finally, the Quality of shipments includes the indicator of the Shipment Cancellation Documents (SHC) percentage, against Shipping Orders (SOs) broken down by customer and the total Shipping Orders against Cancellation orders.

In upcoming releases, productivity indicators that also concern other actions (packing, loading, etc.) are expected to be incorporated on Shipments.

The context productivity OLAP for picking resources corresponds to the receipts OLAP, but the picking actions are the ones being taken into account.

Lot traceability

In the application menu:

Menu > Overview > Lot traceability

A new dashboard has been added to inform the user on the actions log, the stock and related documents per lot.

The dashboard parameters require at least one specific lot to be selected. All lots based on the Production Date and Due Day criteria display with an *.

In addition, the selection criteria include:

Short expired: the range over a number of days from today, based on which the lot considered to be short expired is defined in the parameter of the Short expiry range (days) dashboard, with a default range of 60 days.

Expired: an expired lot is considered to be a lot with an expiry date of less than today.

The first grid returns the results of the lots that meet the dashboard selection criteria. If the lot stock is in different Storage locations, then the corresponding entries display. Stock quantity means the current stock of WMS in a Service MU.

Pressing the button in Stock Information opens the dashboard of the stock at both a Service MU level and in detailed packaging.

Clicking on the Code of the selected lot opens the Lot form.

On the selected sentries the user can either set a Lot qualifier, or update the WMS balance with a Reservation reason, by selecting the corresponding Use cases at the top of the screen.

Clicking on the lot entry displays the WMS context actions related to it, in date order.

The relevant production documents (if any).

The relevant shipment documents and the ability to call the document form.

At the top of the screen, the number of lots per Qualifier for the entries is displayed, as well as the number of Long expired vs Short Expired lots.

Extensions to item and stock EMIs

The extensions concern both Import xls files and EMIS.

In particular, in file StockInitialisationTemplateFile.xls, located in Path ..\ Migration\ESWMSZero, concerning StockInitialisation EMI for the stock Migration was the following:

• The redundant fields concerning the pallet SSCC have been removed from sheet Non_SSCC_ActionItems.
• The action of the container created now also runs as expected on the SSCC_ActionItems sheet (concerns an error correction).

In the Import MU Relations EMI for the Migration of measurement units and item barcodes, it is now possible to modify multiple item codes in already existing entries. This applies to the information entered in Sheet 3 of excel file PRODUCT IMPORT RELATIONS.xls located in Path ..\ ESMigration\ESWMSZero.

In addition, an error has been corrected in order to properly update fields Barcode processing required and Barcode processing code of the Multiple codes (barcodes) for the item. Affects the NEED PROCESSMM1 & PROCESS CODEMM1 fields of Sheet 3 of excel file PRODUCT IMPORT RELATIONS.xls.

Finally, an extension was made to the Import MU Relations EMI, so that it can import a hierarchy of Measurement Units, even if these are not present in the item Measurement Units. The EMI now imports entries into Measurement Units of the item, as long as it is not a Base or Alternative measurement unit.

Integration with the CAS weighing scale

It was requested that the CAS CI-20001AS scale be supported by the application. Its support was implemented with a new file in ESScaleDevice:

<FullyQualifiedName>Entersoft.Framework.Peripherals.Scales.CASCommConnector, ESScaleDevice</FullyQualifiedName>

All other configuration for ESWeighingProxy remains the same as the existing one.

Entersoft WMS Mobile extensions

New RF Android version 2.0.0

The new ESRF Android version 2.0.0 is available. Together with 5.4.0.0, as well as the activation of UI version 2 in the application Settings, it utilizes android functionalities for an easier and nicer user experience.

The main features of this version are:

New Login screen & tile menu

Options list with animations and floating Action button (replaced the status bar)

Added search to the menus

Pop up & message view support

Simplified Inventory menu

In this release, the 8 options in the Inventory menu have been reduced to the following 3:

1. Based on plan: corresponds to existing menu 4. Based on plan

2. No Plan: corresponds to existing menu 6. Location stock

3. Counting, with the following sub-options:

   1. Location counting: corresponds to existing menu 1. Location counting

   2. Container counting this option displays by activating the new parameter in Config.xaml STOCKCOUNT_SHOW_CONTAINER_COUNT_MENU

The QUANTITY DECLARED is removed and incorporated into 3. STOCK COUNTING > 1. LOCATION COUNTING, as long as the RF parameters have been appropriately configured.

STOCKCOUNT_QTY_DEFAULT_VALUE &

STOCKCOUNT_QTY_ISEDITABLE

Default logic always requires to declare the quantity. Otherwise, a quantity of 1 is submitted after each scan.

Option 7. INITIALIZE LOCATION remains available to clear the location balance, but is now located below menu 2. STOCKS

Option 5. LOCATION CONTENT is now called through FK (F2).

Option 8. COUNTING DECLARATION is obsolete and has been removed from the menu.

Lot qualifier in Real time picking

It is now possible, in the Real time picking process, to block the picking of lots that have a qualifier set by the following Config.xaml parameter:

LOT_BLOCKED_QUALIFIERS

While also taking into account the location zone set in parameter:

ZONES_FOR_BLOCKED_LOT_CHECK

Keep in mind that these parameters exist, but the functionality was applied to Consumption and Transfer to Production, in the Item movement processes, in Picking with Reservations, as well as in the Transfer container processes.

Extensions to unpacking during Picking

The extensions concern a change in the application behavior during Picking with reservations, related to parameter PICK_AUTOMATIC_UNPACK of Config.xaml.

Essentially, the parameter now takes into account the MU identified by the item barcode and proceeds accordingly.

During default behavior (false), if the item barcode identification returns an MU below the balance MU, then the user gets a message inquiring about unpacking. There is no suggested quantity in this case, as the unpacking hasn't taken place.

If the barcode identification does not return an MU and there is more than one MU in the stock, then the MU of the request is compared and if it is below the balance MU, then the user will be made to select the stock MU. If there is only one balance MU, then it is automatically selected. If the MU of the request is above the balance MU, then a message occurs “No stock was found for the packaging XXX”.

When the parameter is enabled, if the item barcode identification returns an MU that is below the balance MU, then the unpacking is automatically performed in the barcode MU. The quantity must once more be declared by the user, as the unpacking takes place after the quantity has been suggested.

If the barcode identification does not return an MU, then the request MU is compared and if it is below the balance MU, then the unpacking is automatically performed in the request MU. The quantity must once more be declared by the user, as the unpacking takes place after the quantity has been suggested.

These extensions are also available in the hotfix of version 5.3.0.0.

Unpacking in the Item movement and putaway menu

This new feature concerns the Item movement and Putaway of packaging (with requests or not). The user can unpack the stock being moved to the target location with FK (F2: Change MU). It covers cases where the transported packaging does not “fit” in the target location and must be broken into smaller packages.

Especially during Putaway, there is a restriction, for the proper operation of the process, that the putaway must take place for the entire stock, rather than parts of it. Otherwise, the stock details displayed on the putaway screen will not be correct.

This functionality requires the new ESRF Config.xaml ACTION_TYPE_UNPACK parameter. It is not recommended to modify the default value of this parameter.

Change request lot during Picking with reservations

In process 3. ORDERS > 1. PICKING, two extensions have been made, to cover the requirement to declare a different lot than that of the picking request. A prerequisite for its proper operation is:

• The lot dimension must be recommended in the fulfillment of the picking action, with the request and the document.
• The new parameter PR_CONFIRM_LOT in ESRF Config.xaml must be enabled.

The first extension concerns the case where an item barcode containing the lot information is scanned. The process now identifies the lot and assigns it to the picking action, even if it differs from that of the request. Otherwise, if the above parameter indicates “false”, a message occurs “Item not found”.

The second extension concerns the case where the lot must be declared, after the species has been identified. A new field has been added to Picking, that allows the declaration (scan) of the lot of the picking action.

New Pre-picking process

The new process in Picking, available in menu 3. ORDERS > 4. PRE-PICKING, covers specialized use cases and is therefore available in the menu by activating the new parameter PRE_PICKING_ENABLED, in ESRF Config.xaml.

The pre-picking process allows picking at the item/location/MU and/or balance dimension level, without requiring SSCC declaration of the detailed stock container An use example is picking in places such as Refrigerators, where the stock is kept in containers of package class, nested in pallets. Detailed declaration of the package SSCCs during picking is not possible, as the user must remain in these premises for as short a period as possible.

Essentially, pre-picking does not transfer stock digitally, but creates stock reservations after its execution, so that the stock can then be picked through Picking with reservations. Of course, the picking with reservations takes place in an area outside of the Refrigerator, where the stock can now be entered in detail.

The following are required for the proper operation of the pre-picking process:

• The picking requests generated by the routing process should be Real time picking requests
• A picking request type that reserves (with Quantity management) must be assigned to the new parameter in ESRF Config: PrePicking_RequestType

The flow shall follow the same as in the Real time picking, with the following differences:

First screen - select criteria

• WP is scanned/selected
• No final location set (the field does not even exist)
• These fields are not displayed: Package type, Item type, SSCC.

Second screen - confirm location/SSCC

• A new PQ is run, which returns the requests of real time picking.
• A pallet or a location (depending on whether the stock is in a container - as in the case of real time picking) is scanned.

The PQ that returns the location/pallet stock groups, at an Item/Location/Warehouse/Site/MU/Dimension level (if available in the request). No grouping shall take place at a container level.

• The F6 option is not displayed

Third screen - confirm quantity

The same that applies to real time picking min(open request quantity, quantity from selected stock)

The process creates a new picking item request (and a Request), with the same Request type as the one assigned to the relevant parameter REQUEST_TYPE_PRE_TICKET, in Config.xaml.

A check shall run, if the request type declared is reserves stock. Otherwise, a message occurs:

"No request type with reservation is set in parameter “PrePicking_RequestType”.

The Work Package of the new request is the one that has been declared.

All information required for the item Request with reservations is derived from the item Request of the Real time picking and the stock identified by scanning the location and item or SSCC.

Entersoft WMS Touch extensions

Receipt Station

Extensions to tare management

Extensions have been made to the receipt tare management, which are also available in hotfix of release 5.3.0.0.

The first requirement concerns the case of receipt in container where the weight of the container type is known and must be removed as tare from the weight of the weighing.

A new parameter was added in the ES00KioskParams file of the Receipt Station

WEIGHING_SCALE_GROSS_WEIGHT

with a default value of 0

When it’s equal to 1, every time the receipt to container action is entered, then the net weight of the container type is removed from the weight of the receipt action. The Weight of the Weighing must be larger than 0.

The weight of the weighing shall also update the Gross weight field of the Container.

The second requirement concerns the case of packaging receipt (in or out of a pallet) with a tare that is not stable and should be declared by the user at the time of receipt.

To meet this requirement, if the user opens the weight input screen when weighing with a weighing scale, the weight values are pre-populated to allow the user to modify the tare and thus affect the net weight.

The tare value that is assigned by the user remains stable and is displayed on the weighing screen, for all receipt actions within a Work Package, until the user selects Reset tare T-> 0.

The third requirement concerns the zero tare check to avoid user mistakes. A new parameter was added in the ES00KioskParams file of the Receipt Station

Check_Zero_Tare

with a default value of 0

When it's equal to 1, then at the time accepting the weighing, or the generation of the receipt action, the system checks whether the tare is 0 and an error message pops up for the user.

Other extensions

Extensions have been made aimed at the ease of use of the application and are also available in the 5.3.0.0 hotfix.

The first requirement concerns the default activation of field "Receipt in requests container" via the new parameter in the ES00KioskParams.xml Receipt Station file:

ReceiptToContainerFromRequest

With values true/false

The second extension concerns the container receipt completion message “Container receipt has been completed”. The Yes, Cancel options no longer appears, as this is purely meant for informing the user. At this point, another extension was made so that the focus would return to the SSCC field, rather than the Item, as the process will most likely proceed with a container receipt.

Entersoft MES

ESRF Mobile: Production and putaway of multiple containers

This extension concerns process 7. PRODUCTIONS > 4. PRODUCTION RECEIPT and allows putaway of receipt from production of a homogeneous container.

It is necessary to activate the new parameter in ESRF Config.xaml

RCPT2PUT_WHOLECONTAINER_ENABLED

The container receipt is performed as usual, as at present with a MANDATORY declaration of the receipt location at the beginning.

In the new parameter ESRF Config.xaml parameter:

RCPT2PUT_WHOLECONTAINER_NUMBER

With default value of 1

The number of containers is specified, in which the new screen to enter the putaway target location opens.

If > 1 is set, then for each container received a putaway action is created at the user-defined target location. The document is also fulfilled by the putaway action.

By pressing ESC, the user can exit the putaway target location input screen. In this case, only the receipt is registered and the putaway is carried out after that, by the user for each pallet, separately from the Putaway menu. The receipt containers counter is reset to zero.

Product Receipts Station: receipt from production in nested containers

In case receipt from production is selected for a template container, it is now possible to nest it in a container, provided that this is superior to the item’s template container. It applies in cases where the item's template container belongs to the package class, in which case it may be nested container that belongs to the master package or pallet class.

This extension concerns:

• Fields SSCC, Create new container, and Close container were added to the form (simple and weighing form) of the Product Receipts.
• Create new container displays containers of Class 1 - master package and of Class 2 - pallet. The item's template container of must strictly be 0 - Package. There is no option to create a new container, if the template container is not a Package.
• Similarly, if an existing SSCC is scanned in the SSCC field of Class 0 - Package, a message will appear, informing the user that the nested receipt in a container of package class is not supported when receipt to a template container is selected.

The result of this process during Completion is to generate a production action to target containers of the package class (based on an item template container) and pallet/master Package depending on the user selection.

In regard to reports, if it is necessary to have a standard container (package) label print during Submit production and Complete and a container label (pallet) upon Close Container, then the container label print called during Close Container (pallet label) should be "on demand" and the printing called during Submit production and Complete should be "on close" (package label).

Product Receipts Station: show lot details during creation

A new parameter has been added to Product Receipts Station in ES00KioskParams.xml file:

SHOW_LOT_UDFDATA

where a comma-separated list defines the lot UDF fields, which you wish to display in a pop up dialog upon Completion and creation of the production action.

Example: StringField1,NumericField2

More specifically, during Submit production and Complete the following non-modifiable information is displayed:

• Number of packages = 1, if the item action MU of is a Weight MU, otherwise = quantity of the item action
• UDF lot field (in the order defined in the parameter) of the item action. The name of the lot field is the one defined (optional) in the User-defined lot fields.

It is possible to cancel, which stops the continuation of the process and the creation of the production action. By pressing OK, the action is registered and saved as usual.

This extension covers user reporting needs on lot details considered critical to the production process. For example, Rebate and SEQ. NO FE printing per semi-finished PDO package in the dairy sector.

PDF Version