LS Retail NAV and LS POS

Data Connections Setup Guide

LS Retail NAV 6.2

Author: Gudrun Leosdottir Date: 01.25.2011

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

Contents
1 2 3 Introduction....................................................................................................................... 1 Setting up Data Connections between LS Retail NAV and LS POS ............................ 1 Web Services .................................................................................................................... 4 3.1 Setup ........................................................................................................................ 4 3.1.1 Common Nodes ........................................................................................... 4 3.1.2 Activate the Services ................................................................................... 4 3.1.3 Activate Requests ........................................................................................ 4 3.1.4 Setup Requests ........................................................................................... 5 3.1.5 Print Requests Setup ................................................................................... 5

LS Retail ehf. Hofdatun 2, 105 Reykjavk, Iceland Tel: +354 414 5700 Fax: +354 571 2728

Data Connections Setup Guide

1 Introduction
The following notes should be used when setting up Data Connections between LS Retail NAV and LS POS. This is a short guide that gives you a step by step instructions.It also contains information on setting up Web Services.

2 Setting up Data Connections between LS Retail NAV and LS POS

To set up data connection between LS Retail NAV and the LS POS the following needs to be done: Install LS Retail Data Director Version 3.0 LS Retail Scheduler Distribution Location: Create an entry for the LS POS in table 9901554 Dist. Location Version:

Create a Distribution Location for the LS POS needed:

Using the Version created in the last step, Driver Type = SQL and DB Structure = SQL. UserID and Password for the Data Director is Provided by the LS POS Installation.

Chapter 1 - Introduction

Data Connections Setup Guide

The system will automatically create the connection string. Test the connection using Data Director to make sure everything is working. From the Functions menu button, run Read Design with Data Dir.

Run the functions Insert LSPOS Default Jobs and Insert LSPOS Start Jobs. These functions create Scheduler Job Headers and subjobs as follows: HO2LSPOS Data by actions from NAV to LSPOS with subjobs: LSPHARDWPRF LSPINFOCODETABLE LSPINFOCTABSPEC LSPINFOSUBCODE LSPINVDIMCOMB LSPINVENTGRP LSPINVENTLINKEDITEM LSPINVENTTABLE LSPINVENTTABLEMOD LSPITEMBARCODE LSPLOCPRICEGRP LSPLOYALTYCARD LSPLOYALTYSCHTAB LSPMMLINEGROUP LSPPRICEDISCGRP LSPPRICEDISCTABLE LSPRBOCOLORS LSPRBOINVENTTABLE LSPRBOSIZES LSPRBOSTAFFTABLE LSPRBOSTYLES LSPRBOUNIT LSPSTAFFPERMGRP LSPSTORETABLE LSPSTORETENDCARD LSPSTORETENDER LSPTAXDATA LSPTAXGROUPDATA Hardware Profile to LSPOS Infocode table to LSPOS Table specific infocode to LSPOS Infosubcode to LSPOS Item dim combination LSPOS Item group to LSPOS Linked items to LSPOS Item to LSPOS Inventtable Item to LSPOS Inventtablemodule Barcodes to LSPOS Location Price grp. to LSPOS Loyaltycards to LSPOS Loyalty scheme to LSPOS Mix & Match line groups to LSPOS Price-Discount group to LSPOS Price-Discount Table to LSPOS Colors to LSPOS Item to LSPOS RBO-Inventtable Sizes to LSPOS Staff to LSPOS Staff Styles to LSPOS Unit of Measure to LSPOS Staff permission grp. to LSPOS Store table to LSPOS Tender type card setup to LSPOS Tender type to LSPOS TaxData to LSPOS TaxGroupData to LSPOS

LSPRBOLOYALTYPOINTS Loyalty points to Ls Pos

Chapter 2 - Setting up Data Connections between LS Retail NAV and LS POS

Data Connections Setup Guide

LSPTAXGRPHEADING LSPTAXONITEM LSPTERMINALTABLE LSPTTCARDNOS LSPUNITCONVERT LSPVALIDPERIOD LSPVISUALPROFILE

VAT Bus.post.grp. to LSPOS TaxOnItem to LSPOS POS Terminal to LSPOS Tender card type no. to LSPOS Item unit convert to LSPOS Validation period to LSPOS Interface Profile to LSPOS

LSPOS2HO - Data from LSPOS with subjobs: LSPLOYALTYPOINTS LSPTRANSACTABLE LSPTRANSINFOCODE LSPTRANSPAYMENT LSPTRANSSALESTR Trans. Loyalty Points from LSPOS Transaction Hdr from LSPOS Trans. Infocode Ent from LSPOS Trans. payment Ent from LSPOS Trans. sales Ent from LSPOS

LSPSAFETENDERTRANS Trans. safe tender Ent from LSPOS

HOLSPOSDATA Runs Codeunit 99008803 which performs necessary data conversion by actions. Data from following NAV tables is converted into tables 99008800 99008809 which are replicated to the LS POS. 6 Customer Price group 325 VAT posting setup 340 Customer discount Group 341 Item discount Group 5404 Item Unit of Measure 7002 Sales Price 7004 Sales Discount 10001412 Extended Variant Dimensions 10001413 Extended Variant Values 10001414 Item Variant Registration The PriceGroupTypes in the LSPOS table PRICEDISCOUNTGROUP contains combinations of data from 3 different tables in NAV: Module 0 PriceGroup: Data from NAV Table 6 Module 1 LineDiscGroup: Data from Tables 340 and 341 Modules 2 MultiLineDiscGroup and 3 EndDiscGroup are not implemented for the time being. The functions Insert LSPOS Start Jobs creates HO2LSPOSNORM with subjobs equivalent to the default jobs but the subjobs except those are of the type Normal. All subjobs created have Field Transfer Type = Include List and the field lists are created for each subjob. It is not recommended that the function Update Field List is run for any of those jobs because of the difference in data structure between the NAV tables and the LS POS tables. LSPOS layout and printout changes are not supported from NAV. This needs to be configured outside NAV for the time being but will be addressed in future version.

Chapter 2 - Setting up Data Connections between LS Retail NAV and LS POS

Data Connections Setup Guide

3 Web Services
Web service framework is a set of tables to define supported request and how their request and response xml are constructed. The module consists of: 1. Setup table to define if the module is active and some command Node Names to be used in xml documents. 2. Request setup table to define supported requests and if they are active or not. 3. Request xml setup table to define both request and response xml for each request. 4. Common support functions to read requests process and create response xml. 5. Report to print out xml document layouts. When the web service module is activated for the first time (also if active later and not requests found) and no request exists in the request table the system will create all the default requests. When each request is activated and xml setup is not found for the request (both request and response) the system will create default xml setup for both request and response document. The web services module can be activate or deactivate independent of other parts of the system. The module has to be active for the Web Service to work.

3.1
3.1.1

Setup
Common Nodes

In the Web Service Setup form (LS Retail BackOffice, Setup, Web Services Setup), define all the common nodes, top, ID and response.

3.1.2

Activate the Services

In the Web Service Setup form (LS Retail BackOffice, Setup, Web Services Setup ) you can activate or deactivate the web service module. If no request exists in the WS Request table when you activate the services, the system will create all the default requests.

3.1.3

Activate Requests

Select WS Request List from the Web Service setup menu Web services. In this form you can active or deactivate Web Requests. If no XML Request Setup exists in the WS Request Setup table the system will create the default XML request and response setup for the request.

Chapter 3 - Web Services

Data Connections Setup Guide

3.1.4

Setup Requests

From the menu button Web Service in the WS Request Setup form (LS Retail BackOffice, Setup, Web Services Setup) select Web Requests. From the menu button Request select Request/Response xml. In this form you can work with and define layout of XML documents. Note that when activating the request, the system creates the default setup for each request. Also note that though setup can be changed that doing so will always depend heavily on changing the request process as well. So in fact it is normally not practical or recommended to change the request document. On the other hand changing the response document especially if it is based on a table, that is to add or change field in the response document might be needed.

3.1.5

Print Requests Setup

In the WS Request form (LS Retail BackOffice, Setup, Web Services Setup). From the menu button Web Service select Web Requests), select menu button Request and hit Print xml.

Chapter 3 - Web Services