About This Release
Build no. -
Released - August 31, 2017
This version is built on Microsoft Dynamics NAV 2017, build no. .
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 2017 (10.06).
Hospitality:
Worksheet for Production Time with Comparison to Actual Production Time
The Production Time Worksheet can now be used to adjust the production time of items and recipes on KDS preparation stations. It is also possible to compare the assigned production time on the items to the actual ticket time on preparation stations.
Item Filtering Added to the Item Section Routings Page
Item filtering has been added to the Item Section Routings page to make it easier for the user to see which lines apply to a specific item.
A Retail Item/Recipe Station Mapping Check page has been added where the user can see to which display stations selected items are mapped with certain test criteria.
The online help for the Kitchen Display System has been reorganized in order to make the help articles easier to find.
KDS Order Aging Report Updated
The KDS Order Aging report has been updated to use queries. The report gives an overview of how long it takes to prepare KOTs. The report can show totals per KDS report period or information on each KOT for the selected time period.
LS Omni
Known Issues With LS Nav 10.06
The latest LS Omni release, v2.3.3, has the following known issues with LS Nav 10.06.
iOS Mobile POS:
- When paying an amount that is not in the currency denomination, an error occurs yet a tender line is still created.
- App crashes when a loyalty contact pays with points.
Android Mobile POS:
- App crashes when the user pays with cash and the currency is changed afterward.
- App crashes when a loyalty contact pays with points.
Replenishment:
Adjust Coverage Calculation Time Horizon (From-Date)
This fix is for the Effective Inventory calculation, using calculation type Coverage.
In this calculation type, Sales Orders (Purchase Orders, Transfer Orders) were considered within a time range from tomorrow ("WORKDATE + 1") until the defined time horizon in the Replenishment Setup. This created problems in the calculation: if delayed and/or undelivered, orders remained in the system. Replenishment proposed to reorder these orders when their shipment/receipt date went into the past, because they went out of the calculation horizon.
The lower date range has now been changed to zero date (0D). This means that the Effective Inventory calculation now regards all undelivered/delayed orders with a delivery/receipt date in the past as being "on the way". The calculation will not propose substitute orders, unless the user deletes the old orders. This is according to standard NAV principles.
Field Name Changes in Replenishment Setup
The following fields in the Replenishment Setup page have been renamed:
- RIQ Enable Query is now RIQ - Enable Query
- OOS Enable Query is now OOS - Enable Query
- Track Progress Frequency is now Item Counter Interval.
Hierarchy Relations for Assortment Management
Hierarchy Relations is a new concept in LS Nav which lets you create relations between two Hierarchies of the same or different type. A Hierarchy is a flexible tree structure with Nodes which allows the linking of Items, Deals, Stores, and other entities to the Nodes.
This concept can be used for multiple purposes, one of which is the creation of Assortments. To define an Assortment a relation is created between an item-based Hierarchy and a store-based Hierarchy to define which items are available/replenished in which stores.
The assortment rules are stored in the Item Distribution table which can be maintained on the Retail Item Card, FastTab Distribution. Hierarchy Relations can be used to maintain this information in a simpler and faster way. Hierarchy Relations also let you update the relevant tables manually or via Scheduler Job.
Supported features:
- Easy creation and maintenance of Hierarchy Relations
- Top-down data maintenance approach with inheritance
- Copy function for Hierarchy Relations
- Maintenance of multiple versions of Hierarchy Relations (via Starting Date)
- Simple work log
- Comments for applied changes
- Manual creation of Item Distribution records
- Manual creation of Replenishment Control Data (Data Profiles)
- Scheduler based creation of Item Distribution and Replenisment Control Data.
Planned Sales Demand Worksheet Enhancements
New Planned Demand Types
In this release new calculation types for Planned Sales Demand are added. In previous releases a forecast quantity could only be substituted with a planned substitute quantity. With this release new types are introduced to add to the forecast quantity with absolute numbers or % factors. This makes it very easy to cover complex demand changes (overlapping effects) or demand changes for heterogeneous destinations (varying store sizes, regional aspects).
New fields, Line No., Planned Demand Type, Planned Demand Event, and Status have been added to the Replen. Planned Sales Demand (10012374) table and the Replen. Planned Sales Demand (10012322) page.
Also, the Planned Demand (Qty.) field has been renamed to Planned Demand.
Three types of Planned Demand Type can now be selected from the Replen. Planned Sales Demand page:
- Substitute Quantity - the input Planned Demand will be used to substitute the average daily sales of the affected item.
- Additional Quantity (to Forecast) - the input Planned Demand will be added on top of the average daily sales of the affected item.
- Additional % Factor (to Forecast) - the input Planned Demand will be treated as a % factor which added on top of the average daily sales of the affected item.
Planned Sales Demand Events
Planned Sales Demand lines can now be linked to a Planned Sales Demand Event and be maintained directly from the Event page. Prior to this release, Planned Sales Demand could only be maintained manually on the Retail Item Card, which is inconvenient, especially when a large number of items is involved. As a solution to this, a new Replen. Planned Events (10012326) page has been introduced to allow maintenance of Planned Sales Demand in one place. The page can be found in LS Retail - Replenishment - Automatic - Replenishment Planned Events.
Simple Maintenance of Planned Sales Demand
Planned Sales Demand are easily maintained by using the Add Lines and Remove Lines actions on the page for Planned Sales Demand Events. Those actions let the user add (or remove) Planned Sales Demand lines by using reports with a large variety of filters.
Linking Planned Sales Demand to Discounts and Budgets
Planned Sales Demand is a component of Automatic Replenishment and influences the proposals for Purchase Orders and Transfer Orders. Linking the Planned Sales Demand to Budgets and Discounts lets the user plan promotions or seasonal sales which are picked up and considered by Replenishment.
An event can be linked to Periodic Discount or Retail Sales Budget and Planned Sales Demand can then be directly created from the Periodic Discount or Retail Sales Budget by using the Update Lines action. Currently, Discount Offers and Multibuy Discounts are supported, and the Retail Sales Budget must have Budget Type Item, Period Type Day, and budget entries with Store No.
In order to allow Periodic Discount to be used for Planned Sales Demand creation, a new Replenishment FastTab is added to the Discount Offer (99001594) and Multibuy Discount (99001599) pages. The FastTab consists of the new fields Planned Demand Type, Planned Demand, and Consider Calendar. Two new fields, Planned Demand Type and Planned Demand, have also been added to the Lines FastTab in these pages. Planned Sales Demand is created according to the Validation Period ID and Price Group assigned to the discount. Retail Calendar or Base Calendar can also be taken into consideration, where non-working days will be excluded from Planned Sales Demand creation. This can be setup with the Consider Calendar field in the Replenishment FastTab.
In order to allow Retail Sales Budget to be used for Planned Sales Demand creation, a Replenishment FastTab, consisting of the new fields Planned Demand Type, Consider Calendar, and Allocation Rule Code has been added to the Retail Sales Budget Card (10012418).
Transformation of Budgets
In order to allow Retail Sales Budget to be used for Planned Sales Demand creation, the budget has to be on Day, Item, and Store level. Three new actions, Breakdown to Days, Breakdown to Items, and Breakdown to Stores, have been added to the Retail Sales Budget (10012417) page so that all types of budgets can be converted to the required format for Planned Sales Demand creation.
The Breakdown to Days action will break down budgets that are not in Period Type Day (that is Year, Quarter, Month, or Week) to Day. Similar to Periodic Discount, the action can also take into consideration the Retail Calendar or Base Calendar when performing the breakdown, where non-working days will be excluded from entries creation. The quantity in the initial budget entry will be evenly distributed to the new entries.
The Breakdown to Items action will break down budgets that are not in Budget Type Item (that is Division, Item Category, or Product Group) to Item. Only items that are not blocked from purchasing or transferring will be considered. Similar to Breakdown to Days, the quantity in the initial budget entry will be evenly distributed to the new entries.
A budget entry must have a Store No. in order for it to be usable for Planned Sales Demand creation. The Breakdown to Stores serves the purpose of breaking down budget entries without Store No., according to the Allocation Rule Code setup in the Replenishment FastTab. The quantity in the initial budget entry will be distributed to the new entries based on the weights and share % as per setup for each store in the Allocation Rule.
Replenishment Out of Stock (OOS) Calculation Improvements
Two approaches have been introduced to improve the performance of OOS calculation:
- Query based calculation approach - this can be enabled with the OOS - Enable Query field in Replenishment Setup. By enabling this functionality, the calculation codeunit (10012203, Replen. Out of Stock Mgt.) utilizes new Query objects to calculate OOS instead of the conventional nested loop table read approach. Due to fewer reads from the SQL server, enabling Query reduces the calculation time while it increases RAM consumption of the NAV service. It also produces more accurate results as backdated-posting item ledger entries (ILE) are taken into consideration when performing the OOS calculation.
- Parallel calculation approach - by enabling this functionality the items and ILEs to be calculated are put into a calculation bucket according to the number of existing parallel NAS and Schedulers. The calculation is done on the parallel NAS jobs and the master job on the primary NAS waits until the sub-jobs are finalized before it continues with other Scheduler jobs.
These new approaches can be combined or used individually. A detailed description is available in the document Replenishment Calculation using Multiple NAS LS Nav 2017 (10.06) Memo.pdf in the Older Documentation folder delivered with the cumulative update.
Retail Budgets, Improvements
Enhanced Maintenance of Budgets
A Store No. filter has been introduced in the Edit Retail Sales Budget (10012416) and Edit Retail Purchase Budget (10012415) pages. This allows easy maintenance of budget entries for individual stores in Retail Sales Budget and Retail Purchase Budget. The Store No. filter is defaulted with the Store No. from the Retail Sales Budget or Retail Purchase Budget page, but the filter can always be changed to another value. The budget lines are calculated according to the selected store in the filter. If no Store No. filter is selected, budget lines will be recalculated to show the consolidation of all entries. Also, the fields in the Edit Retail Sales Budget and Edit Retail Purchase Budget pages can now be drilled down to show an overview of the budget entries created
Copy Budget Allows Append or Replace
Prior to this release, the Copy Budget action on the Retail Sales Budget (10012417) page always added or appended the budget entries from the source to the destination budget. In this release, a new Option field has been added to the Copy Budget action. With this new field, customers can now add or replace the entries. When Replace entries is selected, all entries in the destination budget will be deleted and replaced with the entries copied from the source.
Budget Consolidation with Master-Child Budgets
This new functionality lets customers work on multiple budgets (for example for different Item Divisions) simultaneously and to consolidate those budgets into one corporate budget.
A master-and-child relationship can now be defined for Retail Sales Budget and Retail Purchase Budget. To achieve this, a Master Budget field, which lets customers specify if a budget can be consolidated into a master budget, has been added to
- Retail Sales Budget Name (99001555) table
- Retail Sales Budget Card (10012418)
- Retail Purchase Plan Name (10012400) table
- Retail Purchase Budget Card (10012420).
A new Calculate Budget from Child Budgets action has also been introduced in the Retail Sales Budget (10012417) page and the Retail Purchase Budget (10012419) page. This action allows the master budget to pull and recalculate entries from the child budgets.
New fields, Consolidated from Budget Name, Consolidated Date, and Consolidated Time, which store the details of the child budgets when entries are merged into master, have been added to
- Retail Sales Budget Entry (99001556) table
- Cat./Prod. Gr. Budget Entries (99001666) page
- Retail Purchase Plan Entry (10012401) table
- Retail Purchase Plan Entries (10012408) page.
Budget Transformation/Breakdown
New functions are added in this release to transform budgets.
Retail:
Amount Based Line Discount Has Been Fixed
Amount based line discount has been fixed, so changes in calculation sequence will not affect the calculation. This fix requires adding a new field, Amount Based Discount, to the POS discount table (POS Trans. Periodic Disc.). This new field affects three web requests:
- GET_POSTRANS_SUSP
- SEND_POSTRANS_BACKUP
- SEND_POSTRANS_SUSP
The setup of these request must be updated.
Changes in Web POS
- Fix for Manager Key and Permissions on Web POS: disabled buttons are now grayed out.
- Employee images in Staff Management have been moved to the Tenant Media table. The old BLOB Picture field has been removed.
- Fix for images in Web POS (background images, store logos, and so on that were not shown on Web POS).
Deal, Store, and Customer Links in Hierarchies, and Hierarchy Relations Between Hierarchies
The Hierarchy system's user interface has been rewritten; pages have been combined for improved overview.
There are now two types of Hierarchies in LS Nav:
- Item/Deal: for a Hierarchy containing links to Items and Deals.
- Store/Warehouse Loc./Customer: for a Hierarchy containing links to Stores, Store Groups, Warehouse Locations, Customers, and Customer Groups.
Hierarchy Relations is a new concept in LS Nav which lets you relate Nodes in two different Hierarchies of the same or different Hierarchy type.
The Hierarchy page has been changed. Links are now added at the bottom of the page instead of being shown in a FactBox. By clicking the appropriate action, it is now possible to add a Sibling or a Child directly to a selected node. Hierarchy information is now displayed in a FactBox. Links can be copied from one node to another by right-clicking the selected links. Multiple links can be added to nodes using the respective Add actions where filters can be set.
Item, deal, and store links to a Hierarchy can be managed directly from their list or card pages.
The Use Distribution field has been removed from the Hierarchy table. Hierarchies of the Item/Deal type can be filtered to a store and this can be done directly on the Hierarchy Viewer page. Attributes can be managed directly on the Hierarchy Viewer page and saved as default.
The web service GET_HIERARCHY_TREE was renamed to GET_HIERARCHY. Both GET_HIERARCHY and GET_HIERARCHY_NODE now support deals/stores. A hierarchy is now retrieved by its code and not by a Web Store number. The Hierarchy code for a web store is kept in the WI Setup table with other web store information.
The term "tree" has been removed from the Hierarchy functionality. For nodes, the terms Parent, Sibling, and Child are used.
For more details refer to the LS Nav Online Help, Hierarchies and Hierarchy Relations.
LS Hardware Station
- LS Hardware Station is now run as a service rather than a separate application.
- Devices can now be ignored which prevents them from being loaded.
- UI usability for Management Portal has been improved:
- Unused config fields have been removed.
- Labels for virtual devices and ignored devices have been added.
- Device tools have been made more user-friendly.
- Drop-down added for device list.
Named Relations Between Products
It is now possible to create named relations for Items. Item Links is used to link an Item to other Items/Deals.
To create Item Links, an Item Link Group is created first, and then Items/Deals are added to the selected group.
Purchase Orders Created Through Retail Campaign
Purchase Orders (POs) can be now be created on the Retail Campaign card by clicking Create Documents on the Actions menu and filling the Quantity field in the Replenishment Lines FastTab. All POs that are created through Retail Campaign will appear in the Documents FastTab.
POS External Printing: Option to Log and Print a Test Page Has Been Added
A test page can now be printed from the POS External Printers page.
A debug log in the POS External Printing setup can now be enabled to see what is happening inside the Device Manager assembly used in the POS External Printing codeunit.
Status Code on Item Status Link Worksheet Now in Sync
The Status Code on the Item Status Link Worksheet is now in sync with the Item/Item Status Links page for items with variants.
The Item Status module can now be used more effectively by using the worksheet for variants and there use the Items Status blocks.
Transaction Balance Rounding Supported by Mobile POS
The Mobile POS (WEB_POS request) now supports transaction balance rounding. Balance rounding is a combination of sales and payment rounding (when tender rounding is used and there is a difference between sale and payment, the result is transaction balance rounding).
The Mobile POS now allows a transaction to be posted as long as the balance difference is within the limit set by the Allowed Diff. in Trans field on the Store card. This field represents the sum of all tender rounding allowed for a given transaction.
Various Fixes
A number of issues, reported by an LS Retail Partner, have been fixed in the following modules:
Retail Receiving, SPO, POS, POS Data Entry, POS Print, POS Terminal, Inventory Worksheet, Replenishment, Statement, Tender Declaration, Retail Calendar, WS Service, and Sales.