LS Nav 11.0 Release Notes

About This Release

Build no. - 592
Released - February 5, 2018

This version is built on Microsoft Dynamics NAV 2018, build no. 19394.

Note:
The 64-bit client is now the default client when opening NAV.

In this version the POS is only supported to run on the 32-bit Dynamics NAV Windows client. We recommend setting up the 32-bit client in the LS Nav Start tool for the POS.

The following is a list of changes and key features in LS Nav 2018 (11.0).

Upgrade to LS Nav 2018

LS Nav 2018 (11.0) supports upgrade from version LS Nav 2017 (10.x). For this upgrade there is no specific LS Nav upgrade toolkit, the standard upgrade works here.

Upgrades from LS Nav 2015 (8.0) and LS Nav 2016 (9.0) to LS Nav 2018 (11.0) will be available in later releases.

Note: The Standard Dynamics NAV upgrade toolkit from version 2015 and 2016 does not work for LS Nav 2018 (11.0).

Retail:

BackOffice: Mobile Tables Removed

Mobile tables for Mobile POS and Omni that are no longer in use have been removed.

BackOffice: Action Management Removed from Standard Tables

Action Management is now handled using events. So-called “Preactions” are created by subscription events that utilize “Database Table Trigger” events. These events are published by the “Application Management” codeunit.

Check Frequency Reset for "Retail message in use"

The value of the Check frequency (minutes) field on the Retail Message Setup page is now set to zero when the Retail Message in use check box is selected.

Click and Collect: New Method of Finalizing Orders

The Click and Collect process has been modified to ship orders. Instead of items being stored and collected at the store, a transaction is created and posted immediately to ship items directly to the customer.

InStore Management: ICT Removed

The Retail ICT module is now limited to only support journal mirroring. Handling of ICT transfer and document handling has been removed, but the module is still able to mirror journal (G/L and ILE) posting between databases.

InStore Management: Standalone Store Removed

The Standalone Store functionality has been discontinued in LS Nav 2018.

Multiple Web Stores on the Same LS Nav Setup

Multiple Web Stores are now supported in a single company. A Web Store number is required when a basket is calculated and web orders are created.

WI Setup and WI Stores have been moved to the Store table.

Jobs to prepare data for eCommerce have been reduced to two jobs: OMNI_INIT and OMNI_UPDATE. Older jobs, processes, and objects that are not used any more have been removed from the system.

New POS in the Demo Data Company

A  new self-service POS, the Coffee POS, has been added to the Demo Data Company. This self-service POS has the Profile #COFFEE-Q and is set up on terminal P0068 for Restaurant S0010 and on terminal P0071 for store S0001.

POS: Clienteling

Clienteling is a new extension to LS Nav POS which adds a new "customer-in-store" experience to the POS. Using the Clienteling view, store staff can now engage with the customer and navigate items in a way similar to what the customer is accustomed to in web-stores.

 

In this first version, which is currently only available for the Windows POS, the framework and basic functionality for Clienteling has been implemented. Later, Clienteling will also be available for the Web POS.

A new POS setup has been added to the Demo Data company to demonstrate Clienteling with profiles #TAURUS. In the Demo Data company terminal number P0069 has been set up with these profiles.

For more information see Clienteling in the LS Nav Online Help for more details.

POS: Performance Boost in Inventory Lookup

In order to improve performance local inventory lookup for serial and lot numbers has been changed.

Replenishment: Allocation Plan Doc. Factbox

Page 99009132, Allocation Plan Doc. Factbox, did not show the Captions Purchase Orders, Transfer Orders, and Sales Orders correctly. This has now been fixed.

Replenishment: Journal Filter Fix

When the Purchase Replenishment Journal or the Transfer Replenishment Journal is calculated with the Add Items to Journal report, the filters for Vendor No., Replenishment Calculation Type, ABC Amount, ABC Profit, Special Group Code, Item Hierarchy, and Item Attribute will now also work for Replenishment Item Quantity (RIQ) calculation.

In other words, when the Calculate Inventory option is selected in the Add Items to Journal report, these filters will also work for RIQ calculation where only items which fulfill the filter will be considered.

Replenishment: Transfer & Purchase Thresholds Management

Transfer & Purchase Thresholds are a new feature to reduce transportation cost. It is a tool designed to avoid small Purchase Orders or Transfer Orders by setting Threshold limits. If they do not meet the Threshold limits, Purchase Order and Transfer Order proposals in the Replenishment Journal will be marked with a warning.

Actual Values in the Replenishment Journal

Thresholds Management calculates and displays the Actual Values for:

  • Quantity
  • Cost Amount
  • Sales Amount
  • Profit Amount
  • Weight
  • Cubage

in the Replenishment Journal Details and totals the values to Replenishment Journal Lines and the whole Replenishment Journal. An Information FastTab has been introduced in the Purchase Replenishment Journal (10012205) and the Transfer Replenishment Journal (10012215) to show these total values. The total fields are also introduced in the Replen. Template List (10012202) where they will show the total values of all journals under the Replenishment Template. The calculation of the Actual Values is triggered when:

  • The journal is calculated using the Add Items to Journal report.
  • The journal is calculated with the scheduler job.
  • A Replenishment Journal Line or Detail Line is added, changed, or deleted.
  • The Quantity or Unit of Measure fields are changed in the Replenishment Journal Line or Detail Line.

Threshold Fields Visibility Setup

It is possible to set up the visibility of the Actual Value fields. A new Replen. Journals FastTab has been introduced in Replenishment Setup with these check boxes:

  • Show Cost Fields in Purch. Replen. Journal
  • Show Sales Fields in Purch. Replen. Journal
  • Show Profit Fields in Purch. Replen. Journal
  • Show Cost Fields in Transf. Replen. Journal
  • Show Sales Fields in Transf. Replen. Journal
  • Show Profit Fields in Transf. Replen. Journal

The check boxes are used to define which of the Actual Value fields should be displayed in the Journal. These visibility settings will be copied to any newly created Replenishment Template. Existing Replenishment Templates will not be updated when these check boxes are changed. It is also possible to setup the Actual Value fields visibility per Journal or Template. This can be done on the Replen. Template (10012201) page, with the Show Cost Fields in Journal, Show Sales Fields in Journal, and Show Profit Fields in Journal check boxes on the Visible Fields FastTab.

Threshold Rules Setup

A new Threshold Rule (10012310) table and Threshold Rules (10012333) page have been introduced where the upper or lower limit of Threshold Fields can be defined. The upper and lower limit can be set up with the Minimum Value and Maximum Value fields, and the options available for the Threshold Fields to be compared against the limits are:

  • Quantity
  • Cost Amount
  • Sales Amount
  • Profit Amount
  • Weight
  • Cubage

The Threshold Rules can be defined per Vendor, Store/Location, and Item hierarchy (Division, Item Category, Product Group, and Item). Three types of Rules can be set up:

  • Purchase to Warehouse - works with the Purchase Replenishment Journal with Purchase Order Type One Purchase Order per Vendor or One Purchase Order per Vendor with Cross Docking.
  • Purchase to Receiving Location - works with the Purchase Replenishment Journal with Purchase Order Type Purchase Orders for Receiving Locations.
  • Transfer - works with the Transfer Replenishment Journal.

The Threshold Rules page is accessible from LS Retail - Replenishment - Automatic - Administration - Threshold Rules, as well as from the Location and Retail Vendor pages.

Threshold Rule Values Calculation

When a journal is calculated, the Thresholds Management will go through all Threshold Rules and copy applicable rules to the Threshold Rule Value (10012311) table, which is an individual Rule definition for a specific Replenishment Journal. Next, the Thresholds will be calculated for the applicable Rules and the results will be shown in the Actual Value field on the Threshold Rule Values (10012334) page, as well as reflecting the Status of the value if it has violated the Threshold (Below Minimum or Above Maximum). The No. of Exceptions field on the Information FastTab in the Purchase or Transfer Replenishment Journal can be used to check if an Exception is raised.

To support the feature, a new Exception Management FastTab has been introduced in Replenishment Setup. This new FastTab has a check box, Thresholds for Autom. Replen., and the Threshold Rule Values calculation will only be performed, if this box is selected.

Block Documents Creation When Threshold Exceptions Raised

A check box, Thresholds Block Doc. Creation, has been introduced on the Exception Management FastTab in Replenishment Setup. If this box is selected, the creation of Purchase Order and Transfer Order from Replenishment Journals with unresolved Exceptions will be blocked. This applies to the scheduler-based document creation and the Create Purchase Orders, Put Creation of Purchase Orders on Batch Posting Queue, Create Transfer Orders, and Put Creation of Transfer Orders on Batch Posting Queue actions on the Journal pages.

Resolving Threshold Exceptions

The No. of Exceptions field in the Replenishment Journal indicates existing unresolved Exceptions. The Threshold Rule Values page can be opened by drilling down the No. of Exceptions field, or by clicking the Show Thresholds action. On the Threshold Rule Values page, users have a choice of:

  • Accepting the Exceptions without adjusting the quantities.
  • Adjusting the quantities in the journal to increase or decrease the Actual Value until it meets the Thresholds.

The Exceptions can be accepted manually by changing the Rule Action field to Accepted, or by clicking the Accept all Threshold Exceptions action to accept all Exceptions in one step. Alternatively, the Threshold Exceptions Details page can be opened with the Show Details action, where it will show all Replenishment Journal Detail Lines causing the Exception. Quantities can be adjusted from the page and the Recalculate Actual Values action on the Threshold Rule Values page can then be used to recalculate the Actual Values and to check if the Exceptions have been resolved.

For more information see Transfer and Purchase Thresholds in the LS Nav Online Help.

Special Order (SPO) Removed

Special Order (SPO) has been removed from LS Nav 2018. Special Order will be replaced by a new functionality, Customer Order.

These POS commands, all related to SPO, have been removed:

  • ADDCHARGE
  • ORDERMGT
  • ORDPMTHIST
  • CUSTOMERSPO
  • MARKSPO
  • GIFT_MARK_LINE
  • POPUPSPODETAILS
  • SPODETAILS
  • SPOCANELLINE
  • SPOFINALIZE
  • SPOPARTFINALIZE

The list of POS commands in the POS online help and in the corresponding Excel document has been updated.

Web POS: Multiple POSes Can Use One LS Hardware Station for Printing

Multiple Web POSes can now be used with a single LS Hardware Station for printing. For more information about the LS Hardware Station see the LS Nav Online Help.

Web Services: Web Store Basket Calculation Light

A new and lighter version of Web Services has been introduced for Web Store Basket Calculation. This improves LS Nav's ability to handle heavy load on the Web Store Basket Calculation.

Hospitality:

Offline Call Center: Error in Finalizing a Delivery Order

An error occurred when finalizing orders in the Offline Call Center. The Web Service OFFLINECC_SENDFINALORDE did not finish since the table Trans. Hospitality Entry was not optional. This has now been fixed.

Hospitality POS: Tender Declaration, Safe Entry Description Adjusted

The length of the Trans. Safe Entry description has been set to maximum 30 characters in the Start/End float.

Hospitality POS: Journal Lines Disappear after Coupon Line Is Voided

This issue has been fixed. Now, deal lines are not lost when a coupon is voided.

Other:

Online Help

On the Online Help home page, a new link, Release Notes LS Nav 2017 (10.0-10.10), opens a single PDF document with all release notes that were published in 2017.