SAP Point of Sale 2.0 Centralized Electronic Funds ... · IBM Websphere MQ TPS JMS (3rd party...

SAP Point of Sale 2.0Centralized Electronic Funds Transfer 1.7

User Guide

User GuideCopyright© Copyright 2006 SAP AG. All rights reserved.

SAP Library document classification: PUBLIC

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express

permission 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, 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, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are

trademarks or registered trademarks of IBM Corporation 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 Web

Consortium, 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 and

implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned

herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in

several other countries all over the world. Transactionware, POS Xpress, Store Manager, and Configurator are all

registered trademarks of SAP. All other product and service names mentioned are the trademarks of their

respective companies. Data contained in this document serves information purposes only. National product

specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated

companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and

SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP

Group products and services are those that are set forth in the express warranty statements accompanying such

products and services, if any. Nothing herein should be construed as constituting an additional warranty.

SAP - Important DisclaimersSAP Library document classification: PUBLIC

This document is for informational purposes only. Its content is subject to change without notice, and SAP does

not warrant that it is error-free. SAP MAKES NO WARRANTIES, EXPRESS OR IMPLIED, OR OF

MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.

Coding samplesAny software coding and/or code lines / strings ("Code") included in this documentation are only examples and

are not intended to be used in a productive system environment. The Code is only intended better explain and

visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness

of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code,

except if such damages were caused by SAP intentionally or grossly negligent.

Internet hyperlinksThe SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint

where to find supplementary documentation. SAP does not warrant the availability and correctness of such

supplementary documentation or the ability to serve for a particular purpose. SAP shall not be liable for any

damages caused by the use of such documentation unless such damages have been caused by SAP's gross

negligence or willful misconduct.

AccessibilityThe information contained in the SAP Library documentation represents SAP's current view of accessibility

criteria as of the date of publication; it is in no way intended to be a binding guideline on how to ensure

accessibility of software products. SAP specifically disclaims any liability with respect to this document and no

contractual obligations or commitments are formed either directly or indirectly by this document. This document

is for internal use only and may not be circulated or distributed outside your organization without SAP's prior

written authorization.

Table of Contents

Chapter 1 Introduction to Centralized EFTAbout the Centralized EFT Service ...................................................................... 3

Features of the Centralized EFT Service ............................................. 3

About the Centralized EFT system data flow ............................................. 4

Real time data flow .................................................................................. 4

Batch data flow ........................................................................................ 4

About the Centralized EFT system architecture ........................................ 4

About the Centralized EFT Service interface ............................................. 5

Centralized EFT site client .................................................................... 5

APM interface .......................................................................................... 5

SMTP Mail interface ............................................................................... 5

About the Centralized EFT interface ................................................................... 6

Accessing the File Transfer and Centralized EFT interfaces ................... 7

Chapter 2 Performing Administrative FunctionsManaging users ......................................................................................................... 9

Managing tasks .......................................................................................................12

Viewing the audit trail ...................................................................................13

Chapter 3 Managing Settlement and ReconciliationViewing transaction data .......................................................................................15

Viewing mis-matched records .............................................................................17

Finding a specific transaction ..............................................................................20

Tracking missing transaction log data ................................................................21

Purging data ............................................................................................................22

Chapter 4 Running the Response Time Analysis ReportsAbout the response time analysis reports ..........................................................25

Getting the most out of the response time analysis reports ...........................26

Investigating slow performance for a given time interval ...............26

Investigating general system performance ........................................26

Running the reports ...............................................................................................26

Purging your response time databases ................................................................33

Appendix A Configuring the Settlement and Reconciliation FunctionsConfiguring the Directory Monitoring Service for data loading ....................35

Configuring the mismatch report function ........................................................37

Mismatch report tags ....................................................................................38

1

Appendix B Configuring the response time analysis report functionConfiguring the response time analysis report function ..................................41

Appendix C CISP complianceCISP compliance ....................................................................................................43

Index ...................................................................................... 45

2

T
Introduction to Centralized EF
This section provides an overview of the Centralized EFT system and a description of its capabilities.

About the Centralized EFT ServiceCentralized EFT Service (also referred to as the EFT Service) is an enterprise service that allows you to

effectively control and manage authorization requests and responses for financial transactions at the

Point of Sale. In addition to providing a high throughput, low latency switch for authorizations, the

Centralized EFT Service also provides performance metrics, reporting capabilities as well as settlement

and reconciliation capabilities.

Features of the Centralized EFT Service

The Centralized EFT Service is available at the store or head office level. The following capabilities are

available with the EFT Service:

� Authorization requests for the following tender entities:

� Credit cards

� Debit cards

� Checks

� Gift cards or Stored Value cards

� Host-based settlement file generation

� Performance monitor with dynamic alerts

� Reconciliation against multiple service providers

� System-operational metrics

� Reporting capabilities

� Lower cost to change providers because no change is required in the store

� Fault tolerance (head office system only)

� Monitoring and alerts (head office system only)

In addition to supporting your standard SAP products, the EFT Service component includes an

interface which allows you to leverage the capabilities of your non-SAP points of interaction. Similarly,

interfaces available on the host components enable you to develop adapters to connect to your service

providers.

SAP currently maintains a library of pre-built adapters for many service providers and this library is

constantly growing.

3

Introduction to Centralized EFT

About the Centralized EFT system data flow

The fundamental purpose of the Centralized EFT solution is to move and manage authorization

requests from the Point of Sale through the central servers, out to an external service provider and to

get the responses back to the Point of Sale.

Real time data flow

Messages are passed in a generic format from the POS through the various components until they

reach the appropriate Application Programming Module (APM). There they are parsed into the

required format for the service provider and sent to the service provider according to the specifications

of that service provider. The response from the service provider is received by the APM and

immediately translated back into the SAP native format (based on ISO 8583 or xml). It travels in this

format all the way back to the POS from which the request originated.

Entries are created in the database for each transaction at several points during the message life cycle.

This data forms the foundation of the metrics reporting of the Centralized EFT module.

Batch data flow

In order to supply the raw data for the reconciliation function, TLogs and service provider settlement

data files are loaded into the server daily. This is usually done during the non-operational hours, and

may be done several days behind real time (depending on the Service Provider SLA in providing

settlement data files.)

About the Centralized EFT system architecture

Because SAP focuses on implementing both technical and industry (ISO) standards, the Centralized

EFT solution is completely open. This ensures minimal integration and deployment expense and

provides the greatest flexibility in middleware options.

The centralized EFT Service is composed of the following major components:

� Centralized EFT Adapter Module

� Service Provider Specific Application Program Modules (APM)

� EFT Data Load Module

� Centralized EFT Administrative Console (browser-based)

� EFT Monitor

The Centralized EFT Service leverages the product infrastructure which is composed of the following

components:

� Centralized EFT Site Client

� Message Oriented Middleware

� IBM Websphere MQ

� TPS JMS (3rd party software)

� Modem or Socket

� Centralized EFT Server

All components are Java-based and multi-threaded, specifically designed for high throughput

environments. The Centralized EFT Server and APMs leverage connection pools (socket and

database) to optimize the use of system resources.

4

About the Centralized EFT Service

The user interface is browser-based which greatly reduces the system administration burden as well as

provides location independence for users.

About the Centralized EFT Service interface

The Centralized EFT Service is an open and extensible solution. There are multiple published

interfaces that can be used to integrate your other POI-related components into this framework as well

as to participate in the development of interfaces for those service providers which do not have a

pre-built adapter (APM.)

Centralized EFT site client

The Centralized EFT site client has a published interface that supports both JMS and IP Socket

connection types. By having both interface technologies, SAP has delivered a single component which

is compatible with both Microsoft and Java technologies. Any point of interaction can be integrated to

the Centralized EFT services via the Centralized EFT site client interface.

The message formats passed into and out of the site client are XML documents. The message format

used for EFT messages is an XML representation of the ISO 8583 specification.

APM interface

The EFT Adapter module includes a published Java interface which can be used to develop APMs for

unique or in-house service providers. This is the same interface used by all APMs in the SAP library.

While it is generally more efficient for SAP to be engaged to build APMs that are not already in the

library, it is possible for you to assume this development yourself.

SMTP Mail interface

The EFT Monitor generates email via Simple Mail Transfer Protocol (SMTP) when thresholds are

exceeded in message response times.

5


About the Centralized EFT interfaceThe Centralized EFT interface is a Web-based application that serves a variety of functions:

� It provides access to the File Transfer and Centralized EFT configuration interfaces

� It serves as a system administration centre wherein you can set up users, task definitions, and audit

schedules

� It provides access to the payment monitoring system wherein you can run a variety of reports to

monitor payment and settlement transactions at various points in the system

� It provides access to the operations monitoring system, wherein you can run a variety of response

time analysis reports to track the efficiency of your Centralized EFT system or define database

pricing criteria

To access the Centralized EFT interface:

1. On the Centralized EFT server (or any computer with internet access), start your internet browser

program (for example, Microsoft Internet Explorer).

2. Go to the internet address of the computer on which you have installed Centralized EFT (ask

your system administrator for the IP address or bookmark). The Centralized EFT Sign-In page

appears.

3. Enter your user login information. To do this:

a) In the User id field, type your unique Centralized EFT user name (note that this field is case

sensitive). If you do not know or have forgotten your user identifier, please contact your

system administrator.

b) In the Password field, type your unique Centralized EFT password (note that this field is case

sensitive). If you do not know or have forgotten your password, please contact your system

administrator.

Note: Centralized EFT comes with a single default user called Administrator,

which uses the accompanying password of admin. This allows initial access to

the system. When you first set up, your system administrator should assign

unique user identifiers and passwords to each person who will be using the

system. Each user should then change their password the first time they log

into the system.

6

About the Centralized EFT interface

4. Click Login. The Centralized EFT main menu page appears. From this page, you can access all of

the administrative, reporting, and configuration subsystems available.

Accessing the File Transfer and Centralized EFT interfaces

You can access the configuration interfaces for both the File Transfer and Centralized EFT, depending

on which services you have installed, by clicking the relevant menu buttons on the main menu page.

For complete information about accessing and using the functions available in these interfaces, please

consult the File Transfer User Guide and the Centralized EFT Guide.

Note: When accessed from this interface, the File Transfer and Centralized EFT configuration

interfaces appear in a secondary browser window following the login process. To run them, you must

keep both the original and the secondary browser windows running.

This section displays the user name of the current user, and indicates the part of the system being used

Click a menu option to access the desired system component. Some menus display submenus when clicked

This central display section displays the system components as they are accessed

7


8

Performing Administrative Functions

The Administration functions of the Centralized EFT system allow you to maintain and monitor a

variety of administrative tasks. In this section, you can learn how to create and maintain user records

and define individual security clearance information; create and maintain task definitions and rankings;

and monitor user actions within the system using the audit tool.

Managing usersThe user management feature provides a central space in which you can maintain detailed information

and security profiles for each of your users. Here you can:

� Create new user profiles

� Assign user names

� Assign and modify passwords

� Enter and modify personal information (for example, contact information)

� Define and modify user scope privileges (that is, specify the chains, stores, and registers for which

data is available to this user)

� Define and modify security clearance information

The security level information is tied to the information defined in the Tasks section of the software.

In this way, various tasks within the system are assigned security levels, and matched against the

security levels assigned to each user to control access and activity clearance.

Note: Userid or username must not contain spaces or special characters.

9


To access the user maintenance system:

1. On the main menu page, click Administration, and then click Users. The User list page appears.

From here you can add a new user, or select a user whose information you wish to view or modify.

Note: Note that all actions in this part of the software are governed by your

security level clearance and the security levels assigned to the various tasks in

the system. If you are not authorized to view or modify other users’

information, you may not be able to access some sections of the system.

To create a new user:

1. On the User list page, click New. The Create New User page appears.

2. Enter the Identification information for this user (this is required information). To do this:

� In the UserId field, type a unique user name for this user; for example. their first initial and

last name.

� In the Password field, type a unique password for this user. The password will appear as a

series of asterisks (for example, *******) for security reasons.

We advise that you initially assign a very simple password (for example, 12345) to each user,

and then have them each change their password to something unique when they first log into

the system.

� In the Confirm Password field, type the same password again, to confirm it for the system.

Note: The user identification and password functions are case-sensitive. Each

time they are typed into the system, they must match precisely in all regards to

case. For example, if the password is DPeele, the system will not accept an

entry of dpeele.

These fields denote the users authorization level (5 being the highest) and their scope (that is, the chains, stores, and registers for which they can view information

Click to select the user whose information you wish to view or modify

To modify a user’s password, scope, or personal information, select that user, and then click the relevant button

Click New to create a new user profile

To delete an existing user, select that user and then click Delete

10

Managing users

3. Enter the Scope information for this user (this is required information). This will assign this user

an authority level, and specify the chains, stores, and registers in your retail structure for which this

user can view and manipulate information. To do this:

� In the Authority Level field, type an authority level ranging from 1 through 5, with 5 having

the highest authority and access, and 1 the lowest. To review which tasks are available to users

of each level, refer to the Task list page (see “Managing tasks” on page 12 for more

information).

� In the Chain Number, Store Number, and Register Number fields, enter the numbers

corresponding to the systems for which you want this user to view information. To enter

multiples, enter each number, followed by a comma (for example, Store Number: 2, 4, 6). To

denote that a user may have access to all of a particular category, type ALL (for example,

Register Number: ALL).

4. Enter all personal and contact information for the user, as desired. We advise you to treat the

following fields as required:

� The Name fields

� The Email address field

� The Telephone number fields

5. When you have entered all of the required information, click Apply. The information is added to

the system, and a message appears to confirm the addition.

11


Managing tasksThe task management feature maintains a lists of all user tasks defined in the system, together with

their authorization levels. The authority levels correspond to those assigned to each user in the system.

For example, a user assigned an authority code of 3 can perform only those tasks assigned a 3 or lower.

To access the task maintenance system:

1. On the main menu page, click Administration, and then click Tasks. The Task list page appears.

This list is available, as a reference of user tasks and their corresponding authority levels.

This field displays the authority level associated with the task. This corresponds to the authority levels of the users, and defines who can perform each task

Each task is assigned a unique identification number, to provide a reference in audit trails and logs

12

Managing tasks

Viewing the audit trail

The Audit function provides a running log of every action performed in the system listed by date, time,

and user. Each entry is accompanied by a brief description outlining the action performed. This allows

you track information in the system, and to monitor user actions.

To access the audit system:

1. On the main menu page, click Administration, and then click Audits. The Search Criteria

Selection page appears.

2. Enter the selection criteria for the information you want to view. You can select one or multiple

criteria by which to view the audit data.

3. When you have selected all the desired criteria, click Search and View. The information will

appear in a report format. Scroll up or down as necessary to view individual records.

13


4. The Audit list page appears. Here you can review all actions performed in the system. They are

listed by date, time, task identification number, and user, and included with each is a brief

description of the action performed.

This page provides an audit list of all tasks performed in the system, listed by date, time, task ID, and user

The Audit Message field provides abrief description of each action performed

14

Managing Settlement and Reconciliation

The transaction management function allows you to view and track payment data

throughout the settlement and reconciliation process. Here you can view summary or

detailed transaction record information.

Viewing transaction dataThe view data function allows you to view selected recorded payment transactions based on criteria

you select. You can define your selection by chain-store-register combination, date range, and tender,

card, or transaction type. View summary information, or drill down to view detailed transaction record

information.

To view payment data:

1. On the main menu page, click Transactions, and then click View. The Select View Criteria page

appears.


criteria by which to view the data.

15


3. When you have selected all the desired criteria, click either the Summary or Detailed button to

indicate the level of information you wish to view. The information will appear in a report format.

Scroll up or down as necessary to view individual records.

This is an example of a Payment Summary information page. It displays summary record information based on the view criteria selected

Click the Detail button beside any record to view more detailed information about that transaction

16

Viewing mis-matched records

Viewing mis-matched recordsThe mis-match function allows you to view records that are not consistent throughout the system,

such as records found in the store data, but not in the system database, or in the system database, but

not at the bank. The mis-match information is displayed in an easy-to-view comparison report format,

based on criteria you select. You can define your selection by chain-store-register combination, date

range, and tender, card, or transaction type, as well as by selecting the desired comparison type (for

example, Store to Transnet). You can choose to view summary or detailed mis-match information.

Note: When running a mismatch report, we recommend that you either limit the scope of the data

being loaded, or avoid running the report during peak hours so that you avoid overloading your

system.

The Summary Mis-Match Report provides easy-to-read summary mis-match information for each

store you selected to report upon.

The Detailed Mis-Match Report is composed of the following sections:

� A list of all mis-match transactions appearing in the first database chosen, but not in the second

database. For example, if you choose to run a report on mis-matches between the store and the

bank, this section will read ‘Data that exist in store log but not in the bank database’.

� A list of all mis-match transactions appearing in the second database chosen, but not in the first

database. For example, if you choose to run a report on mis-matches between the store and the

bank, this section will read ‘Data that exist in Bank database bit not in store log’. Note that there is

no export checkbox for these mis-matches, as they cannot be easily reconciled from the store end.

� A list of all transaction pre-authorizations.

� A list of all duplicate transactions in the store records.

� A list of all duplicate transactions in the bank records.

17


To view mis-matched records:

1. On the main menu page, click Transactions, and then click Mis-matches. The Select Mis-Match

Criteria page appears.

2. Enter the selection criteria for the information you want to view. The selection criteria includes:

� Chain Number: Specify one or more specific chain numbers to report upon. To specify

multiple select chains, enter the chain numbers in a comma-delimited list (for example,

10,20,30).

� Store Number: Specify one or more specific store numbers to report upon. To specify

multiple select stores, enter the store numbers in a comma-delimited list (for example,

101,102,103,104,107). This field is mandatory for detailed mis-match reports.

� Register Number: Specify one or more specific register numbers to report upon. To specify

multiple select registers, enter the register numbers in a comma-delimited list (for example,

10,20,30).

Note: You must enter at least one chain number, store number and register

number for the report to run. Do not enter 0 or leave these fields blank.

� Start Date: Specify the date from which the report should start including data. If left blank,

the system uses the earliest business date in the database for the start date.

� End Date: Specify the date at which the report should stop including data. If left blank, the

system uses the current business date for the end date.

� Tender Type: Select one tender type or run the report for “All”. Tender types might include

Credit, Debit, and Check.

� Card Type: Select a card type to report on. Card types might include VISA, MasterCard, and

American Express.

� Transactions Type: Select one transaction type or run the report for “All”. Transaction types

might include Sale, Void, Return, and Reversal.

� Credit Service: Select a credit service to report on.

18

Viewing mis-matched records

� Presentation Mode: Select a presentation mode for the report. The options are “Store

Based” or “Service Based” (this determines how the information in the report will be

organized or presented).

� Comparisons: Select a mis-match comparison type on which to base the report. The available

comparison types are Store to Transnet, Store to Bank, and Bank to Transnet. This will

determine the two databases between which the system will search for mis-matched

information.

3. When you have selected all the desired criteria, click either the Summary or Detailed button to

indicate the level of information you wish to view. The information will appear in a comparison

report format. Scroll up or down as necessary to view individual records.

The Summary Mis-Match Reports include the following information:

� Store Total: This section displays data for the store and date indicated. It shows the the

transaction number and net transaction amount. For example, if there were four sales

transactions amounting to $88.20 and two return transaction amounting to $66.30, this

column will show six transactions equalling $21.90.

� Service Provider Total: This section displays data for the service provider and date indicated.

It shows the transaction number and net transaction amount. For example, if the-re were four

sales transactions amounting to $88.20 and two return transaction amounting to $66.30, this

column will show six transactions equalling $21.90.

� Difference: This field displays the difference between the store total and the service provider

total for the date indicated.

� Mis-match Store Total: This field displays the store mis-match totals (the total of all

transactions recorded “in the store but not in the bank”). This data is based on the mis-match

rules defined in the transnet.xml configuration file.

� Mis-match Service Provider Total: This field displays the service provider mis-match totals

(the total of all transactions recorded “in the bank but not in the store”).

� Variance: This field shows the final between the store total and the service provider total after

you have reconciled any repairable mis-matches .

19


Finding a specific transactionThe find function allows you to search the system for a particular payment transaction based on criteria

you select. You can define your selection by chain-store-register combination, date range, transaction

number or type, card number, card holder, authorization number, and amount.

To find a transaction:

1. On the main menu page, click Transactions, and then click Find. The Select Criteria To Find

Transaction page appears.


criteria by which to search for the data.

20

Tracking missing transaction log data

3. When you have selected all the desired criteria, click Find Transactions. All transactions

matching the criteria selected will appear in a report format. Scroll up or down as necessary to

view individual records.

Tracking missing transaction log dataThe Missing Data report allows you to track transaction log data that has not been received or

recorded by the system or by your bank or service provider.

To run a missing data report:

1. Click the Transactions menu, and then click Missing Data.

2. On the Missing Data Report criteria screen, enter start and end dates to specify the dates for

which you want to search for missing transaction log data.

3. Click Run. If the system detected missing data on the dates specified, a report will appear detailing

the stores and dates for which information was not received. (If the system detects no missing

data, the missing data fields will be blank).

4. View the resulting report. It contains the following information:

� Store: The Store column displays the store number for which information is missing.

� New: The New column indicates the date on which the related store became active on the

system.

� Missing TLOG Data: The Missing TLOG Data column gives the dates for which

transaction log data is missing at the system database level for the given store. Note that the

information is provided in MM/DD format (as such, we recommend that you not search

across year boundaries when running a Missing Data report).

� Missing Bank Data: The Missing Bank Data column gives the dates for which transaction

log data is missing at the bank database level for the given store. Note that the information is

This is an example of a Payment Detail information page. It displays detailed record information based on the criteria selected

21


provided in MM/DD format (as such, we recommend that you not search across year

boundaries when running a Missing Data report).

Purging dataThe purge function allows you to remove selected data (for example, older data) from your system,

when you no longer have a need for it.

To purge data:

1. On the main menu page, click Transactions, and then click Purge. The Select Purge Criteria

page appears.

Missing File Report screen here

22

Purging data

2. In the Start Date and End Date fields, enter the date range for the data you want to purge from

the system.

3. Depending on the type of information you want to purge from the system, click one of the

following buttons: Purge Transnet Data, Purge Store Data, or Purge Bank Data. The

specified data is purged from the system, and a message confirms when the process has been

completed.

23


24

Running the Response TimeAnalysis Reports
This section describes the response time analysis reports, and provides instructions on how to run and

interpret them. Topics include:

� “About the response time analysis reports” on page 25

� “Getting the most out of the response time analysis reports” on page 26

� “Running the reports” on page 26

� “Purging your response time databases” on page 33

For information on configuring these reports, see Appendix , “Configuring the response time analysis

report function” on page 41

Note: An SVG viewer is required to view the Response Time Analysis report graphs. If you are using

Internet Explorer, get the Adobe SVG viewer from Adobe’s web site. If you are using Firefox, you

don’t need to get a SVG viewer add-on.

About the response time analysis reportsThe response time analysis reporting utility allows you to analyze and view graphic reports for your

system’s message transfer response times. The data source for the response time analysis reports is the

meter table. Accessed from the Operations menu, the response time analysis sub-menu offers four

report views:

� Average Time — This report displays the average response time versus the time of the day. Use it

to analyze the average response time for your system and your Service Provider over the course of

a month during your chain or store’s busiest hours.

� Response Time Vs Number of Transactions per second — This report displays the

transaction distribution and the corresponding average response time. This can help in analyzing

system performance at higher transactions per second.

� Distribution — This report displays the distribution of transactions across the given date range.

You can use it to determine the volume of transactions for a chain or store across a particular time

period.

� Response Time — This report displays the number of transactions occurring within a given

response time range over a date range and chain/store combination. You can use it to analyze the

response times for a particular store over a selected period.

25

Running the Response Time Analysis Reports

Getting the most out of the response time analysis reportsWe recommend that you employ the following sequence of analysis when using the Response Time

Analysis reports.

Note: To get manageable, meaningful results, target small data sets initially, and then work up to larger

sets as required. Also, to maximize reporting performance and speed, run the response time analysis

reports during off-peak hours.

Investigating slow performance for a given time interval1. View the Average Response Time for the full range.

2. Identify the peak time.

3. View Distribution for the time. Select an interval of one second: this will give the number of hits

per second or View the Average Response Time Vs Number of Transactions per second.

Investigating general system performance1. View the Average Response Time for the full range.

2. View the Response Time for the selected response time range.

Running the reports

To run a response time analysis report based on average time:

1. On the main menu page, click Operations, click Response Time Analysis, and then click

Average Time. The Transnet RTA - Average Response Time report selection criteria page

appears.

2. Enter the selection criteria for the information you want to view. The following criteria must be

provided:


multiple chains, enter the chain numbers in a comma-delimited list (for example, 10,20,30).

26

Running the reports


multiple stores, enter the store numbers in a comma-delimited list (for example,

101,102,103,104,107).

� Date: Specify the date from which the report should start including data. If left blank, the

system uses the earliest business date in the database for the start date.

� Start Time: Specify the time from which the report should start including data.

� End Time: Specify the time at which the report should stop including data.

� Interval(min): Select the intervals (in minutes) into which the report should be broken.

� Credit Service: Select the service provider for which you want to view response times.

3. When you have selected all the desired criteria, click Submit. The requested information will

appear in a graphic report format.

The report displays the following information:

� TN Average: Shows the average response time for your system for the time periods specified.

� TN Minimum: Shows the minimum response time for your system for the time periods

specified.

� TN Maximum: Shows the maximum response time for your system for the time periods

specified.

� SP Average: Shows the average response time for your Service Provider for the time periods

specified.

� SP Minimum: Shows the minimum response time for your Service Provider for the time

periods specified.

� SP Maximum: Shows the maximum response time for your Service Provider for the time

periods specified.

27


To run a response time analysis report based on transaction distribution:


Distribution. The Transnet RTS-Transaction Distribution report criteria selection page appears.


provided:





101,102,103,104,107).

� Date: Specify the date from which the report should start including data.


� End Time: Specify the time at which the report should stop including data.

� Interval(sec): Select the intervals (in seconds) into which the report should be broken.




28

Running the reports

The report displays the number of transactions performed as distributed across the time segments

specified.

To run a response time analysis report based on average time versus transactions:


Average Vs Txns. The Transnet RTA-Response Time Vs. Transactions Per Second report

criteria selection page appears.


provided:





101,102,103,104,107).


29



� End: Specify how many minutes the report should span.





� TN Average: Shows the average response time for your system, as measured against the

number of transactions processed per second.

� TN Minimum: Shows the minimum response time for your system, as measured against the


� TN Maximum: Shows the maximum response time for your system, as measured against the


� SP Average: Shows the average response time for your Service Provider, as measured against

the number of transactions processed per second.

� SP Minimum: Shows the minimum response time for your Service Provider, as measured

against the number of transactions processed per second.

� SP Maximum: Shows the maximum response time for your Service Provider, as measured

against the number of transactions processed per second.

30

Running the reports

To run a response time analysis report based on response time:


Response Time. The Transnet RTA-Response Time Distribution report criteria selection page

appears.


provided:





101,102,103,104,107).


� Minimum Response Time: Specify the lowest response time (in milliseconds) against which

you want to measure the number of transactions.

� Maximum Response Time: Specify the greatest response time (in milliseconds) against

which you want to measure the number of transactions.

� Interval(ms): Select the intervals (in milliseconds) into which the report should be broken.




31



� TN Response: The system response time, as distributed across the number of transactions

performed.

� SP Response: The Service Provider response time, as distributed across the number of

transactions performed.

32

Purging your response time databases

Purging your response time databasesThe purge database function allows you to delete the existing data from a specified response time

database. This allows you to better manage file storage and database size issues.

To purge a response time database:

1. On the main menu page, click Operations, click Purge Database, and then click Tables. The

Selecting Purge Criteria page appears.


provided:





101,102,103,104,107).

� Start Date: Specify the date from which the report should start including data.

� End Time: Specify the date on which the report should stop including data.

� Table Name: Select the table you would like to purge.

3. When you have selected all the desired criteria, click Submit. The designated database table will be

purged.

33


34

nd
Configuring the Settlement aReconciliation Functions
This section describes the Centralized EFT settlement and reconciliation function configuration

processes. Before you can load store and bank transaction data, or run the transaction reports, you

must configure a variety of settings in the transnet.xml files.

Note: We recommend that you use an XML editing tool (such as XMLSpy) when configuring

or modifying any of XML files.

Configuring the Directory Monitoring Service for data loading

In the transnet.xml (server version) configuration file (located by default at C:\Program

Files\transnet\config) there is a tag section required to configure the Centralized EFT data loading

process. These settings pertain to the Directory Monitoring Service, which monitors designated

directories for new bank data and store data TLog files, and loads them into the Centralized EFT

reporting system for settlement and reconciliation.

This section shows a sample of the transnet.xml tag settings specifically required for Directory

Monitoring Service data loading configuration.

<Transnet SystemID="10_1_1">

<Logging>logging.properties</Logging>

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

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

...



<Connection name="StoreTlogLoader" class="com.triversity.transnet.core.tms.file.DirectoryConsumerMonitor" interval="1000" target="data" working_directory="c:/temp">

35

Configuring the Settlement and Reconciliation Functions

<adapter class="com.triversity.transnet.core.reconciliation.ReconciliationFileConsumer">

<Reconciliation chain="10" service="Store" tableName="PaymentDetail_Store" archiveFolder="C:\program files\Transnet\logs\archive" merchantFileName="Merchants.xml">

<Parser name="TlogFileParser" class="com.triversity.transnet.core.tlog.TlogFileParser" />

</Reconciliation>

</adapter>

</Connection>

36

Configuring the mismatch report function

Configuring the mismatch report functionIn the transnet.xml (Tomcat version) configuration file (located by default at C:\Program

Files\transnet\tomcat\webapps\Transnet) there is a tag section called

<MismatchComparison>. Here you need to specify what transaction data is to be used for

data comparison when you run the mismatch report. Define a Field ID for each critical data

chunk. For example, if you define the fields “chain”, “store”, and “register” here, then all the

transactions with same chain, store and register number will be treated as matched transactions.

There must be a <MismatchComparison> section for each chain in your hierarchy, and

each APM or financial service provider you are using, with at least one field identified for

comparison in each.

The field list indicates which files must be compared between the Store TLOG, Service

Provider, and the transaction files. These settings are determined by comparing the file formats

required by each system, and should be configured only in consultation with your qualified SAP

personnel.

For example:

<?xml version="1.0" ?>



<TransnetServerConfiguration>

<MeterTable name="transnet_meter" />



<MerchantFile name="NovaMerchant.xml" service="Nova"/MerchantFile>

<MerchantFile name="WildCardMerchant.xml" service="WildCard"/MerchantFile>



<MismatchComparison SAFFileLocation=".">

<Chain name="ABC" id="10">

<Service name="Nova">

<Mismatch SAFFileLocation=".">

<Field id="1" name="chain" />

<Field id="2" name="store" />

<Field id="3" name="register" />

<Field id="4" name="tender_type" />

<Field id="5" name="card_type" />

<Field id="6" name="card_num" />

37


<Field id="7" name="amount" />

<Field id="8" name="approval_code" />

<SortByRegister>true</SortByRegister>

<HiddenReportDate>none</HiddenReportDate>

<BusinessDateCutOverTime>020000</BusinessDateCutOverTime>

</Mismatch>

</Service>

</Chain>

<Chain name="XYZ" id="20">

<Service name="WildCard">

<Mismatch SAFFileLocation=".">

<Field id="1" name="chain" />

<Field id="2" name="store" />

<Field id="3" name="register" />

<Field id="4" name="txn_num" />

<Field id="5" name="card_num" />

<Field id="6" name="amount" />

<Field id="7" name="approval_code" />

<SortByRegister>true</SortByRegister>

<HiddenReportDate>none</HiddenReportDate>

<BusinessDateCutOverTime>020000</BusinessDateCutOverTime>

</Mismatch>

</Service>

</Chain>

</MismatchComparison>

...

Note: All tag and attribute names are case sensitive, and must be entered as shown.

Mismatch report tags

This table describes the tags and attributes used in the Mismatch configuration section of the

transnet.xml (Tomcat version) file.

Tag Attributes Set to Notes

<MismatchCo

mparison>

SAFFileLocation The location of the

relevant Store and

Forward file.

<Chain> You must have one

entry for each chain/

service provider

combination.

name The name of the chain.

For example, ABCSports

38

Configuring the mismatch report function

id The identification code

for the chain.

For example, 5

<Service> The name of the service

provider used by this

chain.

For example, Nova

You must have one

entry for each chain/

service provider

combination.

name

<Mismatch>

SAFFileLocation The location of the

relevant Store and

Forward file.

<Field>

id The field identification

code.

For example, 1

These are numeric

ascending, for the total

number of fields to be

compared.

name The name of the service

provider used by this

chain.

For example, card_num

The field names should

match the field names

in the PaymentDetail

table.

<SortByRegist

er>

Specifies whether or not

the register or terminal

level will be included as a

reporting sort option.

For example, true

Possible values are:

� true (reports will be

based on chain, store,

register, and business

date)

� false (reports will be

based on chain, store,

and business date)

39


<HiddenRepor

tDate>

A comma delimited list of

the days to exempt from

reporting (such as the days

on which your stores are

closed).

For example, Sat, Sun

To list multiple days,

separate with commas.

Possible values are:

� Mon

� Tue

� Wed

� Thu

� Fri

� Sat

� Sun

� none

<BusinessDat

eCutOverTime

>

The time at which a new

business day should

begin, in the format

HHMMSS.

For example, 020000

40

e
Configuring the response timanalysis report function
This section provides additional detailed information about Configuring the response time analysis

report function in Centralized EFT.

Configuring the response time analysis report functionThere are two configuration points for the response time analysis reports:

� The transnet.xml configuration file (tomcat version)

� The web.xml configuration file

In the transnet.xml (Tomcat version) configuration file (located by default at C:\Program

Files\transnet\tomcat\webapps\transnet) there is a tag section called <MeterTable>. Here you

need to specify the database table used for loading data to the Response Time Analysis reporting

system. The default is “transnet_meter”. Generally, the default values are acceptable.

Note: All tag and attribute names are case sensitive and must be entered as shown.

For example:

<?xml version="1.0" ?>



<TransnetServerConfiguration>



<MeterTable name="transnet_meter" />

...

</TransnetServerConfiguration>

In the web.xml file (located by default at C:\Program

Files\transnet\tomcat\webapps\WEB-INF\web.xml) a set of MIME mapping tags must be

configured to designate the filename extensions to be used in the response time analysis reports.

Generally, the default values are acceptable.

For example:

...

41

Configuring the response time analysis report function





<mime-mapping>

<extension>svg</extension>

<mime-type>image/svg+xml</mime-type>

</mime-mapping>

<mime-mapping>

<extension>svgz</extension>

<mime-type>image/svg+xml</mime-type>

</mime-mapping>



42

CISP compliance

This section provides additional detailed information about how Centralized EFT is CISP compliant.

CISP complianceThe Visa Cardholder Information Security Program, also known as CISP, is a standard developed by

Visa that protects cardholder information during transmission, processing or storage of that data.

Cardholder information consists of the cardholder account number, name and card expiration date.

The following is a list of the general features required to meet CISP compliance. These requirements

apply to the entire system — from the POS to the Xpress server; from the Centralized EFT site client

to the Centralized EFT server; and from the Centralized EFT server to the EFT provider.

� Storing data on a secure machine not accessible to the general network and encrypting the

information using a prescribed encryption method

� Installing and maintaining a working firewall to protect data

� Keeping key security patches up-to-date

� Using and regularly updating anti-virus programs

� Encrypting any cardholder data that is transmitted through a public network. This applies to data

transmission from the POS to the store controller, and from the store controller to the

Centralized EFT site client if the network is accessed externally. It also applies to transmissions

between the Centralized EFT site client and Centralized EFT server, and from the Centralized

EFT server to the EFT provider.

� Restricting user access to business data on a need-to-know basis

� Assigning a unique ID to each person requiring computer access and tracking all user access to

data through unique IDs

� Refraining from using vendor-supplied defaults for system passwords and other security

parameters

� Regularly testing security systems and processes

� Restricting physical access to cardholder data

� Maintaining a policy that addresses information security for employees and contractors

To comply with governmental and contractual regulations pertaining to the protection of personal

information, SAP has enhanced its various products to ensure that they are in compliance with the

standards outlined in CISP. Some of these enhancements include the following:

� Account numbers in the FinancialMessage XML messages logged in the store-side Centralized

EFT logs are masked. When required, account numbers are truncated or display only the last four

digits of the account number.

� The default setting of the HTTPS server for the Centralized EFT administrative interface is set to

encrypt all HTTPS communications and network traffic.

43

CISP compliance

� Centralized EFT uses advanced password management features which ensure that passwords are

changed every 90 days, that they contain at least seven alphanumeric characters, and that new

passwords are not the same as any of the four most recently-used passwords.

� The key used to encrypt cardholder information in the Centralized EFT database is encrypted.

� Passwords on network devices and systems, as well as the application passwords stored in the

Centralized EFT database and the database password, are encrypted.

� Cardholder names and expiration dates are stored in the database in encrypted format.

� Users can configure Centralized EFT to mask the last four digits of a credit card number, and

track two data on the credit card in the log file.

� To address magnetic strip card processing, the reading, writing and searching of the payment

detail store the card number and expiration date in encrypted format, and retrieve them in

unencrypted format.

� In Centralized EFT, searches by card number are conducted using the encrypted card number.

� Each APM logs incoming and outgoing messages with truncated or blanked-out cardholder

information.

� The transmission of data between the Centralized EFT site client and server is transmitted via

SSL.

44

Index

A

administrative tasks

task maintenance 12user maintenance 9users 9

audit function 13

C

Centralized EFT

accessing 6interface 6

CISP 43

D

data

configuring loading process 35loading 35mis-matched records 17purging 22transaction 15

directory monitoring service 35

F

finding transactions 20

I

interface

accessing

Centralized EFT 7File Transfer 7

M

mis-matched records 17missing data report 21missing TLOG data report 21monitoring

directories for TLog data loading 35

R

reconciliation 15reports 15

reports

missing data 21missing TLOG data 21reconciliation 15settlement 15

S

sers 9settlement 15

reports 15

T

task maintenance system 12task management 12TLogs

loading 35missing data report 21

transaction information 15find 20mis-matched records 17purging data 22transaction data 15

U

user maintenance system 10users

creating 10managing 9task management 12user maintenance system 10

V

viewing transaction data 15

45

SAP Point of Sale 2.0 Centralized Electronic Funds ... · IBM Websphere MQ TPS JMS (3rd party...

Documents

Transcript of SAP Point of Sale 2.0 Centralized Electronic Funds ... · IBM Websphere MQ TPS JMS (3rd party...