777_BB_ConfigGuide_EN_US.doc

7/28/2019 777_BB_ConfigGuide_EN_US.doc

http://slidepdf.com/reader/full/777bbconfigguideenusdoc 1/67

EHP3 for SAP ERP 6.0

September 2008

English

777: SAP POSConfiguration

SAP AGDietmar-Hopp-Allee1669190 Walldorf Germany

Building Block Configuration Guide



SAP Best Practices 777: SAP POS Configuration: Configuration Guide

Copyright

© Copyright 2008 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the expresspermission of SAP AG. The information contained herein may be changed without prior notice.

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

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks 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, System i, System i5, System p, System p5, System x, System z, System z9,z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+,OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of

Adobe Systems Incorporated in the 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 the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide WebConsortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented andimplemented by Netscape.

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registeredtrademarks of SAP AG in Germany and in several other countries all over the world. All other product andservice names mentioned are the trademarks of their respective companies. Data contained in this documentserves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliatedcompanies ("SAP Group") for informational purposes only, without representation or warranty of any kind, andSAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAPGroup products and services are those that are set forth in the express warranty statements accompanyingsuch products and services, if any. Nothing herein should be construed as constituting an additional warranty.

© SAP AG Page 2 of 67

Key:

<XXX> à Variable entries

'XXX' à Fixed entries

[XXX] à Pushbutton




Icons

Icon Meaning

Caution

Example

Note or Tip

Recommendation

Syntax

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include fieldnames, screen titles, pushbuttons as well as menu names, paths andoptions.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.EXAMPLE TEXT Names of elements in the system. These include report names,

program names, transaction codes, table names, and individual keywords of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths,messages, source code, names of variables and parameters as well asnames of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or theENTER key.

Example text Exact user entry. These are words or characters that you enter in the

system exactly as they appear in the documentation. <Example text> Variable user entry. Pointed brackets indicate that you replace these

words and characters with appropriate entries.





Contents1 Purpose............................................................................................................................................... 6

2 Preparation.......................................................................................................................................... 6

2.1 Logon to SAP POS....................................................................................................................... 6

2.1.1 Store Server........................................................................................................................... 6

2.1.2 POS Terminal......................................................................................................................... 7

2.2 License for the Xpress Server.......................................................................................................7

2.2.1 System Tag............................................................................................................................ 7

2.2.2 Store Number ........................................................................................................................ 7

2.2.3 Next Steps.............................................................................................................................. 9

3 Configuration..................................................................................................................................... 11

3.1 Copying of the parameter (PARM) files from DVD.....................................................................11

3.2 Configuration of EODPROC.BAT...............................................................................................12

3.2.1 SAP POS Utilities used in the batch file...............................................................................14

3.3 Store Configurator.......................................................................................................................15

3.3.1 First Time running up the Configurator................................................................................16

3.3.2 Copying SAP Best Practices Configurator Database...........................................................17

3.3.3 Setting up the Configurator for first use...............................................................................19

3.3.4 Converting Parms for the first time use................................................................................22

3.3.5 Parameter apply check to the POS......................................................................................25

3.3.6 Adding a New Cashier from the Configurator.......................................................................25

3.4 SAP Transnet Configuration.......................................................................................................29

3.4.1 Transnet Client .................................................................................................................... 29

3.4.2 Transnet Server ...................................................................................................................31

3.4.3 POS.INI................................................................................................................................ 32

4 First Time POS Config...................................................................................................................... 32

4.1 Terminal Define.......................................................................................................................... 32

4.1.1 Running Terminal Define for the First Time.........................................................................33

4.1.2 Trouble Shooting Terminal Define.......................................................................................34

4.2 Running Terminal Define at a Later Time..................................................................................35

5 SAP POS Self Configuration.............................................................................................................35

5.1.1 Summary of changes in POS.INI.........................................................................................35

5.1.2 Configurator Settings............................................................................................................35

5.1.3 Making Configurator Changes..............................................................................................37

5.1.4 Tender Changes................................................................................................................... 39

5.1.5 Returns Modifications...........................................................................................................41

5.1.6 Non Merchandise Settings....................................................................................................42

5.1.7 POS Browser........................................................................................................................485.1.8 Data Capture .......................................................................................................................51





5.1.9 Loyalty Program................................................................................................................... 53

5.1.10 Barcode Printing.................................................................................................................54

5.1.11 Terminal Tab......................................................................................................................56

5.1.12 Register Parameters...........................................................................................................66





777 SAP POS: Configuration Guide

1 PurposeThis configuration guide provides the information you need to set up configuration of SAP POS. Thisincludes the following tasks:

• Copying of the parameter (PARM) files from DVD

• Configuration of EODPROC.BAT

• Store Configurator

• SAP Transnet Configuration

• SAP POS Configuration

2 PreparationBefore you start you must ensure that all databases and SAP POS programs, as well as SAPTransnet are installed.

SAP POS APPLICATION SAP POS DATABASES

Store Configurator POSCFGW Database

Store Manager BACKOFF Database

Electronic Journal JOURNAL Database

Xpress Server Database Tools

POS Xpress

2.1 Logon to SAP POSLogon information for SAP POS varies. In this store business process, the following logon informationwill be used:

User ID Password Authority Level Comment

1111 111111a 1 Level for Cashiers

2222 222222a 2 Level for Supervisors,Managers andother authorizedstore personneldepending on their function rights

3333 333333a 3

4444 444444a 4

5555 555555a 5 – highest

2.1.1 Store Server

1. From Store Server, launch Store Manager

Windows Start à All Programsà SAP Retail Systems à StoreManager





OR

Server Desktop

Double-click shortcut

2. From the Sign On prompt, enter user id and password

2.1.2 POS Terminal

1. From POS Terminal, launch POS Xpress Run POS Xpress if it is not already run.

Windows Start à All Programsà SAP Retail Systems à Point of Sale

OR

POS Desktop


2. In “Sign On” prompt, enter a valid Cashier Number

3. In “Enter Password” prompt, enter the corresponding password

2.2 License for the Xpress Server You also need a license file from SAP. To acquire the license to gather this information for eachXpress Server:

• Number of POS Terminals

• The System Tag

• Store number (The default store number is #1.)

2.2.1 System Tag

While the number of Terminals is self explanatory System Tag is not. The system tag is acquiredusing this procedure:

Open “C:\Program Files\SAP\Retail Systems\Xpress Server\XPS.LOG”

Search for the following text “SYSTEM TAG”.

On the next line you will find this string “THE 'SYSTEM TAG' FOR YOUR SERVER IS 1234567890”

The 10 digit number (in this example 1234567890) is your system tag.

2.2.2 Store Number

You can set the store number in the Xpress Server. It is important that the store number is Matches

the Store Number in your request. If there is any doubt as to what your store Number is Follow thisprocedure:





The last step is to stop and start your server. Do this by clicking the Xpress Server icon

Then click stop.

Wait for the server to stop

Then restart the server by clicking on the start button.

1. From Store Server, launch Xpress Server

Windows Start à All Programsà SAP Retail Systems à XpressServer

OR

Desktop


2. This allows you to see what the server is doing at the time in real time. Anything in this windowalso gets logged to C:\Program Files\SAP\Retail Systems\Xpress Server\XPS.LOG. This step isnot necessary to complete the task but it allows you to watch the process in action.

3. The Xpress Server window displays on screen. You should see the following:





4. Click on the Properties tab and the store number is displayed.

2.2.3 Next Steps

Once you have gathered this information send it to your SAP Representative. It will be processed for you. Soon you will receive an Email that contains an attachment. This attachment is your license.Follow this Procedure:

1. Rename the attached file to “license.lic”

2. Copy the license.lic file to the Xpress Server parm folder “c:\program files\SAP\ RetailSystems\Xpress Server\Parm”



OR

Desktop








6. Click on the Stop Server button.

7. When you see the Running indicator becomes stopped like in this image click Start Again

8. You May click close if you wish.





The Xpress Server Window is just a monitor program. The actual Server is a Service (under windows platforms that run services of course). Closing this program does not close the actual server.

3 Configuration

3.1 Copying of the parameter (PARM) files from DVD

Use

The purpose of this procedure is to copy the parameter files from the SAP POS Best Practices DVDto your System.

Procedure

Parameter files (also known as PARM files) define the rules and functionality that your store will

follow.



OR

Desktop








12. From the Best Practices Documentation DVD copy \Misc\Retail\US\SAP POSFiles\Store\parm\*.* into the store server’s C:\Program Files\SAP\Retail Systems\XpressServer\Parm directory

13. After approximately 30 seconds you should see a flurry of activity on the XPS screen. It will looksomething like this:

14. At this point you know that the parm files have applied at the server. Soon the POS systems willtake the parm files as well.

3.2 Configuration of EODPROC.BAT

Use

After the store is closed, a script file is executed to perform whatever is required at end of day for whatever reason. This script file is called “eodproc.bat” and resides in “\Program Files\SAP\RetailSystems\Xpress Server\”. This file is typically used for:

• Backup

• End of day file preparation for Headquarters

• Processing files from headquarters

• Whatever else is deemed necessary that needs to be executed after the store has closed.

The eodproc.bat is provided as an example. Its sole purpose is to prepare files for PI to process. For those of you who write batch files it is also a quick introduction to some of the SAP Retail utilities.

Procedure

These are the environment variable set by the batch file. You may need to change these variables tosuit your install.

1. Copy from the Best Practices Documentation DVD \Misc\Retail\US\SAP POSFiles\Store\EODPROC.BAT to C:\Program Files\SAP\Retail Systems\Xpress Server\

2. Open notepad and edit “\Program Files\SAP\Retail Systems\Xpress Server\eodproc.bat ” andchange the following lines (bolded and Italicized):

NOTE: Please check if the following directories are existing. If not please create them









This is the directory for the SAP PI machine. It can be a URL as well. This directory will be readfrom SAP PI and pulls the data. Please make sure that this directory is accessible via FTP(please look at the “Retail_Quick_Guide_EN_US_V1603.doc”).

set XI_DIR=C:\Program Files\SAP\Retail Systems\Xpress Server\SAPInbound

This is the directory of Xpress Server.

set XPS_DIR=C:\Program Files\SAP\Retail Systems\Xpress Server

SAP Temporary files to SAP PI and the drive letter.

set SAP_TMP_DRV=c:

set SAP_TMP=c:\SAP_UPLOAD

3.2.1 SAP POS Utilities used in the batch fileThere are two utilities used in this batch file, CVTLOG.EXE and BESETENV.BAT. All SAP POSutilities are found in C:\Program Files\SAP\Retail Systems\Utilities. There are many utilities here andmany are configuration specific. Some of those will be discussed here.

All utilities command line options may be displayed in a command prompt by executing “utilname.exe/?” So for example:

BESETENV.EXE /? Results in:

BESETENV V10.0.0Build3732008-2-8 Patch Level 000- Create POS environment batch file

- 3.2.1(MAY09/96)(C) Copyright 2006 SAP AG. All rights reserved.Usage: besetenv batchFileWhere: batchFile is batch file name to createReturns Errorlevels: 0 if successful; 1 if program failedNotes:

(1) MUST be run from POS/BackOffice program directory. Reads state filessdata/state.srv, sdata/srveod.dat and rdata/state.reg to create specifiedbatch file, which will look something like this:

rem Batch autogenerated by besetenvSET STORENUM=3601 <---

SET TERMNUM=02 <--- Terminal Number if POS, 0 if BackOfficeSET EODNUM=65 <--- Last End Of Day sequence number SET JDATE=333 <--- Julian Date

SET YYYY=1996 <--- Year(from Business Date)SET MM=12 <--- Month(from Business DateSET DD=25 <--- Day(from Business Date

(2) Use besetenv in an end of day batch such as the following:

besetenv unameit.batif errorlevel 1 call errbat.batrem Call this to set environment variables

call unameit.batrem Now use the environment variables as requiredpkzip upload\%STORENUM%%EODNUM% upload\%STORENUM%%EODNUM%.*





From this you’ll see usage and the output in a batch file that can be executed. It must be executedfrom the XPRESS Server directory and allows you to have many store specific parameters for End of day or any other store base batch file.

BE originally stood for Batch Enhance. They were all made to enhance batch files to get many jobsdone. Here is the list and a brief outline of their function:

BEASK.EXE Asks user for input and returns an errorlevel based on the response. Alsoused to pause in a batch file as it the sample eodproc.bat

BEDEL.EXE Enhanced file deletion

BEDISK.EXE Checks to see there is space on the disk.

BEMENU.EXE Allows creation of a simple dos based menu system

BEPROMPT.EXE Prompts user for text and stores it to a file

BESETENV.EXE Discussed above.

BEWHEN.EXE Sets an errorlevel based on time parameters. Similar to Windows ATcommand

“CV” Utilities convert data from SAP POS from binary to a usable ASCII format. CVTLOG for example converts the POS’s Transaction log (also called the “TLOG”) to an ascii format described inSAP POS’s Technical Reference Guide. Again you may enter cvtlog -? And look at the commandline. Please note there are actually two help pages for cvtlog “-h2” brings up the second page. Hereis the list of CVUtilities:

cvcds.exe Converts department by cashier totals to ASCII

cvDcrypt.exe Decrypts the journal file for access to encrypted data. NOTE By default thisutility does not decrypt the data. A live application must be requested by theuser.

cvdit.exe Converts discount totals files to ASCII

CVParm.exe Used by configurator prepares ASCII from the configurator database for theInstore Applications

cvsmv.exe Converts the SKU Movement file from the POS to ASCII

cvspd.exe Convert the Salesperson Productivity file from the POS to ASCII

cvtlog.exe Converts the POS Transaction file from the POS to ASCII

cvtms.exe Converts the Timed Sales file from POS to ASCII

cvtotals.exe Converts the Totals file from POS to ASCII

cvTxn2Xml.exe Used internally

There are many other utilities. Some are for very specific environments.

3.3 Store Configurator The configurator is the main configuration tool for SAP POS. The majority of the transaction set isconfigured here. For the most part this application is kept at the company headquarters and moststore personnel do not even know it exists.

The Configurator consists of a UI and a Database. The database contains your configuration and is tobe backed up as it can represent many man hours of work and not to mention the stability of your stores.

In the Configurator you can make changes to a store and it will prepare files for the in store softwaresuite to use. These files will tell SAP POS how to behave.





There are sections of the configurator that are considered to be for demonstration and testingpurposes only. For example the PLU section of the configurator is not in any way meant to managePLU’s for a live store. It is much too complicated a task and beyond the scope of the Configurator.

3.3.1 First Time running up the Configurator

The First time you run up the configurator you may or may not have to run this short once onlyprocedure. If this does not apply do not be concerned and skip this section.

1. Launch Store Configurator

Windows Start à All Programsà SAP Retail Systems à StoreConfigurator

OR

Desktop


2. The application will display this window. Switch to the Network Tab

3. Select the TCP/IP Check box

4. Click OK





5. The Configurator login prompt should display.

3.3.2 Copying SAP Best Practices Configurator Database

In this section, we will place the SAP Best Practices Data Base in place. After this exercise you willunderstand where the database resides and how to back it up should you require to.

Procedure



OR

Desktop


2. You will be presented with the configurator login screen. We need to create a place in theconfigurator application for the new BP database. Enter “poi” into the password and click on“Create DB”

3. The Configurator will display this prompt. Click on YES.

4. We must name the database and give it a description. In the database name field enter “sapbpcfg”.

5. Under Description enter “SAP Best Practices Database”

6. Click OK





7. The create database dialog will exit and you will be back at the sign on. Click Cancel to exit theconfigurator. This will exit the configurator.

8. Copy from the DVD \Misc\Retail\US\SAP POS Files\Store \SAPBPCFG.db into C:\ProgramFiles\SAP\Retail Systems\Store Configurator\sapbpcfg.db. This will prompt for overwrite fromwindows. Click OK.

9. To test if the procedure was successful, start the configurator again.

10. In the Sign on Screen, select the “SAPBPCFG” database from the database pull down menu.

11. Click on “OK”

12. Select English and click ok

13. Select the Terminal Tab

14. Select the Register Parameters icon





15. Click on open on the Register Parameters Search Screen

16. Switch to the General Tab

17. Look at the “Param set name”. It should read “SAP Best Practices Parameter Set”

18. Click Close twice

19. Exit Store Configurator by clicking the in the top-right corner of the main menu

20. Click on “ YES” when prompted to exit.

3.3.3 Setting up the Configurator for first use

This section of this document assumes that the configurator is on the same system as the rest of the

SAP POS suite. In reality it almost never is. This section will show you how to set the Configurator’soutput files to a directory. These are the Parm files that define the POS’s rules of operation.





There is nothing stopping you from mapping a drive and setting the path this way if you wish.

Procedure



OR

Desktop


2. Login by selecting the SAPBPCFG in the database pull down menu and entering “poi” aspassword then click “OK”

3. From the language selection, select English then click OK

4. From the Configurator’s main screen select the “System Setup” menu and the “System Setup”menu item





5. This screen should display:

6. Examine the “Parm Directory” entry. If it is set to the location of your express server parm

directory then do nothing. If it is not then point it to your Express Server’s Parm Directory. Thedefault install path for Xpress Server is “C:\PROGRA~1\SAP\RETAIL~1\Xpress~1\parm”





It is strongly suggested that you use the windows short directory paths and do not enter the final“\” in the path. For example c:\parm\ will not work c:\parm will.

If you are configuring for different labs you can set the path to “c:\parm” for example. Then

manually copy the files to the parm directory of choice. If you do this be very careful to manage thedirectory. Copy then delete the contents of directory rather than just copying them.

7. Click on Save and Close.

8. Exit Store Configurator by clicking the in the top-right corner of the main menu

9. Click on “ YES” when prompted to exit

3.3.4 Converting Parms for the first time use

In this section we will convert various configuration files from the configurator to the SAP POS.

Procedure


Windows Start à

All Programsà

SAP Retail Systemsà

StoreConfigurator

OR

Desktop








4. On the configurator Main Screen select the Icon, which is shown on the following image toconvert parameter files (also known as “PARM” files).

5. This should result in the following screen:

The “Send Configurator Parameters to” field is taken from the setting we made in theprevious section. If you want to temporarily override this you can do so here.

6. Check “Send Entire File”





7. Click the “Select All” button. Many of the boxes will be checked and the tags will go red.

8. Select the PLU tab and click on PLU Config, PLU CrossRef File,PLU Link Item File,PLU Sec.Desc. File, PLU QTY/Lvl File, PLU File and Promotion File. All fields in this screen must beselected and red.

9. Click on the Keyboards tab and select the 101 Enhanced checkbox

10. Select the Convert button at the bottom of the window

11. The configurator will ask “Do you want to convert Entire files?” Select “YES”

12. The Configurator will go through the conversion process and will come to a prompt similar to thisone. Click OK

13. The configurator will display this prompt. Click OK

14. Files are now successfully sent to the POS





Note: Send Entire File Check Box.

Send entire file has a subtle meaning that is not entirely obvious. There are two configuration filetypes. There is an all or nothing file. This file sends the entire file and replaces the existing

configuration. An example of this file is the Tender file. The Tender file contains all of the rules thatare associated with Cash, Credit and whatever else you accept at the POS Terminal. It is a small fileand does not change often. Then there is a transaction type file these files change often and can bequite large. An example of this file would be the PLU file. There can be many thousands of recordsand you probably do not want this file handled in an all or nothing method. You would not want tosend 100,000 plu records to 100 stores to change the price of a 10 of items. A “Transaction” type fileallows you to send 10 records to change or add 10 items you want to change leaving the restunchanged

If you click send entire file you will notice that some of the names in the export window of theconfigurator change. For example Discount Update becomes “Discount File”. These configurationswill act as if they are an “all or nothing” type of file. They will replace the current table in favor of thisnew one.

3.3.5 Parameter apply check to the POS

To see if files were applied correctly to the POS check the XPS log file with the following process:

1. Open this file “C:\Program Files\SAP\Retail Systems\Xpress Server\xps.log”. It is text so you canuse any text editor.

2. Look for the following text “Applying download file(s)” Check to see that it is from the approximatedate and time for your entry. The next several hundred lines of this log will show that the InstoreServer processed each file here is a small sample:

6/18/2008 5:23:19 PM Copy PLU txn file to directory6/18/2008 5:23:19 PM C:\PROGRA~1\SAP\RETAIL~1\XPRESS~1\parm\txncmp.tcl

6/18/2008 5:23:19 PM Copy of 1 files complete6/18/2008 5:23:19 PM ASCII file snapshot:6/18/2008 5:23:19 PM TENDER.ASC6/18/2008 5:23:19 PM NONMERCH.ASC6/18/2008 5:23:19 PM SQL import of TENDER.ASC: 21 rows applied, 0 rows did not apply.6/18/2008 5:23:19 PM SQL import of NONMERCH.ASC: 25 rows applied, 0 rows did not apply.

3.3.6 Adding a New Cashier from the Configurator

This section will cover adding a new cashier to the POS via configurator. To do this you mustunderstand a little about authority levels in the SAP POS Environment. Each employee has anauthority level associated. Authority levels range from 1 to 5. Level one being the most restricted.What the actual levels represent is up to you. For example you could define levels this way:

1. Cashiers2. Supervisors3. Store Manager 4. Regional Manager 5. Head Office Personnel

Through the configurator if a function is defined as authority level 3. This means an employee with anauthority level 3 or greater can run this function. Using the example above a Store Manager, RegionalManager or Head Office Personnel may also execute this function.

Procedure1. Launch Store Configurator






OR

Desktop




4. On the Configurator Main Screen Click on the Administration tab

5. Then the Employee icon





6. The Employee menu will appear click on the Employee Icon

7. This screen will display next:

8. Click on “New” and enter the information as seen here. For password enter “666666a”. The“Alternative Languages” mush be clicked and un-clicked.





9. Click on “Save” and close Three times.

10. On the configurator Main Screen select the Icon, which is shown on the following image toconvert parameter files (also known as “PARM” files).

11. This should result in the following screen:





12. Check “Send Entire File” checkbox. “Employee Update” will change to Employee File. Asdiscussed earlier your cashier file will be replaced from the one on this configuration.

13. Select the Convert button at the bottom of the window

14. The configurator will ask “Do you want to convert Entire files?” Select “YES”

15. The configurator will display this prompt. Click OK

16. The Employee file is now successfully sent to the SAP POS Suite. You may now log in with thiscashier.

3.4 SAP Transnet ConfigurationThe following must be configured in Transnet for real-time TLOG Trickle and for Customer Order Management

Transnet Client \Program Files\SAP\Transnet\config\Transnet.xml \Programfiles\SAP\Transnet\jtmt\config\client.conf

Transnet Server \Program Files\SAP\Transnet\config\Transnet.xml

3.4.1 Transnet Client

Transnet Client sits in the store. It is a piece of software that communicates with Transnet server atheadquarters. It is capable of file transfer and message transfer. Transnet Client can also beconfigured to connect directly with a credit service for credit processing. In this configuration it sendstransactional data (or transaction logs) to the PI.





3.4.1.1 Client Transnet.xmlCopy the predefined file from the Best Practices DVD \Misc\Retail\US\SAP POS Files\Store \TransnetClient\Transnet.xml to c:\program files\SAP\Transnet\Config

The Transnet Client’s transnet.xml file must be configured in POS to contain only the relevantinformation needed for TLOG trickle and Customer Order Management. You may need to modifyseveral setting to suit your environment:

For Customer Order Management integration, please change the “XIHttpAdapter” connection settingaccording to your environment:

xiadapter="http://<PISERVERHOSTNAME>:<PIWASPORT>/sap/xi/adapter_plain”

sapUser="<username>"

sapPassword="<password>”

<?xml version="1.0" encoding="UTF-16"?><Transnet SystemID="10_1_1">

<Logging>logging.properties</Logging>

<Service class="com.triversity.transnet.core.tms.connection.TNConnectionManager" description="Transnet ConnectionManager" forcedShutdownWaitTime="5000" name="ConnectionManager">

<ActivationInterval unit="seconds" value="10"></ActivationInterval><Connection Version="1" acceptTimeout="1000" class="com.triversity.transnet.core.tms.ip.TNServerSocket"handlerClass="com.triversity.transnet.core.tms.ip.TNXMLSocketServer" host="localhost"

name="ClientSocketConnection" port="10000"></Connection>

<Connection name="TPSClient" autoReconnect="true"class="com.triversity.transnet.core.tms.tps.TPSClientHandler" timeout="25" useSSL="false"></Connection>

<Connection name="XIHttpAdapter"class="com.triversity.transnet.core.tms.connection.TNMessageConsumerConnection">

<adapter class="com.triversity.transnet.adapter.xihttp.XIHttpAdapter"xiadapter="http://<PISERVER.sap.corp>:<PORT>/sap/xi/adapter_plain"senderNamespace="http://sap.com/xi/StoreConnectivity"senderService="COMRequestService"

senderInterface="SalesDocumentQueryResponse_Out"senderParty=""senderAgency=""senderScheme=""QOS="BE"sapClient="001"sapUser="bestprac"sapPassword="welcome"sapLanguage="EN"timeout="25 seconds">

</adapter></Connection>

</Service><Service class="com.triversity.transnet.core.tms.message.TNMessageManager" description="Transnet Message

Manager" forcedShutdownWaitTime="5000" name="MessageManager"><ActivationInterval unit="seconds" value="10"></ActivationInterval>

<MessageDescriptor name="TLogMessage" root="Transaction"/><Route name="TlogRoute" connectionName="TPSClient"/><RoutingRule message="TLogMessage">

<Route name="TLogMessageRoute" timeoutSeconds="30"></Route></RoutingRule><Route connectionName="TPSClient" name="TLogMessageRoute"></Route>

<MessageDescriptor name="XIMessage" root="POSLog"/><Route name="XIRoute" connectionName="XIHttpAdapter"/><RoutingRule message="XIMessage">

<Route name="XIRoute" timeoutSeconds="30"></Route></RoutingRule>

<RoutingRule message="DefaultFinancialMessage"><Route name="DefaultFinancialMessageRoute" timeoutSeconds="30"></Route>

</RoutingRule></Service>

<ThreadPool CleaningIntervalSeconds="60" Debug="false" MaximumThreads="300" MinimumThreads="5"Name="TransnetThreadPool"></ThreadPool>

<WorkingDirectory>C:\Program Files\SAP\Transnet</WorkingDirectory>





</Transnet>

3.4.1.2 Client.conf

The Server Address and Port Number of the Transnet Server have to be added in the ClientConfiguration file (client.conf). You will need to modify “SERVERADDR=<TNServerIP>” to suit your environment.

Copy the predefined file from the Best Practices DVD \Misc\Retail\US\SAP POS Files\Store\TransnetClient\Client.conf to c:\program files\SAP\Transnet\jtmt\conf\ and change id accordingly.

## NTM Client Configuration file## See NTM Client Manual for valid values

APISSLTYPE=0SERVERSSLTYPE=1

# Added by the Transnet Installer SERVERPORT=8400

SERVERADDR=<TNServerIP>#GUILOGS=trueEVENTLOGLEVEL=3DEBUGLOG=1

3.4.2 Transnet Server

3.4.2.1 Server Transnet.xmlThe Transnet Server’s transnet.xml file needs to contain only the relevant information needed for TLOG trickle. Copy this file from the Best Practices DVD \Misc\Retail\US\SAP POSFiles\Headoffice\Transnet_Server\Transnet.xml to C:\Program Files\SAP\Transnet\Config\

<?xml version="1.0" encoding="UTF-16"?><Transnet SystemID="10_1_1">

<Database Driver="com.microsoft.sqlserver.jdbc.SQLServerDriver"Url="jdbc:sqlserver://localhost:1433;databaseName=transnet" type="rdbms">

<ConnectionPool CleaningIntervalSeconds="60" ConnectionLifeSeconds="1800" Debug="false"MaximumConnections="10" MaximumUseCount="25" MinimumConnections="1" Name="TransnetJDBCPool">

</ConnectionPool></Database>

<Logging>logging.properties</Logging>

<Service class="com.triversity.transnet.core.tms.connection.TNConnectionManager" description="Transnet ConnectionManager" forcedShutdownWaitTime="5000" name="ConnectionManager">

<ActivationInterval unit="seconds" value="10"></ActivationInterval>

<Connection TPSDebugLogging="false" TPSPipeName="Transnet" TransactionBufferSize="300000"class="com.triversity.transnet.core.tms.tps.TPSServerHandler" name="TPSServer">

</Connection>

<Connection name="TlogAdapter"class="com.triversity.transnet.core.tms.connection.TNMessageConsumerConnection">

<adapter class="com.triversity.transnet.xtension.tloguploader.TLogUploader"mode="separateFilePerTxn" encoding="UTF-8"

rootPath="c:/tlogupload" dirSpec="" fileSpec="%chain%-%store%-%posid%-%trxno%.txn"fileCutTimeMinutes="30"/>

</Connection></Service>

<Service class="com.triversity.transnet.core.tms.message.TNMessageManager" description="Transnet MessageManager" forcedShutdownWaitTime="5000" name="MessageManager">

<ActivationInterval unit="seconds" value="10"></ActivationInterval><MessageDescriptor name="DefaultFinancialMessage" root="FinancialMessage"></MessageDescriptor>

<Route connectionName="APM connection name goes here" name="DefaultFinancialMessageRoute">





</Route>

<MessageDescriptor name="TLogMessage" root="Transaction"/><RoutingRule message="TLogMessage">

<Route name="TLogMessageRoute" timeoutSeconds="30"/></RoutingRule><Route connectionName="TlogAdapter" name="TLogMessageRoute"/>

<RoutingRule message="DefaultFinancialMessage"><Route name="DefaultFinancialMessageRoute" timeoutSeconds="30"></Route>

</RoutingRule></Service>

<ThreadPool CleaningIntervalSeconds="60" Debug="false" MaximumThreads="300" MinimumThreads="5"Name="TransnetThreadPool">

</ThreadPool><WorkingDirectory>C:\Program Files\SAP\Transnet</WorkingDirectory>

</Transnet>

Ensure that the directory specified in the rootPath for connection “TLogAdapter” exists.

3.4.3 POS.INI

The POS.ini is another configuration point other than the configurator. As its name implies it is text.Comments are headed with the “#” symbol and are documented this way throughout. The file islocated in C:\Program Files\SAP\Retail Systems\Xpress Server\Parm.

The POS.ini is read in a top down process. Meaning it reads line 1 then line 2 and so forth. So if you have the same settings in more than one place the LAST one takes precedence.

It is suggested POS.INI is copied from the best practices DVD using the following process:

1. from the Best Practices DVD copy DVD \Misc\Retail\US\SAP POS Files\Store\POS.INI toC:\Program Files\SAP\Retail Systems\Xpress Server\Parm

2. create a newparm.trg by copying any small file to C:\Program Files\SAP\Retail Systems\XpressServer\Parm\newparm.trg

NEWPARM.TRG is just a trigger file the contents of the file do not matter. Some prefer to createa small batch file in the path (for example C:\Program Files\SAP\Retail Systems\Utilities) calledtrg.bat. inside trg.bat simply paste this text:

echo>>"C:\Program Files\SAP\Retail Systems\Xpress Server\Parm\newparm.trg"

Then anytime you need a trigger file just execute this batch file.

4 First Time POS ConfigIn this section we will configure the POS.

4.1 Terminal DefineTerminal Define configures some of the main pos functionality and as well configures the location of

the instore servers. There are two possible reasons for running Terminal Define. One is the POS isrun for the first time and you need to configure it. The other is the configuration is either wrong or changed and you need to change it. The following Section Running Terminal Define for the First Time





will cover the first time config. This section will cover the changing of the configuration. It is onlynecessary to run this configuration once: Running Terminal Define at a Later Time.

4.1.1 Running Terminal Define for the First Time

Remember that if you make a mistake do not fear you can run this again at any time.

1. From POS Terminal, access POS Xpress


OR

POS Desktop


2. If you get any “File Version Errors” or “Missing Parm Files” throughout this process ignorethem and press any key

3. When the POS runs up for the first time it will prompt NEW POS VERSION PROCEEDY/N Press the Y Key

Although it is fairly rare in modern POS equipment some POS keyboards do not have alphakeys. This said the POS will accept “1” for YES and “0” for NO

4. Press the Y key for the Terminal Define Proceed Y/N

5. Set the Store number to 1 and press enter

6. Set the Terminal ID to 1 and press enter

7. Set the report Group to 1 and press enter

8. Set the Parm Group to 1 and press enter

9. Set the State Province to your local 2 char state or province. (New York for examplewould be “NY”)

10. Set Local PLU to No

11. Set Use Backup Server to No

12. Set Primary Server Name to the IP of your Express Server Box. If it is on the samemachine you can enter 127.0.0.1

Use the Decimal key on the keyboard proper (near the spacebar). The Numeric Keypad willnot work as the POS uses this key.

Server names can be IP’s or hostnames that can be resolved through your host file or DNS.For example if your Xpress Server is on the same machine you can specify “localhost” instead of “127.0.0.1”

13. Set Is Thin Server to no

14. If all is well then the POS will now exit to the Program Function Menu.







4. Follow the steps in the previous section

4.2 Running Terminal Define at a Later Time.Perhaps you configuration has changed or you want to examine more advanced features. It is

possible to run terminal define at a later time.

1. From POS Terminal, access POS Xpress


OR

POS Desktop


2. Sign On to the POS as outlined in Section Logon to SAP POS

3. After you have signed on enter 6 then press F8 or click on the button on thescreen,

4. At this point you may follow the instructions steps 1 through 12 in the Running TerminalDefine for the First Time or you may set whatever settings that are appropriate.

5 SAP POS Self ConfigurationThis section is for those who wish to walk through the configurator to make changes themselves. It isa valuable way to learn the fundamentals. It is not necessary to follow these procedures unless you

wish to learn more about configuration of the product.

5.1.1 Summary of changes in POS.INI

Here is a list of changes from the default pos.ini. You can edit the ini manually. If the entries do notalready exist you must create them.

FORCENUMLOCK=Y

CVTLOG_USECURRENCYCODEFLAG=N

CVTLOG_TXNNUMDIGITS=4

OMDOCUMENTBARCODEID=6

The OMDOCUMENTBARCODEID parameter is the barcode number which will be printed to acustomer order receipt.

5.1.2 Configurator Settings

Following the above processes gave you an insight into some of the basics of the configurator. It issuggested that you start the Xpress Server Window to watch the XPS.LOG in real time so that youmay monitor Parm file applies.

This process will create a copy of the default Database for you to work with.







OR

Desktop


2. You will be presented with the configurator login screen. We need to create a place in theconfigurator application for the new BP database. Enter “poi” into the password and click on“Create DB”

3. The Configurator will display this prompt. Click on YES.

4. We must name the database and give it a description. In the database name field enter “BPSELFCF”.

5. Under Description enter “BP Self Configuration”

6. Click OK





5.1.3 Making Configurator Changes

The next step is to log into the “BP Self Configuration” database and start Configuring.



OR

Desktop


2. Login by selecting the BPSELFCG in the database pull down menu and entering “poi” aspassword then click “OK”






4. You should now be at the Main Screen of the configurator. It should look like this:

You can always tell which database you are working on by looking here:

Before you do any work you would be well advised to look at this to make sure you know whichdatabase you are making changes to.





The Configurator is a complex product and gives you a tremendous ability to change manythings. With the ability comes the responsibility to work carefully and always test your work beforecommitting anything to a live environment. Always create a copy of a database for experimentation.Once experimentation is complete you can always delete it afterwards and you do not risk the original

database. As mentioned earlier the configurator database is precious to your business always have abackup off system. There is no way to go from PARM files back into a database.

5.1.4 Tender Changes

The Tender Table is where the tenders are defined. Tenders are the types of money, charge cardsand really whatever can be used to transact. The obvious tenders are cash, credit cards gift cards,giftcertificates. You can configure shiny rocks if that is what the store accepts. You can define up to 40tenders ID #1 through to 40. One hard and fast rule about tenders is that the country’s base cashtender must be Tender ID 1.

We need to change the base configuration to be US Cash. We need to modify only those tenders thatare US Tenders. There are some foreign currencies. Follow this procedure

1. From the Configurator Main screen Click on the “Tenders” icon

2. Then click on the Tender Setup Icon. You should see a list of tenders. Here is an itemized list of configured tenders:

Tender ID Tender Description

1 'CASH'

2 'CHECK'

3 'TRAV CHECK'

4 'VISA'

5 'MASTERCARD'

6 'AMEX'

7 'DISCOVER'

8 'CDN FUNDS'

9 'GIFT CERT TDR'

10 'RETAILER CHARGE'

11 'DUEBILL ISS.'

12 'STORE CREDIT ISSUE'

13 'STORE CREDIT REDEEM'

14 'Gift Card'

15 'EMPLOYEE CHARGE'

16 'RETAILER BUCKS'

17 'FOOD STAMPS'

18 'Debit Card'

19 'DebitCheck'

20 'EURO'

21 'FRANC'

You will notice that Tender ID’s 8, 20 and 21 are not in US currency. So for the all other Tenders

follow this process:

1. Click on Tender ID 1 then open





2. You will come to a screen like this:

3. Change the currency to “US Dollar”

4. Click the Left arrow highlighted on the previous illustration and change Tender ID 2.

5. Repeat this for every single Tender except for Tender ID’s 8, 20 and 21

6. Click on Save

7. Click on Close 3 times to get to the configurator Main Screen

5.1.4.1 Changing Check Tender

In the best practices system there is no check authorization actually being performed because thiswould require a third party service. We will disable credit authorization for checks. Follow thisprocedure:

1. From the Configurator Main screen Click on the “Tenders” icon

2. Then click on the Tender Setup Icon. You should see a list of tenders.

3. Select Tender ID 2 (Check) and click open.

4. Switch to the “Data Capture Bank” tab. You will get a screen like this one:





5. Remove the text from the Credit Service field so that it is blank.6. Click Save and close until you are at the main screen.

5.1.5 Returns Modifications

We need to modify returns from going out for returns Authorization. Returns Authorization goes out toa central Server to authorize the returns. This stops fraudulent returns activities. Since there is noServer configured we need to disable it. To do this follow this procedure:

1. From the Configurator Main Screen Click on the “Returns” Icon

2. You should see a list select ID 1 then open. The Description is “Return With Receipt”

3. Click on the Click on the Return Authorization Tab

4. You should be looking at this screen:

5. Set the refund service to “NONE”





6. Remove the checks from “Refund To Original Tender and Refund in Local Currency.

7. Also remove the “Retrieve Original Txn From Refund Service” flag.

8. Save and close two times

9. You should be back at the Main Screen

5.1.6 Non Merchandise Settings

Non Merchandise items are just that, chargeable items that are non merchandise. Services, GiftCards and Petty cash are handled through Non Merchandise. Basically any function that requires aTender to come in or out and is not in the PLU file can be handled through Non Merchandise.

Here we will create new Non Merchandise records, especially for the Customer Order ManagementIntegration scenario (only relevant if you are using that scenario):

1. From the Main Menu in the Configurator Select Non Merchandise icon.

2. At the Non Merchandise Search menu click New

3. You will see this screen. Purple Means a required entry

4. Enter the information as seen in the following 4 screens:















7. Now Non Merchandise33









5.1.7 POS Browser

Yes the POS has a built in browser. For the Customer Order Management Integration scenario weuse the POS Browser functionality to connect to the SAP Retail Store “Customer Order” screen.

To launch a browser within the POS simply execute the corresponding manager code. Meaning if you configure a browser ID 1 then you also need to create a manager code 751. You can definebrowsers so therefore you have a manager code range of 751-800. You will see this as part of thisexercise.

Follow this process:

1. Click on the “Pos Browser” icon on the main screen of the configurator.

2. In the Pos Browser Search Screen click on “New”. Enter the data as in the following image.The secure data field is left as is when you click new.





This URL may change in your environment. Choose the SAP Retail Store URL for the Customer Order Management Integration:

http://<WASSERVER>:<WASPORT>/sap/bc/gui/sap/its/wssa_entry?sap-client=020&sap-language=EN&~store_no=M004

3. Choose Sales Order Processing = Enabled

4. Click Save and close twice to get to the main menu.

Now we need to tie this to a Manager Code as discussed earlier we need to create a Manager code755. A manager code is a function that gets executed. For example regular Sale is Manage Code190. Within each Manager code there are the same set of parameters that you can set like printoptions and authority levels and such.

Follow this procedure:

5. Click the Manager POS Functions icon in the main Configurator Menu

6. Click new in the Manager Pos Functions Search Menu

7. Configure following the next three images









8. Click Save and Close twice to get back to the main Screen

5.1.8 Data Capture

Now we need to switch to the Data Capture tab in the configurator. Your screen should look like this:

We need to create a POLICY. A policy is a block of text that gets printed in various places. Anexample of a policy is the “I agree to pay …in accordance to my agreement with…” that you see onreceipts above the signature line when you pay by credit cards.

If you were to configure that credit agreement policy you would go to the tender’s print option andattach that policy to the credit tender’s print options, easy right?

To create a policy follow these steps:

1. Click on the Policy icon under the Data Capture Tab in the Configurator





2. Under Policy Search click on new

3. Configure the Policy according to the following 2 images:





4. Click on Save and Close twice

%LE1 is a variable that the POS replaces with the number of points earned.

5.1.9 Loyalty Program

As discussed before the policy is just a bock of text. Something needs to call it. So we now weneed to attach this policy to a Loyalty Program.


1. Click on the Loyalty Management icon under the Data Capture Tab in the Configurator

2. Then click on the Loyalty Programs icon as in the image below:





3. Select ID 1 or LOYALTY PROGRAM from the menu and modify according to this image:

5.1.10 Barcode Printing

Under the PLU tab you will f ind the barcode printing. This section defines barcodes to be printed by

the pos on the receipt primarily. These barcodes contain information that the POS can key off of tolaunch a transaction. For example the POS can print a barcode at the bottom of the sales receipt thatcontains transaction number store number etcetera. The pos can be configured to recognize thisbarcode and then launch a return transaction for example. Follow this procedure:

1. From the main Configurator Screen select the PLU tab and then the Barcode icon





2. Configure according to the image below.

The POS can identify a barcode based on the Prefix Suffix and Scan Data Type. This of courserequires a scanner that is properly configured to send this information to the POS. Scanner configuration can vary from scanner to scanner and as well by manufacturer.

In this case we will print a barcode that looks like this:

It is important to choose the barcode format that suits your needs for example does the formatsupport alphanumeric and will it handle the length that you require?

3. Click on Save and close twice to get to the main menu.





5.1.11 Terminal Tab

The Terminal tab is where a lot of the various configurations come together into the POS. We willmodify menus for the POS and change some rules of the POS and the keyboard functions as well.

5.1.11.1 Item Entry ControlItem Entry Control is a set of rules for identifying the strings of characters as they are scanned or keyed at the “Scan/Enter Item” prompt or, the “Enter Item” prompt if there is no scanner configured.

What it is in essence is a list of rules the POS uses to identify Barcodes (like the one configured inthe previous section). It works in a bottom up process. Starting with the highest ID and working up thelist until it gets a match or eventually performs a PLU lookup and treats the input as a PLU. Since thisis a bottom up process the more detailed rules get added to the bottom and as the rules get moregeneral the IDs get lower and lower. Using this methodology you can create exceptions.

In this section we will configure a rule that will take in the barcode we entered in above. Remember that it started with 66 and ends in 77.

1. In the Configurator Select the Terminal Tab and select the “Item Entry Control Icon”

2. In the “Item Entry Control Search” window click on “New”

3. Fill in the Screen according to the following Image:





There are two fields highlighted. Just so there is no confusion they are left at default as theyare difficult to read in their current form.

Here we define a barcode that starts with 66 and ends with 77 it must be at least and at most 16characters long. The POS will print this barcode and so will SAP Customer Order Management.

4. Click “Save” and “Close” twice to exit this screen.

5.1.11.2 Menus

There are three major types of menus. These are Standard Menus, Function Menus and CustomMenus. Keyboards are looked at as a kind of menu from the POS

The Standard menus are represented on the POS screen as the actual buttons on the screen. Thereare three sets of Standard Menus Main Menu, Item Menu Tender Menu. Main Menu is displayed after you sign on or after a Transaction is finished. It cannot contain all of the transactions because it wouldnot make sense to allow an item void for example if there are no items to void. Conversely you couldnot allow some functions in mid transaction. After you launch a transaction or ring in your first itemthe Item menu is displayed. The Tender menu is displayed after you press the “TOTAL KEY” OnlyTenders some discounts and such are allowed here.

Function Menus are used to group certain function types for example, Admin Menus are used to

group Manager Codes and Tender Menus group Tenders so on and so forth. These menu types arenot used as much since custom menus give much more flexibility.

Custom Menus are menus that allow you to place a large number of items under them even other custom menus. This gives you the flexibility to create complex menu structures.

In this section we will add the Manager code into the POS’s Main Menu and Item Menu.

Follow this Procedure:





1. In the Configurator Select the Terminal Tab and select the Custom Menu (Items) icon.“

2. Select Custom Menu ID 20 “Non Merchandise” and Click Open

3. We will be adding the “Delivery Options” menu to the “NON Merchandise” menu.

4. At the Custom Menu Maintenance Screen click “Add Option”.





5. Now right click on the new line and a pull down menu will appear. Select Custom Menu.

6. This screen will appear

7. Click and Drag Delivery options onto the blue line you just created.





8. Close the custom menus Drag and Drop screen

9. Save and then close twice.

5.1.11.3 Add Exchange Item to menu

Now we need to add another type of refund to the refund menu. Follow this procedure

1. In the Configurator Select the Terminal Tab and select the Custom Menu (Items) icon.

2. Select Custom Menu ID 10 “Refund” and Click Open





3. This time we are going to add a User Defined Transaction ( usually called a UDT). So asbefore click on new

4. Set the # column to “10” and right click and select “User-Defined Txn” Function”

5. This menu will appear





6. As in the previous exercise drag and drop the function onto the new menu entry.

7. Close the Drag and Drop window

8. Your final result should look like this:

9. Click on Save and close twice

The description column is what actually gets displayed on the POS Menu.

5.1.11.4 Standard Menu –Main Menu

We need to add the interface to the order Management onto the menu. As you may remember thatwe created Manager Code 754 earlier. Well now we need to add this to the main menu.


1. In the Configurator Select the Terminal Tab and select the Standard Menu icon





2. In the Standard Menu Search Window select the Main Menu Window Type select “MAINMENU

3. Select Open

4. Then click on add.

5. Set the # column to 20

6. Right Click the new entry and select MGR/POS Function





7. Drag and Drop Manager Code 755 onto the new entry

8. Click on Save and close twice.

5.1.11.5 Standard Menu – Item Menu

We need to add the interface to the order Management onto the menu. As you may remember thatwe created Manager Code 754 earlier. Well now we need to add this to the item menu. This sectionfollows an almost identical procedure to the previous one.


1. In the Configurator Select the Terminal Tab and select the Standard Menu icon





2. In the Standard Menu Search Window select the Main Menu Window Type select “ITEMMENU”

3. Select Open

4. Then click on add.

5. Set the # column to 18

6. Right Click the new entry and select MGR/POS Function





7. Drag and Drop Manager Code 755 onto the new entry

8. Click on Save and close twice.

5.1.12 Register Parameters

Register Parameters are where the most fundamental rules of POS Operation reside. We need to setsome trickling settings. Trickling is how the POS communicates to PI and hence back in to the SAPBackend. We trickle the Transaction Log back to the SAP Host

Follow this procedure

1. In the Configurator Select the Terminal Tab and select the Register Parameter Icon





2. Select Open in the register Parameter Search Screen

3. Click on the Polling Option Tab

4. Set the Wrap ASCII Tlog in XML and Upload XML Tlog Trickle flags as outlined below.

5. Click on Save and Close twice.

6. Follow the Steps in Converting Parms for the first time use

Date post:	14-Apr-2018
Category:	Documents
Upload:	susmita099
View:	217 times
Download:	0 times

777_BB_ConfigGuide_EN_US.doc

Documents