You are on page 1of 21

June 2007

English

Bonus Buys for POS


Integration
Business Process Procedure

SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
SAP Best Practices for Retail

Copyright

© Copyright 2007 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, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390,
OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity,
Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

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

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

Java is a registered trademark of Sun Microsystems, Inc.

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

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and
services mentioned herein as well as their respective logos are trademarks or registered trademarks
of SAP AG in Germany and in several other countries all over the world. 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.

Bonus Buys for POS integration Page 2 of 21


SAP Best Practices for Retail

Icons

Icon Meaning
Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type Style Description


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, source code, names of variables and parameters as well as
names of installation, upgrade and database tools.
EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the
ENTERkey.
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.

Bonus Buys for POS integration Page 3 of 21


SAP Best Practices for Retail

Contents
1 Scenario Bonus Buy for POS integration .....................................................................................5
1.1 Introduction ..........................................................................................................................5
1.1.1 Connection of Retail Systems........................................................................................5
1.1.2 Using SAP Exchange Infrastructure (SAP XI) for Conversion ........................................5
1.1.3 Remarks........................................................................................................................6
1.2 Prerequisites ........................................................................................................................7
1.3 Overview of Related Master Data.........................................................................................7
1.4 Bonus Buys ..........................................................................................................................7
1.4.1 Introduction ...................................................................................................................7
1.4.2 Procedure......................................................................................................................8
1.5 Limitations..........................................................................................................................21
1.6 References.........................................................................................................................21

Bonus Buys for POS integration Page 4 of 21


SAP Best Practices for Retail

1 Scenario Bonus Buy for POS integration


1.1 Introduction
1.1.1 Connection of Retail Systems
Retail uses the options of distributed data processing in the area of stores. The SAP ERP Retail
system provides open interfaces for connecting to POS systems. The POS uses SAP Transnet File
Transfer Server for data transmission. The SAP NetWeaver 2004s Exchange Infrastructure (XI)
system has the toolset and methodology available for developing a standard mapping schema to
convert the ERP messages to POS formats.

The following diagram shows how distributed retailing systems are typically used for the POS
integration:

1.1.2 Using SAP Exchange Infrastructure (SAP XI) for Conversion


SAP Exchange Infrastructure (SAP XI) provides a platform that allows different interfaces to connect
using a uniform technology. At present, all application systems are connected to XI using adapters.
The adapters are responsible for the conversion of the messages to and from the sender and receiver
protocols.
If retailers use the SAP XI system in conjunction with POS integration content, three scenarios are
possible:

Bonus Buys for POS integration Page 5 of 21


SAP Best Practices for Retail

1. Integrate SAP ERP (Retail) system with an SAP POS system


2. Integrate SAP ERP (Retail) system with a third-party POS system
3. Integrate a third-party ERP (Retail) system with an SAP POS system

The SAP POS system can be either:


SAP (GM) POS
SAP (TE) Enterprise POS

For illustration purposes, the POS system in the diagram is SAP (GM) POS, which requires the use
of a file adapter. For SAP (TE) Enterprise POS system, a JMS adapter is used instead.
For more information, see the SAP XI documentation on the SAP Help Portal.

1.1.3 Remarks
All of the master data in the SAP ERP system can be transferred using the POS interface. The scope
of this document is to describe the outbound POS interface for the bonus buy scenarios, as the POS
integration content has specific requirements for this functionality.

1.2 Prerequisites
The POS only transfers functions correctly if the basic Customizing settings have been made for all
the partners involved, for example, for stores. This means that file ports have to be set up, for
example, and that the partner profiles have to be maintained.

Bonus Buys for POS integration Page 6 of 21


SAP Best Practices for Retail

The XI system must also be configured to receive bonus buy data from ERP and send it to the POS.
For more information, see the SAP Business Package for Store Connectivity POS Integration
Configuration Guide or any other relevant Customizing documentation.

1.3 Overview of Related Master Data


To execute the scenario, use the master data that corresponds to your setup of the preconfigured
system. For the relevant key descriptions, see the following table:

ARTICLE1 ART-01-POS147
ARTICLE2 ART-01-POS148
PRICE1 $30.00 USD
PRICE2 $25.00 USD
STORE1 2101

For the bonus buy scenarios, the relevant discount condition types have been predefined as follows:
Condition type Access seq Bonus buy type Scale basis
BB01 BB00 P (Price) B
BB02 BB00 R (abs disc) B
BB03 BB00 % (% disc) B
BB04 BB00 N (free good) C

1.4 Bonus Buys


1.4.1 Introduction
A bonus buy defines the set of item(s) for which a discount type can be granted when certain
requirements are met. Fixed (or absolute) discount, percentage discount, or free goods discount are
possible for bonus buy conditions. Note that bonus buys in the ERP system are referred to as mix
matches in the POS system.

The following is a subset of the bonus buys scenarios currently supported for the POS integration
content:

Bonus Buy Scenario Supported in GM Supported in TE

Same Combination of Same Combination of


Item items Item items
Buy y number of z items, get X X* X
one free (lowest price*)
Buy y number of z items, get X X
x percent off an additional
item
Buy y number of z items, get X X X

Bonus Buys for POS integration Page 7 of 21


SAP Best Practices for Retail

x percent off purchase


Buy y number of z items, get X X
x dollars off an additional
item

Buy y number of z items, get X X X


x dollars off purchase

Buy one item, get free gift X X X


(same as first scenario)

Note that z items can be the same item or combination of items.

1.4.2 Procedure
The following are steps involved in the end-to-end process for handling bonus buys from ERP to the
POS.
Create article grouping
Create bonus buy
Download using POS outbound
POS sales

1.4.2.1 Create Article Grouping


All the articles that can be considered in the bonus buy are included in the article grouping. Individual
articles can be defined as article groups.
PATH Logistics Retailing Master Data VBG1
Conditions /Arrangements Conditions
Sales Bonus Buy Article Grouping
Create
INPUT Article grouping ‘ArtGroupXX‘ (XX=Optional)
Description <Optional>
TABSTRIP [Article]
INPUT Article >ARTICLE1
Number ‘1’
Unit ‘EA’
Article >ARTICLE2
Number ‘1’
Unit ‘EA’
BUTTON [SAVE]
MESSAGE The article grouping was saved successfully.
BUTTON [BACK]

1.4.2.2 Create Bonus Buy


You can use the bonus buy function to create conditions that only apply if certain prerequisites and
conditions (defined by yourself) have been met. You decide whether the discount for each purchase
is to be granted only once or several times, or which type of bonus buy will be used: multi-deal (OR
link) or combination deal (AND link). For the integration, the bonus buy type will always be multi-deal.
Case 1: This scenario describes a bonus buy in which a free good (with the lowest price) is
granted upon the purchase of three items articles from the same article grouping.

Bonus Buys for POS integration Page 8 of 21


SAP Best Practices for Retail

PATH Logistics Retailing Master Data VBK1


Conditions/Arrangements Conditions Sales
Bonus Buy Bonus Buy Create
INPUT Discount type ‘BB04‘
Bonus buy <Bonus**>
Description <Bonus buy**>
BUTTON [EXECUTE]
POPUP ‘Key Combination’; select radio button Confirm.
<OPTIONAL> “SalesOganization/SalesChannel/Plant/
BonusBuy/Material/SalesUnit”
INPUT Subscreen: Key Combination
Sales organization ‘RC10’
Distribution channel ‘R1’
Valid on <Today’s date>
to <Today’s date + x days>
Subscreen: Condition Is Agreed for
Article grouping ‘X’

Grouping
Min qty Grouping from 1.4.2.1
For
‘3’
Unit
’4’
Are free good
‘EA‘
‘1‘
Subscreen: Prerequisites
Article Grouping
Grouping from 1.4.2.1
Number
‘1‘
Unit
‘EA‘
BUTTON [ENTER]
[SAVE]
MESSAGE The condition records …saved.
BUTTON [BACK]
Notes on the input fields:
o Minimum Quantity indicates the minimum number of items to purchase.
o For indicates the total number of items to be purchased in the bonus buy.
o Are free good indicates the number of free items.

Case 2: This scenario describes a bonus buy in which a 50% discount is granted on an
additional item upon the purchase of two articles from the same article grouping.
PATH Logistics Retailing Master Data VBK1
Conditions/Arrangements Conditions
Sales Bonus Buy Bonus Buy Create
INPUT Discount type ‘BB03‘
Bonus buy <Bonus**>
Description <Bonus buy**>
BUTTON [EXECUTE]

Bonus Buys for POS integration Page 9 of 21


SAP Best Practices for Retail

POPUP ‘Key Combination’; select radio button Confirm.


<OPTIONAL> “SalesOganization/SalesChannel/Plant/
BonusBuy/Material/SalesUnit”
INPUT Subscreen: Key Combination
Sales organization ‘RC10’
Distribution channel ‘R1’
Valid on <Today’s date>
to <Today’s date + x days>
Subscreen: Condition Is Agreed for ‘X’
Article grouping

Grouping
Grouping from 1.4.2.1
% Discount
‘50’

Subscreen: Prerequisites
Grouping from 1.4.2.1
Article Grouping
‘1‘
Number
‘EA‘
Unit
BUTTON [ENTER]
SELECTION Choose condition line.
BUTTON [F2]
INPUT Subscreen: Scales
Minimum qty ‘2’
BUTTON [ENTER]
[BACK]
[SAVE]
MESSAGE The condition records …saved.
BUTTON [BACK]
Note that the Minimum Quantity input field specifies the quantity of items to purchase in order to
receive the percentage discount for an additional item.

Case 3: This scenario describes a bonus buy in which a $30 discount is granted on the total sale
upon the purchase of two articles from the same article grouping.
PATH Logistics Retailing Master Data VBK1
Conditions/Arrangements Conditions
Sales Bonus Buy Bonus Buy Create
INPUT Discount type ‘BB02‘
Bonus buy <Bonus**>
Description <Bonus buy**>
BUTTON [EXECUTE]
POPUP ‘Key Combination’; select radio button Confirm.
<OPTIONAL> “SalesOganization/SalesChannel/Plant/
BonusBuy/Material/SalesUnit”

Bonus Buys for POS integration Page 10 of 21


SAP Best Practices for Retail

INPUT Subscreen: Key Combination


Sales organization ‘RC10’
Distribution channel ‘R1’
Valid on <Today’s date>
to <Today’s date + x days>
Subscreen: Condition Is Agreed for ‘X’
Total Sale

Condition value
‘30’
Currency
’USD’

Subscreen: Prerequisites
Grouping from 1.4.2.1
Article Grouping
‘1‘
Number
‘EA‘
Unit
BUTTON [ENTER]
SELECTION Choose condition line.
BUTTON [F2]
INPUT Subscreen: Scales
Minimum qty ‘2’
BUTTON [ENTER]
[BACK]
[SAVE]
MESSAGE The condition records …saved.
BUTTON [BACK]
Notes on the input fields:
o Minimum Quantity specifies the quantity of items to purchase in order to get the dollar
amount off the total sale.

The remaining scenarios are variations of the bonus buys defined above and can be created
with the information provided.

1.4.2.3 POS Outbound Interface - Download to POS


You use the POS interface - outbound to provide your store POS systems with all the relevant data
that the external systems require to handle the store processes independently.
The POS outbound interface supplies in-store POS systems with current data at regular intervals.
This data is downloaded from ERP to the POS system. The ERP system formats the data in IDoc
format for the POS interface, taking into account the current store assortment, and transfers these
IDocs to the store systems using ALE technology. The system determines which data has changed up
to the current date and which data has changed during the configured runtime.
In addition to the initial supply of data, you have the option of making a direct request. This means
that you can request specific data directly without scheduling beforehand.
SAP ERP for Retail contains specific messages and IDocs for exchanging data with POS systems.
You can see the structure, contents, and description of the IDocs in transaction WE60. The

Bonus Buys for POS integration Page 11 of 21


SAP Best Practices for Retail

appropriate IDocs for the POS interface can be found under the basic types with the object name
WP*. For the bonus buy scenarios, the WPDBBY IDoc is used for the download.

1.4.2.3.1 Procedure
The following section describes how the POS downloads are triggered manually.
PATH Logistics Retailing Master Data WPMA
Conditions/Arrangements Conditions
Sales Bonus Buy Subsequent
Processing POS Outbound
INPUT Sales organization ‘RC10’
Distribution channel ‘R1’
Store >STORE1
Subscreen: Bonus Buy Data
Transfer bonus buy data ‘X’
Bonus buy No. from 1.4.2.2
BUTTON [EXECUTE] Make note of the IDoc created.
[BACK]
Because of the variety of listing conditions, IDocs of different sizes might be sent to the various
stores.

Note that:
1. The data can only be downloaded if you have already maintained bonus buys for this
store in your system.
2. Bonus buy data can only be transferred by means of manual selection.
3. In the case of a deletion in ERP, the bonus buy data can be downloaded automatically
once prompted. If you choose to download the information at a later time, the transfer
must be done manually.

You can display the IDocs created in the POS Monitor in order to check that the changes you have
made have actually been transferred as follows:
PATH Logistics Retailing Distributed Retailing WE02
POS Interface Monitor POS Interface
Display IDoc Chronological
INPUT IDoc number Number of IDoc created above.
BUTTON [EXECUTE]
SELECTION Expand the tree: Data records
DOUBLE-CLICK E1WPA01 Here, you can check the contents
of the IDoc segments.
BUTTON [EXIT]

For more information on the details of the Bonus Buy Conditions IDoc, please refer to the use cases
for the Download of Bonus Buys Promotions.

Bonus Buys for POS integration Page 12 of 21


SAP Best Practices for Retail

1.4.2.3.2 Overview of Mix Matches in SAP (GM) POS - Store


Manager
The following section shows how the SAP (GM) POS interprets the mix matches once they are
downloaded. The information is displayed in the POS Store Manager.

The table below provides a description of the required entries for each type of mix match scenario:
Fields Description
Complete MM This field indicates that the prerequisites of the mix match must be
completely satisfied.
Calculation at Total Time This field indicates that the mix match must be applied at the end of the
transaction.
Discount On Lowest This field indicates that the discount is applied to the article with the
Price lowest price in a set of articles with different prices.
Alt1 Buy Quantity This field indicates the minimum number of items the customer must
purchase to receive the mix match discount.
Alt1 Percentage Off This field specifies the percentage amount discount to be applied to the
number of items specified in Alt1 Buy Quantity field.
Alt2 Buy Quantity This field indicates the number of items for which the mix match is
granted.
Alt2 Dollar Off This field specifies the dollar amount discount to be applied to the number
of items specified in Alt2 Buy Quantity field or to be applied to the total sale.
Alt2 Percentage Off This field specifies the percentage amount discount to be applied to the
number of items specified in Alt2 Buy Quantity field.
Apply Disc To Alt This field specifies whether the discount is prorated or not. For the total
sale, it is prorated.

Case 1: This scenario describes a mix match in which a free good (with the lowest price) is
granted upon the purchase of three item articles.

Bonus Buys for POS integration Page 13 of 21


SAP Best Practices for Retail

Case 2: This scenario describes a mix match in which a 50% discount is granted on an
additional item upon the purchase of two articles.

Case 3: This scenario describes a mix match in which a 50% discount is granted on the total
sale upon the purchase of two articles.

Bonus Buys for POS integration Page 14 of 21


SAP Best Practices for Retail

Case 4: This scenario describes a mix match in which a $10 discount is granted on an additional
item upon the purchase of two articles.

Case 5: This scenario describes a mix match in which a $10 discount is granted on the total sale
upon the purchase of two articles.

Bonus Buys for POS integration Page 15 of 21


SAP Best Practices for Retail

Note that the mix matches can be created in the SAP (GM) POS with the Configurator. If the
bonus buys are downloaded, they cannot be viewed with this tool. The information that is entered for
the mix matches in the Configurator is the same data that is shown above from the POS Store
Manager.

1.4.2.3.3 Overview of Mix Matches in SAP (TE) Enterprise POS -


Manager
The following section shows how the SAP (TE) Enterprise POS interprets mix matches once they are
downloaded. The information is displayed in the POS Manager for a particular store.

The table below provides a description of the required entries for each type of mix match scenario:
Fields Description
Unique Item, Item or Any The selected field indicates where the items must be the same,
Item different, or a combination.
Complete Mix Match This field indicates that the prerequisites of the mix match must be
completely satisfied.
Prorated This field specifies whether the discount is prorated or not.
Op An operator that identifies how the Quantity is to be used.
Qty This field indicates the minimum number of items the customer must
purchase to receive the mix match discount.
Discount This field specifies the type of discount, for example, a percentage or
absolute discount.
Amount This field indicates the amount of the discount, for example, the
dollar value or percentage.

Bonus Buys for POS integration Page 16 of 21


SAP Best Practices for Retail

Apply To This field determines whether the price is the price of each item in
the group, or the price of the entire group.
Lowest Priced Items This field indicates whether the price adjustment applies to the lowest
priced item.

Case 1: This scenario describes a mix match in which a free good is granted upon the purchase
of three of the same article.

Case 2: This scenario describes a mix match in which a 50% discount is granted on the total
sale upon the purchase of two of the same article.

Bonus Buys for POS integration Page 17 of 21


SAP Best Practices for Retail

Case 3: This scenario describes a mix match in which a $10 discount is granted on the total sale
upon the purchase of two of the same article.

1.4.2.4 POS Sales


The software of the POS system determines how sales are handled. For our purposes, the POS
clients are used to illustrate how the mix matches are posted.

Bonus Buys for POS integration Page 18 of 21


SAP Best Practices for Retail

The POS systems can consider the data transferred by analyzing all the articles scanned in one
transaction to determine whether the articles are being purchased in the relevant combination. If so,
the special offer is granted.

1.4.2.4.1 Procedure
Case 1: This scenario describes a mix match in which a free good (with the lowest price) is
granted upon the purchase of two of the same article.
INPUT Enter Item >ARTICLE1
BUTTON [ENTER]
INPUT Enter Item >ARTICLE1
BUTTON [ENTER]
INPUT Enter Item >ARTICLE1
BUTTON [ENTER] (TE only) Bonus Buy description
is displayed with the rebate of
$30.00.

[+] or [TOTAL]
(GM only) Bonus Buy description
is displayed with the rebate of
$30.00.
Total amount due is displayed.

[CASH]
INPUT Enter Tender Amount ’60.00’
BUTTON [ENTER]
MESSAGE Change (or Cash) Due ...

Case 2: This scenario describes a mix match in which a 50% discount is granted on an
additional item upon the purchase of two of the same article.
INPUT Enter Item >ARTICLE1
BUTTON [ENTER]
INPUT Enter Item >ARTICLE1
BUTTON [ENTER]
INPUT Enter Item >ARTICLE1
BUTTON [ENTER] Bonus Buy description is
displayed with the rebate of
$15.00.

[+] or [TOTAL]
Total amount due is displayed.

[CASH]
INPUT Enter Cash Tender Amount ’75.00’
BUTTON [ENTER]

Bonus Buys for POS integration Page 19 of 21


SAP Best Practices for Retail

MESSAGE Change (or Cash) Due ...

Case 3: This scenario describes a mix match in which a $30 discount is granted on the total sale
upon the purchase of two of the same article.
INPUT Enter Item >ARTICLE1
BUTTON [ENTER]
INPUT Enter Item >ARTICLE1
BUTTON [ENTER]

[+] OR [TOTAL] Bonus Buy description is


displayed with the rebate of $30.
Total amount due is displayed.

[CASH]
INPUT Enter Cash Tender Amount ’30.00’
BUTTON [ENTER]
MESSAGE Change (or Cash) Due ...

1.4.2.4.2 Display of POS GM Register (POS Xpress)


The following screenshot illustrates how the register display looks when the mix match “Buy two get
$10 off total purchase” is applied (using the steps defined in Section 1.4.2.4.1).

Bonus Buys for POS integration Page 20 of 21


SAP Best Practices for Retail

1.4.2.4.3 Display of SAP (TE) Enterprise POS Register (POS Client)


The following screenshot illustrates how the register display looks when the bonus buy “Buy three
get one free” is applied (using the steps defined in Section 1.4.2.4.1).

1.5 Limitations
1. When an ERP download is triggered, all active bonus buys should be sent down to the POS each
time. A delta will delete the previously downloaded bonus buys.
2. Any mix matches created in the SAP (GM) POS Configurator will overwrite the previous mix
match data. For instance, if bonus buys were downloaded from ERP and a conversion is
performed through the Configurator, the previously imported data will be deleted. The same is
true if a download occurs after a conversion from the Configurator.
3. The SAP (GM) POS interface does not allow for alphanumeric mix match IDs as the ERP system
does. Value mappings are used through XI to solve this issue. Refer to the use case
documentation for Download of Bonus Buy Promotions to SAP (GM) POS for more details on the
value mapping.

1.6 References
SAP Business Package for Store Connectivity POS Integration Configuration Guide 2.0
Use Case for Download of Bonus Buy Promotions to (GM) POS
Use Case for Download of Bonus Buy Promotions to (TE) POS
Transactionware GM version 9.5 Store Manager User Guide
Transactionware GM version 9.5 Configurator User Guide
Transactionware Enterprise Store Solutions Guide Version 2.0

Bonus Buys for POS integration Page 21 of 21