Integration Guide

Table Of Contents

Configuration of the PSS System

______________________________________________________________________________

WaveWorks PSS, Integration Guide, 1.10 Page 56

Name – Subname

SHOPPING TRIP – TRANSACTION TYPE

SPECIAL BARCODE – CUSTOMERENDOFTRIP

SVCTERMINAl – Card Prefix

SVCTERMINAL – CustomStatusString

SVCTERMINAL – UsePrinters

SVCTERMINAL – UseQuickOrder

TRANSTICKET – DefaultDir

TRANSTICKET –DefaultPrinter

TRANSTICKET – PrinterColumnWidth

TRANSTICKET - Ticket Cut Type

UMS – BadScanFactor

UMS – BaseFactor

UMS – ChargingFactor

UMS – GoodScanFactor

UMS – LaserOnFactor

UMS – MaxBatteryLevel

UMS – MinBatteryLevel

UMS – PopupTimeout

UMS – QueryTimeout

UMS – RadioXmtFactor

5.2 Perform Initial Loading of Customer and Item Data

Both the IBM 4690 POS and the FileBased POS interfaces require the creation of flat ASCII

files of information for PSS to process. The formats and default filenames for the Item and

Customer files are documented in Appendix D of this document. Ultimately the POS should

create both of these file types for PSS to process. An Example Customer file and Item file are

provided in the PSS\PosTools directory for reference. See the readme.txt file in the directory for

more information on the files provided in that directory.

After other configuration steps have been completed and the PSS System has been started, a set

of test Customers and test items can be loaded into the system by placing the example Customer

and Item files into the configured Transfer directory(C:\Pss\Transfer). The PssFileMonitor

service will detect them and trigger the WaveWorks transaction to process them and load the

information into the PSS database.