Transactionware General Merchandise 10.1 - SAP Help Portal

Installation Guide

SAP® Transactionware

General Merchandise10.1

Target Audience

System administrators

Technology consultants

Document Version: 1.01 – October, 2008

© Copyright 2008 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in anyform or for any purpose without the express permission of SAP AG.The information contained herein may be changed without priornotice.

Some software products marketed by SAP AG and its distributorscontain proprietary software components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registeredtrademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex,MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries,xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity,Tivoli, Informix, i5/OS, POWER, POWER5, OpenPower andPowerPC are trademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are eithertrademarks or registered trademarks of Adobe Systems Incorporated inthe United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of theOpen Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,VideoFrame, and MultiWin are trademarks or registered trademarks ofCitrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registeredtrademarks of W3C®, World Wide Web Consortium, MassachusettsInstitute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., usedunder license for technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, andother SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AGin Germany and in several other countries all over the world. All otherproduct and service names mentioned are the trademarks of theirrespective companies. Data contained in this document servesinformational purposes only. National product specifications mayvary.

These materials are subject to change without notice. These materialsare provided by SAP AG and its affiliated companies ("SAP Group")for informational purposes only, without representation or warranty ofany kind, and SAP Group shall not be liable for errors or omissionswith respect to the materials. The only warranties for SAP Groupproducts and services are those that are set forth in the expresswarranty statements accompanying such products and services, if any.Nothing herein should be construed as constituting an additionalwarranty.

SAP Library document classification: PUBLIC

DisclaimerSome components of this product are based on Java™. Anycode change in these components may cause unpredictableand severe malfunctions and is therefore expressivelyprohibited, as is any decompilation of these components.

Any Java™ Source Code delivered with this product isonly to be used by SAP’s Support Services and may not bemodified or altered in any way.

Documentation in the SAP Service MarketplaceYou can find this documentation at the following address:http://service.sap.com/instguides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 24F +49/18 05/34 34 20www.sap.com

http://service.sap.com/instguides

http://www.sap.com/

3

Terms for Included OpenSource SoftwareThis SAP software contains also the third-party opensource software products listed below. Please note that forthese third-party products the following special terms andconditions shall apply.1. This software was developed using ANTLR.2. gSOAPPart of the software embedded in this product is gSOAPsoftware. Portions created by gSOAP are Copyright(C) 2001-2004 Robert A. van Engelen, Genivia inc. AllRights Reserved.THE SOFTWARE IN THIS PRODUCT WAS IN PARTPROVIDED BY GENIVIA INC AND ANY EXPRESSOR IMPLIED WARRANTIES, INCLUDING, BUTNOT LIMITED TO, THE IMPLIED WARRANTIESOF MERCHANTABILITY AND FITNESS FOR APARTICULAR PURPOSE ARE DISCLAIMED. INNO EVENT SHALL THE AUTHOR BE LIABLEFOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIALDAMAGES (INCLUDING, BUT NOT LIMITED TO,PROCUREMENT OF SUBSTITUTE GOODS ORSERVICES; LOSS OF USE, DATA, OR PROFITS; ORBUSINESS INTERRUPTION) HOWEVER CAUSEDAND ON ANY THEORY OF LIABILITY, WHETHERIN CONTRACT, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE)ARISING IN ANY WAY OUT OF THE USE OF THISSOFTWARE, EVEN IF ADVISED OF THE POSSIBILITYOF SUCH DAMAGE.3. SAP License Agreement for STLportSAP License Agreement for STLPort betweenSAP AktiengesellschaftSystems, Applications, Products in Data ProcessingNeurottstrasse 1669190 Walldorf, Germany(hereinafter: SAP)And you(hereinafter: Customer)

a) Subject Matter of the AgreementA) SAP grants Customer a non-exclusive,non-transferrable, royalty-free license to usethe STLport.org C++ library (STLport) and itsdocumentation without fee.B) By downloading, using, or copying STLport orany portion thereof Customer agrees to abideby the intellectual property laws, and to all ofthe terms and conditions of this Agreement.C) The Customer may distribute binaries compiledwith STLport (whether original or modified)without any royalties or restrictions.D) Customer shall maintain the followingcopyright and permissions notices on STLportsources and its documentation unchanged:Copyright 2001 SAP AGE) The Customer may distribute original ormodified STLport sources, provided that:o The conditions indicated in the abovepermissions notice are met;o The following copyright notices are retainedwhen present, and conditions provided inaccompanying permission notices are met:Coypright 1994 Hewlett-PackardCompanyCopyright 1996,97 Silicon GraphicsComputer Systems Inc.Copyright 1997 Moscow Center forSPARC Technology.Copyright 1999,2000 Boris FomitchevCopyright 2001 SAP AGPermission to use, copy, modify, distribute andsell this software and its documentation forany purposes is hereby granted without fee,provided that the above copyright notice appearin all copies and that both that copyright noticeand this permission notice appear in supportingdocumentation. Hewlett-Packard Companymakes no representations about the suitabilityof this software for any purpose. It is provided“as is” without express or implied warranty.Permission to use, copy, modify, distribute and

sell this software and its documentation for anypurpose is hereby granted without fee, providedthat the above copyright notice appear in allcopies and that both that copyright notice andthis permission notice appear in supportingdocumentation. Silicon Graphics makes norepresentations about the suitability of thissoftware for any purpose. It is provided “as is”without express or implied warranty.Permission to use, copy, modify, distribute andsell this software and its documentation forany purposes is hereby granted without fee,provided that the above copyright notice appearin all copies and that both that copyright noticeand this permission notice appear in supportingdocumentation. Moscow Center for SPARCmakes no representations about the suitabilityof this software for any purpose. It is provided“as is” without express or implied warranty.Boris Fomitchev makes no representationsabout the suitability of this software for anypurpose. This material is provided "as is", withabsolutely no warranty expressed or implied.Any use is at your own risk. Permission touse or copy this software for any purpose ishereby granted without fee, provided the abovenotices are retained on all copies. Permissionto modify the code and to distribute modifiedcode is granted, provided the above noticesare retained, and a notice that the code wasmodified is included with the above copyrightnotice.Permission to use, copy, modify, distributeand sell this software and its documentationfor any purposes is hereby granted withoutfee, provided that the above copyright noticeappear in all copies and that both that copyrightnotice and this permission notice appear insupporting documentation. SAP makes norepresentations about the suitability of thissoftware for any purpose. It is provided with alimited warranty and liability as set forth in the

License Agreement distributed with this copy.SAP offers this liability and warranty obligationsonly towards its customers and only referringto its modifications.b) Support and MaintenanceSAP does not provide software maintenance for theSTLport. Software maintenance of the STLporttherefore shall be not included.All other services shall be charged according to therates for services quoted in the SAP List of Pricesand Conditions and shall be subject to a separatecontract.c) Exclusion of warrantyAs the STLport is transferred to the Customer on aloan basis and free of charge, SAP cannot guaranteethat the STLport is error-free, without materialdefects or suitable for a specific application underthird-party rights. Technical data, sales brochures,advertising text and quality descriptions producedby SAP do not indicate any assurance of particularattributes.d) Limited LiabilityA) Irrespective of the legal reasons, SAP shall onlybe liable for damage, including unauthorizedoperation, if this (i) can be compensated underthe Product Liability Act or (ii) if caused due togross negligence or intent by SAP or (iii) if basedon the failure of a guaranteed attribute.B) If SAP is liable for gross negligence or intentcaused by employees who are neither agents ormanagerial employees of SAP, the total liabilityfor such damage and a maximum limit on thescope of any such damage shall depend onthe extent to which its occurrence ought tohave anticipated by SAP when concluding thecontract, due to the circumstances known toit at that point in time representing a typicaltransfer of the software.C) In the case of Art. 4.2 above, SAP shall notbe liable for indirect damage, consequentialdamage caused by a defect or lost profit.D) SAP and the Customer agree that the typical

5

foreseeable extent of damage shall under nocircumstances exceed EUR 5,000.E) The Customer shall take adequate measuresfor the protection of data and programs, inparticular by making backup copies at theminimum intervals recommended by SAP. SAPshall not be liable for the loss of data and itsrecovery, notwithstanding the other limitationsof the present Art. 4 if this loss could have beenavoided by observing this obligation.

F) The exclusion or the limitation of claims inaccordance with the present Art. 4 includesclaims against employees or agents of SAP.4. Adobe Document ServicesAdobe, the Adobe logo, Acrobat, PostScript, and Readerare either registered trademarks or trademarks ofAdobe Systems Incorporated in the United States and/ or other countries. For information on Third-Partysoftware delivered with Adobe document services andAdobe LiveCycle Designer, see SAP Note 854621.

Typographic Conventions

Type Style Description

Example Text Words or characters quotedfrom the screen. These includefield names, screen titles,pushbuttons labels, menunames, menu paths, and menuoptions.

Cross-references to otherdocumentation

Example text Emphasized words or phrasesin body text, graphic titles, andtable titles

EXAMPLE TEXT Technical names of systemobjects. These include reportnames, program names,transaction codes, tablenames, and key concepts of aprogramming language whenthey are surrounded by bodytext, for example, SELECT andINCLUDE.

Example text Output on the screen. Thisincludes file and directorynames and their paths,messages, names of variablesand parameters, source text,and names of installation,upgrade and database tools.

Example text Exact user entry. These arewords or characters that youenter in the system exactly asthey appear in thedocumentation.

<Exampletext>

Variable user entry. Anglebrackets indicate that youreplace these words andcharacters with appropriateentries to make entries in thesystem.

EXAMPLE TEXT Keys on the keyboard, forexample, F2 or ENTER.

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Librarydocumentation to help you identify differenttypes of information at a glance. For moreinformation, see Help on Help GeneralInformation Classes and Information Classesfor Business Information Warehouse on thefirst page of any version of SAP Library.

1 Introduction

7

Contents1 Introduction .........................................................................................8

1.1 About this Document............................................................................. 81.2 New Features.......................................................................................... 91.3 Before You Start ................................................................................... 101.3.1 SAP Notes for the Installation.......................................................... 101.3.2 Information Available in SAP Service Marketplace........................ 101.3.3 Naming Conventions ........................................................................ 11

2 Planning .............................................................................................122.1 Sample Installation Environments...................................................... 12

3 Preparation ........................................................................................143.1 System Requirements....................................................................... 143.2 Hardware Certifications .................................................................... 15Installation Prerequisites........................................................................... 15

4 Installation .........................................................................................174.1 Installing the SAP POS Suite............................................................... 174.2 Installing the Database Tools.............................................................. 184.3 Installing the Xpress Server Database ............................................... 194.4 Installing the Electronic Journal Database ........................................ 204.5 Installing the Xpress Server ................................................................ 204.6 Installing the Electronic Journal Viewer ............................................ 224.7 Installing the Store Manager ............................................................... 234.8 Installing the Point of Sale................................................................... 244.9 Installing the Mobile Point of Sale ...................................................... 254.10 Installing the Store Configurator ...................................................... 284.11 Installing the SDK............................................................................... 29

5 Post-Installation ................................................................................305.1 Starting and Stopping SAP TGM...................................................... 30

6 Additional Information......................................................................316.1 MSI Silent Mode Install...................................................................... 316.2 Replication Installation Process....................................................... 326.3 Setting Up a Backup Server.............................................................. 336.4 Configuring the Mobile Point of Sale Components ........................ 346.5 Running Multiple POSs on a Single Machine.................................. 396.6 Obtaining Database Server Name .................................................... 406.7 Integrating SAP POS and Transnet.................................................. 406.8 Understanding the Data Flow ........................................................... 446.9 About SAP POS User Administration and Authentication............. 51

1 Introduction

1 IntroductionThis section provides introductory information you need to know before you begin installingthe SAP Point Of Sale (SAP POS) suite.

1.1 About this DocumentPurposeThis Installation Guide provides step-by-step instructions for installing the SAPTransactionware General Merchandise (TGM) application. It also includes all prerequisite andpost-installation information to successfully install the application. It is intended for SAP orSAP-approved system administrators and technology consultants.

SAP POS is the leading transaction-management and point-of-sale solution for generalmerchandise retailers including specialty, mass merchandise, discount and departmentstores.

The SAP POS product suite consists of the following components:

POS

Store Manager

Configurator

POSAn advanced point-of-sale transaction processing application, SAP POS provides low- tohigh-volume capabilities. SAP POS is a front-end processing application that scales to yourgrowing business and evolves to encompass changing technology.

Store ManagerStore Manager is the in-store administrative or back-office information managementcomponent of the POS solution suite. It provides in-store and back-office functions such asreporting, payroll entry, file maintenance, cash management, and inventory control.

Store Manager is available at three licensing levels.

Level 1 - POS Manager

Allows POS administrative tasks, such as cash management, to be expedited at thestore level.

Single or multiple terminals can be monitored to facilitate training.

Flexible report generation allows retailers to determine which reports they wish togenerate.

Journal Viewer allows read-only access to all register journals in the store, forsecurity purposes.

Security levels can be set to limit access based on position or level of authority.

Level 2 - Store Manager with Inventory Management

This option offers all the functions of Level 1, plus the following additional one:

Vendor information and SKU maintenance for receiving, transfers, purchase ordersand physical counts

1 Introduction

9

Level 3 - Store Manager Deluxe with Perpetual Inventory Control.

This option offers all the functions of Level 2, plus the following additional one:

An inventory component that can handle on-hand quantities and suggested reorderfor perpetual inventory control on all or selected items.

The ConfiguratorThe Configurator is a key component in the SAP POS Suite. A powerful parameter definitiontool, the Configurator allows your regional and head office personnel to tailor your POSterminals to your retail business needs through a simple user interface. With this interface,you can control all of your POS terminal functions and processes by manipulating theirsettings in a series of detailed data tables. These data tables contain parameter definitionsfor such core functions as your tender and transaction types, tax settings, promotions,keyboard layouts, terminal menus, cashier prompts, customer records, and much more.

From the Configurator, the parameters you define are transferred or converted over to yourPOS terminals during regular system polling, and only those parameter files which have beenchanged are converted, reducing unnecessary drain on system resources. This conversionand update process can be performed as often as required to ensure that all terminals in allstores contain the same information. Many of the parameters in the Configurator need to beset only once, or very infrequently, to reflect core aspects of your business model (forexample, the tender types your company uses, or your terminal display settings). Otherparameters, such as price lookup (PLU) definitions and promotion settings can be modifiedmore frequently for maximum system flexibility.

IntegrationIntegration with Allegiance™ CRM systems allows for powerful customer loyalty programs.

1.2 New FeaturesThe following are new features added to SAP POS:

Area Description

Removal ofretireddatabasesupport

SAP POS has used Sybase SQL Anywhere DBMS since the inceptionof the Windows based POS. The current Sybase version used by POShas been retired and has been replaced by a newer version. In thisrelease, we have removed the retired databases from the availableDBMS solutions.

Addition ofnew supporteddatabases

Added support for Microsoft SQL Server 2005 + Standard, Workgroupand Express Editions: To stay in line with current technology and SAP’sown Product Standards Roadmap, we would like to update the availabledatabase selections to include Microsoft SQL Server 2005 StandardEdition, Workgroup Edition and Express Edition.

UpdateInstallationInfrastructure& Process

Our current installation utilizes a retired version of InstallShield. Wewould like to update this technology to a current version of InstallShield.This will reflect the new SAP branding and will also make theinstallation simpler and more robust with the usage of MSI (MicrosoftInstaller).

1 Introduction

1.3 Before You StartThe following sections provide information about:

SAP Notes for the Installation

Information Available on SAP Service Marketplace

Naming Conventions

1.3.1 SAP Notes for the Installation

Make sure that you have the up-to-date version of each SAP Note, which youcan find in the SAP Service Marketplace at the Internet addressservice.sap.com/notes.There are currently no SAP Notes available for this version.

1.3.2 Information Available in SAP ServiceMarketplaceInformation on the following areas is available in the SAP Service Marketplace.

General Quick Links

Description Internet Address Title

SAP Notes service.sap.com/notes –

Released platforms service.sap.com/platforms –

System sizing service.sap.com/sizing Quick Sizer tool

Front-end installation service.sap.com/instguides Front End InstallationGuide

Security service.sap.com/security –

1 Introduction

11

1.3.3 Naming ConventionsIn this documentation, the following naming conventions apply:

Terminology

VariablesVariables Description

<SAPSID> SAP system ID in uppercase letters

<sapsid> SAP system ID in lowercase letters

<DBSID> Database system ID in uppercase letters

<dbsid> Database system ID in lowercase letters

<INSTDIR> Installation directory for the SAP system

<CD-DIR> Directory in which a CD is mounted

<DVD-DIR> Directory in which a DVD is mounted

<OS> Operating system name within a path

2 Planning

2 Planning2.1 Sample Installation EnvironmentsThe following examples show various combinations of components which can be installedtogether or on different pieces of equipment. You can use these as a guide to compare toyour retail system requirements, and model your installation accordingly.

To install the POS Suite in this type of environment you must do the following:

Install on ServerSystem:

Install on POSSystem

Install on StoreManager System,:

Example Store A

Store A has aserver andseveral separatePOS Terminals

SQL Server andrelated patches

Xpress Server

Xpress ServerDatabase

Database Tools

POS

Example Store B

Store B has aserver with StoreManager andseveral separatePOS Terminals


Xpress Server


Database Tools

Store Manager

POS

Example Store C

Store C has aserver with StoreManager,Electronic Journaland severalseparate POSTerminals

SQL Server andrelated Patches

Xpress Server


Electronic JournalDatabase

Database Tools

Store Manager

Electronic Journal

POS

Example Store D

Store D has aserver, severalseparate POSTerminals, and aseparate StoreManager andElectronic Journal


Xpress Server



Database Tools

POS SQL Client andrelated patches

Store Manager

Electronic Journal

2 Planning

13

Example Store E

Store E has aserver, POSTerminal, StoreManager andElectronic Journalall on one system


Xpress Server



Database Tools

POS

Store Manager

Electronic Journal

3 Preparation

3 Preparation3.1 System RequirementsThis section outlines the system requirements for each component in the SAP POS Suite.For each component, both the minimum and recommended requirements are provided.

The recommended requirements are preferred for optimum applicationperformance.

The specifications given below are based on a typical implementation but because thecomponents can be installed in different configuration combinations and the requirements ofeach retail environment can be different, they should be used as a guideline. It is expectedthat for each configuration, you will need to perform usability testing to determine if thesystem performance is acceptable.

POSMinimum System Requirements Optimum

Windows POS Windows POS

Windows XP Pro/WEPOS Windows XP Pro/WEPOS

233 MHz Pentium Microprocessor 300 MHz Pentium Microprocessor

512 MB RAM 768 MB RAM

100 MB Available Hard Disk Space 100 MB Available Hard Disk Space

Xpress ServerMinimum System requirements Optimum

Windows XP/2003 Windows XP/2003



500 MB Available Hard Disk Space 2 GB Available Hard Disk Space

Databases – Sybase Adaptive ServerAnywhere 9.0; MS SQL Server 2000 (SP 3or later) MS SQL Server 2005

Databases - Sybase Adaptive ServerAnywhere 9.0; MS SQL Server 2000 (SP 3or later) MS SQL Server 2005

3 Preparation

15

Store ManagerMinimum System Requirements Optimum





Databases – same as Xpress Server Databases – same as Xpress Server

ConfiguratorMinimum System Requirements Optimum





Databases – Sybase Adaptive ServerAnywhere 9.0

Databases - Sybase Adaptive ServerAnywhere 9.0

3.2 Hardware CertificationsSAP maintains a list of certified hardware devices which are supported by the POS system.Talk to your SAP representative for specific information on certified hardware.

Installation PrerequisitesEnsure the following to enable your software to install correctly:

All computers must be loaded with the TCP/IP protocol. The NetBEUI protocol may also beloaded, but is optional. The protocol(s) must be installed and configured before any SAPapplications or required support components are installed.

All OPOS drivers must be installed on machines where the POS will be installed.

OPOS drivers should be installed in the mode (that is, at the security level, for example,Administrator) in which the POS will be run. For example, if the OPOS drivers are installed inAdministrator mode, then the POS should always be run in the same mode or some setupconfigurations may not be maintained.

You must have the most up to date version of the ole32.dll file. If the install program doesnot detect the correct file, a warning message appears. When this occurs, you must cancelthe installation process, install ole32.dll and then restart the installation process.

You must have the most current version of the msvcp60.dll file. This file is typically locatedunder C:\Windows [or Winnt or the directory where your operatingsystem is installed]\System32. If you do not find a copy of this file on your system,you can perform a search for it on the Internet using msvcp60.dll download as the searchsentence. After you download this file, copy it to the relevant directory as described above,for example C:\Windows\System32.

3 Preparation

You must download the MSXML 4.0 installer from the following location:http://www.microsoft.com/downloads/details.aspx?FamilyID=3144b72b-b4f2-46da-b4b6-c5d7485f2b42&DisplayLang=en. This will install all files required forthe installation to their required locations.

Prior to installing the Store Manager, the Configurator, the Database Tools or the ElectronicJournal Viewer on the Microsoft Server 2003, you must ensure that the following DLL filesexist on \Windows\System32 directory:

Atl71.dll

Msvcp71.dll

Msvcr71.dll

In case these files do not exist, they can be downloaded from the following third-partyresource: dlldump.com (site recommended by Microsoft).

SAP provides third-party information to help customers find technical support.This information may change without notice. SAP does not guarantee theaccuracy of this third-party information.

This file must exist in C:\Program Files\Common Files\SAP Shared\RetailSystems: AllegianceAdj.dll

This file must exist in C:\Windows\System32: MSWINSCK.OCX

To install Encryption, you will need the security key file called keyfile.txt and itspassword. These should be available from your head office.

The following table lists the disk space requirements for each product installation:

SQL Server 15 megabytes

SQL Client 5 megabytes

Xpress Server 70 megabytes

(including Database Tools andBackoffice / Journal databases)

Store Manager 100 megabytes

Electronic Journal Viewer 20 megabytes

POS 100 megabytes

Configurator 100 megabytes

SDK 10 megabytes

http://www.microsoft.com/downloads/details.aspx?FamilyID=3144b72b-

4 Installation

17

4 Installation4.1 Installing the SAP POS SuiteTo install the SAP POS Suite, do the following:

1. Go to http://service.sap.com/swdc.

2. Choose Download- Installations and Upgrades Entry by ApplicationGroup SAP Industry-specific Components SAP POS.

3. Choose either SAP POS2.0 for GM 10 and later products or choose SAP POS1.0 for GM 9.5 Products

4. In the SAP POS 2.0 page that opens, choose Installation.

5. In the SAP 2.0 window which lists the different products available under thisinstallation package, select the Transactionware GM 10 checkbox.

6. Select the Add to Download Basket button.

7. Select the Download Basket button.

8. Once the application has finished downloading, click the main.msi installer iconfrom the X:\10_0_0...\msinstall directory.

9. On the SAP POS welcome screen, select either the Head Office or the StoreSolution installation path.

Store Solution - this option shows the typical components installed at astore. By default they are pre-selected. To install all the selectedcomponents, select Install and the components will be installed in thefollowing order:

o Database Tools

o Xpress Server Database

o Electronic Journal Database

o Xpress Server

o Electronic Journal Viewer

o Store Manager

o Point of Sale

o Mobile Point of Sale

To install only one or a few components, deselect all components you do notwish to install, and then select Install.

Head Office - this option shows the typical components installed at a headoffice. By default they are pre-selected. To install all the selectedcomponents, select Install. The components will be installed in the followingorder:

o Database Tools

o Store Configurator

o Software Development Kit

http://service.sap.com/swdc

4 Installation

To install only one or a few components, deselect all components you do notwish to install, and then select Install.

10. The SAP TGM component installation will begin.

4.2 Installing the Database ToolsUseThis section provides the steps required to install the Database Tools component of the SAPPOS Suite.

PrerequisitesThe appropriate database must be installed.

Procedure1. When you are in the welcome screen for Database Tools installation, select Next.

2. To install to the folders displayed, select Next. To install to another folder, selectChange. When you are in the Change Current Destination Folder screen appears,navigate to the appropriate folder and select OK.

3. You are on the Database Type screen. The system scans your system for anyinstalled database and completes the screen. If you have no database installed, itdefaults to Microsoft SQL Server.

4. For Backoff Database, do the following:

If the database is Adaptive Server Anywhere 9.0, do the following:

a) Enter the server name.

b) If you want to change the backup folder, select Change.

c) Navigate to the appropriate folder.

d) Select OK.

If the database is Microsoft SQL Server do the following:


b) Select Connect. You are on the Database Server screen.

c) Select Browse to select another server and select OK.

d) Type a Login ID and Password.

e) Select Logon.

5. For Journal Database, do the following:

If the database is Adaptive Server Anywhere 9.0, do the following:


b) If you want to change the backup folder, select Change.

c) Navigate to the appropriate folder.

d) Select OK.

e) If the database is Microsoft SQL Server, do the following:

f) Enter the server name.

g) Select Connect; you are on the Database Server screen..

4 Installation

19

h) Select Browse to select another server and select OK.

i) Type a Login ID and Password.

j) Select Logon.

6. For Store Configuration Database, do the following:

a) Enter the directory path where the Store Configuration Database is to belocated.

b) To change the location of the backup folder, select Change.

c) Navigate to another folder and select OK.

7. To continue, select Next.

8. You are on the Ready to Install screen. To begin the Database Tools installation,select Install.

4.3 Installing the Xpress Server DatabaseUseThis section provides the steps required to install the Xpress Server Database component ofthe SAP POS Suite.


Procedure1. The welcome screen for Xpress Server Database installation appears. Select Next

2. You are on the Destination Folder screen.

3. To install to the folders displayed, select Next.

4. To install to another folder, select Change. The Change Current DestinationFolder screen appears, navigate to the appropriate folder and select OK.

5. You are on the Database Type screen. Choose the appropriate database driver. Thedatabase server displays based on your choice.

If you choose Adaptive Server Anywhere 9.0, enter the database servername and select Next.

If you choose the MS SQL Server 2000/2005 option, enter or browse tolocate the database server then provide the server Login ID and Password.To continue, select Next.

6. You are on the Ready to Install screen. To begin the Xpress Server Databaseinstallation, select Install.

4 Installation

4.4 Installing the Electronic Journal DatabaseUseThis section provides the steps required to install the Electronic Journal Database componentof the SAP POS Suite.


Procedure1. The welcome screen for Electronic Journal Database installation appears. Select Next



4. To install to a different folder, select Change. You are on the Change CurrentDestination Folder screen. Navigate to the appropriate folder and select OK.


If you choose Adaptive Server Anywhere 9.0., enter the database server nameand select Next.

If you choose MS SQL Server 2000/2005, enter or browse to locate the databaseserver then provide the server Login ID and Password. To continue, select Next.

6. You are on the Ready to Install screen. To begin the Electronic Journal Databaseinstallation, select Install.

4.5 Installing the Xpress ServerUseThis section provides the steps required to install the Xpress Server component of the SAPPOS Suite.

PrerequisitesThe appropriate database has been installed.

Procedure1. The welcome screen for Xpress Server installation appears. Select Next

2. You are on the Destination Folder screen. In the Please Select Your StoreLanguage dialog box, choose the appropriate language.


4. To install to another folder, select Change. The Change Current DestinationFolder screen appears, navigate to the appropriate folder and select OK.

5. You are on the Setup Type screen. Choose one of the following setup typesaccording to your requirement.

Typical - this is the default setting. If you have confirmed that there isenough hard disk space on the computer, select Next to continue with theinstallation.

4 Installation

21

Custom - to choose the components you want to install, select this option.You can also change the default EFT Service, if you wish. You are on theCustom Setup screen. Choose the POS components you wish to install. Ifyou need more information about how to make your selections, choose Help.If you need to verify the disk space available, select Space.

Security Key Container - to install a new Security Key Container, you mustensure this checkbox is checked.

Access rights for working with the Security Key Container (for example,deleting, importing, or exporting it) are limited to the user who initially createdthis file. This is a security feature which prevents other users frommanipulating the file after it has been installed. When installing the SecurityKey Container, you must log on to the machine using the same Login ID andPassword used by the person who initially created the security key file. (Thisuser requires administrator rights.) Failure to do this will result in an error.


If you choose Adaptive Server Anywhere 9.0., enter the database servername and select Next.

If you choose MS SQL Server 2000/2005, enter the database server name orselect Browse to locate it.

7. You are on the Database Credentials screen. Choose the Login ID and Passwordthat will be used by Xpress Server to connect to the BackOffice Database.

Login ID and Password should be provided by the Database Administrator.The database account specified by Login ID must have sufficient permissionsfor the BackOffice database.

8. Select Next.

9. If a key container already exists on your system, you will be taken to the UpgradeContainer screen. Enter the appropriate password and select Next.

10. If a key container does not exist on your system, you will be taken to the InstallSecurity Key Container screen. Enter the location of the keyfile.txt in theSelect Location of Keyfile.txt field.

You must have placed the keyfile.txt in a known folder(s) and note thepassword(s) before beginning the installation.

11. Enter the appropriate password. Be aware that passwords are case-sensitive.

12. Select Add to install the key container. Repeat for each key container you wish toadd.

13. Select Next.

14. You are on the Ready to Install screen. To begin the Xpress Server installation,select Install.

It is vital for retail activity to be uninterrupted should a main server experiencea failure. To ensure uninterrupted activity you can set up a backup server tosupport the main server’s functions. For information on how to set up a

4 Installation

backup server, see Setting Up a Backup Server in the Additional Informationsection of this guide.

4.6 Installing the Electronic Journal ViewerUseThis section provides the steps required to install the Electronic Journal Viewer component ofthe SAP POS Suite.


Procedure1. The welcome screen for Electronic Journal Viewer installation appears. Select Next

1. You are on the Destination Folder screen. In the Please Select Your StoreLanguage box, select the appropriate language.

2. To install to the folders displayed, select Next. To install to another folder, selectChange. The Change Current Destination Folder screen appears, navigate to theappropriate folder and select OK.

3. You are on the Setup Type screen. Choose one of following setup types accordingto your requirement.

Typical — this is the default setting. If you have confirmed that there isenough hard disk space on the computer, select Next and continue with theinstallation.

Custom — to choose the components you want to install, select this option.You are on the Custom Setup screen.Choose the POS components youwish to install. If you need more information about how to make yourselections, select Help. If you need to verify the disk space available, selectSpace.

Security Key Container — To install a new Security Key Container, youmust ensure this checkbox is checked.



If you choose Adaptive Server Anywhere 9.0., enter the database servername and select Next.

If you choose MS SQL Server 2000/2005, enter the database server name orselect Browse to locate it.

5. If a Security Key Container already exists on your system, you will be taken to theUpgrade Container screen.

4 Installation

23

6. Type the appropriate password and select Next.

7. If a Security Key Container does not exist on your system, you will be taken to theInstall Security Key Container. Enter the location of the keyfile.txt in theSelect Location of Keyfile.txt screen.

You must place the keyfile.txt in a known folder(s) and note thepassword(s) before beginning the installation.

8. Type the appropriate password. Be aware that passwords are case sensitive. SelectAdd to install key container. Repeat for each key container you wish to add. SelectNext.

9. You are on the Xpress Server Local Path screen. Type the complete directory pathfor where the Xpress Server will be installed. Select Next.

10. You are on the Ready to Install screen. To begin the Electronic Journal Viewerinstallation, select Install.

4.7 Installing the Store ManagerUseThis section provides the steps required to install the Store Manager component of the SAPPOS Suite.

PrerequisitesThe appropriate database has been installed.

Procedure1. The welcome screen for Store Manager installation appears. Select Next


Security Key Container — To install a new Security Key Container, youmust ensure this checkbox is selected.


3. To install to the folder displayed, select Next. To install to another folder, selectChange. You are on the Change Current Destination Folder screen. Navigate tothe appropriate folder and select OK.

4. If the Security Key Container option is selected, the Install Security KeyContainer screen will appear. Enter the location of the keyfile.txt in the SelectLocation of Keyfile.txt screen.

4 Installation



6. You are on the Database Type screen. Choose the appropriate database driver.Type the database server and the database server IP address. To continue, selectNext.

7. You are on the Database Credentials screen. Choose the Login ID and Passwordthat will be used by Store Manager to connect to the BackOffice Database.

Login ID and Password should be provided by the Database Administrator.The database account specified by Login ID must have sufficient permissionsfor the BackOffice Database.

8. Select Next.

9. You are now on the Xpress Server Local Path screen. Enter a complete directorypath for the location of the Xpress Server.

10. To continue, select Next.

11. You are on the Ready to Install the Program screen. To begin the Store Managerinstallation, select Install.

The Store Manager application requires the Windows operating system dateformat be set to MM/DD/YYYY, and the display resolution set to 800 x 600.

4.8 Installing the Point of SaleUseThis section provides the steps required to install the Point of Sale component of the SAPPOS Suite.


Procedure1. The welcome screen for the Point of Sale installation appears. Select Next.


3. To install to the folder displayed, select Next. To install to another folder, selectChange. The Change Current Destination Folder screen appears, navigate to theappropriate folder and select OK.

4. You are on the Setup Type screen. Choose one of following setup type based onyour needs.

Typical - this is the default setting. If you have confirmed that there isenough hard disk space on the computer, select Next and continue with theinstallation

4 Installation

25

Custom - to choose the components you want to install, choose this option.You can also change the default EFT Service, if you wish. You are on theCustom Setup screen. Choose the POS components you wish to install. Ifyou need more information about how to make your selections, select Help.If you need to verify the disk space available, select Space.

Security Key Container - to install a new Security Key Container, you mustensure this checkbox is checked.

Access rights for working with the Security Key Container (for example,deleting, importing, or exporting it) are limited to the user who initially createdthis file. This is a security feature which prevents other users frommanipulating the file after it has been installed. When installing the SecurityKey Container, you must log on to the machine using the same Login ID andPassword as the person who initially created the security key file. (This userrequires administrator rights.) Failure to do this will result in an error.

5. If a Security Key Container already exists on your system, you will be taken to theUpgrade Container screen. Type the appropriate password and select Next.

6. If a Security Key Container does not exist on your system, you will be taken to theInstall Security Key Container screen. Enter the location of the keyfile.txt in theSelect Location of Keyfile.txt screen.

You must have placed the keyfile.txt in a known folder(s) and note thepassword(s) before beginning the installation.This must be the same key file and password that was used for the XpressServer installation.

7. Enter the appropriate password. Be aware that passwords are case-sensitive.Choose Add to install a Security Key Container. Repeat for each additionalSecurity Key Container you wish to add. Select Next.

8. You are on the Ready to Install screen. To begin the POS installation, select Install.

The Point of Sale application requires the Windows operating system dateformat be set to MM/DD/YYYY, and the display resolution set to 800 x 600.

4.9 Installing the Mobile Point of SaleUseThis section provides the steps required to install the Mobile Point of Sale component of theSAP POS Suite.

PrerequisitesMobile Point of Sale has the following prerequisites:

You must install the Xpress Server Database, Xpress Server, Point of Sale andMobile Point of Sale on the machine to which the Mobile Point of Sale device will beconnected before you can install the Mobile Point of Sale application. The POS andXpress Server applications must be upgraded.

4 Installation

You must install the Microsoft Winsock control DLL file mswinsck.ocx to one of thelocations listed below. To get this file, you must download MSWINSCK.CAB at thefollowing location:http://activex.microsoft.com/controls/vb6/mswinsck.cab (forvb6.0).

Copy mswinsck.ocx to one of the following folders depending on your operatingsystem:

Windows XP \windows\system32\MSWINSCK.OCX

After the file is copied to the appropriate system folder, you must register it. Toregister the file, you will need to type one of the following commands at the DOSprompt, depending on your operating system:

Windows XP regsvr32\windows\system32\MSWINSCK.OCX

Microsoft ActiveSync 4.2 or later must be installed on the system and running. If it isnot running you will see a pop-up window asking you to connect during installation. Ifthis is the case, a quick way to start the ActiveSync is to remove the Mobile devicefrom its cradle and put it back in. This will start the Microsoft ActiveSync.

The mobile handheld device must be placed in its cradle before beginning theinstallation. Failure to do this may prevent some necessary files from beingcopied to the handheld device.

Procedure1. You are on the welcome screen for Mobile Point of Sales installation. Select Next


3. To install to the folder displayed, select Next. To install to another folder, selectChange.

4. You are on the Change Current Destination Folder screen. Navigate to theappropriate folder then select OK.

5. You are on the Hand Held Device screen.

6. Enter values in the Store Number and Terminal Number fields.

7. The first terminal number you enter must be 51. You can increment the terminalnumbers by one for each additional POS register you wish to configure as a MobilePOS up to number 54.

8. You can choose one or both of the following:

If you choose the POS Thin Server option, enter the unique IP address assignedto the printer you wish to connect to the Mobile POS device.

If you choose Xpress Server option, choose the appropriate handheld devicefrom the provided list. Enter a socket number and an IP address for the handhelddevice.

http://activex.microsoft.com/controls/vb6/mswinsck.cab

4 Installation

27

The value required in the Socket field is the one that the Thin Server must listen to forrequests from the handheld devices. Listening port numbers must start at 4000 forTerminal Number 51 and increment by one for each additional POS register configuredas a Mobile POS.

The socket number is directly linked to the Terminal ID number therefore thesecond Terminal ID must be 52 and it must be linked to socket number 4001;the next one must be 53 and it must be linked to socket number 4002 and soforth.

The Unique IP address is the IP address of the host machine where the POSregister configured as a thin server resides and with which the Mobile POS devicewill communicate over the WAN.

9. Verify your settings then select Next to continue.

10. You are on the Ready to Install screen. Verify that the handheld device has beeninserted back in its cradle. This will ensure that all required files can be successfullytransferred to the device during the installation process.

11. To begin the Mobile POS installation, select Install. After the Mobile POS installationprocess is completed, you will need to perform additional configuration tasks on thehost machine to support this installation.

12. On the host machine, create a shortcut for the Mobile POS with the followingcharacteristics:

a) In the Program Files\SAP\Retail Systems folder, create a foldercalled MPOS51.

b) In the Program Files\SAP\Retail Systems\Point of Salefolder, locate posw.exe. Highlight this file and create a shortcut for it.

c) Make a copy of this file and place it in the ProgramFiles\SAP\Retail Systems\MPOS51 folder.

d) Modify the properties file of this shortcut as follows:

e) Edit the Target to show C:Program Files\SAP\Retail Systems\Point ofSale\POSW.exe” – 1=c:\program files\SAP\RetailSystems\mpos51\parm\layout.ui0

f) Edit the Start In path to show C:\Program Files\SAP\RetailSystems\mpos51.

g) Place a copy of the same shortcut on the desktop and rename it MobilePOS.

h) Update the m_Pos.ini file with a parameter to handle credit cardmanagement DLL file. This file is located in the C:\ProgramFiles\SAP\Retail Systems\Mobile Point of Sale folder. Todo this, in the m_Pos.ini file, add the following line:

MsrDLLName=Msr3000MCx.dll

The requirement for this *.DLL along with its name may vary depending onthe requirements of any peripheral or service-supporting software in use atthe retail location.

4 Installation

13. Copy m_Pos.ini from C:\Program Files\SAP\Retail Systems\MobilePoint of Sale to the Mobile POS repository folder created for the device type(for example, MC3090).

For more information on how to configure the peripheral components whichsupport the Mobile POS application, see Configuring the Mobile Point of SaleComponents in the Additional Information section of this guide.

4.10 Installing the Store ConfiguratorUseThis section provides the steps required to install the Store Configurator component of theSAP POS Suite.


Procedure1. The welcome screen for Store Configurator installation appears. Choose Next


Security Key Container — To install a new Security Key Container, you mustensure this checkbox is selected.


3. To install to the folders displayed, select Next. To install to another folder, selectChange.

4. You are on the Change Current Destination Folder screen appears, navigate to theappropriate folder and select OK.

5. If the Security Key Container option is selected, the Install Security KeyContainer screen will appear. Enter the location of the keyfile.txt in the SelectLocation of Keyfile.txt screen.



7. You are on the Ready to Install screen. To begin the Store Configurator installation,select Install.

After the Store Configurator is installed, you will need to restart the server.

4 Installation

29

4.11 Installing the SDKUseThis section provides the steps required to install the SDK component of the SAP POS Suite.

PrerequisitesThe appropriate database must be installed. You must know the IP address for yourdatabase server.

Procedure1. The welcome screen for SDK installation appears. Select Next

2. You are on the Destination Folder screen. In the Database Server IP box, enter theIP for the database server.

3. To install to the folders displayed, select Next. To install to another folder, selectChange. The Change Current Destination Folder screen appears, navigate to theappropriate folder and select OK.

4. You are on the Ready to Install screen. To begin the SDK installation, select Install.

5 Post-Installation

5 Post-InstallationThe following section describes activities to perform after the SAP POS componentsinstallation is completed. This allows you to test that the installation was successful.

After the Xpress Server, Xpress Server Database and the Configurator areinstalled, you must reboot the PCs and place all the parameter files exportedby the Configurator application in the following directory: \ProgramFiles\SAP\Retail Systems\Xpress Server\Parm. This is requiredfor a new installation, a re-installation or an upgrade on the Xpress Server.The POS and Store Manager applications require that the Windows operatingsystem date format be set to MM/DD/YYYY, and the display resolution set to1280 x 1024.

5.1 Starting and Stopping SAP TGMFor detailed information about starting and stopping SAP TGM Configurator and POSManager, refer to the appropriate user guides.

6 Additional Information

31

6 Additional Information6.1 MSI Silent Mode InstallOverviewMSI has the built-in feature to use a transform (.mst file) to customize and perform the installsilently. A transform (.mst file) is a simplified Windows Installer database that contains thedifferences between two .msi databases. Transforms enable an administrator to applymodified settings to a database when deploying an installation package.

Applying a transform will modify the installation design and results. Onlyusers with the relevant expertise and a good understanding of theapplication and environment should run this type of installation.

Using the Upgrade.ini FileSAP TGM provides the capability to perform a silent install of the upgrade files. This is doneusing a file called Upgrade.ini.

The Upgrade.ini must be in the same folder as the MSI installation file.

New Installation or UpgradeTo perform a new installation or to upgrade from any version from 8.0 to 9.5, run the followingcommand:

Msiexec.exe /I <PATH>\<MSI> /L*v <PATHTOLOG> /qn

Msiexec.exe /I C:\GM\Point of Sale.msi /L*vC:\GM\POS.log /qn

Upgrade/Repair from GM v10 Build to BuildTo perform an upgrade or repair from build to build in version 10.0, run the followingcommand:

Msiexec.exe /I <PATH>\<MSI> /L*v <PATHTOLOG> REINSTALLMODE=VAMUSREINSTALL=<FEATURES> /qn

The following is a list of parameters for this command:

Component Parameter

POS <FEATURES>=Core_Files,Utilites,Browser,EFT_SERVICE

MPOS <FEATURES>=ALL

BACKOFF <FEATURES>=Core_Files

CFG <FEATURES>=Core_Files,ODBC, DBRegistry

XPS <FEATURES>=Core_Files,Utilites,API,EFT_SERVICE

EJV <FEATURES>=Core_Files

DBTOOLS <FEATURES>=ALL


SDK <FEATURES>=ALL

XPSDB <FEATURES>=Core_Files

EJVDB <FEATURES>=Core_Files

Msiexec.exe /I C:\GM\Point of Sale.msi /L*v C:\GM\POS.log

REINSTALLMODE=VAMUS

REINSTALL=Core_Files,Utilites,Browser,EFT_SERVICE /qn

6.2 Replication Installation Process

The Replication utility is not required by most Transactionware users, and isnot automatically shipped with the product. If you require this utility, it will beprovided by your SAP support analyst.

Follow the directions below to locate and install this utility.

Replication has one dependency in that it must be installed on the same system the XpressServer is installed.

To install the Replication utility:

1. Insert the Installation CD.2. On the Windows status bar select Start, and then select Run. The Run dialog box

appears.3. In the Open field, type x:\rplct\disk1\setup.exe, where x is the letter of your CD-

ROM drive.4. A dialog box appears welcoming you to the Replication Utility setup program. This dialog

box describes the version of the application to be installed, and gives you the opportunityto close any other programs that may be running in order to prevent potential installationconflicts. Read the dialog box carefully, and then select Next to continue.

5. On the next dialog box, you must indicate where you want to install the Replicationapplication. Accept the default as displayed, and then select Next to continue.

6. On the Select Database Server System Directory dialog box, you must indicate whereyour installation of your database program resides. Accept the default as displayed, andthen select Next to continue.

7. On the Select Database Name dialog box, you must enter the name of the databaseserver. Enter the same name used during the Xpress Server application install. In theServer field, type the name of your server, and then select Next to continue.

8. On the next dialog box, you must enter the parameters required to connect to your Oracledatabase. Enter the required Oracle settings, and then select Next to continue.

9. On the next dialog box, you must indicate where your Oracle client is installed. In thePath field, type the Oracle directory path, and then select Next to continue.

10. The next dialog box displays a list of the settings you have chosen for this application.Review the settings, and then select Next to continue.

If you need to make any changes to the settings, select Back.


33

11. A progress bar appears to display the status of the file copy. This process may take a fewminutes. Wait until it has finished.

If, for any, reason you need to terminate the installation procedure at thistime, select Cancel.

12. A Warning box informs you of backup files made during this setup. Read the message,and then select Next to continue.

13. When the Replication utility installation is complete, follow the Exit Installationprocedure by selecting Finish. Then select the Yes, I want to restart mycomputer now option.

6.3 Setting Up a Backup ServerIt is vital for retail activity to remain uninterrupted should a main server experience a failure.To ensure this, you can set up a backup server which the POS terminals can revert to if thishappens. The backup server can support retail processes such as transactions, and PLU andcustomer information lookups. It can also receive trickles of Transaction Log and Journal Fileinformation which provides an additional redundancy of sales data.

The backup server can be a dedicated computer or any one of the regular POS terminalsprovided it meets the minimum requirements to run the Xpress Server software. You mustspecify the terminals that will copy information to the backup server. You can configure any orall of the terminals to work with the backup server.

UseThis section provides the steps required to configure a Backup Server for the SAP POSSuite.

PrerequisitesYou must install a compatible SQL database server application on your backup computerbefore you can configure the backup server.

ProcedureTo set up a backup server, you must do the following:

1. Ensure that the primary Xpress Server is correctly installed and running.

2. On the backup server computer, install the Xpress Server and Xpress ServerDatabase software from the installation CD, following the directions in the installationprogram and entering the appropriate information as required.

3. After you have installed the Xpress Server components, close the installationprogram and reboot the computer.

4. When the computer restarts, the SQL program and Xpress Server will automaticallystart.

5. On the server Main tab, select Start. A series of line messages will appear in themain Xpress Server window indicating that the system has read your licenseinformation and applied any default parameter settings. When it has finishedprocessing all the necessary information, the messages Xpress Server Readyand Trickle Enabled appear.

6. Select on the Properties tab page. On this tab page do the following:


In the Communications section of the screen, select Is Backup Server to indicatethat this computer will be used as the backup Xpress Server.

In the Primary Server Name field, type the machine name or IP address of theprimary server computer.

7. Select Apply to save the information you entered.

8. Select the Main tab page. On this tab page do the following:

Select Stop Server and wait for the server to stop.

9. Select Start Server to restart the server. Watch for the line message indicatingBackup Xpress Server Ready.

At this point, the primary and backup servers will synchronize. The system will thenperform a synchronization query every five minutes to ensure that the Xpress Serverand backup server are working in tandem.

10. Configure the POS terminals to revert to the backup server in case of an interruptionto the main server. You can do this during the initial setup of the POS terminals, oryou can use Manager Code 6 at any time. This is how to do this:

On each POS terminal, perform a Manager Code 6 (Define Terminal) function.

When prompted, indicate that you wish to use a backup server, and also indicate ifyou wish to use a backup credit server as well (for backup credit authorization). Thenenter the server names or IP addresses as prompted. The transaction files will thenbe sent to both the primary and backup servers (but note that the transaction files arenot posted to the database on the backup server).

6.4 Configuring the Mobile Point of Sale ComponentsThe Mobile Point of Sale application is a mobile thin client POS application supported by aninfrastructure that consists of a wireless handheld or mobile device, an access point, and awireless printer. Your environment may also include a magnetic stripe reading device (MSR)or a signature capture device. In addition to installing the application files which set up andlink the Mobile POS as a recognized terminal in your store, you also need to configureadditional components which support the Mobile POS terminal. This section describes how toinstall and configure these components.

The following diagram is an illustration of how the POS components are set up in relation tothe access point:

The following section describes how to set up and configure the Mobile Point of Saleapplication.


35

Mobile POS Application Technical NotesThe current version of Mobile POS is based on Windows CE Thin Client architecture. Theprogram is written using the Microsoft Pocket PC SDK, the Symbol 8100 SDK and Microsoft’sEmbedded VC++ 3.0. The Symbol SDK handles the hardware elements of the program.

Supported DevicesThe Mobile POS Thin Client is composed of a networking module, a simple GUI andhardware components for the scanner and MSR. The printer is a TCP/IP printer.Transactionware Mobile POS and Mobile Inventory support the following devices:

Device Specification

Symbol MC3000/MC3090Up - MobileHandheld Device

Microsoft Windows CE 4.2 ProfessionalEdition

64 MB memory

64 MB Flash

28, 38, or 48 key emulation

Symbol PDT 8146 XScale - MobileHandheld Device

Microsoft Pocket PC 3.0

64 MB RAM

32 MB ROM

28, 37, or 47 key emulation

Ability to add Symbol MSR clip on

Symbol AP 4131 - Wireless Access Point 802.11b 11 Mbps

Zebra QL320 - Mobile Printer 802.11b 11 Mbps

Configuring the Mobile POS Wireless ComponentsAfter you have installed the Mobile POS Thin Server or Xpress Server application files, youmust configure the supporting wireless components and devices which run the Mobile POSnetwork and link it to the business server. You will need to define specific settings for each ofthe following devices:

Wireless switch (controls the Mobile POS wireless network)

Handheld device

Printer

The following sections provide very basic information on the settings you will need toconfigure to get your Mobile POS network up and running. Additional or more specificinformation on each device referenced should be obtained from the vendor web site.


Setting Up the Wireless NetworkRefer to the manufacturer’s User Guide for assistance with setting up your wireless network.

SAP recommends the use of WPA2 which is more secure than WPA To make the key truly secure, use an encryption key with lots of letters,

numbers and special characters.

Connecting Handheld Device to Wireless NetworkMobile POS supports the Symbol MC3000 and Symbol PDT 8146 XScale handheld devicemodels. The following steps describe how to connect the Symbol MC3000 to your wirelessnetwork.

1. To connect the Mobile POS device to the wireless network:

2. On the Mobile POS device, tap the task bar.

3. Tap Menu settings.

4. Enable the Auto Hide option. This hides the status bar at the bottom of the mobiledevice thus providing you with more screen space.

5. Tap the task bar again. Tap the Wireless Network icon.

6. The Wireless Switch name is the ESSID. For example, ESSID=101. Connect to theESSID.

7. Tap the Authentication tab and select WEP 128 as the encryption standard.

8. Enter the required secure encryption key.

9. In the IP Configuration field, ensure that DHCP is selected.

10. Test your wireless infrastructure by pinging the printer from the Mobile POS serversystem

Connecting Printer to Wireless NetworkFor instructions on connecting a printer to the wireless network, refer to your hardwaremanufacturer’s User Guide.

SAP recommends the use of the QL320+ printer that supports 802.11G.

Test your wireless infrastructure by pinging the printer from the Mobile POS server system.

If you face problems communicating with the devices using the ping utility, callyour hardware vendor for assistance.

Running the Mobile POSAfter the handheld device is connected to the host PC, you can begin to operate it. You canstart the Mobile POS by double-clicking the icon on the Desktop or by tapping Start and thenRun.

Sometimes you may encounter a resetting of the configurations following a cold reboot. Toprevent this, you can export settings in the WLAN profile manager. Go to Options Export.Choose both export options: Export Options and Export All Profiles.


37

To start the Mobile POS application by clicking the icon, do the following:

1. On the host version of the POS, set Manager Code 6 for the Thin Client CE using thefollowing settings:

Terminal ID = 51. The current configuration supports a maximum of fourterminal IDs. The remaining three can be set to 52, 53, and 54 respectively.

Report Group = No change is required to this parameter.

Parm Group = No change is required to this parameter unless you arerunning the POS and Mobile POS with different menus. Consult yourtechnical analyst if you require any changes to a Parm Group.

Is Thin Server = Yes

Enter Pacing MS = 10

Display Popup = Yes

Thin Client Type = Mobile CE POS

Listen Socket Number = 4000. This value increases by one for eachadditional terminal ID. For example, this setting will be 4001 for Terminal ID52.

2. Double-click the mobile POS icon on the handheld device.

3. To start the Mobile POS application by selecting Start, do the following:

a) On the Windows status bar of the host POS terminal, select Start, and thenselect Run. The Run dialog box appears.

b) Depending on the type of application you wish to run, type one of the following inthe Open field:

If you are installing the Mobile POS Thin client on a system that alreadyhas the POS software installed, and you want to use multiple POSsystems on the one PC, then type C:\Program Files\SAP\RetailSystems\mpos51\posw.exe. Otherwise, type C:\Program Files\SAP\Retail Systems\Point of Sale\posw.exe.

This brings up a host version of the POS on your terminal.

Or

If you have installed the emulator, type c:\ProgramFiles\Windows CETools\wce300\MS PocketPC\emulation\palm300\windows\shell32.exe.

c) On the host version of the POS, set Manager Code 6 for the Thin Client CE usingthe following settings:

Terminal ID = 51. The current configuration supports a maximum of fourterminal IDs. The remaining three can be set to 52, 53, and 54respectively.

Report Group = No change is required to this parameter.

Parm Group = No change is required to this parameter unless you arerunning the POS and Mobile POS with different menus. Consult yourtechnical analyst if you require any changes to a Parm Group.

Is Thin Server = Yes

Enter Pacing MS = 10


Display Popup = Yes

Thin Client Type = Mobile CE POS

Listen Socket Number = 4000. This value increases by one for eachadditional terminal ID. For example, this setting will be 4001 for TerminalID 52.

d) Turn on the handheld device.

e) Select OK on the Welcome window.

f) Double-click the EXIT icon.

g) Double-click the CEMPOS TWGM icon; this opens the Mobile POS application.

h) Select OK at the Connect to Server message. You are now ready to use theMobile POS.

It has been detected that a cold boot of the mobile device maycause resetting of the configuration settings. To prevent this, youcan export options

Troubleshooting the Mobile POSThe following section provides some frequently-asked questions that may come up as youconfigure the Mobile POS device.

How do I warm boot the mobile device?

Response: Press and hold down sequence keys 7, 9 and the red power button at the sametime. This warm boots the mobile device.

What can I do if the device says Not Connected?

Response: Check the following:

Check that the Thin Client which resides on the handheld device is running.

Check that the handheld device is able to ping the server on which the MobilePOS application is installed.

Check that all the settings in M_pos.ini are correctly set.

The device is not printing.


Check that the printer is turned on.

Check that the IP address for the printer is properly defined in M_pos.ini.

The device has an MSR device attached but nothing happens when a card is swiped.


In the Main section of M_pos.ini, check that the MsrDLLName is correctlydefined.

Confirm that the MSR device was attached to the handheld device prior tolaunching the Thin Server and Thin Client.


39

6.5 Running Multiple POSs on a Single MachineWhen more than one POS runs on the same machine, each active POS may look identical tothe next one. This can cause the main screen to look cluttered and confusing. Since eachPOS has a distinct layout file, you can use the layout file to designate a specific location onthe screen for each active POS as well as define other distinctive display features such asthe size of the window or the colors and style of the buttons which can distinguish one POSfrom another.

Modifying Layout FilesYou can use Manager Code 40 to create a layout file. This file is stored in the Parm directory.

Currently only layout.ui0 is supported.To create a layout file:

1. Start the main POS.

2. Run Manager Code 40 and modify the layout for that POS as required.

3. When you are done, on the menu options select Save Changes.

4. At the Send File to Server Proceed prompt, select No.

Choosing Yes to this prompt sends a copy of the current layout file to theserver. This results in the server sending the layout file to each additionalPOS installed on that machine and overwrites any distinguishing layoutoptions that may have been set for the other POSs.

5. Copy the layout file to the Parm directory for each POS by doing the following:

a) Start each POS.

b) Copy the new layout file into each additional POS \parm directory.

c) Customize the layout file for each POS by doing the following:

o In the Parm directory for each additional POS, double-click on the layout fileand open it using Notepad.

o Alter the settings in the layout file as required to customize it for that specificPOS.

In the example below, the following settings were configured in the layout file:

[General]

NoResize=0

xSize=50

ySize=50

xOffset=0 (in increments of 10 depending on the POS)

yOffset=0 (in increments of 10 depending on the POS)


Launching Additional POS InstancesTo apply the changes made to the layout file, restart each POS.

To toggle between the various POSs, use the <Alt><Tab> function inWindows. The terminal number and program name will be displayed in thestatus bar.

6.6 Obtaining Database Server NameTo obtain the individual database engine name at a store, perform the following steps on thecomputer on which the Xpress Server is installed.

You must already be signed on to the system.To obtain the store database server name:

1. On the Windows status bar, select the Start button.

2. Choose Programs SAP SQL Service Manager. The SQL Anywhere ServiceManager dialog box opens. The Service Name field contains the name of the databaseengine.

3. Select Close to exit.

6.7 Integrating SAP POS and TransnetAs part of their complete retail point of interaction solution, many Transactionware users alsopurchase the Transnet product suite. A platform-independent transaction switch, Transnetprovides the foundation for a smart, secure, and seamless retail communications network. Tofacilitate ease of integration between these two products, when you install POS on yoursystem, the install program also silently installs the basic client software for Transnet FileTransfer and Transnet Message Transfer. If you also intend to run Transnet on your system,you simply need to change a few settings to activate these clients, and then configure thesystem to suit your needs.

To activate the Transnet client software in POS, do the following:

1. Install the POS Suite on your system at each of your head office, back-office, and POSterminal levels, as required.

2. Install the Transnet product suite at your head office (see the Transnet userdocumentation set for complete information).

3. At the store level, on your Xpress Server and backup server machines, change theconfiguration file settings, as follows:

a) In the main Xpress Server directory (by default, located at C:\ProgramFiles\SAP\Retail Systems\Xpress Server), locate the NFM and NTM folders.These folders contain the Transnet client files.

b) In the NTM folder, locate the Conf folder, and then locate the following files:client.conf and clientapi.conf.

c) Open the client.conf file in a text editor (such as Notepad), and perform thefollowing configurations:

LISTENADDR: Enter the IP address of your Transnet client. This willgenerally be the same as that of your Xpress Server. This setting isnecessary only if you have more than one network card installed.


41

LISTENPORT: Enter the port used by your Transnet client. This willgenerally be the same as that of your Xpress Server (the default is port8300). This setting is necessary only if you have more than one network cardinstalled.

SERVERADDR: Enter the IP address of your Transnet Message Transferserver.

SERVERPORT: Enter the port used by your Transnet MessageTransferserver (the default is port 8400).

ICONNECT: If set to TRUE, when started, the client will immediately try tomake a connection with the server. This eliminates a connection startupdelay when a transaction is received and must be sent to the server since theconnection is already active. However, if you want the client to wait until ithas a transaction before initiating a connection to the server, then set thisoption to FALSE.

ALERT: There are different levels of severity when errors occur. Some arerecoverable or expected; some are not and can cause a major failure. Whenone of these severe errors occurs, if an alert command has been configured,the client will execute that command. The command can contain a percentsign (%) that is replaced with an error message. This can be used to havethe client submit an error message to the executable that will be started.

If you wanted to execute a program called sendemail with an email addressas the first parameter , and an error message as the second parameter, setthis option to be: ALERT=sendemail [<email address>]%, where thepercent sign would be replaced with a quoted error message before the clientexecutes the command.

o Set the TACTIONLOG setting to TRUE or FALSE, depending onwhether you wish to create a transaction log.

o If set to TRUE, specify a name for the log in the TACTIONLOGNAMEsetting (it should contain a full path and file name).

o Set the DEBUGLOG setting to TRUE or FALSE, depending on whetheryou wish to create a log for debugging purposes. Use this log forproblem determination only; do not enable it by default as it will decreaseperformance and use large amounts of disk space.

o If set to TRUE, specify a name for the log in the DEBUGLOGNAMEsetting (it should contain a full path and file name).

o Set the EVENTLOGLEVEL setting to the severity level up to which youwant events to be logged.

o Specify a name for the log in the EVENTLOGNAME setting (it shouldcontain a full path and file name).

RASPRI: If the client is to access the server via a dial-up connection and youwish to have the client automatically initiate the RAS connection, set this optionto be the correct RAS configuration name. When started, the client will initiate theRAS connection and wait for it to become active before trying to access theserver. If the connection drops the client it will restart the RAS connection.

RASSEC: This is a secondary RAS configuration name. If the client fails toconnect using the primary configuration (RASPRI), then it switches and tries touse this one. If this one fails, it switches to the primary. It will switch back andforth until a connection is established or stopped.


INACTIVITYTO: The inactivity time-out option is used to disconnect a RASconnection from the server when transactions are not being transmitted. Bydefault, the client keeps the connection active continuously but in some cases(like long distance dial-up connections); this may not be the desired option. Thisoption can be used to have the client drop the connection after a specifiednumber of minutes expire with no transactions transmitted or received. Set thisoption to the number of minutes to wait before having the time-out occur. A valueof zero turns off the inactivity time-out.

4. Set the COMPRESSION to TRUE or FALSE, depending on whether you want to usecompression in your information transfer. The client has the ability to compress data tominimize the amount of bandwidth required for transactions. This is especially importantfor slower dial-up connections. Keep in mind that on fast connections, such as Ethernet,compressing small transactions may hinder instead of help.

If set to TRUE, specify the percent of compression you want to use in theCOMPRESSION% setting. Although most transactions will compress to some extent,others will not. If compression does not produce a smaller transaction, then thattransaction is sent uncompressed. With this option you can go one step further. Thisoption specifies a minimum percentage of space that must be saved when a transactionis compressed. For example, if you set this option to be 10 (ten percent) then atransaction that initially is 100 bytes long must compress to a length of 90 bytes or less. Ifnot, it is sent uncompressed. Do not set this value to an unlikely percentage. A value of 0disables this option.

5. For the SERVERSSLTYPE setting, specify an SSL encryption type for your server(optional).

If you specify an SSL type here, it must match the settings on your SAP TGMXpress Server.

6. For the APISSLTYPE setting, specify an SSL encryption type for your client API(optional). This option specifies whether the client will use SSL when acceptingconnections from applications using the API. You can turn off SSL with the setting ofNONE.

If you specify an SSL type here, it must match the SSL setting in yourclientapi.conf file.

7. Take care not to add any additional spaces or tabs following the settings you enter hereor the configurations will not work. When you have finished configuring the settings, saveand close the file.

8. Open the clientapi.conf file in a text editor (such as Notepad), and perform thefollowing configurations:

APIID: This option is used to set a unique API ID that is inserted into everytransaction that is sent by the API. This ID can be used to locate and tracktransactions generated by a specific copy of an application. This ID should be uniquethroughout the entire NTM network. This ID is set using a numeric value (forexample, APIID=1) and the value of zero means no ID is to be used. Possible valuesrange from 1 to 232.

CLIENTADDR: Enter the IP address of your Transnet client. This will generally bethe same as that of your Xpress Server.

CLIENTPORT: Enter the port used by your Transnet client. This will generally be thesame as that of your Xpress Server (the default is port 8300).


43

TIMEOUT: Normally, but not always, when a transaction is sent it will generate aresponse that is sent back to the application via the API. These responses areexpected to arrive at the API within a specified amount of time. The default time is 10seconds. If the response is not received within the time-out period, then an alert issent to the application. Use this option to change the time-out period which is inseconds.

ALERT: There are different levels of severity when errors occur. Some arerecoverable or expected; some are not and can cause a major failure. When one ofthese severe errors occurs, if an alert command has been configured, the client willexecute that command. The command can contain a percent sign (%) that isreplaced with an error message. This can be used to have the client submit an errormessage to the executable that will be started.

If you wanted to execute a program called sendemail with an email address asthe first parameter , and an error message as the second parameter, set thisoption to be: ALERT=sendemail [<email address>] %, where thepercent sign would be replaced with a quoted error message before the clientexecutes the command.

AUTORECONNECT: This option is simply to allow the API to automaticallyreconnect to the client if the connection is lost. This prevents the application fromhaving to stop and reestablish the connection via the API on its own.

9. Set the TACTIONLOG setting to TRUE or FALSE, depending on whether you wish tocreate a transaction log.

If set to TRUE, specify a name for the log in the TACTIONLOGNAME setting (itshould contain a full path and file name).

10. Set the DEBUGLOG setting to TRUE or FALSE, depending on whether you wish tocreate a log for debugging purposes. Use this log for problem determination only; do notenable it by default as it will decrease performance and use large amounts of disk space.

If set to TRUE, specify a name for the log in the DEBUGLOGNAME setting (it shouldcontain a full path and file name).

11. Set the EVENTLOGLEVEL setting to the severity level up to which you want events to belogged.

12. Specify a name for the log in the EVENTLOGNAME setting (it should contain a full pathand file name).

13. For the SSL setting, specify an SSL encryption type for your client API (optional). Thisoption specifies whether the client will use SSL when accepting connections fromapplications using the API. You can turn off SSL with the setting of NONE.

If you specify an SSL type here, it must match the APISSLTYPE setting inyour client.conf file.


14. Set the COMPRESSION to TRUE or FALSE, depending on whether you want to usecompression in your API information transfer. The client has the ability to compress datato minimize the amount of bandwidth required for transactions. This is especiallyimportant for slower dial-up connections. Keep in mind that on fast connections, such asEthernet, compressing small transactions may hinder instead of help.

If set to TRUE, specify the percent of compression you want to use in theCOMPRESSION% setting. Although most transactions will compress to some extent,others will not. If compression does not produce a smaller transaction, then thattransaction is sent uncompressed. With this option you can go one step further. Thisoption specifies a minimum percentage of space that must be saved when atransaction is compressed.

If you set this option to be 10 (ten percent) then a transaction that initially is 100bytes long must compress to a length of 90 bytes or less. If not, it is sentuncompressed. Do not set this value to an unlikely percentage. A value of 0disables this option.

15. Take care not to add any additional spaces or tabs following the settings you enter hereor the configurations will not work. When you have finished configuring the settings, saveand close the file.

6.8 Understanding the Data FlowThis section describes the overall data flow across the various SAP POS components.

Business Day Data FlowThis section describes the flow of data through the SAP POS during each phase of thebusiness day.

During a standard retail day, certain tasks are performed using the POS Suite. On a businessflow level, these tasks can be grouped into four general areas:

Pre-Open

Store Open

Terminal Open

End of Day (EOD)

As business flow tasks are completed by the product end user, whether that user is a cashier,a manager, or head office personnel, data is created and moved or stored in some locationfor future reference. This creation and movement of data is known as the data flow and isinvisible to the eyes of the end user but absolutely vital to the operation of the system.


45

The four phases of business flow can be mapped to seven phases of data flow as shownbelow.

Business Flow Data Flow

Pre-open Pre-open

Store Open Opening the Store

Opening the terminal

The Sales Day The Sales Day

End of Day Closing the terminal

End of Day

Polling

Pre-OpenIn the Pre-open phase (or at any point in the day), a store’s head office can send newparameter (parm) files to the stores. It can also send files from other systems, such aspricing files from a merchandising system, or updates to employee records from a HumanResources program.

The Pre-open process begins when parameter files are created or updated in theConfigurator or another third-party application. (Third-party applications need SAP’sDownload File Formats to produce parameter files which the POS can recognize.) When theparameter files are created in the Configurator application, they are saved to the SQLdatabase and converted from binary format (within the SQL DB) into ASCII for transmissionto the stores. For example, a Tender parameter file will be converted into an ASCII file namedtender.asc.

After the conversion process is completed, the head office can dial into the stores andtransfer any new or modified parameter files to the \parm directory of the Store server sothey can be accessed by the POS applications.

When a parameter file is applied, it means that the Xpress Server has converted theparameter ASCII files back into the binary format used by the store-level POS components.See The Parameter Apply Process section for more information.

The server continuously polls the \parm directory for a file called Newparm.trg. Thepresence of this file indicates to the server that there are new ASCII parameter files presentand prompts it to apply them to the Store’s files. Because the server polls the \parmdirectory for a Newparm.trg file every 30 seconds (by default), as soon as one is found, theserver automatically applies it.

The Parameter Apply ProcessThe following section outlines the process for the store server to apply parameter (parm) filesreceived from head office:

The server copies all *.asc files from the \parm directory into \TXNSAVE.

The server picks up applicable *.asc files from the \parm directory and applies their data tothe appropriate table in the SQL database.

Upon successful completion of the previous step, the server applies the POS data (more*.asc files) from the \parm directory into the appropriate binary table, also located in the\parm directory.


Binary files are renamed according to the following convention:99990000.xxx

xxx identifies the type of file (for example, 99990000.tdr is renamed tender.tdr)9999 = Store number00 = Region number00 = Reserved for future useThe Xpress Server determines which *.asc files are required at the SQL level (for the StoreServer and the Store Manager applications), and which need to be applied to the binary table(solely for the use of the POS POS).

The newparm.trg file is deleted from the \parm directory, and the *.asc filesremain in the \TXNSAVE directory until they are overwritten by the next set ofincoming update files.

If a particular parameter does not apply successfully, you can check therelevant parameter file in the \TXNSAVE directory to identify the fault.

Store OpenThe following processes occur during the Store Open process:The server determines if and how many unclosed terminals exist from the night before anddisplays the appropriate warning message if required.The server puts the business date up on the screen and prompts the user for verification (ifthis option has been enabled in the Configurator).The server checks to ensure that the business date selected is not a duplicate business date.If it is a duplicate, a warning message is displayed. The system derives the business datefrom the system date at the time of Store open. For example, if you performed a Store Openat 9:00 AM, and then an End of Day process at noon, if you then performed another StoreOpen that same day at 1:00 PM, the business date would be the same as (and in conflictwith) the previous business date.The server updates the state.srv file in the \sdata directory, and the SERVER STATETABLE in the SQL database.An Open Store status message is sent to the terminals. The indicator on each terminalchanges from Store Closed to Open.If specified in the Configurator, and if the STORE OPEN function was run from a POSterminal, you are prompted to open the current terminal as well.

Business Date and System DateThe business date is chiefly unseen as it is related only to reporting (although it can appearon some receipts). The system date is visible on the screen, receipts, and so on. Promptingfor business date during Store Open can be turned off in the Configurator (RegisterParameters).Should you wish to change the business date on a terminal at any time, run Manager Code426 - Change Business Date.If a terminal does not close during the end of day process, on the next day that terminal willhave a business date conflict with the server. If this occurs, you can correct a business dateconflict by running Manager Code 424 - Change Business Date. This prompts the terminal torequest the correct business date from the server, and then reset itself to that date.

Note that you must have a live server connection to run Manager Code 424.


47

Terminal OpenThe following processes occurs during the Terminal Open phase:

The terminal synchronizes its system date and time with the date and time detected on theserver machine.

The terminal retrieves, from the server, any new parameter files that have arrived over thecourse of the evening, by comparing the server’s \parm directory with the terminal’s, anddownloading any new files from the server’s \parm directory into its own \parm directory.

The terminal will consider a parameter file to be new, and therefore apply that file, if the filehas a different file time, file date, or file size than that of the file currently existing in theterminal’s \parm directory.

The terminal updates its open/close state in the state.reg file, which is located in theterminal’s \rdata directory.

An Open Terminal status for that terminal is sent to the server.

Parameter File TypesThere are four different types of parameter files, with each type being stored or behaving in aseparate manner.

Parameter File Type Examples

Type 1The following are characteristics of the Type 1 parameter file type:

The parameter file is pulled to the register if it has changed.

The register only looks to its own local copy.

Changes made at the server to this type of parameter file would not be instantlyreflected across the store.

The majority of parameter files are Type 1 parameter files. For example:

Register and keyboard files

Department files (such as dept.dpt)

Tax files (such as taxtable.tax)

Tender files (such as tender.tdr)

Type 2The following are characteristics of the Type 2 parameter file type:

The parameter file does not get pulled to the register. Instead, the register requeststhe relevant data from the server whenever it is needed.

Changes made to a Type 2 parameter file are instantly reflected across the store. Forexample:

PLU files

Layaway and other Pending Transaction files


Type 3The following are characteristics of the Type 3 parameter file type.

The parameter file gets pulled down to the register.

The terminal still looks only to the server’s copy for its information, unless the POS isoffline.

There is only one Type 3 parameter file:

cashier.clg

Type 4The following are characteristics of the Type 4 parameter file type.

The file is not converted, only read, so the Configurator is not needed to makechanges to it. It is copied to the register during a Manager Code 414, but the POSonly takes notice of the changes once you have exited and re-invoked the software.

POS.ini

The Local.ini file is generally a copy of the POS.ini file. If there are any differencesdetected between the two files, the server will always use the settings found in theLocal.ini rather than the POS.ini. Because of this feature, you can create a globalPOS.ini file for all your stores, and still use individual Local.ini files for regional settings.

Directory StructureThe Xpress Server and POS applications have the same sub-directory structure branching offof their program directories. C:\Program Files\SAP\Retail Systems\XpressServer is the default program directory for the Xpress Server, while C:\ProgramFiles\SAP\Retail Systems\Point of Sale is the default program directory for theterminal and POS.

Two of the most important sub-directories that appear in both the server and the terminal are\rdata and \sdata. The r in \rdata stands for register. The s in \sdata stands for serveror store.

The Sales DayThroughout the sales day, transactions are run through the terminal, where the customerpays for goods in order to take them home. The following describes the basic flow of dataduring a typical transaction. This scenario assumes that the server is online with the POS andthat the system is configured to use server data first in the case of Local PLU or BackupServer configurations.

After the cashier scans an item, the POS sends the PLU to the server, requestingdetails.

The server accesses the PLU file in the SQL database and returns information suchas price, description, taxes, and so on.

The returned information is immediately placed into RAM and posted to the LD.jrnfile (in ASCII format) located in the terminal’s \rdata directory.

Steps 1to 3 are repeated until all of the customer’s items are entered.

As the cashier totals the transaction and accepts tender from the customer, moreinformation is placed into RAM and posted to the LD.jrn file.

If the tender is a credit card, the card information is sent to the server, where it istransmitted to an application-specific credit service provider.


49

Once the server receives a response from the credit provider, it transmits the answerback to the POS, which then posts this additional information (masked card number,credit verification) into RAM, and into the LD.jrn file.

Credit verification requests and responses are in accordance with CISP standards.

The transaction in RAM is now posted to the binary LD.txn file.

Everything done at the POS is captured in the LD.txn and LD.jrn files, includingsales, manager code functions, open and close actions, and reports.

If you enable the powerfail option in the POS.ini file, you can have a file calledPowfail.sus in your \rdata directory. This powerfail option copies each line ofthe current transaction record to the Powfail.sus file. Then, following the event ofa power outage, when the POS comes back online it can retrieve the currenttransaction data from the Powfail.sus and place it back into memory. The cashiercan then complete the transaction in progress.

The Trickle ProcessThe data for inclusion in both the LD.txn file and the LD.jrn file are continually fed, ortrickled, to the server throughout the day. The trickle process is initiated by the server as itpulls both the LD.txn and LD.jrn files from the registers’ \rdata directory during idle timein the day. If the server is busy performing a consolidation request, or exit terminal request,the trickle will pause. Otherwise, the trickle process is continuous. Data from the LD.txn file(also known as the TLOG) is received from the POS and written to the server’s sdatadirectory (see below for naming convention). A separate process (that is, independent of thetrickle process) is responsible for reading and posting this data from the txn file to the SQLdatabase.

TLOG RenamingAs the TLOG data reaches the server, it is written to data files in the \sdata directory usingthe following convention:

LD.txn becomes SSSSTT00.txn

LD.jrn becomes SSSSTT00.jrn

where:

SSSS = Store number

TT = Terminal number

00 = The current day’s file for that terminal (00 always means today)

Totals Files and ReportsAt the end of a transaction at the POS, after the information has been posted to the TLOG,Totals files are updated in the \rdata directory of every register.

There are several different Totals files built from information in the TLOG, with each file namebeginning with rd, which stands for Register – Daily. The format of each of the Totals files isbinary.

If you request a Store Sales report from Store Manager, the Store Manager requests theserver to initiate a consolidation request. A consolidation request triggers the server torequest and consolidate the appropriate rd.* file from each online POS device. Thisconsolidated file is then posted to SQL, which the Store Manager uses for the report.


If you request a Store Sales Report for a POS terminal, the appropriate rd.* file is pulledfrom each online POS terminal and consolidated to an sc.* data file (sc stands for StoreConsolidation). The process follows a pull, consolidate, pull, consolidate pattern until the datafrom all of the POS terminals has been processed.

Terminal CloseThe following details the Terminal Close process:

Any outstanding trickling is completed.

All rd.* files are copied from the register’s \rdata directory and consolidated tosd.* files on the server’s \sdata directory.

The server then increments the *00.txn and the *00.jrn, so that the ‘00’ changesto show the close number specified in that terminal’s state.reg file.

The server then moves the incremented txn file to the \upload\keep0 directory.

By default, the jrn file is copied to upload\keep0 only if the parametercontrolling the polling of the journal files is set in the Configurator.

The server then zeroes out and re-initializes the terminal’s LD.txn and LD.jrn filesso that they are set for use again.

The terminal’s rp.* files (from the previous day’s totals) are replaced by the rd.*files still on the register.

The rd.* files on the terminal are re-initialized.

The terminal sends a Close terminal state message to the server, signs off thecashier, and displays Closed on the POS screen.

End of Day (EOD)The End of Day process can be run from either a POS terminal or the Store Manager. TheEOD process is as follows:

The server closes all unclosed terminals and checks for any duplicate Close Storerequests from other machines.

The server prepares summary files for polling by depositing them into the \uploaddirectory.

The server copies its own TLOG into \keep0.

The server posts the sd.* to the Store Manager databases and renames sd.* tosp.* (that is, from Store – Daily to Store – Previous), and then zeros out the sd.*.

The server copies all files from \keep0 to \upload and increments \keep0 to\keep1, and so forth, up to the limit you specify (max 99). The server deletes thelimit directory, then works its way down the chain (that is, it deletes \keep99, thenrenames \keep98 to \keep99, and so forth).

The server creates a new \keep0 directory for the next night’s files.

The store’s State, Business Date, Sequence Number, Audit Totals, and so on arezeroed out, and the information is posted to the event.log file in the \xpsdirectory.

The server clears out a terminal’s states, including a terminal’s open next day state.


51

An endofday.trg file is created in the \upload directory to trigger the Head Officepolling procedure.

The server executes the EOD user script file (this is the same process which takes place inthe Properties tab page of the Xpress Server user interface).

6.9 About SAP POS User Administration andAuthenticationSAP TGM does not rely on a central user management system for user management andauthentication, since SAP TGM users are only valid within the SAP TGM applications. This,however, does not minimize the level of security the component provides.

Transactionware General Merchandise 10.1 - SAP Help Portal

Documents

Transcript of Transactionware General Merchandise 10.1 - SAP Help Portal