Vous êtes sur la page 1sur 59

Configuration Guide for

POS Integration

Based on Integration Content for SAP ERP 6.0, EhP 5


and SAP POS 2.3
Using SAP Services Technology; Store Connectivity 3.0
Document Version: 1.5 - January 2012

SAP AG

Copyright
2011 SAP AG. All rights reserved.
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, SAP BusinessObjects Explorer,
StreamWork, 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.

Configuration Guide for POS Integration

SAP AG

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
Business Objects Software Ltd. Business Objects is an
SAP company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products
and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of Sybase, Inc. Sybase is an SAP company.
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.
The information in this document is proprietary to SAP. No part of this document may be
reproduced, copied, or transmitted in any form or for any purpose without the express prior written
permission of SAP AG.
This document is a preliminary version and not subject to your license agreement or any other
agreement with SAP. This document contains only intended strategies, developments, and
functionalities of the SAP product and is not intended to be binding upon SAP to any particular
course of business, product strategy, and/or development. Please note that this document is
subject to change and may be changed by SAP at any time without notice.
SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the
accuracy or completeness of the information, text, graphics, links, or other items contained within
this material. This document is provided without a warranty of any kind, either express or implied,
including but not limited to the implied warranties of merchantability, fitness for a particular
purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without limitation direct, special,
indirect, or consequential damages that may result from the use of these materials. This limitation
shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has no control
over the information that you may access through the use of hot links contained in these materials
and does not endorse your use of third-party Web pages nor provide any warranty whatsoever
relating to third-party Web pages.

Configuration Guide for POS Integration

SAP AG

Icons
Icon

Meaning
Caution
Example
Note
Recommendation
Syntax
Tip

Document History
Version

Date

Change

1.0

Sept 2011

This version contains content revised from previous POS Integration projects and is
designed to complement the release of SAP POS 2.3.

1.1

Oct 2011

Section 5.2.3.2. has been updated to provide details for the automated configuration
process.

1.2

Nov 2011

Section 5.2.3.2 has been updated to provide a workaround for a limitation in SAP
NetWeaver PI that only allows one-to-one mappings in integration scenarios. New
step is added to the Automated Configuration Process.

1.3

Nov 2011

Section 8.3 Merchandise Hierarchy Download: Clarification of the functionality of the


initial merchandise category download.
Section 8.5 Bonus Buy Download: Clarification on the service to use to transfer
promotional Bonus Buys to the POS.

1.4

Nov 2011

Provided SP version information for the XI CONTENT STORE CONNECT 3.0 and
XI CONTENT GM STORECONNECT 2.0 components in sections 5.2.1 and 5.2.2.
Updated sections 8.1 and 8.5 with references to SAP Notes related to those topics.

1.5

Jan 2012

Added Store Connectivity 3.0 to guide title

Configuration Guide for POS Integration

SAP AG
Icons........................................................................................................................................................................... 4
1

Purpose ...................................................................................................................................................................... 6

Overview .................................................................................................................................................................... 6

System Landscape Overview .................................................................................................................................... 7

SAP POS Landscape Requirements ......................................................................................................................... 7

SAP NetWeaver PI Landscape .................................................................................................................................. 9


5.1

Overview ............................................................................................................................................................. 9

5.2

Set Up Requirements for SAP NetWeaver PI .................................................................................................. 10

5.2.1

System Landscape Directory .................................................................................................................. 10

5.2.2

Integration Repository ............................................................................................................................. 11

5.2.3

Integration Directory ................................................................................................................................ 11

Unicode Communication with Unicode-Enabled SAP ERP System and SAP POS ................................................ 23

Connect Back-End Applications to SAP PI .............................................................................................................. 25

7.1

IDOCs Scenario ................................................................................................................................................ 25

7.2

SAP Services Scenario..................................................................................................................................... 25

Functional Details for Implementing SAP POS Integration Content ........................................................................ 26


8.1

General Information .......................................................................................................................................... 26

8.2

Article Master Data Download .......................................................................................................................... 26

8.3

Merchandise Category Hierarchy Download .................................................................................................... 27

8.4

Promotion Download ........................................................................................................................................ 27

8.5

Bonus Buy Download ....................................................................................................................................... 28

8.6

Employee Master Data Download .................................................................................................................... 29

8.7

Physical Inventory Count Sheet ....................................................................................................................... 29

8.8

POS Transaction Log Data ............................................................................................................................... 30

8.9

Internal Value Mapping ..................................................................................................................................... 30

Appendix A Example of SAP NetWeaver PI Configuration ......................................................................................... 31


Appendix B Store ID Length Discrepancy Issue .......................................................................................................... 43
Appendix C Bonus Buy Information ............................................................................................................................. 46
Appendix D Value Mappings for IDocs ........................................................................................................................ 56

Configuration Guide for POS Integration

SAP AG

1 Purpose
This guide describes the steps to successfully configure the exchange and integration of data between SAP POS and
SAP ERP. It is intended for both technology and application consultants. This guide does not cover configuration of
the SAP POS front-end application. For more information on installing and configuring the SAP POS front-end
application, refer to the installation guides on SAP Service Marketplace at http://service.sap.com/instguides
Industry Solutions Industry Solution Guides SAP for Retail SAP Point-of-Sale.

2 Overview
The Store Connectivity POS Integration content enables retailers to connect a point of sale system to SAP ERP and
SAP NetWeaver Business Warehouse, and to exchange master and transactional data with these systems. The
functionality and strength of SAP ERP, SAP Point-of-Sale (SAP POS), and SAP NetWeaver Business Warehouse
(SAP NetWeaver BW) are combined to support flawless retail sales operations. Integration between these systems is
carried out either through SAP service-oriented architecture, or IDocs technologies where service-oriented
architecture technology is not available. This document focuses on integration content that is created in a landscape
that uses service-oriented architecture. For further information on IDocs-based integration content, refer to the SAP
Business Package for Store Connectivity SAP POS Integration document available at the following location:
http://service.sap.com/retail Expert Knowledge Corner Interfaces POS Integration.
The SAP Point-of-Sale integration scenario includes the movement of data from SAP ERP to the POS system, and
from the POS system to SAP ERP and SAP NetWeaver Business Warehouse. The following table shows the
elements that comprise the data flow in each direction.

Data flow direction

Elements in data flow

SAP ERP to POS system

Defined article and price data: Inventoried and value-only article types in
various article categories (for example, single article, or generic article)
along with their attributes

Merchandise category data including hierarchies: Provides a structure of


the logical grouping of the articles in the ERP system

Bonus buy data with requirements and conditions necessary to define a


specific discount

Promotion data with special prices, and start and end dates for a promotion

Employee Master Data

Physical Inventory Count Sheet data

POS system to SAP ERP and SAP


NetWeaver Business Warehouse

The data transfer from the POS system to SAP ERP and SAP NetWeaver
Business Warehouse consists of POS transactions (often called TLOG, for
Transaction LOG), and may include some or all of the following information:

Sales and returns: Article purchases or returns processed at the POS

Tendering data

Financial transactions: Involving monetary flow recorded at the POS


without movement of goods (for example, cashier withdrawals)

Control transactions: Technical information regarding the behavior of the


POS such as settings that control the opening or closing of the cash
drawer

Physical Inventory Count Sheet

Configuration Guide for POS Integration

SAP AG

3 System Landscape Overview


The following diagram illustrates the system landscape for SAP POS Integration.

The following list shows the required systems for SAP POS Integration:
System
SAP for Retail (SAP ERP 6.0)
SAP POS Data Management (SAP NetWeaver Business Warehouse)
SAP Point-of-Sale
SAP NetWeaver Process Integration

Releases
EA-RETAIL 605
BI_CONT 7.05
2.3
Latest SP

Additionally, you must import the newest CR content. For more information, see SAP Note: 669669.

4 SAP POS Landscape Requirements


This section describes the elements of the POS landscape required for integration with SAP ERP. Depending on your
desired outcome, you may not need to configure all the elements listed.

Element of POS landscape

Description or requirements

File trickle and End-of-Day batch


processing

The SAP POS system can send TLOG files to SAP POS Data Management
(SAP POS DM) through either of the following processes:

File trickling

End-of-day batch processing

The file trickling process is a real-time, TLOG transfer process that generates
ASCII files after every transaction occurs.
Configuration Guide for POS Integration

SAP AG
The end-of-day (EOD) batch process is triggered when the end-of-day
processing is executed on the POS side. This process sends all the
transactions of the business day at one time.
Note
SAP NetWeaver PI does not support switching from the file trickle to EOD
batch processing as a method of receiving data from the POS. You must
choose one method and configure the integration processes accordingly.
SAP POS Store Data Transfer
1
for Retail application setup

The SAP POS system uses the SAP POS Store Data Transfer for Retail
application to move and handle TLOG files originating on the POS side. This
application can be set up in different modes and configurations depending on
the store setup.
SAP POS Store Data Transfer for Retail uses several adapters to transfer files
to SAP NetWeaver PI. The adapters vary according to the protocol used for the
data transfer for example, whether by FTP or HTTP and according to their
encryption capabilities. For more information on the encryption capabilities, see
the installation and security guides for SAP Centralized EFT located at the SAP
Service Marketplace at http://service.sap.com/instguides Industry Solutions
Industry Solution Guides SAP for Retail SAP Point-of-Sale SAP
POS Relevant Release Installation Guide SAP Centralized EFT, and
Security Guide SAP Centralized EFT.

This application was formerly


called SAP Centralized Electronic
Funds Transfer (SAP CEFT),
which was known previously as
Transnet
Custom development TLOG
format

When you set up adapters in the SAP POS Store Data Transfer for Retail, you
must synchronize them with the adapter type used by the SAP NetWeaver PI
communication channel. Since File Transfer Protocol (FTP) is used as the
communication protocol between SAP POS and SAP NetWeaver PI, the FTP
server must also be enabled on the POS side. In cases where the Internet
Information Server (IIS) with FTP server is enabled, the folder which is used for
the file transfer should be the FTP home directory. The home directory must
receive read and write permissions from FTP server configurations, and the
same directory within the operating system should be shared to allow
anonymous logon from SAP NetWeaver PI.
The SAP POS 2.3 system allows custom development to be carried out on the
POS side and provides an option to generate a modified body of the TLOG
record through user exits.
Caution
It is extremely important that customers develop TLOG formats that are
compatible with SAP NetWeaver PI interface mappings. For example, the
standard TLOG format does not use any delimiters but a custom
development user exit might include a delimiter such as a comma. Since
standard SAP NetWeaver PI interface mappings do not support commadelimited TLOG records, those TLOG formats would not transfer to SAP
ERP. Refer to the POS Transaction Log Data section of this guide for
details on how to resolve instances where delimiters are found in user exit
records.

Security Setup

To enable end-to-end security between the SAP POS system and SAP POS
DM, SAP POS DM provides a public key that the POS Store Data Transfer for
Retail system uses to encrypt the data on the POS side. After receiving data,
SAP POS DM decrypts the data using the private key. For more information on
how to setup secure transfer of customer information, see the SAP POS
security guide.

SAP Retail Store

A connection to SAP Retail Store is required to support the Customer Order


Management (COM) scenario. This scenario allows customer layaway
transactions.
To access the SAP Retail Store, the POS system must be configured using a
HTTP link to a relevant SAP ERP system. For information on how to configure
the HTTP link, see the documentation at http://help.sap.com SAP for

Configuration Guide for POS Integration

SAP AG
Industries SAP for Retail SAP Point-of-Sale Relevant version SAP
Transactionware GM Head Office Functions Store Configurator
Transaction Functions POS Browser Using SAP POS for Sales Order
Processing.

5 SAP NetWeaver PI Landscape


5.1 Overview
In the SAP NetWeaver Process Integration landscape, there are two scenarios each with their own specific setup
requirements.
Outbound Scenario
The diagram below illustrates the sender and receiver interfaces for the outbound communication between SAP ERP
and SAP POS.

Configuration Guide for POS Integration

SAP AG

Inbound Scenario
The diagram below illustrates the sender and receiver interfaces for the inbound communication between SAP POS
and SAP NetWeaver BW, or SAP ERP.

5.2 Set Up Requirements for SAP NetWeaver PI


The following sections provide details to set up SAP NetWeaver PI for inbound and outbound communication. You will
need to make settings or enter information in each of the following sections of the SAP NetWeaver Process
Integration tool:

System Landscape Directory (SLD)

Integration Repository

Integration Directory

5.2.1

System Landscape Directory

To successfully execute the SAP POS integration scenario, you must set up each of the systems in the table below as
technical and business systems in the System Landscape Directory (SLD) of the SAP NetWeaver PI Integration
Builder.
For more information about the system landscape directory, see the documentation at
http://www.sdn.sap.com/irj/sdn/nw-sld .

System

System Type

Product

Software Component
Version (minimum)

SAP RETAIL

Web AS ABAP

SAP ERP ENHANCE PACKAGE


version EHP5 FOR SAP ERP 6.0

EA-RETAIL 6.05
SAP ABA 7.00
SAP APPL 6.00

SAP POS

Third-Party

SAP POS version 2.3

XI CONTENT STORE
CONNECT 3.0 - SP04
XI CONTENT GM
STORECONNECT 2.0 SP00

SAP NetWeaver BW

Web AS ABAP

Configuration Guide for POS Integration

SAP NETWEAVER version SAP


EHP2 FOR SAP NETWEAVER 7.0

SAP NW 7.0 BI CONT


ADDON 7.05
10

SAP AG

This section provides details on how to configure the technical and business systems for the SAP POS Integration
scenario in the SLD of SAP NetWeaver PI. After starting the Integration Directory in PI, do the following:
Step
Configure the technical systems in SLD

How to do the step


1. From the SLD home page, choose Technical Systems.
2. Choose New Technical System.
3.

Configure the business systems in SLD

Select the appropriate product and software components for the


desired system.

1. From the SLD home page, choose Business Systems.


2. Choose New Business System.
3. Follow the steps to define the business systems. Refer to the
technical system that you previously defined above.
4. In the installed product step, list the required software components
for each business system.

5.2.2

Integration Repository

The PI content of the SAP POS integration is based on the following software components. These software
components must be installed on the SAP NetWeaver PI system through the Integration Repository module.

5.2.3

SAP Marketplace

SAP NetWeaver PI Repository

XI CONTENT SAP_APPL 604


(Optional)

SAP_APPL, version 6.04

XI CONTENT SAP ABA 700

SAP ABA, version 7.00

XI CONTENT BI CONT 7.05

BI CONT, version 7.05

XI CONTENT STORE
CONNECT 3.0

XI CONTENT STORE
CONNECT 3.0 - SP04

XI CONTENT GM
STORECONNECT 2.0

XI CONTENT GM
STORECONNECT 2.0 - SP00

XI CONTENT EA-RETAIL 605

EA-RETAIL, version 6.05

Integration Directory

The following table provides information to guide you through the configuration process in the Integration Directory
module.

Tip
If you prefer, you can also create the configuration through an automated process that uses integration
scenarios defined in the Integration Repository of the SWCV STORE CONNECTIVITY 3.0 as a base. For
more information on this configuration method, see information in the Automated Configuration Process
section.

Configuration Guide for POS Integration

11

SAP AG

5.2.3.1

Manual Configuration Process

After starting the Integration Directory in PI, do the following:


Action

How to do this

1. Create the configuration scenario.

a) From the main menu bar of the Integration Directory


(Configuration) of PI Integration Builder, select Object New.
b) On the Create Object screen, select Configuration Object
Configuration Scenario.
c) Save.

2. Define the business system in the system


landscape directory.

a) Choose the Objects tab page.


b) Place your cursor on Service Without Party and click the right
mouse button.
c) Select Assign Business System.
d) On the Assign Business System screen, choose Continue.
e) In the Assign Party step, choose Continue.
f)

In the Select Business System step, select the checkboxes for


business systems you created in the SLD.

g) Choose Finish.
h) Save.
3. Define the business service in the system
landscape directory.

a) Select the Scenarios tab page.


b) Select your configuration scenario to find the Service Without
Party node.
c) Place your cursor on Service Without Party and click the right
mouse button.
d) Select Business Service to create new service for the
configuration.
e) On the Business Service screen, enter the service name, then
select the configuration scenario and choose Continue.
f)

Choose Create.

g) On the Business Service creation screen, enter the appropriate


description.
h) Save.
4. Add a business system to your
configuration scenario.

a) Choose the Objects tab page.


b) Choose Service Without Party from the selection tree.
c) Select one of the business systems that you previously
assigned.
d) Right-click and choose Add To Scenario. Select the configuration
scenario you previously created.
e) Repeat steps 1-4 for each business system in the landscape.
f)

5. Create communication channels for the


receiver service.

Save.

a) Choose the Scenarios tab page.


b) Choose Service Without Party from the selection tree of the
configuration scenario.
c) Expand the selection tree for the Receiver Service defined for
the configuration (for example, <SAP POS Business system>).
d) Right-click Communication channel from the selection tree, and
choose New.

Configuration Guide for POS Integration

12

SAP AG
e) On the Create Object screen, enter one of the following
communication channels for the desired scenario:

Steps continue below list of communication channels.

Scenario

Communication Channel

Communication Channel template

Article Master Data Download

FlatFileGMPluTxnFlat

GMPluTxnFlatFileChannelTemplate

FlatFileGMLinkTxnFlat

GMLinkTxnFlatFileChannelTemplate

FlatFileGMXrefTxnFlat

GMXrefTxnFlatFileChannelTemplate

FlatFileGMMRPTxnFlat

GMMRPTxnFlatFileChannelTemplate

FlatFileGMDeptTxn

GMDeptTxnFileChannelTemplate

Promotion Download

FlatFileGMPromoTxnFlat

GMPromoTxnFlatFileChannelTemplate

Merchandise Category Hierarchy Download

FlatFileGMCatTxn

GMCatTxnFileChannelTemplate

FlatFileGMGroupTxn

GMGroupTxnFileChannelTemplate

FlatFileGMDeptTxn

GMDeptTxnFileChannelTemplate

FlatFileGMMixMatch

GMMixMatchChannelTemplate

FlatFileGMDiscInEx

GMDiscInExFileChannelTemplate

Employee Master Data Download

FlatFileGMEmpxTxn

GMEmpxTxnChannelTemplate

Physical Inventory Count Sheet

FlatFileGMInventory

GMPhysicalInventoryReceiverFileChan
nelTemplate

All

FlatFileGMTriggerFile

GMTriggerFileChannelTemplate

Bonus Buy Download

Action
5 continued. Create communication channels
for the receiver service.

How to do this
f)

On the Edit Communication Channel screen, go to the menu


Communication Channel and choose Import template using one
of the template names specified in the table above.

After you select a template, the information in the following table is


displayed. Some of the properties may differ depending on the
communication channel. There is no need to change the information
unless you are specifically advised to.

Steps continue below system output example.


Adapter Type
Receiver
Transport Protocol
Message Protocol
Adapter Engine
File Access Parameter
Target Directory
Create target Directory
File Name Scheme
FTP Connection parameters
Server
Port
Data Connection
Timeout(sec)
Configuration Guide for POS Integration

File (SAP BASIS 7.00)


Selected
File Transfer Protocol (FTP)
File Content Conversion
Integration Server
/parm/%dir%
Checked
%file%.asc

21
Passive
30
13

SAP AG
Connection Security
Anonymous login
Connect Mode
Transfer Mode
Maximum Concurrency
Processing Parameters
File Construction Mode
File Type
Run Operating System Command Before Message Processing
Command Line
Timeout (secs)
Terminate Program After Timeout
Run Operating System Command After Message Processing
Command Line
Timeout (secs)
Terminate Program After Timeout
Content Conversion Parameters
Record Structure
ActionMap.addHeaderLine
ActionMap.fieldSeparator
Header.addHeaderLine
Header.fieldFixedLengths
Header.fixedLengthTooShortHandling
Header.endSeparator
Body.addHeaderLine
Body.fieldSeparator
Variable Substitution(Target Directory/ File name Scheme)
Enable
Disable Security Checks
Adapter-Specific Message Attributes
Use Adapter-Specific Message Attributes
Adapter Status
Status
Advanced Mode
Action
5 continued. Create communication channels
for the receiver service.

None
Unchecked
Per File Transfer
Binary
1
Append
Binary

Header, Body
0
nl
0
0,0
Cut
0
0
nl
Checked
Unchecked
Unchecked
Active
Unchecked

How to do this
g) Enter the server name and adjust the port number for your FTP
connection.
h) Provide the user and password for your FTP connection.
The following variables are used:
%dir% to generically identify the directory where files will be
stored
%file% to generically identify the file names
The path can be taken from the payload. For example,
%file%: payload:GMPluTxnFlat,1,Header,1,FileName,1
%dir%: payload:GMPluTxnFlat,1,Header,1,StoreNumber,1
i)

Save.

j)

Repeat the previous steps to create communication channels for


the remaining SAP POS flat files used in the desired scenario.
Choose the appropriate template for each communication
channel.
Tip
You only need to create the communication channel once, even
though it is used by multiple scenarios.

Configuration Guide for POS Integration

14

SAP AG

k) Repeat the previous steps to create the communication channels


for additional scenarios.
l)

Create a new communication channel for the business system


added for the POS Inbound Transaction scenario by rightclicking on the Communication Channel node. Choose New.

m) Define the following parameters to assign the communication


channel to a scenario.

Party

Service

Communication Channel

Add to Scenario

Choose Create.
n) Add the following information to the communication channel
before saving it.
Adapter Type
Transport Protocol
Message Protocol
Adapter Engine
Addressing Type
Target Host

XI
HTTPS 1.0
XI 3.0
Integration Server
URL Address
<Target system URL>

Service Number
Path Prefix

<Target system port>


/sap/xi/engine?type=entry

Authentication Data
Authentication Type
User Name
User Password
Logon Language
Client

Use Logon Data for SAP System


<Valid Username for the Target Host>
<Valid Password for the Target Host>
<Valid Language>
<Target Host Client>

o) Create a new communication channel for the business system


that will handle the Inbound Physical Inventory Count Sheet
scenario by right-clicking on the Communication Channel node.
Choose New.
p) Define the following parameters to assign the communication
channel to a scenario.

Party

Service

Communication Channel

Add to Scenario

Choose Create.
q) Add the following information to the communication channel
before saving it.
Adapter Type
Transport Protocol
Configuration Guide for POS Integration

IDoc
IDoc
15

SAP AG
Message Protocol
Adapter Engine
RFC Destination
Port

6. Create communication channels for the


sender service.

IDoc
Integration Server
<Destination for SAP ERP system>
<Target system port>

a) Choose the Scenario tab page.


b) Choose Service Without Party from the selection tree of the
configuration scenario.
c) Expand the selection tree for the Sender Service defined for the
configuration (for example, <POS Configured VM>).
d) Right-click Communication channel from the selection tree and
choose New.
e) On the Create Object screen, enter the Business Service,
Description and the Scenario. Choose Create.
f)

Enter one of the following communication channels for the


desired scenario:
Scenario

Communication Channel

Transactions

GMTLogTransaction

Inbound Physical Inventory


GMTLogPhysicalInventory

Count Sheet

Use the following parameters on the Edit Communication


Channel screen.
Adapter Type

File

Communication Channel Type

Sender

Transport Protocol

FTP (File Transfer Protocol)

Message Protocol

File Content Conversion

Adapter Engine

Integration Server

File Access Parameters


Source Directory
File Name
Physical Inventory)

<Valid Directory at the host>


*.asc (for transaction ) or count.dat (for

FTP Connection Parameters


Server

<IP Address of Transnet Server>

Port

21

Data Connection

Passive

Connection Security

None

Anonymous Login

Yes

Connect Mode

Permanently

Transfer Mode

Binary

Processing Parameters
Configuration Guide for POS Integration

16

SAP AG
Quality of Service

Exactly Once (EO)

Poll Interval (secs)


30 (for Physical Inventory)

10 (for transaction) or

Processing Mode

Delete

Empty-File Handling

Do Not Create Message

File Type

Binary

Content Conversion Paramaters

Transactions

Inbound Physical Inventory Count


Sheet

Document Name

GMTLog

GMTLogTransaction

Document Namespace

http://sap.com/xi/GMStoreConnectivity

http://sap.com/xi/GMStoreConnectivity

Recordset Structure

Line,*

GMTLogTransaction8,*

Recordset Sequence

Variable

Variable

Key Field Name


Key Field Type

TransactionType
String (Case-Sensitive)

Action
7. Create receiver agreement for each
communication channel.

String (Case-Sensitive)

How to do this
a) Choose Receiver Agreement from the selection tree of the
configuration scenario.
b) Right-click and choose New.
c) On the Create Object screen,
i.

Add the <SAP ERP Business System> as sender Service for


Outbound or <SAP POS Business system> as sender
Service for Inbound.

ii.

Add the <SAP POS Business system> as receiver Service


for Outbound or <SAP ERP Business System> as receiver
Service for Inbound.

iii.

Select one receiver Interface from the list in the desired


download scenario:

Outbound Scenario
Article Master Data Download
GMPluTxnFlat_In
GMXrefTxnFlat_In
GMLinkTxnFlat_In
GMMRPTxnFlat_In
GMDeptTxn_In
GMTriggerFile_In
Merchandise Category Hierarchy Download
GMCatTxn_In
GMDeptTxn_In
GMGroupTxn_In
GMTriggerFile_In
Promotion Download
Configuration Guide for POS Integration

17

SAP AG
GMPromoTxnFlat_In
GMTriggerFile_In
Bonus Buy Download
GMMixMatchFlat_In
GMDiscInExFlat_In
GMTriggerFile_In
Employee Master Data Download
GMEmpxTxn_In
GMTriggerFile_In
Physical Inventory Count Sheet
GMInventoryCount_In
GMTriggerFile_In

Inbound Scenario
POS Tlog Data
PointOfSaleTransactionERPBulkCreateRequest_In
Physical Inventory Count Sheet
WVINVE.WVINVE03

iv.

Choose Create.

v.

On the Edit Receiver Agreement screen, enter the


communication channel corresponding to receiver interface:

Steps continue below list of receiver interfaces.

Receiver Interface

Communication channel

GMPluTxnFlat_In

FlatFileGMPluTxnFlat

GMXrefTxnFlat_In

FlatFileGMXrefTxnFlat

GMLinkTxnFlat_In

FlatFileGMLinkTxnFlat

GMMRPTxnFlat_In

FlatFileGMMRPTxnFlat

GMDeptTxn_In

FlatFileGMDeptTxn

GMCatTxn_In

FlatFileGMCatTxn

GMGroupTxn_In

FlatFileGMGroupTxn

GMPromoTxnFlat_In

FlatFileGMPromoTxnFlat

GMMixMatch_In

FlatFileGMMixMatch

GMDiscInEx_In

FlatFileGMDiscInEx

GMEmpxTxn_In

FlatFileGMEmpxTxn

GMInventoryCount_In

FlatFileGMInventoryCount

GMTriggerFile_In

FlatFileGMTriggerFile

PointOfSaleTransactionERPBulkCreateRe
quest_In

GeneratedReceiverChannel_XI_secure

WVINVE.WVINVE03

Inventory_IDOC_receiver

Configuration Guide for POS Integration

18

SAP AG
Action
7 continued. Create receiver agreement for
each communication channel.

How to do this
vi.

Save

vii.

Repeat the previous steps to create the receiver agreements


for the remaining Receiver Interfaces of the desired
scenario.
Note that the receiver agreement for a specific interface
needs to be created only once, even though it is used by
multiple scenarios.

viii.

8. Create the interface determination.

Repeat the previous steps to create the receiver agreements


for additional scenarios.

a) Choose Interface Determination from the selection tree of the


configuration scenario.
b) Right-click and choose New.
c) On the Create Object screen,
i.

Add the <SAP ERP Business System> as sender Service for


Outbound or <SAP POS Business system> as sender
Service in case of Inbound.

ii.

Enter one of the following for the sender interface depending


on the type of master data or POS data to send.

iii.

Add the <SAP POS Business system> as receiver Service


for Outbound or <SAP ERP Business System> as receiver
Service for Inbound.
Steps continue below the list of interfaces for the outbound
scenario.

Outbound Scenario

Interface

Article Master Data Download

MerchandiseERPReplicationBulkRquest_Out

Merchandise Category Hierarchy Download

ProductCategoryHierarchyERPReplicationRequest_Out

Promotion Download

RetailEventERPStoreReplicationRequest_Out_V1

Bonus Buy Download

RetailIncentiveERPStoreOfferReplicationBulkRequest
_Out_V1

Employee Master Data Download

HRMD_ABA.HRMD_ABA05

Physical Inventory Count Sheet

WVINVE.WVINVE03

Inbound Scenario
POS TLog Data

GMTLogOut

Physical Inventory Count Sheet

GMTLogTransactionPhysicalInventory_Out

Action

How to do this

8. continued. Create the interface


determination.

d) On the Edit Interface Determination screen,


i.

Select Enhanced for Outbound or Standard for Inbound in


Type of Interface Determination field.

ii.

Select Maintain Order At Runtime for Quality of Service field.

iii.

Enter one of the following for the interface mapping


depending on the desired scenario.
Tip
The software component version should be Store Connectivity
3.0.

Configuration Guide for POS Integration

19

SAP AG
Steps continue below the list of interfaces for the outbound
scenario.

Outbound Scenario

Interface

Article Master Data Download

MerchandiseERPReplicationBulkRequest_Out_To_GMStore

Merchandise Category Hierarchy


Download

ProductCategoryHierarchyERPReplicationRequest_Out_To_GMSt
ore

Promotion Download

RetailEventERPStoreReplicationRequest_Out_V1_to_GMStore

Bonus Buy Download

RetailIncentiveERPStoreOfferReplicationBulkRequest_Out_V1
_To_GMStore

Employee Master Data Download

ERPHRMasterDatatoGMEmployee

Physical Inventory Count Sheet

ERPPhysicalInventoryToGMInventoryCount

Inbound Scenario
POS TLog Data

GMTLog2PointOfSaleTransactionERPBulkCreateRequest

Physical Inventory Count Sheet

GMTLogTransaction2ERPPhysicalInventory

Action

How to do this
e) Save.

8 continued. Create the interface


determination.

f)

In the Inbound Interfaces section, the following interfaces should


be automatically filled depending on the scenario:

Steps continue below list of software component versions.

Scenario

Inbound Interface Name

Software Component Version

Article Master Data Download

GMPluTxnFlat_In
GMXrefTxnFlat_In
GMLinkTxnFlat_In
GMMRPTxnFlat_In
GMDeptTxn_In
GMTriggerFile_In

GM STORE CONNECTIVITY 2.0

Merchandise Category Hierarchy


Download

GMCatTxn_In
GMDeptTxn_In
GMGroupTxn_In
GMTriggerFile_In

GM STORE CONNECTIVITY 2.0

Promotion Download

GMPromoTxnFlat_In
GMTriggerFile_In

GM STORE CONNECTIVITY 2.0

Bonus Buy Download

GMMixMatchFlat_In
GMDiscInExFlat_In
GMTriggerFile_In

GM STORE CONNECTIVITY 2.0

Employee Master Data


Download

GMEmpxTxn_In
GMTriggerFile_In

GM STORE CONNECTIVITY 2.0

Physical Inventory Count Sheet Outbound

GMInventoryCount_In
GMTriggerFile_In

GM STORE CONNECTIVITY 2.0

Configuration Guide for POS Integration

20

SAP AG
POS TLog Data

PointOfSaleTransactio
nERPBulkCreateRequest
_In

GM STORE CONNECTIVITY 2.0

Physical Inventory Count Sheet Inbound

WVINVE.WVINVE03

SAP APPL 6.00

Action

How to do this
g) Repeat the previous steps to create the interface determination
for any additional scenarios.

8 continued. Create the interface


determination.
9. Create the receiver determination.

a) Choose Receiver Determination from the selection tree of the


configuration scenario.
b) Right-click and choose New.
c) On the Create Object screen,
i.

Add the <SAP ERP Business System> as sender


Service for Outbound or <SAP POS Business system>
as sender Service in case of Inbound.

ii.

Enter one of the following for the sender Interface


depending on the desired scenario:

Steps continue below list of outbound scenario interfaces.


Outbound Scenario

Interface

Article Master Data

MerchandiseERPReplicationBulkRquest_Out

Merchandise Category
Hierarchy Data

ProductCategoryHierarchyERPReplicationRequest_Out

Promotion Master Data

RetailEventERPStoreReplicationRequest_Out_V1

Bonus Buy (Mixmatches) Data

RetailIncentiveERPStoreOfferReplicationBulkRequest_Out_V1

Employee Master Data

HRMD_ABA.HRMD_ABA05

Physical Inventory Count Sheet

WVINVE.WVINVE03

Inbound Scenario
POS TLog Data

GMTLog_Out

Physical Inventory Count Sheet

GMTLogTransactionPhysicalInventory_Out

Action

How to do this

9 continued. Create the receiver


determination.

d) On the Edit Receiver Determination screen, in the Type of


Receiver Determination section, add the <SAP POS Business
system> for Outbound and <SAP ERP Business System> for
Inbound as configured receivers in the Service field by choosing
Add.
e) Save.
f)

5.2.3.2

In the Configuration Overview for Receiver Determination


section, the interface mapping and receiver agreement should be
automatically filled with previously configured data.

Automated Configuration Process

You can define the configuration scenario using the integration scenarios defined in the Integration Repository of the
SWCV STORE CONNECTIVITY 3.0. The relevant configuration objects are calculated on the basis of the information
saved in the integration scenario, as well as on additional assignments that you make interactively. This mechanism
Configuration Guide for POS Integration

21

SAP AG
automates the configuration and thus simplifies the initial setup of the systems. The following is a list of the supported
integration scenarios:

Outbound Scenario

PI Integration Scenario

Article Master Data Download

MerchandiseERPReplicationBulkRequest2GMStore

Merchandise Category Hierarchy Download

ProductCategoryHierarchyERPReplicationRequest2GMSt
ore

Promotion Download

RetailEventERPStoreReplicationRequest2GMStore

Bonus Buy Download

RetailIncentiveERPStoreOfferReplicationBulkRequest
2GMStore

Employee Master Data Download

ERPHRMasterData2GMEmployee

ERPPhysicalInventory2GMInventoryCount

ERPPhysicalInventory2GMInventoryCount

Inbound Scenario
POS TLog Data

GMTLog2POSDMPointOfSaleTransactionERPBulkCreateReq
uest

Physical Inventory Count Sheet

GMTLogTransaction2ERPPhysicalInventory

Note
You must create one configuration scenario for each outbound and inbound scenario.
After starting the Integration Directory in PI, do the following:
Action

How to do this

1. Create the configuration scenario.

a) From the main menu bar of the Integration Directory


(Configuration) of PI Integration Builder, select Tools Apply
Model from ES Repository.
b) On theTransfer Model From ES Repository screen, specify the
process integration scenario for ES Repository Model Reference.
c) Choose Continue.
g) In the Create Configuration Scenario step, choose Finish.
h) In the Result screen, choose Close to start Model Configurator.

2. Assign business systems to the


configuration scenario.

a) Select the Assign Components button under the Component


View name.
b) Under the Business System Components for A2A configuration,
select the checkboxes for the business system you created in
the SLD for each of the application components in the
component view. Use the arrow buttons to move from one
application component to another.
Note
Both the source and target systems should be defined in SLD as
business systems.

3. Create the communication channels for


the receiver service.

Configuration Guide for POS Integration

a) Under the Component View name, select the Configure


Connections button.
b) Under the Connections from Component Assignment, select the
Create Communication Channel with Template for the selected
connection. Use the default values specified in the Create
Communication Channel screens. Use the arrow buttons to
22

SAP AG
move from one connection to the next to create all the required
connections.
Note
The communication channel templates specified in Step 5 of
Section 5.2.3.1 are used in the definition of the connections of
the configuration scenario.
c) After you create the communication channels, specify the IP
address of the FTP Server.
4. Create the receiver determination,
interface determinations and receiver
agreements.

a) Select the Create Configuration Objects button in the Model


Configurator screen.
b) In the Settings screen, select Generation. Select all options in
the Scope of Generation.
c) Select Start.

Note
There is a limitation in PI that only allows one-to-one mappings in integration scenarios, For the ERP-to-POS
processes, the configuration mode uses split mappings with different receiver interfaces. The following is a
workaround that enables you to use the defined integration scenarios described above despite this limitation:

5. Update the interface determination.

a) Choose generated Interface Determination from the selection


tree of the configuration scenario.
b) Choose ok .
c) Select the Enhanced button for the Type of Interface
Determination.
d) Select the corresponding Interface Mapping for the desired
scenario from the Value List.
e) Save your entry.

For further information on how to use the integration scenarios to create configurations, refer to the SAP NetWeaver
Process Integration documentation entitled Configuring Integration Scenarios available at the following location:
http://help.sap.com SAP NetWeaver SAP NetWeaver 7.3 SAP NetWeaver 7.3 Library English SAP
NetWeaver Process Integration Developing and Configuring Integration Scenarios.

6 Unicode Communication with Unicode-Enabled SAP ERP


System and SAP POS
The following table provides you with modification steps you must make to enable a Unicode character set when
configuring communication to SAP POS 2.3, if required.

Step

Description

1. Identification

Determine the number of business services you need to create. This is determined by the
number of localization groups you have that use the same code pages/character sets
(Example: German, Chinese, Japanese, and Russian).
Create a business system or business service for each of the localization groups identified.
Follow step 2 in the Integration Directory section to create each business service.
Specify the File Encoding property within the Communication Channel Processing Parameters
for all adapter file types. Follow step 4 in the Integration Directory section except for the

2. Creation
3. Configuration of
the

Configuration Guide for POS Integration

23

SAP AG
communication
channel

following:
a. To set the File Encoding property within the Communication Channel Processing
Parameters, change the File Type property to Text.
b. Enter the specific File Encoding parameter in the input field.
For example:
FlatFileGMPluTxn_Germany

4. Configuration of
the receiver
determination

File encoding: Cp1252

FlatFileGMPluTxn_ChineseSi
mplified

File encoding: GB18030

FlatFileGMPluTxn_Japanese

File encoding: SJIS

FlatFileGMPluTxn_Cyrillic

File encoding: Cp1251

Configure the routing for all of the existing entries so that the receiver determination can call the
right business system or business service. If desired, you may define conditions for forwarding
the message to the receivers.
Follow step 9 in the Integration Directory section. In the Configured Receivers section, open the
Condition Editor and do the following:
1. Click the Condition field. Use the Expression Editor to navigate to the appropriate service or
IDOC, and then select the field that corresponds to the store number.
Scenario

Field

Article Master Data


Download

MerchandiseERPReplicationBulkRequest/
MerchandiseERPReplicationRequestMessage/Merchandise/
ReceivingStore/StoreInternalID

Merchandise Category
Hierarchy Download

N/A

Promotion Download

RetailEventERPStoreReplicationRequest_V1/
RetailEvent/ReceivingStore/StoreInternalID

Bonus Buy Download

RetailIncentiveERPStoreOfferReplicationBulkRequest_V1/
RetailIncentiveERPStoreOfferReplicationRequestMessage_V1/
RetailIncentive/ReceivingStore/StoreInternalID

Employee Master Data


Download

N/A

Physical Inventory
Count Sheet

/WVINVE03/IDOC/E1WVINH/FILIALE

2. Specify the condition for each group that corresponds to the specific business system or
business service. You must specify this for each entry in the Receiver Determination
section.
For example:
The condition, MerchandiseERPReplicationBulkRequest/
MerchandiseERPReplicationRequestMessage/Merchandise/ReceivingStore/
StoreInternalID (= 0001) or (= 0002) or ( = 0003), will map to Business System for
German language.

Configuration Guide for POS Integration

24

SAP AG

7 Connect Back-End Applications to SAP PI


This section describes how to connect back-end application to SAP NetWeaver PI using IDocs and SAP Services.

7.1 IDOCs Scenario


This section describes how to connect back-end applications to SAP NetWeaver PI for integration scenarios that use
IDocs.

Connecting to SAP NetWeaver PI in SAP ERP

The following steps describe how to connect to SAP NetWeaver PI.

Use transaction SM59 to create an RFC destination for the PI system.

Use transaction WE21 to define a transactional RFC Port.

Use transaction WE20 to add the following message types for each store (Partner type KU = customer) in the
outbound parameter section. Use the correct IDoc type for each IDoc message type as shown below:

Idoc

IDoc Message Type

WVINVE

WVINVE03

HRMD_ABA

HRMD_ABA05

In the details view of each partner, set up the right receiver port. In this case, this is the port that was
previously defined in transaction WE20.

Connecting to SAP ERP in SAP NetWeaver PI

1. Use transaction IDX1 to define a port. Refer to the RFC destination that was created for the SAP ERP system.
2. Assign the following IDoc types for the port that you previously created using transaction IDX2.

Idoc

IDoc Message Type

WVINVE

WVINVE03

HRMD_ABA

HRMD_ABA05

7.2 SAP Services Scenario


This section describes how to connect back-end applications to SAP NetWeaver PI for integration scenarios that use
SAP Services.
1. Verify the proxy configuration in the SAP ERP system. Verify that the proxy configuration is complete (for
example, for http / https) and, if required, activate the services by calling transaction SICF. For more details,
see the section Internet Communication Framework via SAP Web Application Server in the SAP NetWeaver
PI configuration guide.
2. Verify the RFC destinations in your SAP ERP system. Call up transaction SM59 and ensure that every RFC
destination required for communication with your SAP XI/PI system (for example, your integration server)
exists. Use the Test Connection functionality.
3. Use transaction sxmb_adm to check that the Corresponding Integ. Server of the PI system is correctly set.
Configuration Guide for POS Integration

25

SAP AG
4. Activate the business function in your SAP ERP system. Call up transaction SFW5 and activate the business
function 'ISR_RETAIL_POS_INTEG'. In order to activate the business function 'ISR_RETAIL_POS_INTEG'
you also need to activate some prerequisite business functions. For more details, see the documentation
available in transaction SFW5.
5. Create settings in Customizing in the SAP ERP system. The data transfer from the SAP ERP system to
the POS system is controlled by Customizing settings. To make these settings call up transaction SPRO and
expand the Implementation Guide as follows: SAP Customizing Logistics General Retail Enterprise
Services Outbound Messages.
For more information, see the document entitled Configuration of Trade Outbound Enterprise Service Integration
Framework (TOF) available at the following location: http://service.sap.com/retail Expert Knowledge Corner
Interfaces POS Integration.

8 Functional Details for Implementing SAP POS Integration


Content
This section covers high-level specification and design details that you must consider when you implement SAP POS
Integration content.

8.1 General Information


The following section provides general information about integrating SAP POS with SAP ERP.

When master data is transferred to the SAP POS head office server, it is saved in different directories. Each
directory identifies a specific store.
For example, data for Store 2101 is saved in directory 2101.
In some cases, the store number is extracted from the outbound service messages. For further details,
see the Add a business system to your configuration scenario section in the SAP NetWeaver PI
Configuration Integration Directory section.

For Employee download and Merchandise Category Hierarchy download, there is no store number available
in the IDOC or service. For Employee download, the organization unit of the employee is mapped to the
appropriate stores through value mapping. For Merchandise Category Hierarchy download, the receiver
system is used as the target directory name.

The length of the Store ID in the SAP POS data is six (6) digits. The SAP ERP Site ID is used to generate Store
ID for SAP POS for service-based integrations however the Site ID field is limited to four (4) digits. See Appendix
B for a list of possible solutions to deal with the Store ID length discrepancy.

When flat files are created on the POS server, two records are created for every item in the download: a Delete
record (action code = 3) and an Update record (action code=2). The delete action record ensures that previous
data in the SAP POS system associated with the record is deleted. The update action record creates a record for
the new incoming data in the POS system.

To export the home currency code to the real-time trickle TLOG, CVTLOG_USECURRENCYCODEFLAG=Y must
be set in file POS.ini in the SAP POS system.

See SAP Note 1652813 for further information on the initialization mode in the service-based integration process
(transaction WESOUT) and the solution proposed to delete existing entries in the POS system before data sent from
SAP ERP is applied in the POS system.

8.2 Article Master Data Download


The following section provides general information about the Article Master Data Download from SAP ERP.

In the Article Master Data download, SAP ERP provides PLUs (EANs) for articles, and SKUs for crossreference numbers and sales set items. The article number is associated to the PLU with the base unit of
measure.

Configuration Guide for POS Integration

26

SAP AG

Items with EAN and No Price are only stored in the PLUTXN table. These items are assigned a default price
of 0. When a customer purchases these items, the cashier must enter the correct price for them. The same
process applies to any articles with multiple units of measure.

If an item without a price needs to be sold and it has a promotion associated with it, the promotion can only be
applied if it is available in the POS article download file. Otherwise, the cashier must enter the promotion for
the item manually at the POS.

In the SAP POS system, the length for the article description field is limited to a maximum of 40 characters.
The description is truncated at the SAP POS client due to this limitation in the user interface.

8.3 Merchandise Category Hierarchy Download


The following section provides general information about the Merchandise Category Hierarchy download from SAP
ERP.
There are three category hierarchy levels in the SAP POS application however SAP ERP may have more defined
levels. You can specify the number of hierarchy levels to send to SAP POS in transaction WESIMG. SAP ERP sends
the number of levels you specify beginning at the bottom level. For example, if five levels are specified in SAP ERP
and the configuration to SAP POS is set to export three levels, ERP sends the three bottom levels.
Level 1 RP01
Level 2 R100
Level 3 R1100

SAP ERP sends these 3 levels


to SAP POS

Level 4 R1120
Level 5 R1121

To support the download of the Merchandise Category Hierarchy, you must do the following:

In the IMG activity (transaction WESIMG) for the Trade Outbound Framework (TOF), specify the number of
category levels to export for service ProductCategoryHierarchyERPReplicationRequest_Out. For example, since
the SAP POS application supports only three category levels, you must set the MGH: Levels value in
ProductCategoryHierarchyERPReplicationRequest_Out to 3 for application POS.

In Define Filter Objects, specify the merchandise category hierarchy.


When the merchandise category hierarchies are downloaded to the POS, the default functionality is to clear the POS
database before the categories are processed. For instance, when each of the flat files for hierarchies is generated,
the first entry in the flat file is 99 before any categories are listed. This process is known as initialization. For other
downloads, there is no such mechanism available.

8.4 Promotion Download


SAP NetWeaver PI supports the following promotion types: new price, percentage and dollar discounts. They can be

article-based or merchandise category-based promotions.


The following are the SAP ERP transactions related to promotions:

WAK1

Create promotion

WAK2

Change promotion

WAK3

Display promotion

In the ERP system, the length for the promotion description field is longer than the length of the field in SAP POS,
which is limited to a maximum of 40 characters. Therefore the description is truncated at the SAP POS client due to
this limitation in the user interface.
Configuration Guide for POS Integration

27

SAP AG
New price promotions
When you create a new price promotion with transaction WAK1, you must enter all the articles to be included in the
promotion through the Fast entry link in the Create Promotion screen. Enter distinct units of measure separately
according to their GTIN number. After you create the promotion, to download it successfully you must run the Price
Activation process (transaction WAK5) in SAP ERP.
Percentage discount promotions
Percentage discount promotions can include articles, the merchandise category, or both. If the required article also
happens to be part of the merchandise category, the Discount on merchandise category will be effective. When you
create a percentage discount promotion, you must activate it by choosing the Activate button in the Discounts tab,
however no further subsequent processing is required to send it out with TOF.
Dollar discounts
On the SAP POS side, dollar discounts are treated as markdowns. The dollar discount is similar in process to the
percentage discount. Both are possible for either article-based or merchandise-category-based promotions. Price
activation is required for both. If merchandise category is used for dollar discount, the unit of measure must be
specified and must be compatible with the specified merchandise category.

8.5 Bonus Buy Download


The following section provides general information about the Bonus Buy download from SAP ERP. A detailed
description of the SAP ERP Bonus Buy interface and a list of possible bonus buy scenarios currently supported for
this content can be found in Appendix C.

Only PLUs (EANs) are used to associate articles to bonus buy promotions, even if the article number is available.
This is because the article download also uses the EANs to identify articles.

In SAP POS, there is support for inclusion and exclusion of articles in mix match definitions. The SAP ERP bonus
buy transactions only allow you to list the articles that can be purchased or rewarded. There is no option to specify
articles to be excluded from the bonus buy definitions. This means that any articles not in the Buy or Get set of
articles are excluded from the mix match promotion by default.

In SAP POS, an identifier is required for each inclusion/exclusion rule. The SAP ERP Bonus Buy interface does
not require or support such identifiers. To provide a corresponding value for this field in SAP POS, ERP uses the
bonus buy number to create inclusion or exclusion IDs for the Buy and Get sides. It derives the inclusion/exclusion
ID by appending digits from 1-9 to the end of the MixmatchID (on SAP POS) depending on the number of
specified Buy and/or Get groups (in SAP ERP). For example, if there are 5 Buy and Get groups, the numbers from
1 to 5 are appended to the end of the bonus buy number. Note that only a maximum of 9 Buy and Get groups can
be defined in SAP ERP.

Inclusion/exclusion identifiers are maintained in SAP POS. These identifiers are created when a mix match is
created, and deleted when the mix match is deactivated. In ERP, the bonus buy number is the only information
provided in the Retail lncentives Service message that can be used to create an inclusion/exclusion identifier
when a bonus buy is deactivated. Because ERP creates inclusion/exclusion IDs for SAP POS by appending a
sequential digit representing each Buy/Get group to the end of the bonus buy number, the number of identifiers is
unknown in a delete action and some identifiers presented to SAP POS might not exist. This does not cause any
functional issues other than additional mapping effort, but it may involve additional processing in SAP POS.

The SAP POS interface does not accept alphanumeric mix-match IDs while ERP does. You can resolve this issue
by using value mappings in PI.

Any mix matches created in the SAP POS system overwrite previous mix-match data received from ERP. For instance,
if bonus buys were downloaded from ERP and a conversion process (which is required to apply settings made on the
POS system) is performed, the previously imported data will be deleted. The same is true if a download occurs after a
conversion from the Configurator; the download will overwrite settings made on the POS system.

When bonus buy promotions are defined, the currency code should correspond to the currency at the SAP POS
Store. The SAP POS flat files for mix-matches do not allow for a currency to be specified.

When there are multiple overlapping mix-matches, the SAP POS system has logic to determine which mixmatches should be applied. The sequence in which they are downloaded to the SAP POS system does not
necessarily determine the order in which they are applied.

Configuration Guide for POS Integration

28

SAP AG

There is no validation of article pricing in the bonus buy creation application in SAP ERP, but there is validation in
the SAP POS system. If the article pricing or mix-match conditions do not validate, it is possible that the mixmatch discount will not be applied.

The requirement number in the SAP ERP Bonus Buy Maintenance screen is used to map to the lowest price flag
in the Mix-match definition screen in SAP POS. Note that this flag only works for the Buy One, Get One (BOGO)
scenario. In other scenarios, the highest priced PLUs will get the discount for the mix-match.

The length of the mix-match description is limited to a maximum of 20 characters in SAP POS. The
description is truncated at the POS client due to the limitation of the user interface.

In a bonus buy definition in SAP ERP, the Price Unit can be specified. If the result of the division of the
Amount or Price discount by the price unit rounds to a value of more than 2 zero decimals (for example
0.001), the mix-match definition will show a 0 value for Sell Price or Amount Off. Although SAP POS accepts
the mix-match definition, the mix-match is not applied since a zero value discount is not possible.

The promotional bonus buys created by transaction WAK1 in SAP ERP can only be transferred to SAP POS
through the bonus buy service (RetailIncentiveERPStoreOfferReplicationBulkRequest_Out_V1) and not
through the promotion service (RetailEventERPStoreReplicationRequest_Out_V1).

See SAP Note 1653825 for further information on the restrictions and limitation of the bonus buy download and the
solutions proposed to address them.

8.6 Employee Master Data Download


The following section provides general information about the Employee Master Data Download process.

SAP ERP does not support an authority level for an employee. This should be configured at the store level.
You can update the POS Integration content to allow an employees position to determine their authority level
in the SAP POS application.

You must define the organizational management hierarchy with the store at the lowest level in SAP ERP. You
must maintain the mapping table between store and organizational unit in SAP ERP. See Appendix D for
details on the value mappings required for Employee Master Data Download.

SAP ERP creates one employee (maintenance) file for each store. Each file should contain at least one
employee.

Maintain the password for an employee at the store level. It is currently left blank or defaulted to 0 in SAP
POS.

8.7 Physical Inventory Count Sheet


The following section provides general information about the Physical Inventory Count Sheet process per
outbound or inbound scenario.
Outbound Scenario
The inventory file is available for processing in the directory xps/dnload. To locate the inventory documents for a
store, use the following naming convention: SSSSNNNN.ivp, where SSSSSS refers to the store number and
NNNN corresponds to the last four digits of the IDoc number.
Inbound Scenario

The transaction file contains all entries for the TLog Transactions, the Physical Inventory Counts, and the
Time Punch scenarios. The Physical Inventory Counts scenario must be handled separately since its records
are routed to different receiver systems and interfaces. Only record type 8 is relevant for the Physical
Inventory Counts scenario. To extract these records data, execute the following command:
cvtlog -i8

<GM_PhysInventoryCounts_flat_file>

<GM_txn_files>

For more information, refer to the SAP POS CVTLOG documentation.

Only delta messages are allowed when a Physical Inventory document is still open. This is necessary
because the SAP ERP system continues to add all physical inventory counts as long as the Physical
Inventory document remains open.

Configuration Guide for POS Integration

29

SAP AG

All counting must be done based on PLU numbers. To enforce this, check the setting in the SAP POS
Configurator application under Inventory Parameter Setup General Item Entry Type.

8.8 POS Transaction Log Data


In the SAP POS system, transactions (purchases) are executed at the POS client. The system generates an
ASCII formatted file containing all the information related to the purchases and then interacts with the SAP POS
Store Data Transfer for Retail application for further processing and eventual delivery to SAP NetWeaver PI.

The FTP server is configured on the machine on which the SAP POS Store Data Transfer for Retail
application is installed. This facilitates communication between the SAP NetWeaver PI box and eventually to
the SAP ERP system.

The SAP POS DM inbound service receives data from the SAP NetWeaver PI system and creates a POS
transaction.

The POS transaction can be located in the POS workbench (/n/posdw/mon0) on the SAP POS DM system
using key parameters such as Store ID, Business date and Transaction number.

There are 2 possible solutions to handle delimiters introduced by user exit enhancements so that the POS
integration content can be processed:

Manually remove the delimiters from the TLOG data file, or

In the Content Conversion of the receiver Communication Channel for the TLog of the SAP POS Business
Service, specify the delimiter used in the TLOG as the Line.FieldSeparator.

8.9 Internal Value Mapping


For the SAP POS integration content, there are value mappings (for example. switch conditions) that allow source
values to be mapped to target values. For instance, GMTenderID in SAP POS has a numeric value (01, 02, and
so on). This value must be mapped to a String value (for example, Cash, Check, and so on) in SAP POS DM. A
value mapping, TenderValueMapping, exists to do the conversion.
These value mappings are stored in SOAPOSiNTG archive and can be found under Mapping Objects
Imported Archives of SWCV, STORE CONNECTIVITY 3.0 in the Integration Repository. Below is a summary of
the value mapping files delivered in the integration content:

Filename in Archive
MerchandiseERPReplicationBulkRequestValueMapping.xsl
ProductCategoryHierarchyERPReplicationRequestValueMapping.xsl
RetailEventERPStoreReplicationRequestValueMapping_V1.xsl
RetailIncentiveERPStoreOfferReplicationRequestValueMapping_V1.xsl
GMTLog2POSDM_ValueMapping.xsl

Note that these files must be modified if changes are required to existing values or if new mappings are needed
for new target fields. The new values need to be referenced from the source message mapping file.

Configuration Guide for POS Integration

30

SAP AG

Appendix A Example of SAP NetWeaver PI Configuration


This section provides screen shots to illustrate a sample configuration of a SAP NetWeaver PI configuration with SAP
POS 2.3.

System

Description

SAP NetWeaver PI

System X7X/001

Scenario POS_INT_Scottsdale

SAP ERP EhP 5

Systems QS5/441

SAP POS DM (SAP NetWeaver


Business Warehouse)

System Q77/003

SAP POS 2.3 installed with client


application of SAP POS Store Data
Transfer for Retail application (Transnet)

VM 10.4.45.58
Outbound Folder: C:\SAP_data\SAP_Outbound
Remarks about this configuration:
1. In this scenario, PI sends information to the Outbound folder
located on the SAP POS side. SAP POS Xpress server
processes files that come into this folder. It is possible to
define the Outbound folder directly as a default Xpress server
parm folder, but since this is a test system, it was preferable
to keep this folder separate to control data that is propagated
to the Xpress server.
2. This POS system has a Transnet client system installed that is
connected to Transnet server on the system 10.4.45.57.
3. This POS system has the TLOG trickle process enabled,
meaning that each transaction triggers the creation of an *.asc
file that eventually trickles to the SAP POS DM system
Inbound scenario.
4. This system has IIS with FTP installed. The FTP folder defined
is the Outbound folder.

Server application of SAP POS Store


Data Transfer for Retail application
(Transnet)

VM 10.4.45.57
Inbound Folder: C:\SAP_Data\SAP_Inbound
Remarks about this configuration:
1. In this scenario, the SAP POS application delivers the trickle
file to the Transnet server at the end of each transaction and
places it in the Inbound folder. SAP NetWeaver PI is
configured to read data from this folder via FTP, and to delete
files after it has read them.
2.

Configuration Guide for POS Integration

This system has IIS with FTP installed. The FTP folder
defined is the Inbound Folder.

31

SAP AG

POS_INT_Scottsdale Scenario Objects

Note
Employee Outbound and Physical Inventory is not configured for this system in Receiver Determination, even
though the communication channel for employee is defined.

Configuration Guide for POS Integration

32

SAP AG

POS_INT_Scottsdale Sender Agreement and Receiver Agreement Objects

Configuration Guide for POS Integration

33

SAP AG
Business System Q77_003 Communication channel

Configuration Guide for POS Integration

34

SAP AG
Configuration of the Communication Channel for Outbound Scenario (example of an Outbound channel)

Configuration Guide for POS Integration

35

SAP AG
Configuration of the Communication Channel for Outbound Scenario, continued

Configuration Guide for POS Integration

36

SAP AG
Configuration of the Communication Channel for Inbound Scenario

Configuration Guide for POS Integration

37

SAP AG
Configuration of the Communication Channel for Inbound Scenario, continued

Configuration Guide for POS Integration

38

SAP AG
Receiver Determination Outbound (Example of an Outbound Receiver Determination)

Configuration Guide for POS Integration

39

SAP AG
Receiver Determination Inbound

Configuration Guide for POS Integration

40

SAP AG
Interface Determination Outbound (Example of one Outbound Interface Determination)

Interface Determination Inbound

Configuration Guide for POS Integration

41

SAP AG
Sender Agreement

Receiver Agreement (Example of one outbound Receiver Agreement)

Configuration Guide for POS Integration

42

SAP AG

Appendix B Store ID Length Discrepancy Issue


This section describes issues related to transferring the site identifier from SAP ERP to SAP POS 2.3 due to a change
in the length of the SAP POS Store ID.
The site identifier in SAP ERP is an alphanumeric field with a length value of 4, whereas the Store ID on SAP POS is
a numeric field with a length value of 6. Additionally, for each site in SAP ERP, there is an associated alphanumeric
customer number of length 10. The site number from SAP ERP is used to generate Store ID for POS in service-based
integration, instead of the customer number.
Below is a list of possible solutions to address this issue.
.

Solution 1: Use integration content with Store ID numeric value of length 4


The standard integration content will continue to support a numeric length of 4 for the stores in SAP POS.

Implication
1. For the outbound processes, changes are required in the process which generates the header of the flat files
(.ASC). The fields representing the Store ID must be generated by pre-pending high order 0s to fill the empty
spaces.
2. All the SAP systems, ERP, POS and POS DM will be limited to having a store number range of 0001-9999.

Solution 2: Update service messages in SAP NetWeaver PI to use CustomerNumber


1. Add an extra field, Customer Number, following the Site Id for the service messages from TOF.
2. In the message mappings from SAP NetWeaver PI, replace the use of Site Id with CustomerNumber.
Implication
1. The Customer Number on SAP ERP must be restricted to a numeric value less than 1000000 since this is a
limitation on SAP POS.
2. In SAP POS DM, the StoreID of the POS and Site ID provided by SAP POS must be the same. If not, some
functions in SAP POS DM will not work properly.

Solution 3: Use value mapping for conversion


Introduce a value mapping to close the gap between the different data representations of Store ID in each system. In
SAP ERP, since the site ID is a 4-character alpha-numeric identifier, there can be 1679615 (36^4-1) possible values.
In SAP POS, with the extension of the Store ID from 4 to 6 numeric length, there can be 999999 possible values. With
the value mapping, the Store ID R310 in SAP ERP will equal to StoreID 027310 in SAP POS. See below for an
example of a possible value mapping.
Implication
1. All systems, ERP, POS and POS DM could have support for more stores but there would not be a one-to-one
relationship.
2. This value mapping must be maintained for each store.

Configuration Guide for POS Integration

43

SAP AG

This table provides an example of value mapping to illustrate how Store ID values in SAP ERP can be converted to
Store IDs in SAP POS.

ERP

PI (XI)

Store Number (SITE ID)

POS
Store Number (Store ID)

SITE ID: X+3N

Store ID: 0+XX+3N

3N

Value Mapping

XX

3N

NNN

<=>

00

NNN

NNN

<=>

01

NNN

NNN

<=>

02

NNN

NNN

<=>

03

NNN

NNN

<=>

04

NNN

NNN

<=>

05

NNN

NNN

<=>

06

NNN

NNN

<=>

07

NNN

NNN

<=>

08

NNN

NNN

<=>

09

NNN

NNN

<=>

10

NNN

NNN

<=>

11

NNN

NNN

<=>

12

NNN

NNN

<=>

13

NNN

NNN

<=>

14

NNN

NNN

<=>

15

NNN

NNN

<=>

16

NNN

NNN

<=>

17

NNN

NNN

<=>

18

NNN

NNN

<=>

19

NNN

NNN

<=>

20

NNN

NNN

<=>

21

NNN

NNN

<=>

22

NNN

NNN

<=>

23

NNN

NNN

<=>

24

NNN

NNN

<=>

25

NNN

NNN

<=>

26

NNN

NNN

<=>

27

NNN

NNN

<=>

28

NNN

NNN

<=>

29

NNN

NNN

<=>

30

NNN

NNN

<=>

31

NNN

NNN

<=>

32

NNN

NNN

<=>

33

NNN

NNN

<=>

34

NNN

Configuration Guide for POS Integration

44

SAP AG
Z

NNN

<=>

35

NNN

Example of Value Mapping for Store ID


In this sample mapping we can have 35999 [(36*10^3)-1] stores, however this creates a limitation against the
standard for naming and creating stores in SAP ERP [Char 1 = Alpha-Numeric][Char 3 = Numeric].

R310

<=>

027310

1200

<=>

001200

100

<=>

000100

Configuration Guide for POS Integration

45

SAP AG

Appendix C Bonus Buy Information


Bonus Buy Scenarios
The following table provides a summary of the supported bonus buy scenarios in the POS integration:

Definition

Examples

Buy X items from Group A, Get Y items from


Group B for free

Buy 2 shirts, get 1 for free

Buy 2 shirts, get 1 tie for free

Buy any 2 burgers of a group, get 1 water for free


Buy X items from Group A, Get Y items from
Group B at Z % off

Buy any 2 burgers of a group, get 1 drink 50% off

Get 20% off from 3rd item

Buy any 3 burgers of a group, get any drink (from


another group) for 50% off
Buy X items from Group A, Get Y items from
Group B at Z $ off

Buy any 2 burgers of a group, get 1 drink 0.50$ off


Buy 3 burgers of a group, get any 2 drink for 0,50$ off
each

Buy 2 kg onions, get 2nd kg 0,50$ off


Buy X from Group A, Get Y items from Group
B at fixed price

Buy any 2 burgers, get drink for 1


Buy 5 burgers, get 2 for 1 each

Buy any 2 burgers of a group, get 1 drink of another


group for 1
Buy X items from Group A, Get Z % off

Buy any 2 soft drinks of a group, get 20% off

Buy any 1 table of a group and any 2 chairs of different


groups,
get 20% off

Buy any 3 burgers of a group, get 10% off on total


purchase
Buy X items from Group A, Get Z$ off
Configuration Guide for POS Integration

Buy any 3 burgers of a group, get 1 off on total


46

SAP AG
purchase
Buy X items from Group A for fixed price

Buy any burger plus drink for 3$

Buy X items or more from Group A, Get Z %


off each item

Buy 2 or more soft drinks, 20% cheaper

Buy X items or more from Group A for fixed


price per item

Buy 3 or more socks, pay $2.50 each

Buy X items or more from Group A, Get Z$


off each item

Buy 5 or more t-shirts, get $5.00 off each

Spend X$, Get Y items from Group A for Z%


off

Spend 100$, get free gift

Limit is restricted to1 due to limitation on SAP POS.

Spend X$, Get Y items from Group A for Z$


off

Spend 100$, get a certain article 10$ off

Limit is restricted to1 due to limitation on SAP POS.

Spend X$, Get Y items from Group A for fixed


price

Spend 10$, get drink for 1$

Limit is restricted to1 due to limitation on SAP POS.

Spend X$ , Get Z % off

Get 5% discount on purchase over 50$

Spend X$ , Get Z$ off

Get 5$ discount on purchase over 50$

Limit is restricted to1 due to limitation on SAP POS.

Buy X items and Y items from any group, Get


Z% off for items

Buy 1 table and 2 chairs, get 20% off

Buy X items and Y items from any group, Get


Z amount off for items

Buy 2 shirts and 1 tie, get 10$ off

Note that Y is restricted to 1 due to limitation on SAP


POS.

Buy X items and Y items from any group at


fixed price

Buy 1 burger and 1 drink at 3$

Note that the limit number on SAP ERP refers to the number of times that the bonus buy can be applied. This field
maps to Repeat Count on the SAP POS. For some mix-match scenarios, the limit number (or repeat count) is
restricted to 1 because of logic on SAP POS for the Threshold Amount. This field is not fully compatible with the
meaning of Total Minimum Value in SAP ERP when the limit number is greater than 1.

Configuration Guide for POS Integration

47

SAP AG

User Interfaces for Bonus Buys


SAP ERP provides an interface screen for defining bonus buys. The following are the transactions you can use to
define or maintain a bonus buy:

RDMBBY01

RDMBBY02

RDMBBY03

RDMBBY06
In the SAP POS, mix-match promotions can be created in the Configurator application or the Store Manager
application. Mix-matches downloaded from SAP ERP are only visible through the Store Manager application.
The following section provides screen shot examples of possible bonus buy definitions. The relevant fields in the user
interfaces are highlighted. An explanation of the fields is provided in the tables that follow.

Configuration Guide for POS Integration

48

SAP AG
EXAMPLE 1A ERP Bonus Buy Definition

Configuration Guide for POS Integration

49

SAP AG
EXAMPLE 1B SAP POS Mix-match Definition

Configuration Guide for POS Integration

50

SAP AG

SAP ERP Data


Fieldname

Description

SAP POS Data


Fieldname

Limit Number

Numeric value that represents how many


times the bonus buy should be applied at
the POS.

Repeat Count

Organization Data
Sales Organization,
Distr. Channel and Site

Store for which the bonus buy should be


applied.

Link Category

There are 2 possible values: AND Link


and OR Link. This category indicates
how the line items are linked.

Line Item Type

The type indicates whether the line item


represents an article or article grouping
(for example, group of articles).

Line Item Identifier

The identifier corresponds to the


material number of an article or the
name of the article grouping.

Quantity Buy

Note that the article grouping in ERP


can be created through this UI by
selecting the Local Article Grouping
icon.
Numeric value that represents the
number of items to be purchased as a
prerequisite.

In the POS, all the


conditions in Alt [1-9] must
be satisfied to be applied.
Therefore, only the AND
Link is supported in the
POS integration

Each PLU is specified in


an inclusion/exclusion set.
Each set has its own
inclusion/exclusion
identifier.

Alt [1-9] Qty

Quantity Get

Numeric value that represents the total


number of items required to receive the
specified discount.

Alt [1-9] Qty

Discount Type

There are 3 types of discounts on the


individual line items: Discount Percent,
Discount Amount and Price Amount.

Each type corresponds to


%Off, $Off and SellPrice,
respectively in SAP POS.

Discount Value

Depending on the discount type


selected, the value corresponds to a
percentage or monetary value.

The value is specified on


an Alt level (1-9) under the
respective column.

Price Unit

Quantity on which a discount is based.


For example, if we have value discount
2$ for Price Unit 2, it means that
discount value for 1 unit would be 1$.
This field is applicable for Discount
Amount and Discount Price scenarios.

The value is used to


derive the $Off or
SellPrice amount.

Requirement

This number is customizable under


Sales and Distribution Basic
Functions Bonus Buy Define
Requirements. It can be used at the
point of sale to scan for any special
requirements for which the eligibility of
a bonus buy discount should be
evaluated (for example, lowest price on
POS = ERP value 1).

Discount On Lowest Price

Configuration Guide for POS Integration

51

SAP AG
EXAMPLE 2A ERP Bonus Buy Definition

EXAMPLE 2B SAP POS Mix-match Definition

Configuration Guide for POS Integration

52

SAP AG
SAP ERP Data Fieldname

Description

SAP POS Data Fieldname

Total Minimum Value

Monetary value specifies the


minimum amount to be spent
in order for the bonus buy to
be applied.

Threshold Amount

Total Discount

Indicates where the discount


is applied to the total
purchase.

Discount Type

There are 3 types of


discounts on the individual
line items: Discount Percent,
Discount Amount and
PriceAmount.

Each type corresponds to


%Off, $Off and SellPrice,
respectively in SAP POS.

Discount Value

Depending on the discount


type selected, the value
corresponds to a percentage
or monetary value.

The value is specified on an


Alt level (1-9) under the
respective column.

Configuration Guide for POS Integration

53

SAP AG
EXAMPLE 3A ERP Bonus Buy Definition

EXAMPLE 3B SAP POS Mix-match Definition

Configuration Guide for POS Integration

54

SAP AG

SAP ERP Data Fieldname

Description

SAP POS Data Fieldname

Scale Type

This numeric value specifies


the quantity range (for
example, 3 or more).

AllowGreaterThanAlt1

The scale type has 3 possible


values:

A From

B Up To

C Equal

For the Or more scenario, the


value of A-From should be
supported in addition to the
C-Equal value.

Configuration Guide for POS Integration

55

SAP AG

Appendix D Value Mappings for IDocs


For runtime, the following value mappings (example values) must be maintained in the Integration Directory under
Tools Value Mapping.
Caution
For performance reasons, it is important to specify all possible source values, even if the target values are
identical. Otherwise, the cached value mapping data is not used for these values. This would cause a tremendous
loss of performance.

Employee Master Data Download


Organizational Units
USE: The organizational units from SAP ERP must be defined to corresponding stores.
Source Agency: ERPOrganizationUnit
Source Schema: ERPOrganizationUnitSchema
Target Agency: IXRetailHomeStore
Target Schema: IXRetailHomeStoreSchema
Where to find the source values
Organizational units are customizable in SAP ERP. You can find the organizational units available in
the configuration of your system (IMG) by choosing:
Personnel Management Personnel Administration Organizational Data Organizational
Assignment Organizational Plan Define organizational units.
Where to find the target values
The target values correspond to the stores available in the configuration of the SAP POS system.
Mapping details
HRMD_ABA.HRMD_ABA05 WorkerManagement
HRMD_ABA.HRMD_ABA05

E1PLOGI->E1PITYP->E1P0001->ORGEH

WorkerManagement

WorkerManagement Worker WorkLocation HomeStore

Address Types
USE: The address types from SAP ERP are defined to list the different addresses that an employee
can have. These constants should never be changed.
Source Agency: ERPAddressType
Source Schema: ERPAddressTypeSchema
Target Agency: IXRetailAddressTypeCode
Target Schema: IXRetailAddressTypeCodeSchema
Where to find the source values
Address types are customizable in SAP ERP. You can find the address types available in the
configuration of your system (IMG) at the path specified below:
Personnel Management Personnel Administration Personal Data Addresses Create
address types.
Where to find the target values
The target values are the constants:

Home

Work

Configuration Guide for POS Integration

56

SAP AG

Delivery

Pickup

Billing

The values are case-sensitive. The target value is used to find the Home address from SAP ERP and
send it to the target Address fields in the GMEmpxTxn message.
Mapping details
HRMD_ABA.HRMD_ABA05 WorkerManagement
HRMD_ABA.HRMD_ABA05

E1PLOGI E1PITYP E1P0006 ANSSA

WorkerManagement

WorkerManagement Worker PersonalInformation Address


@TypeCode

Telephone Types
USE: The telephone types from SAP ERP are defined to list the different telephone numbers that an
employee can have. These constants should never be changed.
Source Agency : ERPTelephoneType
Source Schema: ERPTelephoneTypeSchema
Target Agency: IXRetailTelephoneTypeCode
Target Schema: IXRetailTelephoneTypeCodeSchema
Where to find the source values
The telephone communication types are customizable in SAP ERP. You can find the address types
available in the configuration of your system (IMG) at the path specified below:
Personnel Management Personnel Administration Personal Data Addresses Enter
communication types.
Where to find the target values
The target values are the constants below:

Home

Home2

Mobile

Work

Work2

WorkFax

HomeFax

Pager

The values are case-sensitive. The target value is used to find the Home Telephone number from
SAP ERP and send it to the target Phone field in the GMEmpxTxn message.
Mapping details
HRMD_ABA.HRMD_ABA05 WorkerManagement

HRMD_ABA.HRMD_ABA05

E1PLOGI E1PITYP E1P0006 COM [01-06]

WorkerManagement

WorkerManagement Worker PersonalInformation Telephone


@TypeCode

Configuration Guide for POS Integration

57

SAP AG
E-mail Types
USE: The e-mail types from SAP ERP are defined to list the different e-mails that an employee can
have. These constants should never be changed.
Source Agency: ERPEMailType
Source Schema: ERPEMailTypeSchema
Target Agency: IXRetailEMailTypeCode
Target Schema: IXRetailEMailTypeCodeSchema
Where to find the source values
The e-mail communication types are customizable in SAP ERP. You can find the address types
available in the configuration of your system (IMG) at the path specified below:
Personnel Management Personnel Administration Communication Create communication
types.
Where to find the target values
The target values are the constants below:

Work

Home

The values are case-sensitive.


Mapping details
HRMD_ABA.HRMD_ABA05 WorkerManagement

HRMD_ABA.HRMD_ABA05

E1PLOGIE1PITYP E1P0105 USRTY

WorkerManagement

WorkerManagement Worker PersonalInformation Email


@TypeCode

Inbound Physical Inventory Counts


Store ID
USE:

Physical Inventory Scenario, Generic, IXRetail to SAP ERP

Source Agency:

IXRetailPOSLogRetailStoreID

Source Schema:

IXRetailPOSLogRetailStoreIDSchema

Target Agency:

POSDWRETAILSTOREID

Target Schema:

POSDWRETAILSTOREIDSCHEMA

Where to find the source values


You can display the store ID in the SAP POS Configurator application. On the POS Configurations
screen, choose Code Maintenance, then Store.
Where to find the target values
In the SAP NetWeaver BW system, use transaction SE16 to display the contents of table KNA1. The
fields in PIPE correspond to the values of column KUNNR. This table contains the customer master
general data.
In the SAP ERP system, use transaction SE16 to display the contents of table T001W, column
WERKS.
Suggested or sample mapping
The target value range covers much more than stores. While most, if not all, source values should be
value-mapped to a target value, not all target values will be in the value mapping.
Configuration Guide for POS Integration

58

SAP AG
Mapping details
GMTLog IXRetail PIPE
GMTLog IXRetail SAP ERP
GMTLog

GMTLogTransactionLine[*]/StoreID
GMTLogTransactionLine[2]/TransferStore

IXRetail

Transaction/RetailStoreID
Transaction/InventoryTransaction/other/SAPTransfer/ToParty
Transaction/InventoryTransaction/other/SAPTransfer/FromParty

PIPE

IT_TRANSACTION/item[*]/RETAILSTOREID
IT_TRANSACTION/item[*]/GOODSMOVEMENT/item/TOPARTYID

SAP ERP

/WVINVE03/IDOC/EDI_DC40/SNDPRN

List of Buckets
USE: Physical Inventory Scenario, Generic, IXRetail to SAP ERP
Source Agency:

IXRetailPOSLogSAPBucketID

Source Schema:

IXRetailPOSLogSAPBucketIDSchema

Target Agency:

WVINVE_E1WVINH_LGORT

Target Schema:

WVINVE_E1WVINH_LGORTSCHEMA

Where to find the source values


You can display a list of buckets in the SAP POS Configurator application. On the POS
Configurations screen, choose Transaction Functions. Choose Inventory, then Accumulator / Bucket
Definition.
Where to find the target values
LGORT corresponds to a storage location (table T001L) that can be maintained in Customizing
(transaction SPRO). In Customizing, choose Enterprise Structure Definition Materials
Management Maintain storage location.
Suggested or sample mapping
Source

Target

001

0001

Mapping details
GMTLog IXRetail SAP ERP
GMTLog

GMTLogTransactionLine[8]/BucketID

IXRetail

Transaction/InventoryTransaction/InventoryCount/other/SAPBucketID

SAP ERP

/WVINVE03/IDOC/E1WVINH/LGORT

Configuration Guide for POS Integration

59