November 2010

■

■

■

© Copyright 2010 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, Excel, Outlook, and PowerPoint are

registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5,

System p, System p5, System x, System z, System z10, System

z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM,

z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel

Enterprise Server, PowerVM, Power Architecture, POWER6+,

POWER6, POWER5+, POWER5, POWER, OpenPower,

PowerPC, BatchPipes, BladeCenter, System Storage, GPFS,

HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2,

Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner,

WebSphere, Netfinity, Tivoli and Informix are trademarks or

registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S.

and other countries.

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 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.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign,

Clear Enterprise, SAP BusinessObjects Explorer, 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 other countries.

Business Objects and the Business Objects logo,

BusinessObjects, Crystal Reports, Crystal Decisions, Web

Intelligence, Xcelsius, and other Business Objects products and

services mentioned herein as well as their respective logos are

trademarks or registered trademarks of SAP France in the

United States and in other countries.

All other product and service names mentioned are the

trademarks of their respective companies. Data contained in

this document serves 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 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.

Disclaimer

Some components of this product are based on Java™. Any

code change in these components may cause unpredictable and

severe malfunctions and is therefore expressively prohibited,

as is any decompilation of these components.

Any Java™ Source Code delivered with this product is only to

be used by SAP’s Support Services and may not be modified

or altered in any way.

Documentation in the SAP Service Marketplace

You can find this documentation at the following Internet

address: service.sap.com/instguides

Typographic Conventions

Type Style Represents

Example Text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

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 key words 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, names of variables and parameters, source code as well as names of installation, upgrade and database tools.

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.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such

as F2) or the ENTER key.

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Master Guide SAP Enterprise Point-of-Sale

November 2010 5

History of Changes

The Master Guide is regularly updated in SAP Service Marketplace at

service.sap.com/instguides under Industry Solutions → Industry Solution Guides

→ SAP for Retail → SAP Enterprise Point-of-Sale.

Make sure you have the latest version of the Master Guide by checking SAP Service Marketplace immediately before starting the installation.

The following table provides an overview of the most important changes that were made in the latest versions.

Master Guide Version Important Changes

1.0 July 28, 2009 Initial Version

1.1 December 22, 2009 Minor edits based on initial feedback

1.2 November 29, 2010 Updated the list of SAP documents and deleted Demo Topology

Master Guide SAP Enterprise Point-of-Sale

6 November 2010

Contents

1 Getting Started ......................................................................... 7

1.1 About this Document .................................................................. 7

1.2 Related Information .................................................................... 8

1.2.1 Planning Information ..................................................................... 8

1.2.2 Further Useful Links ...................................................................... 9

1.3 Important SAP Notes .................................................................. 9

2 SAP Enterprise POS Overview .............................................. 10

2.1 Software Units of SAP Enterprise POS ................................... 10

Application Components ...................................................................... 10

Technical/Platform Components ......................................................... 11

2.2 Software Component Matrix .................................................... 15

2.3 System Landscape .................................................................... 16

2.3.1 Local Store Server Topology....................................................... 17

2.3.2 Central Store Server Topology .................................................... 18

3 Implementation Sequence ..................................................... 21

3.1. Overall Implementation Sequence ......................................... 21

DEV Landscape ..................................................................................... 21

TEST Landscape ................................................................................... 22

PROD Landscape .................................................................................. 22

4 Solution-Wide Topics............................................................. 23

4.1 Inter Node Communications........................................................... 23

4.2 Integration ........................................................................................ 24

4.4 Project and Implementation Team Considerations ...................... 31

5 References .............................................................................. 33

6 The Main SAP Documentation Types ................................... 36

1 Getting Started

November 2010 7

1 Getting Started

1.1 About this Document Purpose

This Master Guide is the central starting point for the technical implementation of SAP Enterprise Point-of-Sale (SAP Enterprise POS).

Use the Master Guide to obtain an overview of SAP Enterprise POS, its software units, and its scenarios from a technical perspective. The Master Guide is a planning tool that helps you to design your system landscape. It refers you to the following required detailed documentation:

Installation guides for single software units

SAP Notes

Configuration documentation

SAP Library documentation

For a general overview of the available SAP documentation, see The Main SAP Documentation Types.

The Master Guide consists of the following main sections:

SAP Enterprise POS Technical Solution Overview

This section lists the application components and platform components and provides a brief overview of the role of each in the solution. In addition, the deployment of these components onto physical nodes is described for each certified topology.

Solution Implementation Topics

This section describes topics that are critical to consider and understand when planning and executing an SAP Enterprise POS implementation project. The main points covered are inter-node communications, integration, and high level project considerations. While these topics are not necessarily unique to SAP Enterprise POS among other SAP solutions, these topics are particularly important to consider for a Point of Sale implementation due primarily to the distributed nature of the application.

References

This section contains a comprehensive set of links to relevant documentation and information sources

You can find the most current information about the technical implementation of SAP Enterprise POS and the latest installation and configuration guides on SAP Service Marketplace at http://service.sap.com

We strongly recommend that you use the documents available here. The guides are regularly updated.

Constraints

The business scenarios that are presented here serve as examples of how you can use SAP software within your company. The business scenarios are only intended as models and do not necessarily run the way they are described here in your customer-specific system landscape. Make sure that you check your requirements and systems to determine whether these scenarios can be used productively at your site. Furthermore, we recommend that you test these scenarios thoroughly in your test systems to ensure they are complete and free of errors before going live.

1 Getting Started

8 November 2010

This Master Guide primarily discusses the overall technical implementation of SAP Enterprise POS, rather than its subordinate components. Only the major software elements of the solution are described in this document. You can find more information on specific detailed components in the corresponding installation guides and other documents referenced in this Master Guide.

1.2 Related Information

1.2.1 Planning Information For more information about planning topics not covered in this guide, see the following content on SAP Service Marketplace:

Content Location on SAP Service Marketplace

Operation Guide, Installation Guide, Upgrade Guide

service.sap.com/instguides under Industry

Solutions → Industry Solution Guides → SAP for Retail → SAP Enterprise Point-of-Sale

SAP Enterprise POS and SAP for Retail Security Guides

service.sap.com/securityguide under SAP for Retail

SAP Education Curriculum for SAP Enterprise POS

sap.com/services/education/catalog/in

dustry under Retail → SAP Enterprise POS

SAP Business Maps - information about applications and business scenarios

service.sap.com/businessmaps

Sizing, calculation of hardware requirements (CPU, disk, and memory resource) for the SAP Enterprise POS systems can be found in the SAP Enterprise POS Sizing Guide

Sizing SAP Enterprise Point-of-Sale (POS), Version 3.1

Network Bandwidth/Capacity estimation for SAP Enterprise POS can be found within the Front End Network Requirements for SAP Business Solutions document

Front-End Network Requirements for SAP Business Solutions

Released platforms and technology-related topics such as maintenance strategies and language support

service.sap.com/pam

SAP Enterprise POS Performance Tuning Guide,

SAP Enterprise POS EFT User Exit Technical Reference Guide

service.sap.com/retail under Expert

Knowledge Corner → Sales → SAP Enterprise POS

Information about Support Package Stacks, latest software versions and patch level requirements

service.sap.com/sp-stacks

1 Getting Started

November 2010 9

1.2.2 Further Useful Links The following table lists further useful links on SAP Service Marketplace:

Content Location on SAP Service Marketplace

Information about creating error messages service.sap.com/messages

SAP Notes search service.sap.com/notes

SAP Software Distribution Center (software download and ordering of software)

service.sap.com/swdc

SAP Online Knowledge Products (OKPs) – role-specific Learning Maps

service.sap.com/rkt

1.3 Important SAP Notes You must read the following SAP Notes before you start the installation. These SAP Notes contain the most recent information on the installation, as well as corrections to the installation documentation.

Make sure that you have the updated version of each SAP Note, which you can find on SAP Service Marketplace at service.sap.com/notes.

SAP Note Number Title Description

1295002 Release Restrictions for SAP for Retail 2009

This note provides information about the limitations in all solutions bundled in SAP for Retail 2009

1146445 Release Restrictions for SAP for Retail 2008

This note provides information about the limitations in all solutions bundled in SAP for Retail 2008

1063418 Release Restrictions for SAP for Retail 2007

This note provides information about the limitations in all solutions bundled in SAP for Retail 2007

2 SAP Enterprise POS Overview

10 November 2010

2 SAP Enterprise POS Overview Designed for general merchandise and multi format retailers, SAP Enterprise Point of Sale is a highly configurable point of sale (POS) application. At the point of sale, SAP Enterprise POS provides retailers with the following functions:

Discounts, promotions, and mix-and-match pricing

Layaway and special-order functions to meet customer needs

Accuracy and fraud reduction with a centralized recall transaction for merchandise returns

Receipt and document printing, including rebates,

Special policies and other retailer-defined documents

SAP Enterprise POS is a Java Enterprise Edition-based application with flexible deployment options. It is integrated with SAP ERP and SAP POS Data Management using SAP NetWeaver Process Integration.

2.1 Software Units of SAP Enterprise POS SAP Enterprise POS delivers as a set of components, including application components containing retail business logic as well as platform components, which provide more generic middleware functions.

Application Components POS Client is the application that runs on the register and presents the user interface to the operator and the customer. The POS Client has no business logic, but rather contains presentation tier logic to support complex data forms as well as interactions with retail peripheral devices (For example, bar code scanner or cash drawer). The POS Client is a Java application, which uses Java Swing as the primary user interface technology. As the POS Client has no business logic, it must be connected to an instance of POS Server or OLC Controller to process retail transactions. The POS Client includes the fail over algorithm that provides the high availability that is required for any Point Of Sale solution.

The Mobile POS Client is special instance of the POS Client, adapted to retail-specific mobile computing devices. The user interface, the supported peripheral devices and the supported operating systems of the Mobile POS Client are different from the standard POS Client. The Mobile POS Client is developed in C/C++ in contrast to the other components of SAP Enterprise POS. The mobile POS Client is currently not translatable and is also only available for use in the United States and Canada.

The POS Server contains the business logic required to process transactions. The POS Server includes the Electronic Funds Transfer (EFT) Manager component, which is used in the integrated EFT model. The POS Server has no user interface; that is provided by the POS Client. The POS Server (and its derivative the OLC Controller) are the most critical component of SAP Enterprise POS and are therefore deployed in multiple locations to provide high availability. Each POS Client is configured with the location of the appropriate POS Server and Backup Server instances and it is the POS Client that manages failing over between the known instances of POS Server to deliver a highly available solution for transaction processing. The business logic executed by the POS Server is defined and managed by the Configurator application component and there are numerous extension points (user exits) in the POS Server that can be leveraged to implement solution extensions to satisfy requirements that go beyond the configurability of the standard solution.

2 SAP Enterprise POS Overview

November 2010 11

The POS Offline Capable Client (OLC) Controller provides the POS Client with the business logic necessary to process transactions if the POS Client loses connection with all instances of POS Server. The OLC Controller is based on the POS Server and is built with the same source code, but is stripped down to enable operation on a register. The OLC controller can only provide business logic for a POS Client that is located on the same physical device, meaning that the OLC Controller services at most one POS Client and that the OLC is always deployed onto a register.

The POS Manager is the other major business logic component of SAP Enterprise POS. The POS Manager is responsible for the store administration capabilities of SAP Enterprise POS, such as tender management, store opening, closing, and operational reporting. The POS Manager is a browser based application that can be accessed remotely.

The Centralized Transaction Services (CTS) component handles service requests from the POS Server and POS Manager Application components. The CTS component has no user interface as its function is to expose services that other SAP Enterprise POS components can leverage. The primary business services provided by CTS include cross store returns and layaways. CTS also expose extension points so that service requests from POS Server or POS Manager can be routed to external systems. SAP Enterprise POS can be integrated with customer loyalty systems using such an extension point, for example. CTS also manage posting of transaction logs from POS Server on the back office server. The MDI Controller manages the Master Data Import process on the head office database server.

The POS Configurator is the component to customize the behavior of the SAP Enterprise POS system. The accepted tender (for example credit cards) is maintained within the POS Configurator. The final configuration is distributed to the store server. Within the store server, the components, such as the POS Server, work according to the configuration. The end user uses a browser based client to access the Configurator.

Technical/Platform Components SAP Enterprise POS includes a complete set of platform components (referred to as the middleware). These platform components are IBM products provided for use exclusively with SAP Enterprise POS. SAP customers need to engage directly with IBM to discuss the usage of the platform components for other purposes. While SAP product documentation includes some content covering the IBM platform components, it is necessary to leverage the IBM documentation to access the complete set of information. One of the most useful information

channels for IBM products is through the set of IBM Redbooks (www.redbooks.ibm.com/).

2 SAP Enterprise POS Overview

12 November 2010

WebSphere Application Server WebSphere Application Server (WAS) is IBM’s family of Java EE application server. In a SAP Enterprise POS system landscape, WAS is used to host the SAP Enterprise POS Java EE application and its components. As a Java EE application server, WAS provides the runtime environments and services required by SAP Enterprise POS. In addition, WAS provides various services that improve system performance, scalability, and availability. For instance, WAS supports data source pooling that minimizes the overhead of making database connections. WAS also supports server clustering.

Below are the runtime environments and services used by SAP Enterprise POS:

EJB Container

An Enterprise Java Bean (EJB) container provides a runtime environment for EJB’s running in the application server. It handles all aspects of an EJB’s operation and acts as an intermediary between the EJB’s business logic and the services provided by the environment. These services include transaction management, EJB life cycle management, bean instances pooling, resources, access, and so on. For entity EJB, the container also synchronizes the bean’s data with the corresponding persistent data storage. SAP Enterprise POS’s transactional framework (ETF) is implemented using EJBs. The majority of the SAP Enterprise POS business components are executed within the context of an EJB.

Web Container

A Web container implements the Web component interfaces of the Java EE specifications. These interfaces specify a runtime environment for Web components such as Servlet and Java Server Page (JSP). The runtime environment provides services to handle security, Web components life cycle management, transaction deployment, and session management. SAP Enterprise POS’s Configurator and POS Manager are Web application components. The presentation layer of these components is implemented as Java Servlets. WAS’s Web container provides the runtime environment for these Servlets. In addition, it provides the required HTTP/HTTPS access points for the application clients (Web browser).

2 SAP Enterprise POS Overview

November 2010 13

Transaction Management One important goal of the SAP Enterprise POS Transaction Framework is to maintain data consistency. Rather than implementing custom transaction monitoring logic, SAP Enterprise POS takes advantage of the transaction management service of the Java EE application server. By using a consistent programming model described by the Java EE specification, business component developers are not required to handle the transaction explicitly. Transaction boundaries are defined in deployment descriptors and the SAP Enterprise POS framework determines whether to roll back a transaction if an error condition occurs. WebSphere Application Server’s Transaction Manager Supports distributed transactions and can handle transactions that involve multiple transactional resources. Resource Management SAP Enterprise POS employs a number of middleware components. Accessing these components requires connection to various middleware resources such as JMS and JDBC connection factories. WAS provides access to these resources through standard Java EE APIs. To improve performance, WebSphere Application Server implements a resource pooling mechanism to reduce the overhead of making costly connections.

WebSphere Application Server Community Edition WebSphere Application Server Community Edition (WAS CE) is a light-weight Java EE application server. In a SAP Enterprise POS deployment topology that supports Offline Capable Clients (OLC), WAS CE serves as the Java EE application server that hosts the SAP Enterprise POS business components. WAS CE’s low system requirement makes it suitable to be used on an OLC terminal with limited resources.

WebSphere MQ WebSphere MQ is IBM’s family of message-oriented middleware. SAP Enterprise POS utilizes WebSphere MQ as the JMS service provider. It is used to exchange asynchronous messages between SAP Enterprise POS nodes such as head office and stores. SAP Enterprise POS accesses WebSphere MQ through application server managed connection factories. Access to WebSphere MQ is always transactional and is managed by the application server. Types of SAP Enterprise POS messages that are processed using JMS include the following:

Tlog posting

Services request/response

Configuration deployment and confirmation

Data maintenance and synchronization

Event notification

Timer notification

EFT Manager request/response Depending on the message type, JMS messages are sent using either Point-to-Point (queue) or Publish/Subscribe (topic) mode. Integration Points As a means of exchanging information between SAP Enterprise POS and external systems, a set of JMS destinations (queues and topics) are designated as integration points. For example, an external system can subscribe to a specific JMS topic to receive all Tlog messages. Note: Offline Capable Client (OLC) does not support JMS messaging.

2 SAP Enterprise POS Overview

14 November 2010

DB2 DB2 is IBM’s relational database management system (RDBMS). It is the primary persistent data storage of SAP Enterprise POS. SAP Enterprise POS data stored in the database includes:

Master data

Configuration data

Tlog data

Application state information

Register and safe management data Master Data Replication SAP Enterprise POS is a distributed system. SAP Enterprise POS master data resides on all nodes of a deployment topology. To ensure data consistency at all SAP Enterprise POS nodes, the SAP Enterprise POS Master Data Import (MDI) component uses DB2’s data replication feature to synchronize store servers’ databases. When master data (for example, Item) is updated at head office, the change is replicated to the applicable store server databases. This is also used to synchronize store servers with Offline Clients (OLCs), if used.

DB2 Express DB2 Express is a light-weight edition of the DB2 RDBMS. It supports all the core functions of DB2, but leaves out certain features to reduce system requirements. DB2 Express provides persistent storage of the Offline Capable Client (OLC). DB2 Express and WebSphere Application Server Community Edition (WAS CE) together form the light weight middleware stack of the OLC terminal.

Tivoli Provisioning Manager for Software Tivoli Provisioning Manager for Software (TPM4SW) is the software installation and updated infrastructure used to automate software deployment to servers and registers distributed across different environments and locations — quickly, easily and cost-effectively.

Tivoli Monitoring The following components are included in the license but not included in the standard installation packages:

Tivoli Composite Application Manager for WebSphere 6.1

Tivoli Provisioning Manager for Software 5.1.1.1

Enterprise Console 3.9.0.6

Omegamon XE for Messaging v6.0

Tivoli Monitoring v6.1.0.4 FP1

Tivoli Monitoring for Databasesv6.1

These components are installed according to the IBM product documentation.

CA Wily Introscope The Wily Introscope Component is a part of the Standard SAP runtime diagnostic set. Introscope enables predicative and proactive management of the SAP Enterprise POS application environment and automatically detects performance problems before end users are affected. The Introscope agent is installed on all store server and back office server nodes of a SAP Enterprise POS deployment.

2 SAP Enterprise POS Overview

November 2010 15

Solution Manager Diagnostics The Solution Manager Diagnostics is a Java-based tool within the SAP Web Application Server that provides essential functions to centrally monitor and analyze a complete SAP Enterprise POS solution landscape. It especially provides functions to support Java-based components – therefore it is mandatory that an active Java stack is used within your NetWeaver system. The displayed information is gathered by the following agents: Saposcol, Sapccmsr, Introscope Agent, and Component Analyzer. These agents are installed on all store server and back office server nodes of a SAP Enterprise POS deployment.

As of NetWeaver 04 Service Package 10, the Solution Manager Diagnostics is part of the standard NetWeaver installation. It is mandatory to install one Solution Manager Diagnostics system within your SAP solution landscape. All functions of the Solution Manager Diagnostics can be used using a standard Web browser.

For more information about SAP Solution Manager, see service.sap.com/solutionmanager.

2.2 Software Component Matrix The majority of the business processes and scenarios supported by SAP Enterprise POS leverage a common set of components and therefore this document does not contain an explicit listing of components for each supported business process or scenario.

For more information on the Enterprise POS scenario, see service.sap.com/ibc under

Industry Solutions → SAP for Retail → Enterprise POS.

Scenario lists and descriptions are also part of SAP Solution Manager. For more information about SAP Solution Manager, see service.sap.com/solutionmanager.

All business scenarios supported by SAP Enterprise POS are delivered using the SAP Enterprise POS components. However, there are small numbers of scenarios described for SAP Enterprise POS that require components in addition to the SAP Enterprise POS components.

Most SAP Enterprise POS deployments require integration to a 3rd

party payment service provider (United States only) or a 3

rd party payment terminal/subsystem to provide integrated

payment authorization during the transaction. However, it is possible to implement the solution with no integrated payments environment, in which case the retailer needs some form of stand-beside terminal, and the operator is required to enter data into the terminal to indicate the amount required for authorization.

To support payment card authorization in SAP Enterprise POS, it is required to integrate a 3rd

party payment provider (United States only) or a payment terminal/subsystem deployed on the register. Integration development is almost always required to integrate the payments environment into SAP Enterprise POS using one of the two defined extension points: Transnet EFT APM (for United States only) or Payment terminal User Exit.

2 SAP Enterprise POS Overview

16 November 2010

2.3 System Landscape A productive system landscape for SAP Enterprise POS contains the following node types:

Node Type Description

Standard Register Customer and operator facing device

OLC Register Customer and operator facing device (optional)

Mobile POS device Operator facing device (optional). Usage limited as per Product Availability matrix to US/Canada

Store Server Deployed in the store for Local Store Server topology and at Head Office in the Remote store server topology. Deployed onto two hosts as app server/db server pair in Remote Store Server topology and onto a single host in the store for the Local Store Server Topology

Back Office Server Deployed in Head Office for all topologies. Usually deployed onto two hosts as an app server/db server pair

Stored Value Server Deployed onto two hosts as an app Server/db server pair. Optional component. Usage limited per Product Availability Matrix to the United States/Canada.

Admin

Tivoli Provisioning Manager Server

The TPM console is deployed onto a dedicated system and also leverages a second system as the depot for the install and upgrade images.

Admin

SAP Solution Manager An instance of SAP Solution Manager is required in all SAP landscapes. The Solution Manager console is installed on a dedicated system. This single instance of Solution Manager can manage all SAP solution elements in the IT landscape.

Integration

SAP Process Integrator (PI)

Required to integrate SAP Enterprise POS with SAP ERP and SAP POS Data Management. Optional when integrating with a non-SAP backend.

The instances of SAP Solution Manager and Tivoli Provisioning Manager are not shown in the individual topology pictures as they are not part of the productive environment for SAP Enterprise POS and are the same for all topologies. SAP PI is also not represented as that is part of the integration architecture and does not vary by SAP Enterprise POS topology.

2 SAP Enterprise POS Overview

November 2010 17

2.3.1 Local Store Server Topology

WA

N

Head OfficeStore

Register

POS Client

OLC Controller

Store Server

POS Server

Back Office Server

POS Server

POS Manager

Configurator

Centralized

Transaction Services

The local store server topology is the nominal topology for SAP Enterprise POS, appropriate for all retailers. In this topology there is a POS server instance in each store with a shared instance of POS Manager at head office. The Configurator, Centralized Transaction Services as well as a backup instance of the POS server are also installed on this head office system.

It is possible (and recommended) to have some registers deployed as Offline Capable in this topology. The portion of registers in each store deployed as OLC is determined by a large number of factors, but the solution enables all combinations: All OLC, all standard, and a mixture of standard and OLC.

Mobile POS is an optional in-store component that can be deployed in the local store server topology. Consult PAM for all software components as the Mobile POS is currently only available in English and restricted for use in the United States and Canada only.

The POS Client uses the instance of the POS server on the store server node as its primary source for transaction processing logic. If the POS Client cannot connect to the POS server on the store server, the secondary target is the instance of POS server that is located on the back office server (at the head office). If the POS Client can’t connect to that instance, then the tertiary target is the OLC Controller (if deployed on the register).

Physical System Landscape – Local Store Server Topology

Some or all of the registers in each store should be deployed as OLC.

Single dedicated physical server in each store. Note that at this time, the standard solution is not certified to operate the standard POS Client on the same host as the POS server.

System at head office is deployed onto two hosts (back office application server and back office database server). For small retailers it is possible to have a single back office server hosting both the application and database.

2 SAP Enterprise POS Overview

18 November 2010

SAP SMD SAP Solution Manager Diagnostics

IBM WAS CE IBM WebSphere Application Server – Community Edition

IBM WAS IBM WebSphere Application Server

IBM WMQ IBM WebSphere MQ

IBM TPM4SW IBM Tivoli Provisioning Manager for Software

IBM JRE IBM Java Run Time Environment

2.3.2 Central Store Server Topology

WA

N

Head OfficeStore

Register

POS Client

OLC Controller

Store Server

POS Server

Back Office Server

POS Manager

Configurator

Centralized

Transaction Services

2 SAP Enterprise POS Overview

November 2010 19

The Central Store Server topology is an alternate topology that is possible with SAP Enterprise POS. This topology is suitable only for a small subset of retailers as it relies heavily on the Wide Area Network (WAN) infrastructure, which is one of the elements of most retail IT infrastructures with the highest failure rate.

In the Central Store Server topology, there is no server in the store. POS transaction processing logic is housed on the store server, which is physically located in the retailer’s data center or head office. This adds a significant load to the WAN and also means that perceived POS responsiveness is directly dependant on the latency of the WAN (the larger the inherent latency, the slower the POS is perceived to be by the operator). In this topology, it is strongly recommended that some or all of the POS devices in the store be provisioned with the Offline Capable controller, enabling them to process transactions in the event of a WAN failure.

One of the benefits of this topology is that the transaction information is never in the store since the transaction occurs on the store server in the data center. This leads to a lower probability of data loss. The store server in the data center supports multiple stores, which lowers the total cost of ownership when using SAP Enterprise POS in this topology because there is no need for a separate device for each store, but also because system maintenance in a data center is considerably less expensive than maintenance that must be executed in a store.

As mentioned previously, this topology incurs a greater dependence of SAP Enterprise POS performance on WAN latency, so this technical aspect must be considered before this topology can be selected. Further, there is larger WAN bandwidth consumption in this topology when compared with the local store server topology. Finally, it should be noted that Mobile POS is not supported in this topology.

This topology targets retailers with small footprint stores (1 or 2 registers) with a reliable WAN that has low latency.

Physical System Landscape – Central Store Server Topology

Some or all of the registers in each store should be deployed as OLC.

Store server system in the data center is deployed onto two hosts (store application server and store database server). Larger retailers may choose to implement multiple store server pairs (APP+DB). For small retailers it may be appropriate to have a single store server hosting both APP and DB.

Back office system at head office is deployed onto two hosts (back office application server and back office database server). For small retailers it may be appropriate to have a single back office server hosting both APP and DB.

20 November 2010

SAP SMD SAP Solution Manager Diagnostics

IBM WAS CE IBM WebSphere Application Server – Community Edition

IBM WAS IBM WebSphere Application Server

IBM WMQ IBM WebSphere MQ

IBM TPM4SW IBM Tivoli Provisioning Manager for Software

IBM JRE IBM Java Run Time Environment

3 Implementation Sequence

November 2010 21

3 Implementation Sequence You can find all documents relevant for the Enterprise POS Business Scenario including the SAP for Retail Master Guide, scenario descriptions and configuration documentation at service.sap.com/ibc under Industry Solutions → SAP for Retail → Enterprise POS.

3.1. Overall Implementation Sequence SAP Enterprise POS projects must implement three landscapes following the best practice of all SAP projects. An implementation project incorporates a development landscape (DEV), a testing and quality assurance landscape (TEST) and a production landscape (PROD).

At this time, promotion of code and configuration (customization) between landscapes is a manual process and requires careful management during the project.

We recommend you ensure that the IBM Tivoli Provisioning Manager and SAP Solution Manager are installed before creating any further landscapes. The SAP Enterprise POS installation documentation provides all the details needed to deploy the operational software into any of the following landscapes.

DEV Landscape The DEV landscape is the first to be deployed and is leveraged early in the project and continually throughout the implementation project. A fairly minimal landscape is required, just one or two store servers with a few registers on each. The DEV landscape must match production topology and technology but does not implement the back office server as an APP/DB pair.

The hardware leveraged is considerably less powerful (and therefore less expensive) than is required for the PROD landscape. It must be clear that performance can’t be measured using the DEV landscape.

While there are variations in implementation projects, it is common to set up DEV before the master data integration with the customers ERP system is in place. The DEV system can provide value early in the project implementation cycle using test or sample data.

The DEV landscape is leveraged for the development of the integration to the payments system and may also be leveraged for other extension development.

The landscapes (DEV, TEST, and PROD) do not include their own instances of Solution Manager or Tivoli Provisioning Manager. We recommend that these components are installed early in the implementation project.

3 Implementation Sequence

22 November 2010

TEST Landscape The TEST landscape is deployed during the early part of the realization phase of the implementation project (about 1/3 way into realization is common). The TEST landscape must match the targeted topology and technology. The TEST landscape has more systems, to support the larger test team.

Some projects implement TEST at the sizing required for PROD; however this is not necessary as PROD can be used for final implementation phase performance validation. However, once the system has gone live, it is useful to have TEST sized large enough to support realistic volume and performance scenario validation.

Integration to ERP for master data must be present to support later stage testing.

Technical monitoring (Tivoli and Solution Manager) must be set up on the TEST environment. This helps to develop expertise required in production, but can also detect issues in the TEST landscape during the test phase that the testers may not notice ( for example, certain exceptions may be there that have no visible impact to the testers but are recorded in the logs).

PROD Landscape The PROD Landscape is not deployed until the later stages of the realization phase. The most significant use of PROD during the implementation phase is for volume and performance validation.

Of course, the PROD landscape must be fully sized as per the sizing guide and performance validation undertaken to confirm the sizing guideline produced through the sizing guide.

Tivoli Provisioning Manager must be leveraged to manage the promotion of new software (ESB, service pack, and so on) to all nodes of all landscapes. It is not necessary to have separate instance of Tivoli servers for each landscape, one instance serves all landscapes.

Similarly, only one instance of SAP Solution Manager is required. This instance of Solution Manager serves all three landscapes (DEV, TEST, PROD).

SAP Enterprise POS configuration must also be managed carefully and follow a structured promotion process between landscapes. We recommend you have a separate instance of Configurator deployed into each landscape. This has the benefit of ensuring all landscapes match production.

Once testing of a configuration is completed in DEV, then configuration profiles must be exported to XML from the SAP Enterprise POS Configurator in DEV and imported into the Configurator instance in TEST. Similarly from TEST to PROD, once acceptance testing is completed in TEST. We recommend you archive the exported configuration profiles in an external version control system of some form. This is a prudent disaster and error recovery policy.

4 Solution-Wide Topics

November 2010 23

4 Solution-Wide Topics This section outlines several topics that span the solution and are critical to consider when planning a SAP Enterprise POS implementation project. This document is not intended to provide a complete Implementation Guide, but rather to highlight the most critical issues that are common to most projects.

4.1 Inter Node Communications This section describes the communication architecture of the overall solution, breaking it down by node type. You must understand the inter node communications protocols to ensure that the Wide Area Network is appropriately configured to enable SAP Enterprise POS to operate correctly.

There are four protocols to manage for inter node communication in production, and a further set of protocols for system administration, monitoring and diagnostics.

Production Protocols RMI-IIOP: Protocol specifics are configured properties of the relevant WebSphere Application Server nodes and WebSphere RMI client nodes. The SAP Enterprise POS installation process preconfigures RMI communication to use the default settings of IBM WebSphere Application Server. Details of the WebSphere communications protocols can be found in the appropriate IBM Redbook. For more information, see www.redbooks.ibm.com/Redbooks.nsf/RedbookAbstracts/sg247304.html?Ope

nDocument.

JMS: Protocol specifics are configured properties of the relevant WebSphere MQ nodes. The SAP Enterprise POS installation process preconfigures the JMS communication to use the default settings of IBM WebSphere MQ. For more information, see

www.redbooks.ibm.com/abstracts/sg247128.html?Open.

DB2 Replication: Protocol specifics are configured properties of all relevant IBM DB2 nodes. The SAP Enterprise POS installation process preconfigures the DB2 replication protocols to use the default settings of IBM DB2. For more information, see

www.redbooks.ibm.com/abstracts/sg246828.html?Open.

HTTP/HTTPS: POS Manager is a browser based application deployed at head office but intended for use by store personnel. Any system that is used to access POS Manager requires HTTP/HTTPS protocol connectivity to the back office server. It is common practice to access POS Manager from a register directly.

System Administration Protocols Tivoli Provisioning Manager for Software: Protocol specifics are configured in the relevant TPM4SW nodes. SAP Enterprise POS uses the default. For more information, see www.redbooks.ibm.com/abstracts/sg247261.html?Open.

Solution Manager Diagnostics: Protocol specifics are configured in the relevant SMD nodes.

4 Solution-Wide Topics

24 November 2010

For more information about SAP Solution Manager, see service.sap.com/solutionmanager.

Standard Register The POS Client on the standard register communicates only using RMI-IIOP to the POS Server instance on the store server (primary) and the back office server (secondary) to access POS transaction processing business logic.

Offline Capable Register The POS Client on the OLC register communicates using RMI-IIOP to the instance of POS Server on the store server node (primary) and the back office server (secondary) and to the OLC

Controller on the OLC registers itself (tertiary) to access POS transaction processing logic.

To reconcile after operating in OLC mode, the OLC server communicates transactions to the store server using RMI-IIOP

The store server pushes master data to the OLC Controller using DB2 replication.

Store Server The store server communicates using JMS with the head office server for Transaction (TLOG) posting as well as for service request/responses. The service

requests include transaction retrieval and customer/loyalty lookups.

The head office server pushes master data to the store server using DB2 replication.

4.2 Integration Point of sale solutions are integrated into the retailer’s landscape in all cases. Point of sale cannot viably be operated without some form of integration. Further, experience has shown that the integration stream is the project stream that causes overall implementation project delays. It is critical to consider the technical, functional, and scheduling aspects of integration early in a POS implementation project.

4 Solution-Wide Topics

November 2010 25

SAP Enterprise POS has extension points embedded in the solution to enable integration of the standard solution into any landscape without modifying the base product. It is also possible (and common) to leverage other elements of the SAP Solution portfolio to integrate SAP Enterprise POS into a retailers IT landscape. Specifically, SAP NetWeaver Process Integration (PI) is commonly used to transform master data that is inbound to SAP Enterprise POS (Item, Price, and so on) as well as TLOG data that is outbound from SAP Enterprise POS. If there is a need for aggregated TLOG data, then SAP POS Data Management is the appropriate component to leverage as there are user exit and extension points specifically to support such aggregation.

4.2.1 Electronic Funds Transfer (EFT) To complete the authorization process for payments within SAP Enterprise POS, it is required to integrate it with an external component or service.

SAP Enterprise POS supports two different paradigms to enable EFT payments, both of which ultimately require integration with 3

rd party software or services to complete the

authorization process. The fundamental difference between the two approaches is the amount of payments logic that is managed by SAP Enterprise POS versus the 3

rd party

system and more tactically, which system manages the direct interaction with the payment peripheral devices. Both models provide similar customer and operator experience where the payment process is an integral part of the overall transaction process at the register.

Integrated EFT was the original infrastructure contained in SAP Enterprise POS. SAP Enterprise POS does not itself contain the appropriate business logic or device integration to support the wide variety of payment technologies, infrastructures, regulations, and business models in different regions of the globe. Therefore, support for Stand Beside EFT was added to SAP Enterprise POS to enable the solution to operate effectively in regions outside of North America. Canada has adopted chip and pin regulations (similar to the United Kingdom), the Integrated EFT approach does not have the required function to support Canada, leaving the United States as the only region where the use of Integrated EFT is appropriate.

The result is that for most regions and customers, the use of the Stand Beside EFT model is appropriate because it allows the integration of 3

rd party payment subsystems, which do have

the appropriate support local payment technologies and business models into the solution without requiring custom development of SAP Enterprise POS. Using this model also ensures that a single version of SAP Enterprise POS can be leveraged in multiple regions by integrating regional payments systems using the same user exit.

Stand Beside EFT with Payment Terminal/Subsystem

The Stand Beside EFT model is one where the SAP Enterprise POS does not interact at all

with the payment peripherals, but rather interacts with a payment subsystem that is active on

the register. The payment subsystem contains all of the code required to interact with the

payment peripherals (and the customer). The payment subsystem also includes the logic

required to build the authorization request for the acquirer and to communicate with the

acquirer. Everything related to EFT payments abstracts from the POS in this model.

These 3rd

party systems are regional and incorporate specific capabilities and requirements

of each region (for example, Chip and Pin requirements in the United Kingdom and Canada).

4 Solution-Wide Topics

26 November 2010

By abstracting the payment process to the payment subsystem, it is possible to configure the system so that the POS is not involved in processing, storing, or transmitting cardholder data and excludes PCI-DSS.

When running in the Stand Beside EFT mode, the payment subsystem is connected directly with the payment peripherals including Magnetic Stripe Reader (MSR), Pin pad, Magnetic Ink Character Recognition (MICR) reader. The payment subsystem is responsible for interacting with these peripherals to gather the appropriate data and also to send the authorization requests to the acquirer. In this mode, SAP Enterprise POS has no knowledge of the details of the payment process and effectively requests the payment subsystem to authorize an amount and waits for a response.

The user exit to support payment terminals is physically part of the POS Client. While the user exit specifications can support variations on the model described above (specifically allowing the POS Client to gather payment instrument data and then pass this through as part of the authorization request) there needs to be a strong justification to implement such a variation. Once the POS Client participates in gathering cardholder data, it needs to be included in the scope of a PCI-DSS Audit and encryption needs to be enabled (See SAP Enterprise POS Security Guide).

For more information on the payment terminal user exit, see the SAP Enterprise POS EFT User Exit Technical Reference in service.sap.com/retail under Expert Knowledge

Corner → Sales → SAP Enterprise POS.

The Stand Beside EFT mode is appropriate for most regions and customers.

4 Solution-Wide Topics

November 2010 27

Integrated EFT Integrated EFT is an option only for some customers in the United States and some regions of Latin America. Integrated EFT is not supported in Europe, Canada, and most of Asia.

The Integrated EFT model is one where the POS Client manages all interaction with the

payment peripherals and the customer to acquire all the information needed to support the

authorization request. The information gathered from the payment peripherals is sent to the

SAP Enterprise POS Server component, which uses this information in addition to

information from the POS transaction to compose a generic EFT authorization request that is

fully qualified (has all the data required by the acquirer to approve or decline the authorization

request).

In this mode, it is necessary to have a user exit extension in the form of a Transnet APM (Application Programming Module) to connect the EFT Manager of the POS Server with a payment service provider (also known as an acquirer in some markets). Connections from the Transnet APM to the service provider are based on IP Sockets, with the protocol and the message formats being specified by the acquirer.

In the Integrated EFT model, the logic to interact with all payment peripherals and parse the

acquired data codes directly in the POS Client. The logic to interact with chip readers is not

present in SAP Enterprise POS, nor is it planned to be implemented in future releases. The

logic and data structures required to deal specifically with the Chip and Pin processes and

regulations is not present in SAP Enterprise POS, nor is it planned to be implemented in

future releases.

4 Solution-Wide Topics

28 November 2010

The POS is directly involved in the processing, storage and transmission of cardholder data,

and the POS is subject to PCI-DSS. Therefore the required encryption, access control, and

audit trails for PCI-DSS compliance must be present and enabled in the POS to leverage the

integrated EFT model. Where possible, it should be encouraged to leverage the Stand

Beside EFT model for all new customers (including those in the United States).

4.2.2 Master Data (Item) and TLOG All data integration to SAP Enterprise POS is processed using the SAP Enterprise POS back office server in the data center. The back office server is responsible for directing data to the appropriate store server nodes. Similarly TLOGs from all stores flow up to the data center and are exported from the back office server. One of the fundamental differentiators of SAP Enterprise POS from SAP POS and most other competitive solutions is that there is no polling required.

In almost all projects an instance of SAP NetWeaver Process Integration (PI) is involved. The integration of SAP Enterprise POS with SAP ERP and SAP POS Data Management both are executed using NetWeaver PI. In the case of an environment with a non-SAP backend, the use of PI is optional but recommended.

SAP has implemented intermediate steps in PI that support the ARTS XML industry standard message formats. This can simplify integration of SAP Enterprise POS with non-SAP backend systems.

4 Solution-Wide Topics

November 2010 29

Operational/Master data is extracted from SAP ERP using IDocs or Enterprise Services and processed in PI into formats required for SAP Enterprise POS. Operational data for any and all stores drops on the SAP Enterprise POS back office server and the Master Data Import process (MDI) of SAP Enterprise POS manages the rest of the processing and distribution automatically. For low volume environments, it is possible to turn off MDI and leverage a JMS based distribution approach.

TLOGs produced by SAP Enterprise POS are exported in real time using IBM WebSphere MQ directly into SAP PI where the data formats into the structure required by POSDM and posted directly into the POS Inbound Processing Engine (PIPE) of POSDM using an RFC or an Enterprise Service. This inbound service on POSDM is available together with the outbound services on the ERP side. You must recognize that POSDM is the entry point for TLOGs into the SAP landscape and that the standard integration content for TLOGs only supports POSDM. If a retailer wants to implement SAP Enterprise POS with and SAP backend without POSDM, there is extensive integration development required in the project and must be strongly discouraged.

4.2.3 Customer Order Integration with SAP Retail Store You can directly integrate Customer Order capabilities of SAP ERP, usually via SAP In Store Merchandise and Inventory Management with SAP Enterprise POS. The implementation of this scenario requires SAP Retail Store to be in place as well as POSDM and PI.

Customer Order Integration is supported up to SAP Enhancement Pack 4 for SAP ERP 6.0 only.

The customer order function of SAP ERP is accessible from SAP Enterprise POS using an embedded web browser in the POS. Access to customer orders is configured as a menu option in SAP Enterprise POS. Once connected to SAP ERP, the POS operator can create a new order, retrieve an existing order, or modify an existing order. Once the operator has finalized the actions in SAP ERP, the order data is passed back to SAP Enterprise POS including the required down payment for the customer order. The operator can enter any other items into the transaction and then tender out the transaction and the customer order status in SAP ERP is updated.

The deployment of this solution includes many integration points and requires synchronized configuration of SAP Enterprise POS and SAP ERP to ensure smooth integration.

For more information on this scenario, see service.sap.com/ibc under Industry

Solutions → SAP for Retail → Cross Channel Customer Order Management.

4 Solution-Wide Topics

30 November 2010

4.3 Monitoring

The following is the list of Tivoli components that are included in the SAP Enterprise POS Bundled software license:

Tivoli Composite Application Manager for WebSphere 6.1

Tivoli Provisioning Manager for Software 5.1.1.1

Tivoli Enterprise Console 3.9.0.6

Tivoli Omegamon XE for Messaging v6.0

Tivoli Monitoring v6.1.0.4 FP1

Tivoli Monitoring for Databases v6.1

The Tivoli monitoring infrastructure is an optional element of the SAP Enterprise POS solution and is not installed as part of the default installation scripts. It is strongly recommended that the Tivoli monitoring infrastructure is deployed into the production and test environments.

As of Release 3.1 SP3, SAP Solution Manager 7.0 (SP18) provides functions to support certain SAP operation standards such as E2E Root Cause Analysis and a basic System Monitoring for SAP Enterprise POS. The main focuses for the current release (SAP Enterprise POS as well as SAP Solution Manager) are on specific diagnostics capabilities for SAP Enterprise POS application for the head office server as well as the store server applications. A part of these diagnostics capabilities are implemented using CA Wily Introscope, which is considered as an integral part of SAP Solution Manager.

SAP Solution Manager is installed in a similar way to any SAP NetWeaver-based product using SAP installation tools (SAPINST). In addition CA Wily Instroscope Enterprise Manager is installed, on the same server environment as SAP Solution Manager.

On the managed system side (SAP Enterprise POS head office server and store server) the deployment of the SAP SMD agent is required. The installation of this agent is part of the installation procedure of SAP Enterprise POS store server. There is no SMD agent to be installed on the POS Clients. The final deployment (activation) can be managed from the SAP Solution Manager.

The Tivoli monitoring infrastructure has been licensed for use with SAP Enterprise POS only.

Monitoring: A combination of SAP support tools (for example, SAP Solution Manager) and Tivoli Monitoring must be used. SAP Solution Manager provides capabilities for system (SAP software stack) and business process monitoring. The monitoring with SAP Solution Manager is using the same infrastructure (SAP Solution Manager, CA Wily, SMD agents) required for diagnostics.

Diagnostics: The diagnostics capabilities of SAP Solution Manager (including CA Wily Introscope) are used for root cause analysis. With SAP Solution Manager, SAP provides a support platform, which is used by SAP support engineers as well as the retailer’s support organization for safe access to the production environment for root cause analysis as part of the incident management process. For a detailed analysis we also consider tools and functions, which are part of the SAP Enterprise POS application and the underlying IBM Websphere application server.

4 Solution-Wide Topics

November 2010 31

Finally we consider all functions in SAP Solution Manager to support the Application Lifecycle Management primarily for SAP delivered products and application. SAP Solution Manager is not intended for the infrastructure management, for example infrastructure-level monitoring. This is where Tivoli Monitoring can be used. In the provided bundling of IBM Tivoli Monitoring (ITM) it includes agents to deeply monitor WebSphere Application Server, WebSphere MQ, and DB2, along with Operating System aspects.

To achieve a full-featured systems management solution, we recommend that all of these components be used. We recommend working with a qualified Tivoli Monitoring organization to properly set up and tune the usage of ITM.

For more information on Tivoli Monitoring, see “Run SAP for Retail” Best Practice for Solution Operations, Manage Operations for SAP Enterprise POS at

http://service.sap.com/~sapidb/011000358700000667612009E.

For more information on "Run SAP for Retail" and additional Operations Best Practice documents, for example Manage Operations for POS Inbound or POS Download, see Run SAP for Retail BPX Wiki page at http://wiki.sdn.sap.com/wiki/display/Retail/Run+SAP+for+Retail

4.4 Project and Implementation Team Considerations This document is not intended to provide a complete guideline for implementation project teams. However, this section includes some high level considerations regarding the composition of the implementation team as well as some other more general considerations. This list is not intended to be comprehensive nor is unique to SAP Enterprise POS, however, the concepts have surfaced regularly in the past and considering these during the planning phase increases the probability of project success.

Skills/Roles required during a SAP Enterprise POS implementation project:

Point of Sale Business Analysts

SAP Enterprise POS Configuration consultants

Deployment/Technical consultants

Quality Assurance

IBM platform specialists (WebSphere, MQ, DB2)

Integration/Extension developers

Project management

It may not be required for resources with these skills to participate in every phase of a project, but they are required at one or more points of the project.

There are some common pitfalls that have been observed on previous SAP POS implementation projects that must be avoided to increase the success probability of a SAP Enterprise POS implementation project. These include:

Lack of business involvement

Projects can become stalled at User Acceptance if the business is not actively engaged earlier in the project

4 Solution-Wide Topics

32 November 2010

Re-creating the present – exactly

Users and sponsors may begin to question the value of the large investment in a new solution if it appears and behaves exactly the same as the previous solution, including replicating the weaknesses in the previous solution.

Aiming too high or over committing to the business for the first release

The business can have a large backlog of requests that could not be delivered with the previous solution. It is critical to limit the scope of the implementation project, obtain SAP Enterprise POS live and then phase in new capabilities.

Over aggressive or optimistic scheduling

This one is clearly not unique to POS deployments, but dates can be committed too early in the project without sufficient allocation for risks or unknowns.

Lack of planning for end user training

One of the defining characteristics of Point of Sale is that there are a large number of users and casual users. It is critical to plan training for the end users or the solution may not be successful once it is in production.

Not obtaining buy in from store managers or operators (what is in it for me)

The leaders in each store are critical to the success of the solution. Change is not welcome in the stores, you must emphasize the benefits for the local leaders so that they can act as change agents for the staff on the ground

Lack of preparation for internal help desk

SAP Enterprise POS includes concepts and technologies that are quite advanced compared to the systems that are in place. The internal help desk needs to be prepared with knowledge and practical experience before the solution goes into production.

PI integration content needs to be validated against all configuration changes

The data produced by the systems can be directly affected by configuration of the systems. There can be a large number of minor configuration changes that result from user acceptance testing (more when the business has not been heavily involved early in the project), and these changes may affect the PI integration content. Regular end to end testing is required throughout the project cycle

Under sizing or lack of iterative performance testing

The results of the sizing guideline are not exact. It is critical to validate the sizing during the implementation project with performance and volume testing.

Many of these considerations are not the direct responsibility of the implementation team; the retailer assumes these directly. However, it is important for the implementation team to ensure that they are addressed or the overall success of the project can be directly impacted.

5 References

November 2010 33

5 References Information Repository Retail@BPX

The recommended single point of access to all documents mentioned in this Master Guide is the SAP Enterprise POS Wiki page on the Business Process Expert Community (BPX). BPX is the online community platform provided by SAP centering on business processes and SAP business applications, such as SAP Enterprise POS.

Title Where to Find

SAP Enterprise POS on BPX http://wiki.sdn.sap.com/wiki/display/R

etail/SAP+Enterprise+Point+of+Sale

List of SAP Documents

Title Where to Find

SAP Enterprise POS Operation Guide, Installation Guide, Upgrade Guide, Patch Guide,

Disaster Recovery Guide,

Fiscal Printer User Exit Technical Reference Guide, and Release Notes

service.sap.com/instguides under Industry

Solutions → Industry Solution Guides → SAP for Retail → SAP Enterprise Point-of-Sale

SAP Enterprise POS and SAP for Retail Security Guides

service.sap.com/securityguide under SAP

for Retail

SAP Education Curriculum for SAP Enterprise POS

sap.com/services/education/catalog/ind

ustry under Retail → SAP Enterprise POS

SAP Business Maps - information about applications and business scenarios

service.sap.com/businessmaps

SAP for Retail Business Scenario Documentation

service.com/ibc under Industry Solutions →

SAP for Retail

SAP Enterprise POS Application Help help.sap.com under SAP for Industries → SAP

for Retail → SAP Enterprise Point-of-Sale

SAP Enterprise POS Configurator Documentation

See Application Help under Head Office Functions → Configurator

SAP Enterprise POS Store Manager Documentation

See Application Help under Head Office Functions → POS Manager

SAP Enterprise POS Technical Product Reference

See Application Help under Technical Product Reference

SAP Enterprise POS Sizing Guide Sizing SAP Enterprise Point-of-Sale (POS), Version 3.1

SAP Network Sizing Guide Front-End Network Requirements for SAP Business Solutions

5 References

34 November 2010

SAP Enterprise POS Performance Tuning Guide

service.sap.com/retail under Expert

Knowledge Corner → Sales → SAP Enterprise POS

EFT User Exit Technical Reference service.sap.com/retail under Expert

Knowledge Corner → Sales → SAP Enterprise POS

POS Integration Connectivity Kits Promoted Integration Scenario:

wiki.sdn.sap.com/wiki/display/CK/Home

under Connectivity Kit for Integration Scenario 'POS Integration (SOA based integration)

Alternative Integration Scenario:

wiki.sdn.sap.com/wiki/display/CK/Home

under Show children → Exchange Infrastructure - SAP POS Integration (IDoc based integration)

SAP Enterprise POS Integration Use Case Documentation

http://wiki.wdf.sap.corp/display/CKSaleCashTender/Use+Case+Documentation

SAP Stored Value Program Installation Guide and Upgrade Guide

service.sap.com/instguides under Industry

Solutions → Industry Solution Guides → SAP for Retail → SAP Enterprise Point-of-Sale

―Run SAP for Retail‖ Best Practice for Solution Operations: Manage Operations for SAP Enterprise POS

http://service.sap.com/~sapidb/011000358700000667612009E

"Run SAP for Retail" BPX Wiki page http://wiki.sdn.sap.com/wiki/display/Retail/Run+SAP+for+Retail

5 References

November 2010 35

List of IBM Documents

IBM Redbooks are an essential source of technical and practical information for IBM software. SAP does not republish documentation content on the IBM components embedded in SAP Enterprise POS, so it is important for SAP Enterprise POS implementation teams to reference the IBM Redbook documentation.

Title Where to Find

IBM Redbook Home www.redbooks.ibm.com/

IBM Tivoli Provisioning Manager

www.redbooks.ibm.com/abstracts/sg247261.html?Open

IBM WebSphere Application Server System Management & Administration

www.redbooks.ibm.com/Redbooks.nsf/RedbookAbstracts/sg247304.html?OpenDocument

IBM WebSphere MQ Fundamentals www.redbooks.ibm.com/abstracts/sg247128.html?Open

DB2 Replication www.redbooks.ibm.com/abstracts/sg246828.html?Open

DB2 Deployment Guide www.redbooks.ibm.com/abstracts/sg247653.html?Open

Database Partitioning, Table Partitioning, and MDC for DB2 9

www.redbooks.ibm.com/abstracts/sg247467.html?Open

6 The Main SAP Documentation Types

36 November 2010

6 The Main SAP Documentation Types The following is an overview of the most important documentation types that you need in the various phases in the life cycle of an SAP solution.

Documentation types in the software life cycle

ImplementationImplementation

Master Guide

Configuration

DocumentationRelease Notes

Component

Installation Guide

Component

Upgrade Guide

Upgrade Master Guide

OperationOperation UpgradeUpgrade

Solution Management

Guide

Implementation Guide (IMG) Delta and Upgrade IMG

Security Guide

SAP Library

SAPterm

Cross-Phase Documentation

SAPterm

SAPterm is SAP’s terminology database. It contains SAP-specific vocabulary in over 30 languages, as well as many definitions and glossary entries in English and German.

Target group:

Relevant for all target groups

Current version:

Located in the SAP Help Portal at help.sap.com → Additional Information → Glossary

(direct Access) or Terminology (available as terminology CD)

In the SAP-System in transaction STERM

SAP Library

The SAP Library is a collection of function and process-oriented documentation for SAP components. The SAP Library also contains the Business Scenario Descriptions.

Target group:

o Consultants

o System administrators

o Project teams for implementations or upgrades

Current version:

o Located in the SAP Help Portal at help.sap.com

6 The Main SAP Documentation Types

November 2010 37

o Located in the SAP Service Marketplace at service.sap.com/ibc (only the Business Scenario Descriptions)

Security Guide

The Security Guide describes the settings for a medium security level and offers suggestions for raising security levels. A collective security guide is available for the SAP NetWeaver technologies like SAP Web Application Server (SAP Web AS). This document contains general guidelines and suggestions about system security. Other technologies and individual applications have a Security Guide of their own.

Target group:

o Technology consultants

o Solution consultants

o Project teams for implementations or upgrades

Current version:

o Located in the SAP Service Marketplace at service.sap.com/securityguide

Implementation

Master Guide

The Master Guide is the starting point for implementing an SAP solution. It lists the required SAP components and third party applications that are required for each Business Scenario. It provides scenario-specific descriptions of preparation, execution, and follow-up of an implementation. It also offers references to other documents, such as Component Installation Guides and SAP Notes.

Target group:

o Technology consultants

o System administrators

o Project teams for implementations

Current version:

o Located in the SAP Service Marketplace at service.sap.com/instguides

Component Installation Guide

The Component Installation Guide describes the technical implementation of an SAP component, taking into account the combinations of operating systems and databases. It does not describe any business-related configuration.

Target group:

o Technology consultants

o Project teams for implementations

Current version:

o Located in the SAP Service Marketplace at service.sap.com/instguides

Configuration Documentation in SAP Solution Manager

SAP Solution Manager is a tool with various functions, one of its main functions being the configuration of SAP solutions and Business Scenarios. It contains IMG activities, transactions, and so on, as well as documentation. Instead of the configuration documentation in SAP Solution Manager, there may be separate Business Scenario Configuration Guides in the SAP Service Marketplace for earlier shipments of the Business Scenarios.

Target group:

o Solution consultants

o Project teams for implementations

6 The Main SAP Documentation Types

38 November 2010

Current version:

o In SAP Solution Manager

o Located in the SAP Service Marketplace at service.sap.com/ibc

Production Operation

Solution Operation Guide

The Solution Operation Guide is the starting point for operating an SAP solution. The guide refers users to the tools and documentation that are needed to carry out various tasks, such as monitoring, backup/restore, master data maintenance, transports, and tests. It also refers users to other documents, for example the SAP Library, the Master Guide, and the Component Management Guides.

Target group:

o System administrators

o Technology consultants

o Solution consultants

o Project teams for implementations or upgrades

Current version:

o Located in the SAP Service Marketplace at service.sap.com/instguides

Upgrade

Upgrade Master Guide

The Upgrade Master Guide is the starting point for upgrading the Business Scenarios of an SAP solution. It provides scenario-specific descriptions of preparation, execution, and follow-up of an upgrade. It also refers to other documents, such as the Component Upgrade Guides and SAP Notes. Instead of an Upgrade Master Guide, there may be several Business Scenario Upgrade Guides or a Solution Upgrade Guide for earlier shipments of the Business Scenarios of an SAP solution.

Target group:

o Technology consultants

o Project teams for upgrades

Current version:

o Located in the SAP Service Marketplace at service.sap.com/instguides

Component Upgrade Guide

The Component Upgrade Guide describes the technical upgrade of an SAP component, taking into account the combinations of operating systems and databases. It does not describe any business-related configuration.

Target group:

o Technology consultants

o Project teams for upgrades

Current version:

o Located in the SAP Service Marketplace at service.sap.com/instguides

Release Notes

Release notes are documents that contain short descriptions of new features or changes in an SAP component since the previous release. Release notes about ABAP developments enable the SAP system to generate delta and upgrade IMGs.

Target group:

o Consultants

6 The Main SAP Documentation Types

November 2010 39

o Project teams for upgrades

Current version:

o Located in the SAP Service Marketplace at service.sap.com/releasenotes