Platform Changes LS Retail NAV 2013 for download/Older...In LS Retail NAV 2013 the Standalone Store includes both server and client on the same server so the sum of both Server and

© Copyright 2013, LS Retail ehf. All rights reserved. All trademarks belong to their respective holders

LS Retail NAV - 2013

© Copyright 2013, LS Retail ehf. All rights reserved. All trademarks belong to their respective holders

LS Retail ehf. Katrinartun 2, 105 Reykjavik, Iceland

Tel: +354 414 5700 Fax: +354 571 2728

1 Introduction ................................................................................................................................ 5

1.1 General Changes ........................................................................................................................... 5

1.1.1 Flow fields in replication and Transaction Server jobs 5

1.1.2 Demo Data Company 7

1.1.3 POS Commands 8

1.2 System Requirements ................................................................................................................ 8

2 3Tier Design ............................................................................................................................. 12

2.1 The Architecture ....................................................................................................................... 12

2.1.1 Standalone POS 12

2.1.2 The Online POS 13

2.2 The NST – Navision Service Tier ........................................................................................ 13

3 Menu Suites .............................................................................................................................. 16

3.1 Redesign of the POS Menu .................................................................................................... 16

3.2 The Design Part ......................................................................................................................... 17

3.3 The POS Part ............................................................................................................................... 20

3.4 Redesign of the BackOffice Menu ....................................................................................... 22

3.4.1 Product Design 23

3.4.2 Sales & Marketing 25

3.4.3 Store Management 27

3.4.4 Sales History 30

3.4.5 Reports and Analysis 31

3.5 Administration for LS Retail ................................................................................................. 33

4 Pages ........................................................................................................................................... 36

4.1 Search Pages ............................................................................................................................... 36

4.2 Factboxes ..................................................................................................................................... 36

4.3 Presenting Information in Graphs ..................................................................................... 39

4.3.1 Sales History Toplist 40

4.3.2 Viewing Sales by Stores 41

4.3.3 Sales by Hours 42

5 Assembly, BOM and Prepack .............................................................................................. 45

5.1 Introducing Assembly ............................................................................................................. 45

LS Retail ehf. Katrinartun 2, 105 Reykjavik, Iceland

Tel: +354 414 5700 Fax: +354 571 2728

5.1.1 A New Concept 47

5.2 BOM ................................................................................................................................................ 48

5.3 Prepack ......................................................................................................................................... 50

6 Dimensions ............................................................................................................................... 53

7 Import Export Changes ........................................................................................................ 54

7.1 The Import Export Worksheet ............................................................................................ 54

8 Starting the POS Terminal .................................................................................................. 58

8.1 POS Terminal .............................................................................................................................. 58

8.2 POS LogLevel .............................................................................................................................. 59

8.3 POS LogFile .................................................................................................................................. 61

9 Converting Reports ............................................................................................................... 62

9.1 Future Possibilities .................................................................................................................. 64

10 Staff Permissions .................................................................................................................... 66

10.1 Staff Permissions .................................................................................................................... 66

10.2 Staff Permission Group ........................................................................................................ 68

10.3 Staff Permissions and Permission Group Details ..................................................... 71

10.4 List of Privileges ..................................................................................................................... 76

11 POS Changes ............................................................................................................................. 79

11.1 A New Design for the POS ................................................................................................... 79

11.2 The LS Retail Startup Tool .................................................................................................. 79

11.3 Building Upon the ##DEFAULT Menu .......................................................................... 80

11.4 Run Hospitality Startup ....................................................................................................... 84

12 Appendix 1: POS Commands – New and Removed ..................................................... 86

12.1 New in LS Retail NAV 2013 ................................................................................................ 86

12.2 Not a Part of LS Retail NAV 2013 .................................................................................... 87

Platform Changes - User Guide

Chapter 1 - Introduction 5

With LS Retail NAV 2013 several platform changes are presented. In this guide an overview and some further details are given. The main issues in this document are the following:

3Tier Design o The 3Tier Design introduces new architecture for LS Retail NAV 2013

Menu Suites o The Menu Suites have been redesigned

Pages o Adopted to the Microsoft Dynamics NAV standards for NAV 2013

Assembly, Prepack and BOM o Adaptions and exceptions in LS Retail NAV 2013

Dimensions o Issues that need to be taken into account when handling dimensions

Import/Export changes o Makes it possible to copy POS Setup data from a database to another or between

companies DB Users

o New means in settings for the POS user Converting Reports

o New possibilities in reports and changes to the present ones Staff Permissions

o New and simplified process, yet giving more opportunities POS Changes

o Overall changes that are important in connection to the platform changes

There are more user manuals available that cover other changes that are a part of the LS Retail NAV 2013 the main being the following:

LS Retail NAV 2013 - POS Setup User Guide LS Retail NAV 2013 – Scheduler Changes User Guide LS Retail NAV 2013 – Safe Management User Guide LS Retail NAV 2013 – Mobile Loyalty User Guide



The Flow Fields are not supported in LS Retail NAV 2013 replication or traditional Transaction Server jobs using Data Director. This is because the C/Front option is not available in NAV 2013

Transaction Server requests that use flow fields must be run through web service calls that are defined on the POS Functionality Profile.

Example is Customer Balance and Inventory Lookup A list of requests not supported in the Transactions Server is at the end of this chapter. An

example of the setup of the Functionality Profile is found below Error message will appear for the functionality that is not supported

Setup of Web Services on a Functionality Profile

Flow fields are no longer supported in replication jobs.

Transaction Server

Transaction Server Requests

TS (Data Director()

Web Services



Here is a list of all the Transaction Server jobs. Since the flow fields are not supported any more, Transaction Server cannot be used for all jobs.

Send Transaction TS or Web Service

Void Posted Transaction TS or Web Service

Susp. Retr. Transaction TS or Web Service

Customer Only Web

Data Entries Only Web (if using Voucher Entries)

Staff Validation TS or Web Service

Floating Cashier TS or Web Service

Inventory Lookup Only Web

Login Staff TS or Web Service

Member Only Web Service (sending a transaction does however preserve the member’s points)

Online Trans. Backup TS or Web Service

POS Cash Mgt. Only Web Service

Customer Invoice Only Web Service

Sales Document Only Web Service

A big effort has been made in order to make the Demo Company even better than before. A transfer tool (import/export worksheet) is provided and is useful in new installations.



At the end of this User Guide there is an Appendix where new POS Commands are listed, and those who are not a part of the LS Retail NAV 2013 but were formerly in the LS Retail NAV 6.4 are also listed.

Buttons on the POS with unsupported POS Commands are disabled in the LS Retail NAV 2013. These include:

Special Orders Warranty Hotel Forecourt Offline/Online Call Center Delivery and Takeout

The system requirements for LS Retail NAV 2013 are similar to those for Microsoft Dynamics NAV 2013 but an extended document will be published on the LS Retail NAV 2013 specifications.

The system runs on MS-SQL 2008/2012.

This information is available in the: System Requirements for Microsoft Dynamics NAV 2013 that is available at the Microsoft website.

What is most important for the LS Retail NAV 2013 solution are the Operating system, Server and Client, including the Memory and the Hard Disk space.

According to the Microsoft Dynamic NAV 2013 specifications these are:



For the Microsoft Dynamics NAV Server:

Operating System Microsoft Dynamics NAV Server only runs on 64-bit editions of the following versions of Windows:

Windows 8 Professional or Enterprise

Windows 7 professional, Ultimate or Enterprise

Windows Server 2012

Windows Server 2008

The Microsoft Dynamics NAV Server Administration tool does not run on Windows Server 2008. It does run on Windows Server 2008 R2

Windows Small Business Server 2008

Windows Small Business Server 2011

Hardware Resources For Microsoft Dynamics NAV 2013 the requirements are:

Hard Disk space:

500 MB

Memory:

2 GB

In LS Retail NAV 2013 the Standalone Store includes both server and client on the same server so the sum of both Server and Client requirements are a minimum. In LS Retail NAV 2013 more space and memory will be needed because of the Data Director. For LS Retail NAV 2013 a separate document will be provided at later stages.

Additional Software Microsoft .NET Framework 4.5. Microsoft Dynamics NAV 2013 installs this software if it is not already present on the target computer

Active Directory is required for the Microsoft Dynamics NAV Portal Framework for Microsoft Sharepoint 2010

Windows PowerShell 2.0 is required for the cmdlets for Microsoft Dynamics NAV Administration. Windows PowerShell 2.0 is included with Windows Server 2008 R2 and Windows 7

Microsoft Report Viewer 2010 is required for Save as Excel or Save as PDF functionality. Windows Dynamics NAV 2013 Setup installs this software if it is not already present on the target computer



For the Microsoft Dynamics NAV Windows Client:

Operating System The Microsoft Dynamics NAV Windows client runs on the following versions of Windows:

Windows 8 Professional or Enterprise, 32 or 64-bit editions

Windows 7 Professional, Enterprise or Ultimate, 32 or 64-bit editions

Windows Server 2012

Windows Server 2008 R2

Windows Server 2008, 32 or 64 bits editions

On 64-bit editions of Windows the Microsoft Dynamics NAV Windows client runs in WOW64 emulation mode

Hardware Resources For Microsoft Dynamics NAV 2013 the requirements are:

Hard Disk space:

30 MB

Memory:

1 GB

In LS Retail NAV 2013 the Standalone Store includes both server and client on the same server so the sum of both Server and Client requirements are a minimum. In LS Retail NAV 2013 more space and memory will be needed because of the Data Director. For LS Retail NAV 2013 a separate document will be provided at later stages.

Additional Software Microsoft .NET Framework 4.5. Microsoft Dynamics NAV 2013 Setup installs this software if it is not already present on the target computer

Microsoft Lync 2010 or Microsoft Office Communicator 2007 is required for instant messaging and Telephony API (TAPI)

Microsoft Office 2010 is required for mail merge. Microsoft Office 2010 or Microsoft Office 2001 SP1 is required for Outlook client integration, budget import and export and from Microsoft Excel XML and Sharepoint links

Microsoft Dynamics NAV 2013 Setup can only install the Excel Add-in if Excel 2010 is present on the target computer

Microsoft Office 2010 is required of OneNote intergration. However, OneNote integration is not supported for 64-bit editions of Microsoft



Office 2010 running on Windoes Server 2008

Active Directory and Microsoft Exchange Server 2010 are required for email logging


Chapter 2 - 3Tier Design 12

With the 3Tier design of LS NAV 2013 and LS Retail NAV 2013 native databases are no longer used

and the system only runs on MS SQL databases.

The three tier architecture of the NAV 2013 consists of the following:

1. The Database Tier:

The database components run on the following versions and editions of SQL Server:

Microsoft SQL Server 2012 Express, Standard, Enterprise or Business

Intelligence (64-bit editions only).

Microsoft SQL Server 2008 R2 Express, Workgroup, Standard or Enterprise (64-

bit editions only).

Microsoft SQL Server 2008 Express, Workgroup, Standard or Enterprise (64-bit

editions only).

2. The Server (middle) Tier. The Navision Service Tier, NST, also needs 64-bits.

3. The Client Tier. This is the RTC, browser or Sharepoint. Here 32-bits are sufficient.

Standalone POS: Needs to run 1, 2 and 3 and therefore has to be 64-bit.

The Client can be any of those:

An RTC Client running BackOffice or POS

A browser running BackOffice functionality. Note that some parts of the BackOffice

functionality are not supported in a browser (charts and more).

Sharepoint

The Standalone POS requires 64 bits as a minimum.



The Online POS requires only 32 bits as a minimum on the POS hardware.

A lot of what used to be processed on the Client in earlier versions of the LS Retail NAV is now

processed on the middle (NST) tier.



NST serves many Clients at

The same time

SQL Server

The SQL Server serves many NST at

the same time

Client:RTC

Browser Share-point

A lot of activites have moved

from Client to NST in NAV 2013

NST: Not always necessary to send requests to SQL, the NST layer is able to process

data

In previous versions of LS Retail NAV the OCX and Automation played an important part but the

new 3Tier design uses a different approach where the Data Director (DD) is for instance working on

partly different levels of the design. There is an overview of this in the following table.

NAV 2013 NST (NAV Service Tier) Windows Client (RTC)

OCX No No

Automation No Yes

.NET Add-ins / libraries Yes Yes

Yes: It is possible to run the following integration options on the NST/Client

No: The integration option is not available.

The main changes are: If possible the .NET Add-in / libraries are used. If the task doesn’t involve a

user then it can be run on the NST tier, otherwise on the Windows Client.

Documents like Word and Excel are either processed on the NST or Client depending on the nature

of the tasks performed. There is a difference on the way this is done.

When you are uploading documents or data, then the data is copied from the NST to the

Client.

When you are downloading documents or data then the data is copied from the Client to the

NST.



POS Running:

NAV 2013 NST Client (RTC, browser or

Sharepoint)

OCX NO No

Automation No No

.NET Add-ins / libraries Yes. Dataset requests are run

on the NST

Yes. Add-ins running the

interface are run here

The preferred way of handling data is to process it at the NST level. In some cases it is still a advisable to use the RTC Client.


Chapter 3 - Menu Suites 16

The Menu Suites have been redesigned in the LS Retail NAV 2013 to serve the purpose of simplifying the design and make it easier to use and the access to the most important tasks in a more direct way than before.

Under the LS Retail there is now an option called: Point of Sale that is divided into two main menu parts, the POS and the Design sections.

A part of the forms formerly under the POS is not there anymore. These are the forms that are neither necessary for the POS design or use of the POS. They will be available under BackOffice, either as new pages or pages with functionality that formerly was also available as a form in BackOffice, in the earlier versions of the LS Retail NAV BackOffice.

This division is clear and reflects the emphasis on keeping the design of the POS and the use of the POS as separate parts. Here functionality that was earlier a bit more obscure and sometimes required some digging into a setup is accessible on the surface and most often just one mouse-click away. Anything that was in the menu before but not related directly to the use of the POS has been moved to a more logical location.

All the tables that the POS uses should now be more easily accessible.

When you select the Point of Sale directly you can either:

Choose by department … or choose by category



The Design part of the Point of Sale sub-menu is divided into:

Lists Tasks Administration

These headings are a part of the overall new structure of the Menu Suite, for the POS and the BackOffice and correspond to similar menus.





Under the menu Lists there are the following sections, each with one or more sub-sections:

Interface Data Functionality Appearance Hardware

Here there are three sections that special attention should be paid to. Under Interface there are many important pages that decide the contents of the POS as well as setting the controls used.

Under Data the Menu Profiles, Menus, Data Tables and Tags pages can be found.

Finally the Appearance section includes the both the predefined Style Profiles and Button Skins and provides tools for making new ones. This is also where Fonts and Color Setup is accessed.

Being able to access the Interface, Menus and Styles directly has the main purpose to make all work on it faster and more effective. Better overview should be provided and it should be possible to get together all the parts that are needed in creating the POS in relatively quick and easy manner.

Under the menu Tasks you will find one section:

Design Transfer

This is where you go if you want to import POS design from one company or store to another.



Under the menu Administration are the pages that are expected to be in use more often than other pages. Here you will find the following sections:

General Setup

Under the POS part of the Point of Sale sub-menu there are several options that concern the use of the POS. The following main sections under this part of the menu suite is:

Tasks History Administration



There is one option under the Task part of the POS menu: Run Client, which opens the POS with all its complex functionality.

The History part gives access to past activities for overview and further inspection.

Under Administration there is direct access to Retail Users, which is an improvement to the menu. Otherwise the menu is divided into two sections:

Profiles General



The main purpose of the redesign of the BackOffice menu is to enable the user to access from one location everything he or she needs to perform a certain task. There is in a few places some overlap. It may be necessary to be able to perform similar tasks in different roles, for instance as a sales person or a store manager. The overlap is both within the different parts of the BackOffice menu as well as between the BackOffice and the POS menus.

The BackOffice redesigned menu contains five main categories shown on the main menu:



In the menu, when you select the BackOffice directly you can either select to:

Choose by department

… or choose by category

We will take a closer look at the departments as an approach to the menus but either way you

choose - departments or categories - you will get all the options available under BackOffice.

The Product Design menu gives you an access to everything that has to do with items and item handling. The sub-menu is organized in a standard Microsoft Dynamics NAV 2013 way divided into Lists and Administration.



Under the Administration menu the Groups menu shows the item hierarchy. It is also where you will find the Barcodes, Variant Framework, Unit of Measure and Attributes.



In the Additional section there are several pages that can be useful to be able to reach directly, such as Retail Price Groups, Inventory Setup and Item Finder.

The menu reflects the connection between the activities in BackOffice and on the POS.

This part of the BackOffice menu covers what is needed to get the products to the marked. It involves everything that concerns prices and sales, discounts and special offers. Within the menu the main assignments are grouped together. Everything aims at being able to meet the user’s needs which is exactly what is included in the idea of role based menus.



The Pricing, Offers and Coupons sections can be found under three sections: Lists, Tasks and Reports and Analysis but with different roles according to the corresponding headers.



In the Store Management the emphasis is on the Store Manager and his or hers interaction with the

Stores. This is where the POSes are set up, the Payment Types are decided and the End-of-Day

management takes place as well as other related issues such as getting statistics from the sales.



The End-of-Day procedure is dealt with under Lists, Tasks, Reports and Analysis, History and

Administration but in different way according to what is implied in the different headers.





Sales History gives a more general overview over activities on the POS and sales as a whole than the previous options for Store Management and Sales and Marketing.



Reports and Analysis provide tools to build upon in planning and for various information gathering and processing. The menu is a long one consisting of the following sections:

Item o Item o Stock o Shrinkage o Analysis

Sales & Receivables o Analysis o Sale o Group Sale o Item







There is a separate Administration section that has been put directly under the LS Retail menu. Under this section is now some of the General Setup, that formerly was under either the POS or the BackOffice, but was in fact more general to be under either.

Here we will find for instance Numbering, Dashbord, Basic Setup, Data Setup, Statistics and Web Services.




Chapter 4 - Pages 36

One very important part of the Microsoft Dynamics NAV 2013 is the transformation from forms to pages. This includes redesign and new opportunities in using the pages: The LS Retail NAV 2013 is built upon the new way of thinking and at the same time the features and functionality of the earlier versions of LS Retail NAV are preserved. All the functionality that is in use has been kept but unnecessary fields and features are gradually being removed to simplify and clarify the part of the functionality that is important. Pages are a core part of the new design and present many new possibilities. They are in LS Retail NAV 2013 adapted to the Microsoft standards as they are in the Microsoft Dynamics NAV 2013. There are several new features in the new Microsoft Dynamic NAV 2013 that LS Retail has already started to utilize and even more future prospects.

Anyone that is familiar with the Microsoft Dynamics NAV 2013 should also be at home in the LS Retail NAV 2013.

All the pages of LS Retail NAV have undergone some changes in structure and appearance in the 2013 version. Functional changes have also been introduced. The object of the changes is both to adapt the LS Retail NAV to the Microsoft Dynamics NAV standards and improve the earlier versions.

There are several novelties such as use of Factbox that are a part of both Microsoft Dynamics NAV 2013 and LS Retail NAV 2013. Therefore if you have good understanding on Microsoft Dynamics NAV 2013 and the changes that have been introduced with that version of the product LS Retail NAV 2013 should be quite easy to pick up. Not everything has been implemented in exactly the same way in these two products but on the whole the similarities are rather a rule than exception.

The Search option (Ctrl+F3) is a useful tool when finding your way in the new LS Retail NAV menus, since considerable changes have been made on the menus for the BackOffice and the POS.

In sync with the Microsoft Dynamics NAV 2013 there is a Search field in the top right corner of the address bar on every page. There you can search for any page you want.

You will be shown the options for pages when you start typing in the Search field according to the Microsoft Dynamics NAV 2013. A drop-down list shows page names containing the character(s) you type. The drop-down list changes as you type more characters, and you can select the correct page from the list when it is displayed. The second column in the drop-down list shows the navigation paths to the found pages.

One of the new features in the pages of LS Retail NAV 2013, originated from the Microsoft Dynamics NAV 2013, are the Factboxes. They list places and task pages and provide you with additional



information. This means that you can quickly find related information about an order, customer, invoice, item, or vendor.

For example, on the Retail Customers list, you can use the Sell-to Customer Sales History and Customer Statistics – Bill-to Customer Factboxes to get a quick overview of a customer’s sales statistics without opening the customer card.



From the Facbox it is possible to access data more directly than before and without opening the page for the customer in question in this case.

LS Retail uses Factboxes when setting up the system, including Stores, POS Terminals and Import/Export Worksheet.



There are new possibilities for the presentation of data in various kinds of graphs in the LS Retail NAV 2013. Some have already been implemented. These are, as other platform changes, based on the features that are available in the Microsoft Dynamics NAV 2013. Sales information can be presented and compared in many ways as the following examples show.

Under Sales History, LS Retail, BackOffice, Sales History, Reports and Analysis, there are many ways to view and present data in graphs and the examples are taken from there.



Various information on the Sales History Toplist can be viewed in graphical way. Go to LS Retail, BackOffice, Sales History, Reports and Analysis, Reports and Analysis, POS Transactions, Toplist. After selecting the options such as selecting period if needed and deciding whether you want to see the graph broken down by:

Transaction Customer Item Category Product Group Staff

Then the Chart option is selected.

In this case a Toplist Pie Chart Amount by Product Group is shown.



If you select to view Toplist Pie Chart Qty. by Items another graph is presented.

The graphs can, just as the lines, show all sorts of combinations by using filters and sorting the sales data by the different criteria such as No,, Quantity, Amount, Profit or Discount Amount. On the chart the combination is visible, such as: Amount by Product Group or Quantity by Items.

It is also possible to view sales data in graphical way either for one store or compare data between different stores. You can for instance compare sales between periods for different stores. Select LS Retail, BackOffice, Sales History, Reports and Analysis, Ledger Entries, Store Hierarchy, set Date Filter and select Chart to get the Sales by Stores for the period.



It can be useful to know which opening hours attract most customers. One of the options to view graphs over sales is to see number of items sold per hour in different stores. You will find this at: LS Retail, BackOffice, Sales History, Reports and Analysis, POS Transactions, Hourly Store Sales, set Date Filter and other criteria and select the Chart to view. There are several filters that can be used, both for periods, stores, presentation and what information is required such as, Gross sales, No. of Items or Transactions or Averages for the No. of Items or Amount:

One selection might be Gross Sales per Hour shown per day as a Line Chart:



If the selection is No. of Items and the period interval is an hour a column graph looks like this:



These examples are just a few of many possibilities that can be retrieved from the sales data and presented in many different ways, given various criteria.


Chapter 5 - Assembly, BOM and Prepack 45

There have been some changes on how BOM (Bill of Material) is treated and a new concept and procedure, Assembly and Assembly sales have now replaced most of the functionality where BOM was formerly used. This is how things are done in the Microsoft Dynamics NAV 2013 and in most cases LS Retail NAV 2013. Anyone familiar with the standard Microsoft NAV approach will also be at home in LS Retail NAV 2013 for this functionality.

There is only on two exceptions, when the earlier BOM or Prepack functionality is used. This is:

In certain cases when statements are booked and posted using BOM Using the Prepack functionality

Looking at the exceptions the statement posting is still done mostly as it was before in the earlier versions of LS Retail NAV. In this case the LS Retail method is used in handling statement BOM instead of using Assembly BOM.

Before taking a look at the exceptions here is a short overview over how the Assembly is introduced in the documentation for Microsoft Dynamics NAV 2013. However it is expected that the users of this guide are familiar with the general procedures of the Dynamics NAV 2013 and able to find necessary information in the product’s user guides and online documentation.

The location for Assembly and the Assembly Sales can be looked up in the new Menu Suite quite easily.





A new concept, Assembly Management is now being introduced as a complete feature set to manage assemblies in integration with Sales, Panning and Warehousing.

In the earlier versions of LS Retail NAV another approach has been used to resolve the issues that Assembly is using.

An assembly item is defined in Microsoft Dynamics NAV 2013 as a sellable item that contains an assembly BOM. Assembly items can be set up to be assembled to order or to stock. Usually this depends on how much customization is needed to fulfill a customer’s order for the item.

Just like production orders, assembly orders are internal orders that are used to manage the assembly process and connect the sales requirements with the involved warehouse activities. They



differ from other order types because they involve both output and consumption when you post them.

On the Retail Item Card (LS Retail, BackOffice, Product Design, Lists, Retail Items, select an item) it is decided whether BOM is exploded when a statement is posted. If you want to do that the Explode BOM in Statem. Posting is marked of each item you want to handle so.



One simplified example of how this is used could be an offer with chicken as a primary product, sold with sauce and French fried. This offer could be handled in two different ways. Either with the Explode BOM in Statem. Posting checkbox marked or unmarked.

A chicken sold as an offer with sauce and French fried with the checkbox marked would be handled in this way:

When the chicken was sold with sauce and French fried the sale is treated as a sale of the primary product, the chicken, alone. This requires Positive/Negative adjustment of the



goods, since the chicken has some additional (positive) items sold with it, but the sauce and the French friend would be negatively adjusted, since they are now sold as a part of the chicken. When the statement for this sale is posted it only contains the chicken.

In the sales overview and reports you can only see that a chicken has been sold.

If the Explode BOM in Statem. Posting checkbox is not marked then the procedure would be as this:

When the chicken, sauce and the French fried are sold the sale would be for all three items separately and the posting of the statement as well.

In the sales overview and reports you can see that a chicken, sauce and French fried have all been sold.

In real life this example would normally be even more complicated, since the additions would also be the ingredients of the chicken part crust or coating.

The Prepack functionality has not been changed to adapt the changes that were made when the Assembly features took over most of the previous BOM and Prepack behavior.

A prepack is a collection of items that are normally packed in one unit which is called prepack. An example is an item that is manufactured in many sizes and/or colors (sweaters, skirts). Such items are usually opened and each item sold separately in stores. This opening is similar to the BOM exploding procedure. The content of a prepack is stored as a Retail BOM Component. This means that every single item in a prepack is an item in the Item Master.

On the Retail Item Card at LS Retail, BackOffice, InStore Management, Item, Retail Items (there are more paths available to reach the Retail Item Cards) under the Attributes tab the BOM Type filed is set to Prepack when you intend to use the Prepack option for an Item.



For further information on the Prepack functionality the Pre-Pack Quick Guide for LS Retail NAV 6.2 should be consulted.

The page for the Prepack worksheet is at LS Retail, InStore Management, Worksheets, Tasks, Prepack.



This opens a page for prepack worksheet where filters can be applied if needed.


Chapter 6 - Dimensions 53

There have been some radical changes on handling dimension in the Microsoft Dynamics NAV 2013. This is reflected in LS Retail NAV 2013 as much as possible, but certain issues have to be resolved because of the nature of these changes.

There is an issue that has to be handled carefully when using the LS Retail procedure for the stocks and supply part of the LS Retail NAV system. When a dimension ID is used in multiple databases using replication, there is no guarantee that the dimension ID will be the same in both or all databases.

Earlier on the dimensions for the data were kept to store them but now the IDs for the dimensions are kept, instead of the dimensions themselves.

An example could be that a booked line would be linked to the dimension ID in the present Microsoft Dynamics NAV 2013 instead of being linked directly to the dimensions as before.

Normally this is no issue at all but one has to be thoroughly ware of the risks that may be included under exceptional circumstances. This is especially if data is being moved from one database to another one. There is no guarantee that the data would keep the same ID as before when it is entered into the new database.

In the LS Retail NAV 2013 this issue has been resolved for the InStore Management module (Standalone Store). Specific measures have been taken by LS Retail to avoid this affecting the data in this particular module.

Since the dimensions that are at a risk, even though minor, are most often related to financial procedure this is pointed out to emphasize that it is safer to be careful about the IDs. Also to point out which part of the LS Retail NAV 2013 has been dealt with specifically because of this.


Chapter 7 - Import Export Changes 54

With LS Retail NAV 2013 a new tool been created. It makes it possible to copy Setup data from a database to another database or between companies. The tool to this is the Import Export Worksheet.

The tool exports the selected data into a XML file and then imports the data from the XML file. The user has to take care of to be active in the company the data is being exported from and imported to.

This subject is also covered in the LS Retail NAV 2013 POS Changes User Manual.

The Import Export Worksheet tool is found in one of the following locations:

LS Retail, Administration, Tasks, Design Transfer LS Retail, Point of Sale, Tasks, Design Transfer



The POS setup data which is possible to export and import is:

POS Profiles POS Commands POS Data Table POS Tag Schedule Job Header WS Request

The Import Export Worksheet:



To Export data:

1. Be active in the company the data is being exported from 2. Open the tool: Import Export Worksheet 3. Select the group or profile line which is going to be exported

a. The profile’s ID has to be selected before they can be exported. To do so go to the No. of Records to Export field, open the drop down list, select one or more profile by checking the field Export Profile for each profile to export

b. For data in the Other group, all records are automatically selected and it is not possible to select individual records to export

4. Use the action Export 5. A windows explorer window opens

a. Select your destination b. Optional is to edit the File name

6. Finish the action by pressing the SAVE button 7. The XML file is created

It is not possible to export all data groups in one go, each group or profile type is exported individually

For Profiles the user checks profiles to export; No. Of Records field displays the number of checked profiles

The export tool exports the selected data table and all of its related tables as displayed in the Related Tables window

To Import data:

1. Be active in the company to import the data into 2. Open the action Import Export Worksheet 3. Be active in the group or profile line data to receive the imported data



4. Use actions Import 5. A windows explorer window opens to select the folder where the import file is

a. Select your file 6. Finish the action by pressing the Open button 7. The system displays this window

8. Use Yes or No depending on what is wanted 9. The imported XML file is read into its data tables

By answering the Overwrite existing records window with No it is possible to import only new data

There is a known issue related to the Import Export Worksheet. When he user has used this tool the NAV client has to be stopped and reloaded to prevent and error in the system. This error has no effect on the Import Export process.


Chapter 8 - Starting the POS Terminal 58

The handling of Retail Users and how they are connected to different Stores, Terminals and databases has been simplified a lot in the LS Retail NAV 2013. Instead of earlier, when the access of the Retail User was set in the POS Local Setup form and the LSRetail.ini file it is now set directly on the Retail Users card. The location is: LS Retail, Point of Sale, POS, Administration, Retail Users, where the access is set for each user in the column POS Terminal. There are also two more settings on this card that special attention should be paid to, the POS LogLevel and the POS LogFile.

It is possible to use the LS Retail Startup Tool to start the POS with various parameters, including UserID. The LS Retail Startup Tool is covered in chapter 11 in this document.

The POS Terminal column has now fully replaced the previous POS Local Setup form and all that is needed to do now is to select which Terminal or POS each Retail User that uses the POS is linked to.



The Location Code of the Store decides which Terminals are available for each Store and the Retail User will not see any other terminals.

If the POS Super User checkbox is checked the Retail User has rights to make changes on the POS.

On the POS LogLevel you can select what kind of logs you prefer, None, Errors, Warnings or Debug.



When you log on the POS you will get an overview over either Errors, Warnings or Debugs as long as you have selected one of those.



You can decide to keep the log file by entering the path to the folder where you want the log file to be saved in the POS LogFile column.


Chapter 9 - Converting Reports 62

Already most of the reports have been converted to the Microsoft Dynamics NAV 2013 mode from older versions in the LS Retail NAV 2013. Eventually all the reports will be converted.

You can select different Output Types, sucha as Detailed, Totals, Matrix and more. The reports are easily opened and saved in Excel, PDF and Word.



When you select to open a report it is presented in the NAV but it is also possible to see how the report looks as it is in the Print Layout view. .

In the Print Layout view the pages in the report are presented and you can flip them as they will be available in the actual printout.



With the release of LS Retail NAV 2013 the reports only reflect what was available in the reports in the earlier version of the product and the same kind of representation. In the future there will be numerous possibilities to add more features to the basic reports. An example of how the LS Retail data can be presented in the Standard MS NAV Reports gives an idea of the options that are available:



In this example an analysis of how the Cost Share Distribution of a 9” Margarita Pizza can be divided either:

By Material and Labour By Direct and Indirect cost

This kind of presentation allows you to get a quick idea about the cost distribution given serveral

different factors. All the data is already available in the LS Retail NAV 2013 and this information is

the basis for the future reports.


Chapter 10 - Staff Permissions 66

The Staff Permissions decide which rights individuals and staff groups have within the LS Retail NAV 2013 system. If a member of staff is a member of a Staff Permission Group, the group rights always overwrite the individual rights unless the staff has been given an exception. Recent changes on Staff Permissions aim at making it easier to have overview of each person’s or group’s rights. They are all visible on one page and it is not possible to give contradictory rights to anyone.

The main changes are the following:

When you select Yes in the Manager Privileges field, all fields that are controlled by the manager privileges become uneditable and get the relevant option

Privileges from group with exceptions on Staff Permission group for the staff dependent on the store in question All permissions that were boolena fields (check mark) are now options, Yes or No. Staff

permissions also have a blank option indicating that the permission for that comes from the permission group.

All permissions are positive, that is, if the option value is Yes, the staff has permission for the action. There were earlier a few negative permission fields, such as No Payment Allowed. These have all been reversed: Payment Allowed – Yes, No.

You can undo changes in both the Staff Permissions page and the Staff Permission Group Card that you have made after you opened the pages.

The Staff Permissions can be set at LS Retail, BackOffice, Store Management, Staff List, select member of staff and select the Permissions button.



This will open Staff Permission card for the staff member in question. If he or she is a member of Staff Permission Group it will be shown at the top. The card gives an overview of all the permission this member of the staff has. Changes and further details are dealt with later in this chapter.





Staff Permission Groups can be created and permissions assigned to them. As mentioned before the rights of the groups always overwrite the personal Staff Permissions unless you give the staff member exceptions. The path to creating a new or viewing and changing existing Staff Permission Groups is: LS Retail, BackOffice, Store Management, Staff List, select member of staff and select the Permissions button. At LS Retail, Point of Sale, POS, Administration, General, Staff Permission Groups you have a different access to Staff Permission Groups. This page gives an excellent overview over the permissions of the existing groups and makes it easy to compare the rights of each group to another one.

4. For a new group the New button is selected or Ctrl+N.

5. A name has to be selected for the group. 6. Then the rights are assigned to it. 7. Once concluded the group will be added to the Permission Group drop-down list

that can be opened on the Staff Permission card. It can for instance be accessed from the Staff List or the Staff Card.



The Staff Permission Group card displays all the rights and permissions that an employee that belongs to that particular group has.



Various measures have been taken to ensure that the staff permissions are not inconsistent and lead the user through the settings.

1. When you select Yes in the Manager Privileges field of a Staff Permission Groups or Staff Permissions card all fields that are controlled by manager privileges, become uneditable



and get the relevant option. The path to the groups is LS Retail, Point of Sale, POS, Aministration, General, Staff Permission Groups, select or create a group.

2. The Staff Permissions card will open when you select the Permissions button on a Staff List Card or Staff Card at LS Retail, BackOffice, Store Management, Lists, Staff Lists, select a member of the staff, or LS Retail, Point of Sale, POS, Administration, General, Staff.



3. If you try to change one of the uneditable fields, that can be identified by the grey color, for instance change a Yes to a No if will automatically change back to the Yes.

4. When you select No in the Manager Privileges field, the program asks whether you want to reset the fields and resets them on confirmation, otherwise the stay as they were. If the Permission Group has Manager Privileges, the staff must be also, hence, no fields can be changed for the staff except for non-manager privileges dependent fields.



5. When you select a permission group, upon confirmation, the staff fields become blank,

indicating that the permissions are coming from the permission group. If the permission group does not have manager privileges, you can select No or Yes for each field for the staff to make exceptions to the permissions.



6. For the discount fields (Max Discount to Give % and Max. Total Discount %), the Discount from Perm. Group field indicates whether the discount amounts are coming from the staff or the permission group for the staff. 0 discount indicates no discount. 100 discount full discount.

7. You can also select a permission group for the staff dependent on the store in question. The Staff Store Link contains Permission Group field. When deciding on staff permissions, the program first checks whether there is a permission group assigned to the staff store link in question. If so, this permission group decides on the permissions for the staff (no staff exception are then valid). If not, the permission group on the staff decides on the permissions with any exceptions from the staff. The staff store link line that contains the default store (Store selected for the staff), must have a blank permission group and is not editable. The permissions for the default store always come form the Staff permissions page.

In both the Staff Permissions page and the Staff Permission Group Card you can click the button Undo Changes to revert back to the settings as they were when you opened the page.



Staff Privilege Command Place Manager Priv (Key)

Open Draw. Without Sale

OPEN_DR Pos Session Yes

XZY-Report Printing

PRINT_X,PRINT_Z,PRINT_Y Pos Session Yes

Suspend Transaction

SUSPEND Pos Session Yes

Tender Declaration

TENDER_D,HOSP_TENDDECL Pos Session Yes

Floating Declaration

FLOAT_ENT,REM_TENDER

HOSP_FLOAT,HOSP_REMTEND

Pos Session Yes

Void Transaction VOID Pos Session Yes

Void Line VOID_L Pos Session Yes

CID-Report Printing

PRINT_CID Pos Session Yes

Void Prepayment VOIDPP Pos Session Yes

Void Prepayment Line

VOIDPP_L Pos Session Yes

Change Prepayment Amt.

CHGPP_L Pos Session Yes



Add Prepayment Amt.

ADDPP_L Pos Session Yes

Add Payment TENDER_K Pos Session Yes

Transfer Dining Tables

TRTBL_PART Pos Session Yes

Split Bills SPLITBILL Pos Session Yes

Switch Dining Table Layout

LAY_USEASDESIGN,LAY_DESIGN_ALL,LAY_CHANGE Pos Session Yes

Adjust Dining Tables

LAY_ADJUSTMODE Pos Session Yes

Design Dining Table Layout

LAY_DESIGNMODE Pos Session Yes

Price Override PRICECH Pos Session Yes

Max. Discount to Give %

DISC – Staff or Manager (Man. Key) with highest percentage controls the max. Discount. 0 is not disount

Pos Session NO

Max. Total Discount %

TDISC – same as for DISC Pos Session NO

Return in Transaction

QTYCH,REFUNDLINE

InsertItemLine, ChangeQtyPressed

– POS terminal.Return in Transaction – if both staff and terminal are NO, return is not allowed

Pos Session

Pos Transaction

YES

Max. Tender Decl. Difference

T.D: Init – POS Session functions called Pos Session

Tender Declaration

NO

Max. Warning Count

T.D: Init – POS Session functions called Pos Session Tender Declaration

NO

Action After Diff. Warning

T.D: Init – POS Session functions called

If Staff Acc. – No action

If None/Mgr. Action – No action if Mgrkey

Pos Session Tender Declaration

YES

Show Difference in Warning

T.D: Init – POS Session functions called Pos Session Tender Declaration

NO

Show Trans. Amount

T.D: Init – POS Session functions called

C.M:

Pos Session Tender Declaration

Cash Management

No

Create Customers CUSTCREATE Pos Session YES

Update Customers CUSTUPDATE Pos Session YES



View Sales History CUSTHISTORY Pos Session YES

Customer Comments

CUSTCOMMENTSHOW

False if None

CUSTCOMMENTNEW

False if not View & Edit

Pos Session YES


Chapter 11 - POS Changes 79

Some of the most extensive changes in LS Retail NAV 2013 are on the POS. A separate User Guide for the setup of the POS has been created: LS Retail 2013 – POS Setup – Changes and New Features. It deals with the necessary changes needed to be able to set up the POS in the new environment. In this chapter some other issues regarding the new POS are addressed as well as a brief introduction is given.

In LS Retail NAV 2013 a new POS design is introduced. The setup has been simplified and centralized but the Business logic used is the same as in the older versions of LS Retail NAV.

As a part of more centralized environment there is an advanced ##DEFAULT setup in the Demo Data Company.

It is important to use this as the base for the setup and when there is need or desire for different approach to set it up as an exception of the default.

Even though the POSes that are a part of the LS Retail Demo Data may look identical to the earlier versions of the POSes they have undergone radical changes. Several new features and possibilities are introduced in the LS Retail NAV 2013.

In LS Retail NAV 2013 there are tools to extract setup from the Demo Company and import it to a new company. In the Demo Data Company a default setup has definitions for:

Profiles (Hardware, Functionality, Interface and Menu) Panels and Panel Controls which are a part of the Interface Profile Style: New profile where skin, font and color is defined. Lookup

The purpose of the ##DEFAULT setup is:

If no active profile is found, the ##DEFAULT profile automatically becomes the active profile When the system looks for data in the active profile and does not find it then it automatically

looks for this data in the ##DEFAULT profile

This feature is practical since some data does not need to exist in every profile. This feature saves a lot of implementation and maintenance work since some of the data is only created once instead of many times.



The LS Retail startup tool is a program that offers simple user-interface to start an Microsoft Navision Client exists: LSStartConfig. This program can be useful to start up the POS.

The LS Retail startup tool, or normal Windows login, controls which user logs into the NAV Windows client. In that way, the LS Retail startup tool can control which POS terminal is active because POS terminal is linked to the User ID.

Future development of the startup tool may include more ways to select a POS terminal at startup.

The tools is used to start up the NAV client (POS) with various parameters. The parameters include:

Fullscreen which removes the close button from the NAV pages RunPage?Page=99008950 to start the POS client directly Username/password to log in as a specific user

In the startup tool, it is possible to have shortcuts for up to 3 different POS clients. This is useful when the same machine runs more than one configuration, for instance a Restaurant and a Bar.

The Close button in the startup tool can run any Windows program, such as shutdown.exe to automatically shut down the terminal.

LS Retail expects to add more features to the startup tool such as:

Connection to web services for automatic updates of the POS terminal (.NET add-ins and .FOB objects)

Other automated processes



One of the main changes in LS Retail NAV 2013 is that the ##DEFAULT profile setup, mentioned before, is now the core thing in setting up a POS.

This requires dealing with setup issues that are different from the previous versions. The basis for all POSes in LS Retail NAV 2013 is the ##DEFAULT with a simplified version of a POS that can be altered and adapted to everyone’s needs. There are available methods to extract setup from Demo Company and import into a new Company.

There are two main ways to do this:

1. Either the ##Default setup can be used as a basis and some pre-defined flavors added to it – pre-designed menus such as #HYPER or #FASHION - and developed to the direction of each wishes. This is the recommended route.

2. Or it is possible to build upon the simple version of ##DEFAULT without using the pre-designed standard menus. This method requires much more effort on the user’s side.

If the former approach is used, to use the ##Default setup and some pre-defined flavors upon it such as #HYPER, then there are actually only two issues that need to be defined:

Items Payment Method

Both the Items and the Payment methods need to be accessible from the POSes buttons.

Once another profile, for instance the #HYPER has been added to the basic ##DEFAULT you will get a more advanced type of a POS. The additional profile, if it exists, will always be the one you see, since it is the one searched for. The basic ##DEFAULT profile will only appear if none has been selected or no features have been defined specifically.



Those who prefer to use only the ##DEFAULT setup will find a very simplified version of the POS with the basic LS Retail color scheme available. On top of defining Items and Payment Method here it is needed to add a layout and styles of one choice and this requires both effort in design and defining styles and panels and its functionality.

A new profile based on the ##DEFAULT profile with the addition of #POS is a minimalistic one, mostly without defined styles such as colors and other significant features.



An example could be to create a new interface profile, the LS-NEWPRO, that consists of the bare minimum features a profile can have. The ##Default profile has been copied and the #POS added to it but no other changes have been made, so it appears with the greyscale features. The only activities available are the ones for Items and Payment Method. The menu properties can be viewed by right-clicking any part of the menu and select Menu Properties.



Compared to the more advanced interface profiles, for instance those that are included in the LS Retail Demo Company, the ##DEFAULT, plus the #POS needs a lot of additional work before being able to perform similar tasks. The difference of the appearance is also significant.

But there is always an option to use either method, building a new interface menu from the basic ##DEFAULT one or build upon one of the menus available in the Demo Company.

A new field Run Hospitality Startup in the POS Terminal card has been added. LS Retail, Point of

Sale, POS, Terminals; select a terminal, go to the Hospitality tab. This field lets the POS Client load

as a Hospitality POS instead of a Normal POS.




Chapter 12 - Appendix 1: POS Commands – New and Removed 86

Function Code Description

1 BOM_REPRINTPRINTER Receipt:

2 CUSTCOMMENTNEW Create Customer Comments

3 CUSTCOMMENTSHOW Show Customer Comments

4 CUSTCREATE Create New Customer

5 CUSTHISTORY View Customer Sales History

6 CUSTOM Custom Pre Command

7 CUSTUPDATE Update Customer Information

8 DEL-CONTACTCOMMENT Edit Delivery Contact Comment

9 DEL-CONTACTDETAIL Edit Delivery Contact Detail

10 DEL-DRIVERLIST Delivery Driver List

11 DEL-DRIVEROFF Delivery Driver Off

12 DEL-DRIVERON Delivery Driver On

13 DEL-HISTFILTER Posted Delivery Order Filter

14 DEL-OVERVIEWFUNC Delivery Overview Functions

15 DTP_NEXTMONTH POS Calendar: Get next Month

16 DTP_NEXTYEAR POS Calendar: Get next Year

17 DTP_PREVMONTH POS Calendar: Get previous Month

18 DTP_PREVYEAR POS Calendar: Get previous Yea

19 DTP_SELECT POS Calendar: Select Date

20 EDIT_GRID_REC Edit the Active DataGrid Record

21 EDIT_LOOKUP_REC Edit the Active Lookup Record

22 FUNCTION CODE Description

23 HARDWARECARD Show POS Hardware Card

24 HARDWAREINFO Show POS Hardware Info

25 HOSP-OPEN-NEWORDER Open up Sales POS, new order

26 HOSP-OPEN-POS Open up Sales POS, new or existing order

27 HOSP-ORDEREDIT Edit selected order directly



28 HOSP-SWITCH-TYPE Switch Hospitality Types

29 KM-FUNC Kitchen Monitor Functions

30 KM-PANEL Kitchen Monitor Panel

31 MEMBERCARDREAD Read Member Card

32 MEMBERCONTACT Member Contact Management

33 POPUP_CLEAR_SEL Pop-up - Clear selection

34 POPUP_GROUPSEL Pop-up - Group selection

35 POPUP_MULTSEL Pop-up - Multiple selection

36 POPUP_OK Pop-up - OK

37 POPUP_QTYCH Pop-up - Change quantity

38 POPUP_SINGLESEL Pop-up - Single selection

39 PRINT_LAST_C Print slips from last trans.

40 PRINT_LAST_IC Print invoice from last trans.

41 PRINT_Y Print Y report

42 REFUND_MARK_ALL Mark all Lines for Refund

43 REFUND_MARK_LINE Mark Line for Refund

44 RESET_SELECTION Reset Selection

45 SHOWDATATABLE Shows a DataTable View on the Active Data Grid

46 SHOWPANEL Show POS Panel

47 ZOOM_GRID_REC Zoom the Active Data Grid Record

48 ZOOM_LOOKUP_REC Zoom the Active Lookup Record

Function Code Description

1 ADDCHARGE Additional Charges

2 ADDPP Add prepayment on transaction

3 CLEAR_QTY Clear current selection

4 COLLECT Spo Collect

5 CUSTOMERSPO SPO Customer Registration

6 FINDPOSTEDORDER Find Posted Special Order



7 MARKASSPOENTRY Mark Line as Special Order

8 MARKSPO Mark As Special Order

9 NEW A Generic Command to Add Record in List/Form

10 ORDERMGT Special Order Mgt

11 ORDPMTHIST Get Payment History

12 POPUPITEMLIB Item Library Pop-up

13 POPUPITEMLIBUPD Item Library Pop-up Update

14 POPUPPOSORDHDR POS Order Header Pop-up

15 POPUPRZ POS Retail Zone Pop-up

16 POPUPRZPC POS Post.Co. for R.Zone Pop-up

17 POPUPSPODETAILS POS SPO Order Details Pop-up

18 RUNPOS Hosp.: Run POS on Temp Profile

19 SPOCANCELLINE SPO Cancel Item line

20 SPODETAILS SPO Details

21 SWITCH_GROUP Switch Pop-up Group