Guide CCO Server EN

CUSTOMER
SAP Customer Checkout 2.0 Feature Pack 09

Document Version: 2.0 Feature Pack 09 – 2/28/2020
SAP Customer Checkout manager Guide

© 2020 SAP SE or an SAP affiliate company. All rights reserved.
THE BEST RUN

Content
1 SAP Customer Checkout Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2 What You Can Do with SAP Customer Checkout Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2.1 Benefits of using SAP Customer Checkout manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2 Country/Region Versions and Languages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.3 Technical Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Integration with ERP Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
SAP Event Ticketing Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Minimum Hardware Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Operating System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Database Management System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Software Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3 Installing SAP Customer Checkout manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

3.1 Preparing the Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Downloading the SAP Java Virtual Machine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
3.2 Installing Prerequisite Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Database Management System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Java Application Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
4 Updating SAP Customer Checkout manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
5 Working with SAP Customer Checkout Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

5.1 Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
5.2 Logging In to SAP Customer Checkout manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Creating New User Passwords in SAP Customer Checkout manager. . . . . . . . . . . . . . . . . . . . . .28
5.3 SAP Customer Checkout manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Tenants. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
5.4 Point of Sales Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Organizational Structures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Time Recordings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Time Recordings Export. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Monitoring Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

2 CUSTOMER Content
Receipt Exports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Vouchers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Receipts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Sales Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Articles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Price Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
POS Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Stock Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Migrations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Customers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187
Central Drawer Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Business object locks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .200
5.5 Loyalty Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Coupons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Point Assignments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209
Loyalty Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Promotion Code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Loyalty Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Loyalty Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
6 Integrate SAP Customer Checkout Manager with SAP Customer Checkout. . . . . . . . . . . . . . 226
7 Using SAP Customer Checkout Manager as the Backend System. . . . . . . . . . . . . . . . . . . . . . 227

7.1 Configure and Create Data in SAP Customer Checkout manager. . . . . . . . . . . . . . . . . . . . . . . . . . 227
7.2 Initial Configuration Settings in SAP Customer Checkout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
7.3 Maintain Relevant Settings in SAP Customer Checkout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
8 Using SAP Customer Checkout manager in Multi-Tenant Mode. . . . . . . . . . . . . . . . . . . . . . . 229
9 Initial Configuration of SAP Customer Checkout manager. . . . . . . . . . . . . . . . . . . . . . . . . . . 230

9.1 Resetting the Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
10 POS Security Regulation 2020 for Germany. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

10.1 Data Export for DSFinV-K Interface in SAP Customer Checkout manager. . . . . . . . . . . . . . . . . . . . 233
11 POS Software Certification in Compliance with NF 525 (France). . . . . . . . . . . . . . . . . . . . . . 235
12 Security Guidelines and Recommendations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

12.1 Initial Password and Password Policy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
12.2 Resetting the Admin User Password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
12.3 User Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
12.4 Firewall. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

Content CUSTOMER 3
12.5 Auto Logout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
12.6 Secure Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
12.7 Virus Scanner. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .238
12.8 Software Updates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

4 CUSTOMER Content
1 SAP Customer Checkout Manager
If you are working with SAP Customer Checkout and plan to include the SAP Customer Checkout manager, this
guide is for you. It shows how to install, configure, and run SAP Customer Checkout manager, both from a
technical and from a business viewpoint.
You’ll also get an overview of SAP Customer Checkout manager, its components, the integration options with
SAP Customer Checkout, as well as instructions about how to work with the application.

SAP Customer Checkout Manager CUSTOMER 5
2 What You Can Do with SAP Customer
Checkout Manager
SAP Customer Checkout manager is a web application and a component of SAP Customer Checkout. It forms
a basis for the central management of vouchers, loyalty users, bonus points, and coupons used in SAP
Customer Checkout.
 Note
Loyalty users within SAP Customer Checkout manager do not represent the customers stored in your ERP
system or in the SAP Customer Checkout application.
SAP Customer Checkout manager also offers the opportunity to include and manage a loyalty points program
through the Loyalty API.
Example
Users can register via the Loyalty API and use the loyalty points program.
You can create and edit coupons for your loyalty users. Vouchers can be created and managed in SAP
Customer Checkout manager, and then used in SAP Customer Checkout. The application serves as central
platform and enables integration with SAP Event Ticketing.
SAP Customer Checkout manager helps you with:
● Voucher and user management

● Handling of coupons
● Assigning bonus points to loyalty users
● Integration with SAP Event Ticketing
2.1 Benefits of using SAP Customer Checkout manager
● Manage all vouchers centrally

● Handle multiple organizational units within your company
● Manage all receipts posted from your SAP Customer Checkout applications centrally
● Use SAP Customer Checkout manager as your back-end system

6 CUSTOMER What You Can Do with SAP Customer Checkout Manager
● Track the time recording of all employees within your organization
● Monitor all your point-of-sale applications to react quickly
● Update your point-of-sale software versions and installations centrally within a short space of time
● Generate sales reports for your POS systems and for specific time periods
● Import articles, prices, and users via a CSV file
● Create articles and price lists in a few steps when using SAP Customer Checkout manager as a back-end
system
● Handle sales sets that you can use in your SAP Customer Checkout applications
● Manage loyalty users, promotion codes, and coupons centrally
● Analyze the buying behavior of your loyalty users
● Create vouchers and coupons in a few short steps
● Benefit from a simple user interface within the configuration
● Adopt user profiles and the related information from SAP Event Ticketing accounts
● Reward your loyalty users with customized coupons
2.2 Country/Region Versions and Languages
SAP Customer Checkout manager is available in various languages and countries/regions.
Country Versions
SAP Customer Checkout manager is officially supported in Germany, Austria, Switzerland (DACH), Great
Britain, Ireland, and France.
However, if you are a partner or customer of another country/region, you are free to evaluate the software. If it
meets all functional and legal requirements of your country/region, you can purchase the software in the
country/region version of your choice.
Languages
The UI is available in the following languages:
● English
● German
● Dutch
● French
● Italian
● Japanese
● Polish
● Russian

What You Can Do with SAP Customer Checkout Manager CUSTOMER 7
● Portuguese (Brazil)
● Spanish
● Danish
● Swedish
● Hebrew
● Simplified Chinese
● Arabic (limited support)
 Note
SAP Customer Checkout manager supports the Arabic language, but only on a smaller scale. Arabic is
made available to users to provide support and guidance. However, its current scope could not fulfill all
of the requirements of an Arabic-speaking user.
All terms have been translated and are displayed on the user interface. However, with a few exceptions,
the user interface itself and the layout of the user interface is not aligned from right to left (as would be
required for Arabic script).
For the foreseeable future, there are also no plans to align all user interfaces from right to left for Arabic
script. Errors would still be resolved, but every change request requiring effort in terms of Arabic font
on the user interface or the orientation from right to left will either not be carried out or will be decided
on by the product team on a case-by-case basis.
2.3 Technical Overview
When using SAP Customer Checkout manager, the interaction between components works as follows:
● SAP Customer Checkout manager web application

The web application provides you with the central management of vouchers, loyalty users, and coupons.
● SAP Customer Checkout application
SAP Customer Checkout serves as basis for using the SAP Customer Checkout manager application. It is a
point of sale solution that is locally installed on your POS system and provides views for all sales
transactions within a retail or merchandise shop.
 Note
With the release of SAP Customer Checkout 2.0, all vouchers that have been created and edited in SAP
Customer Checkout manager, can be used and redeemed in SAP Customer Checkout.
● Optional: SAP SAP Event Ticketing

The SAP Event Ticketing solution lets you generate ticket sales for your events across all sales channels. In
SAP Customer Checkout manager, you have the option to integrate with SAP Event Ticketing to
authenticate loyalty users.

2.3.1 Integration with ERP Systems
The application can run without an ERP system, so no integration with ERP systems such as SAP Business
One, SAP Business ByDesign, or SAP ECC is needed.
However, SAP Customer Checkout manager provides the interface for integration with SAP Event Ticketing.
The integration can be set within the Configuration tab of SAP Customer Checkout manager.
 Note
Integration with SAP Event Ticketing is supported only in SAP Event Ticketing 6.1
2.3.2 SAP Event Ticketing Integration
SAP Customer Checkout can be integrated with SAP Event Ticketing.
 Note
SAP Event Ticketing helps you sell tickets for your events across all sales channels. You gain an overview of
your customers and costs and maximize your revenue per seat through efficient ticket sales. For more
information about SAP Event Ticketing, see https://help.sap.com/viewer/product/
SAP_EVENT_TICKETING/.
With the integration of SAP Customer Checkout with SAP Event Ticketing, you can retrieve tickets directly from
SAP Customer Checkout and place them in a shopping cart. This means that is one sales and payment process
in SAP Customer Checkout.
Various steps and settings are required for integrating SAP Customer Checkout with SAP Event Ticketing:
● The destination for SAP Event Ticketing is configured on the Destinations tab on the Configuration tile in
SAP Customer Checkout manager. For more information, see Configuring the Destination for SAP Event
Ticketing Integration [page 65].
● Create a user for communication with the SAP Event Ticketing system. For more information, see Users
[page 29] on the External credentials tab.
● Articles must be created within the Articles tile in SAP Customer Checkout manager, with the relevant
account from the SAP Event Ticketing system. For more information, see Creating an Article for Integration
with SAP Event Ticketing [page 144].
● For calling up tickets from the sales screen in SAP Customer Checkout, you first have to create a button
that triggers the Fetch external Business Object function. Go to the POS Configuration tile under Quick
Selections in SAP Customer Checkout manager to do so. For more information, see Pushbuttons with
Special Features [page 169].
● Download separate print software "SAP Event Ticketing local" (ET local) for printing tickets in SAP
Customer Checkout from SAP Service Marketplace. For more information, see "SAP Event Ticketing
Integration" in the SAP Customer Checkout Configuration Guide.
● You configure the communication with SAP Event Ticketing under Configuration in SAP Customer
Checkout. For more information, see the SAP Customer Checkout Configuration Guide.

2.3.3 Minimum Hardware Requirements
SAP Customer Checkout manager can only run on a system that fulfills the minimum hardware requirements.
 Note
These hardware requirements do not include the database server hardware requirements.
Hardware Requirements
Hardware Minimum Recommended
CPU Dual core processor with 2GHz > Quad core processor with 2 GHz
RAM 2 GB >= 8 GB
Hard disc 64 GB > 64 GB SSD
2.3.4 Operating System Requirements
SAP Customer Checkout manager can run on the following operating systems.
The following operating systems are supported:
● Microsoft Windows 7 32-bit

● Microsoft Windows 8.1 32-bit
● Microsoft Windows 8.1 64-bit
● Microsoft Windows Server 2012/ 64-bit
● Microsoft Windows Server 2012 R2/ 64-bit
● Microsoft Windows Server 2016/ 64-bit
● Microsoft Windows Server 2016 R2/ 64-bit
● SUSE Linux Enterprise Server 15 64-bit
 Note
For up-to-date information, see the Product Availability Matrix at http://service.sap.com/sap/support/pam

.
2.3.5 Database Management System Requirements
SAP Customer Checkout manager runs on several database management systems.
The following database management systems are supported:

● Microsoft SQL Server 2012 Standard
● Microsoft SQL Server 2014 Standard
● SAP HANA Database 1.0
 Note
SAP HANA Database 1.0 is supported as of SAP Customer Checkout manager 2.0
● SAP HANA Database 2.0
 Note
SAP HANA Database 2.0 is supported only as of SAP Customer Checkout manager 2.0 Feature Pack
05.
If you are using an older version of SAP Customer Checkout manager, you first need to update it to
version 2.0 FP05 or higher, before updating SAP HANA 1.0 to SAP HANA 2.0.
●  Note
See the SAP HANA product documentation for details on which operating systems are supported by
SAP HANA.
2.3.6 Software Requirements
To install and run SAP Customer Checkout manager, you need additional software.
The following software is required:
● Java VM Java SE Runtime Environment Version 8 or SAP Java Virtual Machine 8.1
● Java Application Server
 Recommendation
To install the Java Application Server, Apache Tomcat Version 8.5 or above is recommended, for the
latest information, see the Product Availability Matrix, under http://service.sap.com/sap/support/pam
.
For Apache Tomcat, the initial memory pool must be set to at least 1024 MB and the maximum
memory pool to at least 4096 MB.
● Database management system

You can use the embedded Apache Derby database
 Note
Do not use the embedded Apache Derby database in a production environment.
● Google Chrome web browser
The following separate database systems are supported with SAP Customer Checkout manager:
● SAP HANA, using SAP Hana JDBC Driver (ngdbc.jar version 1.92.0)

● Microsoft SQL Server, using Microsoft SQL Server JDBC Driver 3.0
● JNDI, using the Java JNDI API
The necessary JDBC drivers are included in the SAP Customer Checkout manager Web Application
Archive and can be selected during the initial setup of the SAP Customer Checkout manager.
 Note
For up-to-date information, see the Product Availability Matrix at http://service.sap.com/sap/support/pam

.

3 Installing SAP Customer Checkout
manager
This section describes how to install SAP Customer Checkout manager and perform the initial technical
configuration when starting the software.
 Note
When installing SAP Customer Checkout manager, make sure that the version matches the release version
and the version of the feature pack of SAP Customer Checkout.
3.1 Preparing the Installation
Context
The installation file is available for download in the SAP Software Download Center and is included as a
separate component in the SAP Customer Checkout download file.
Procedure
1. Go to https://launchpad.support.sap.com/#/softwarecenter .
2. Choose Installations and Upgrades -> By Category -> INDUSTRY-SPECIFIC COMPONENTS -> SAP
CUSTOMER CHECKOUT -> SAP CUSTOMER CHECKOUT 2.0 -> SAP CUSTOMER CHECKOUT MANAGER
2.0.

Installing SAP Customer Checkout manager CUSTOMER 13
3.1.1 Downloading the SAP Java Virtual Machine
This section describes how to download SAP JVM 8.1 and the required archiving program SAPCAR.
Context
SAP JVM 8.1 and the archiving program SAPCAR must be downloaded in accordance with the operating
system used.
Procedure
2. Choose Installations and Upgrades -> By Category -> INDUSTRY-SPECIFIC COMPONENTS -> SAP
CUSTOMER CHECKOUT -> SAP CUSTOMER CHECKOUT 2.0 -> SAP CUSTOMER CHECKOUT 2.0 -> SAP
JVM 8.1
3. Select the SAP JVM 8.1 version appropriate for your operating system and download it.
 Note
For a 64-bit Microsoft Windows operating system, choose WINDOWS ON X64 64BIT.
For a 64-bit Linux operating system, choose LINUX ON X86_64 64BIT.
Downloading SAPCAR 7.21

5. Select Downloads from the dropdown list and search for SAPCAR 7.21.
6. Select the SAPCAR 7.21 category in the search result.
7. Select the SAPCAR 7.21 version appropriate for your operating system and download it.
 Note
For a 64-bit Microsoft Windows operating system, choose WINDOWS ON X64 64BIT.
For a 64-bit Linux operating system, choose LINUX ON X86_64 64BIT.
3.2 Installing Prerequisite Software
Before you start installing the SAP Customer Checkout manager, make sure that the prerequisite software is
installed and set up on the system.
The following software is required before you can install the SAP Customer Checkout manager application:

14 CUSTOMER Installing SAP Customer Checkout manager
● Java Application Server
● A database management system
3.2.1 Database Management System
3.2.1.1 Using the Apache Derby Database
When using the Apache Derby database, no additional configuration steps are necessary for the installation of
SAP Customer Checkout manager. Apache Derby is a file-based database created automatically by SAP
Customer Checkout manager and used in embedded mode.
 Recommendation
3.2.1.2 Using SAP HANA Database
Context
The installation of SAP Customer Checkout manager in combination with a SAP HANA database requires a
configured and running SAP HANA database server.
Procedure
1. Start your SAP HANA database.

2. Create a new schema within your SAP HANA database, in order to structure the SAP Customer Checkout
manager database, then enter a name for the schema (for example: CCOm).
 Caution
SAP recommends creating your own user for the database connection. For reasons of security you should
avoid using the default SYSTEM user for the database connection, as this user possesses a wide range of
authorizations that are not required by SAP Customer Checkout manager.
3. Expand the Security directory and choose the Users subdirectory.

4. Right-click and select New user to create the new user.
5. Specify a user name, password, and password confirmation.
6. On the Object Privileges tab, add the newly created db schema (for example: CCOm).
7. Enable the CREATE ANY permission for the object.
8. Save your changes.
9. Use the newly created user for the database connection during the initial configuration of SAP Customer
Checkout manager.
3.2.1.3 Using Microsoft SQL Server
Context
When using a Microsoft SQL Server database, you need to create a separate database in order to install SAP
Customer Checkout manager.
 Note
If you are installing Microsoft SQL Server for the first time, we recommend that you configure the following:
● Feature Selection:
Make sure that the following checkboxes are selected:
○ Database Engine Services
○ Management Tools – Complete
● Collation: SQL_Latin1_General_CP1_CS_AS
● Authentication mode: Mixed mode
Procedure
1. Open Microsoft SQL Server Management Studio.

2. Create a new database for SAP Customer Checkout manager and enter a name (for example, CCOM).
3. After the new database for SAP Customer Checkout manager has been built, select the new database and
choose the Security folder.
4. Create a new schema below the Security folder.
5. Enter a name for the newly created schema (for example, CCOM).
6. Use the default user sa, which is automatically created during the Microsoft SQL Server installation
process as database user.
If you are using an SAP HANA or Microsoft SQL Server, the respective system has to be running before you
start the Java Application Server on which SAP Customer Checkout manager is deployed.

Optional: Creating a New User in Microsoft SQL Server
If you do not want to use the default user account sa, you can also create an alternative user account in
Microsoft SQL Server.
Follow these steps to create a new user in Microsoft SQL Server:
1. Open Microsoft SQL Server Management Studio.

2. In the Object Explorer window, expand the Security folder.
3. Choose the Logins subfolder and right-click to create a new login.
4. In the window that opens, enter the login details.
5. On the General tab, enter a login name and select SQL Server authentication.
6. Enter a password for this login and confirm the password.
7. On the Server Roles tab, select the necessary server roles for this login.
 Note
Make sure that you have selected the server roles public and sysadmin.
8. On the User Mapping tab, map the user to the respective database that you have created (for example,
CCOM).
9. Choose OK to save your changes.
10. Select and expand the Security folder of your new database (for example, CCOM).
11. Select the Users subfolder, and verify that the login that you created is displayed as a new user.
For more information, see the Microsoft documents at www.microsoft.com.
3.2.2 Java Application Server
 Recommendation
To install the Java Application Server, Apache Tomcat Version 8.5 or above is recommended, for the latest
information, see the Product Availability Matrix, under http://service.sap.com/sap/support/pam .
3.2.2.1 Installing with Apache Tomcat on Microsoft

Windows
Prerequisites
Ensure that you have completed the required database steps described in Database Management System
[page 15], before you perform the following steps.

Context
 Recommendation
For Apache Tomcat, the initial memory pool must be set to at least 1024 MB and the maximum memory
pool to at least 4096 MB.
Procedure
1. Go to http://tomcat.apache.org/ and download the installation file for Apache Tomcat.

2. To start the installation, double-click the .exe file.
3. Perform the steps required for installation.
4. Start your Web browser and open <server name>:8080 to verify the installation of Apache Tomcat.
5. Copy the ccos.war file extracted from SAPCUSCHKSVR*.zip (downloaded from SAP Software Download
Center) to the webapps subfolder of your Apache Tomcat server (by default, the webapps subfolder is
located in directory C:\Program Files\Apache Software Foundation\Tomcat 8.5 at installation).
6. Before proceeding, restart the Apache Tomcat server. Extracting the SAP Customer Checkout
manager .war file may take some time.
7. Once the .war file has been extracted, you can start SAP Customer Checkout manager by following the
steps described in Initial Configuration of SAP Customer Checkout manager [page 230].
3.2.2.1.1 Using the SAP Java Virtual Machine for Running

Apache Tomcat on Microsoft Windows
Perform the following steps to use SAP JVM 8.1 for Apache Tomcat and SAP Customer Checkout manager on
Microsoft Windows.
Context
You can configure Apache Tomcat to use SAP JVM 8.1.
Procedure
1. Follow the steps as described under Installing the SAP Java Virtual Machine in the SAP Customer Checkout
Installation and Update Guide.

 Note
You do not need to execute the step that describes how to create the CCO_JAVA_HOME environment
variable. The environment variable is not required to run the Apache Tomcat.
2. During installation of Apache Tomcat as JVM, select the jvm.dll file from SAP JVM 8.1.
Example:
C:\Program Files\Java\sapjvm_8\jre\bin\server\jvm.dll
3. After installing Apache Tomcat, open the Apache Tomcat Monitor and choose the Java tab.
4. Delete all values from the Java 9 Options field and save your changes.
Apache Tomcat is now ready to run with SAP JVM 8.1.
3.2.2.2 Installing with Apache Tomcat on Linux
The installation of software on a Linux system can differ greatly depending on the Linux distribution used (for
example, SUSE Linux Enterprise Server, Red Hat Enterprise Linux, and so on) and the used software tools (for
example, YaST, GNU Wget, RPM Package Manager, and so on).
See the following for the most important points for a successful installation of SAP Customer Checkout
manager on Linux.
● A Java runtime environment is required for the operation.
 Note
SAP Customer Checkout manager supports SAP JVM 8.1 and Oracle Java SE 8. In general, however,
the application should also be able to be operated using other Java distributions in version 8 (for
example, OpenJDK 8), but SAP does not assume any legal obligations if any problems arise.
● To run SAP Customer Checkout manager, a Java Application Server is required.
 Note
To install the Java Application Server, Apache Tomcat Version 8.5 or above is recommended, for the
latest information, see the Product Availability Matrix, under http://service.sap.com/sap/support/pam
.
● Due to the advanced user and authorization system on Linux, additional steps may be necessary to
successfully install and execute SAP Customer Checkout manager. For this, the following points should be
fulfilled:
○ The ccos.war file must be located in the Apache Tomcat webapp subfolder
○ The user who runs the Tomcat service should have all the permissions required to run the ccos.war
file
○ By default, SAP Customer Checkout manager creates configuration and log files under the path \SAP.
If the appropriate authorizations are missing when SAP Customer Checkout manager is run, the SAP
folder cannot be created. In such a case, it may be necessary to create the SAP folder manually and
provide the executing user with the appropriate authorizations so that SAP Customer Checkout
manager can create the required files.

The installation of SAP Customer Checkout manager with Apache Tomcat and SAP JVM 8.1 on SUSE Linux
Enterprise Server 15 is described as an example in the following sections.
3.2.2.2.1 Providing SAP JVM 8.1 for Running Apache

Tomcat on SUSE Linux Enterprise Server 15
The path described here is an example of how SAP JVM 8.1 can be provided for Apache Tomcat on SUSE Linux
Enterprise Server 15.
Context
Procedure
1. Follow the steps as described in section Downloading the SAP Java Virtual Machine [page 14] to download
the archive for SAP JVM 8.1 and the archiving program.
2. Transfer both files to the Linux system via SFTP client software.
3. Use the command-line tool and navigate to the folder in which the files are located.
4. Execute the SAPCAR application with the -xvf parameters and the name of the SAP JVM 8.1 archive.
 Note
./<name of SAPCAR application>-xvf./<name of SAP JVM 8.1 archive>
Example:
./SAPCAR_721-20010453 -xvf ./SAPJVM8_55-80000211.SAR
The archive is unpacked. The sapjvm_8 folder contains the required SAP JVM 8.1 files.
5. Move the folder sap_jvm8 to the operating system location on which you want to save the SAP JVM 8.1
permanently, for example /user/lib64/jvm/. To do so, execute the following command: mv
sapjvm_8 /usr/lib64/jvm/

3.2.2.2.2 Installing Apache Tomcat with SAP JVM 8.1 on
SUSE Linux Enterprise Server 15
The path described here describes an example of how to install an Apache Tomcat on SUSE Linux Enterprise
Server 15 and to configure it such that SAP JVM 8.1 is used for execution.
Context
You can install Apache Tomcat using the configuration tool YaST.
 Recommendation
For Apache Tomcat, the initial memory pool must be set to at least 1024 MB and the maximum memory
pool to at least 4096 MB.
Procedure
1. To open YaST, enter the command yast
The YaST Control Center opens.

2. Choose Software and then Software Management.
 Note
To install the Java Application Server, Apache Tomcat Version 8.5 or above is recommended, for the latest
information, see the Product Availability Matrix, under http://service.sap.com/sap/support/pam .
3. Search for tomcat and install Apache Tomcat.

To run Apache Tomcat and SAP Customer Checkout manager with SAP JVM 8.1, the path for the JAVA_HOME
parameter must be adjusted accordingly in the configuration file of the Apache Tomcat.
4. Navigate to the folder containing the configuration file tomcat.conf. For example: cd /usr/share/
tomcat/conf/
5. Open the configuration file tomcat.conf with a text editor (for example, vi): vi tomcat.conf.
6. Replace the path for the JAVA_HOME parameter with the path where the SAP JVM 8.1 is stored in the
system, for example: JAVA_HOME="/usr/lib64/jvm/sapjvm_8".
Apache Tomcat can now be run with SAP JVM 8.1.

3.2.2.2.3 Installation of SAP Customer Checkout manager
on SUSE Linux Enterprise Server 15
This section provides an example of how to install SAP Customer Checkout manager with Apache Tomcat on
Linux Enterprise Server 15.
Prerequisites
Ensure that you have completed the required database steps described in Database Management System
[page 15], before you perform the following steps.
Context
Procedure
1. Transfer the ccos.war file that you have extracted from the SAPCUSCHKSVR*.zip file downloaded from
the SAP Software Download Center, via SFTP client software to the Linux system.
2. Copy the ccos.war file to the webapps subfolder of your Apache Tomcat server (after installation, the
webapps subfolder is located under the path /srv/tomcat/webapps by default).
When installing Apache Tomcat, the tomcat user is automatically created in the Linux system. To enable SAP
Customer Checkout manager to run with Apache Tomcat, the user tomcat must be assigned as the owner for
the ccos.war file.
3. To assign the user tomcat as the owner, execute the following command: chown tomcat:tomcat /srv/
tomcat/webapps/ccos.war.
For SAP Customer Checkout manager to be able to create configuration files and log files on the Linux system,
the SAP folder must be created in the root folder and the user tomcat must be assigned as the owner.
4. To create the SAP folder, execute the following command: mkdir /SAP.
5. To assign the user tomcat as the owner, execute the following command: chown tomcat:tomcat /SAP.
SAP Customer Checkout is now ready for the initial configuration and can be started via Apache Tomcat.
6. To start the Apache Tomcat server, execute the following command: service tomcat start
7. Perform the steps described in the section Initial Configuration of SAP Customer Checkout manager [page
230].

4 Updating SAP Customer Checkout
manager
To benefit from new features and protect SAP Customer Checkout manager from vulnerabilities, keep the web
application up to date.
 Note
SAP Customer Checkout and SAP Customer Checkout manager must always have the same release
version and the same feature pack. To update to a new release or feature pack, first update SAP Customer
Checkout manager, then SAP Customer Checkout.
 Note
During an upgrade of SAP Customer Checkout manager to version 2.0 Feature Pack 07 or higher, the data
layout is switched from "row store" to "column store", if SAP Customer Checkout manager is installed on a
SAP HANA database.
To update SAP Customer Checkout manager, make the new version available to the web application.
1. Download the latest SAP Customer Checkout manager version from the SAP Software Download Center.
2. Rename the SAP Customer Checkout manager .war file that you downloaded to the same name as in
your local installation folder (for example, ccos).
3. Place this file into the webapps subfolder of your local installation.
 Note
When you are using Apache Tomcat, the subfolder is located by default in C:\Program Files
\Apache Software Foundation\Tomcat 8.5.
For more information, see Java Application Server [page 17].
4. The update process may take a few minutes. You can then access SAP Customer Checkout manager again.
 Note
If the update process does not start, restart Apache Tomcat.
5. Start the SAP Customer Checkout manager in your web browser, and log in.
 Note
Should you encounter errors when accessing applications following the update, empty the browser
cache. In Google Chrome, press the Ctrl + Shift + R keys to empty the browser cache.
 Caution
After updating from SAP Customer Checkout version 2.0 to version 2.0 Feature Pack 01, you have to
reassign roles and permissions for users created manually in the previous version.

Updating SAP Customer Checkout manager CUSTOMER 23
6. To check whether SAP Customer Checkout manager was updated successfully, select the Configuration
application, then the Configuration subapplication, then choose the About tab, and verify the SAP
Customer Checkout manager version.

24 CUSTOMER Updating SAP Customer Checkout manager
5 Working with SAP Customer Checkout
Manager
5.1 Getting Started
When you start SAP Customer Checkout manager, you will see the following sections:
● SAP Customer Checkout manager: Maintain SAP Customer Checkout manager-related settings
● Point of Sales Management: View and centrally maintain settings for SAP Customer Checkout applications
● Loyalty Management: Maintain settings related to the Loyalty API integrated in your application
Each section has tiles for specific tasks:
SAP Customer Checkout manager
Tile Description
Configuration Adjust various configuration settings, such as security or in

tegration settings..
Jobs Display all job runs and create new jobs
Tenants Create and manage tenants when using SAP Customer

Checkout manager in multi-tenant mode.
 Note
This tile is displayed only if you are logged in to the mas
ter tenant.
For more information, see Using SAP Customer Check

out manager in Multi-Tenant Mode [page 229]
Roles Create and manage roles in SAP Customer Checkout man

ager and in SAP Customer Checkout applications.
Users Create and manage user accounts in SAP Customer Check

out manager and in SAP Customer Checkout applications.

Working with SAP Customer Checkout Manager CUSTOMER 25
Point of Sales Management
Tile Description
Organizational structure Provides a view of all POS groups, POS systems, and their
dependencies.
Time recording Centrally check time recordings made from all users in vari
ous SAP Customer Checkout applications.
Time recording exports Export time recording files that can be imported into any
third-party time tracking system.
Monitoring See all status messages and status information sent from
various SAP Customer Checkout applications to SAP Cus
tomer Checkout manager.
Monitoring reports Generation of monitoring reports for status messages and

status information sent to SAP Customer Checkout man
ager within a specific timeframe.
Vouchers Manage vouchers used in SAP Customer Checkout.
Receipts Centrally check and track receipts created in SAP Customer

Checkout.
Receipt exports Exporting receipts that are stored in SAP Customer Check
out manager.
Software Manage software versions and installations of various SAP

Customer Checkout applications.
Sales Reports Generate sales reports for various transactions in SAP Cus
tomer Checkout within a specific time period.
Tables View and edit all tables handled using table management
mode in SAP Customer Checkout applications.
Sales summaries Central review and tracking of day-end closings created in

SAP Customer Checkout applications.
Drawers Central management of drawers that are used in central

drawer management in SAP Customer Checkout applica
tions.
Articles Centrally manage articles when using the SAP Customer

Checkout manager as your back-end system.
Customers Centrally manage customers when using SAP Customer

Price Lists Centrally manage price lists when using the SAP Customer

26 CUSTOMER Working with SAP Customer Checkout Manager
Tile Description
POS configuration Edit the settings for tax rates, article groups, currencies,
code lists, quick selections, payment card types, character
istics profiles, characteristics, and warehouses.
Stock transactions Centrally manage stock transactions when using SAP Cus
tomer Checkout manager as your back-end system.
Business object locks Central management of business object locks.
Migrations Import articles, prices, and users via a CSV file from an ex
ternal source into the SAP Customer Checkout manager
system.
Loyalty Management
Tile Description
Coupons Create and edit coupons.
Point Assignments Manage bonus points assigned to loyalty users in SAP Cus
Loyalty users Modify the settings for all loyalty users in SAP Customer
Checkout manager.
Promotion Codes Create and edit promotion codes that can be redeemed by
loyalty users to collect loyalty points.
Loyalty Reports Generates reports for loyalty users, coupons, and loyalty
points.
Loyalty Configuration Create and define various settings for loyalty points and loy
alty users.
5.2 Logging In to SAP Customer Checkout manager
Context
To access the features of SAP Customer Checkout manager, you have log in to the system using your user
name on the start page.

 Note
Accessing SAP Customer Checkout manager requires the "Access SAP Customer Checkout manager"
authorization.
Procedure
1. Open the start page for SAP Customer Checkout manager.

2. Log in.
5.2.1 Creating New User Passwords in SAP Customer

Checkout manager
Context
If you log in to SAP Customer Checkout manager with a user whose password has expired (according to the
selected password policy), you have to set a new password.
 Note
If you make five unsuccessful attempts of setting a new password, SAP Customer Checkout manager
prevents any new attempts for a period of 15 minutes. This period increases with each further attempt, up
to a maximum of 60 minutes until the next possible attempt.
Procedure
1. Log in to SAP Customer Checkout manager.

2. If your password has expired, you are prompted to set a new password.
3. Enter and confirm the new password.
Results
Your new password is now valid. You are forwarded to the start page for SAP Customer Checkout manager.

5.3 SAP Customer Checkout manager
5.3.1 Users
You can manage users for SAP Customer Checkout manager and SAP Customer Checkout on the Users tile.
You can create, edit, lock, delete, or copy users. You can assign roles, authorizations, applications, and
organizational units to users.
 Note
SAP Customer Checkout manager is delivered with the Admin user by default. In the initial configuration
settings, you have to set the password for this user.
Each user account contains tabs with additional information: Details, Authorizations, Applications, and
Organizational Units.
The Details tab provides the following information:
User Details
Option Description
User name Name of the user used to log in to SAP Customer Checkout
manager.
 Note
The username is case sensitive.
Name The user's first and last name.
Role Role that is assigned to this user
For more information about each of the roles, see Roles

[page 39].
 Note
Depending on the role you select to be used for this
user, the authorizations will be adapted by the respec
tive role.
Language Language used on the user interface for this user.
Locale Locale used by this user.

Option Description
Color Color used in the SALES screen when this user is logged on
to SAP Customer Checkout
Barcode Secret Alternative login ID.
For example, this can be used for logging in with a magnetic

card.
This is also the key you have to print out as a bar code or
store on a magnetic card to log in.
 Caution
When logging in to SAP Customer Checkout with the
barcode secret, you must enter % at the beginning
and ? at the end.
Example: If you entered 12345 for logging in the user,

you must enter the following in SAP Customer Check
out: %12345?.
If you want to print this key as a barcode or save it to a

magnetic card for logging in, you must also enter:
%12345?
 Note
On the Users tile, you can use the search and filter func
tion to find a user using a barcode secret.
Locked Defines whether the user can log in. The following statuses
are available:
● True: the user cannot log in (for example, a user who

has left the company is locked and can no longer log in),
● False: The user can log in.
Password Locked Password status for the user. The following statuses are
available:
● True: the user cannot log in (for example, a user enters

the wrong password multiple times).
● False: The user can log in.
This status is set to true, if the user exceeded the maximum

login fail attempts, which are specified in the password pol
icy.
Force password change Forces the user to change his or her password when next
logging in to SAP Customer Checkout Manager.

Option Description
Technical user Activate this option in large system landscapes for users you
want to use for communication between SAP Customer
Checkout and SAP Customer Checkout manager.
If the option is enabled, Last login at information is not dis

played in SAP Customer Checkout manager and is not saved
in the database.
 Note
For performance-related reasons, we also recommend
using several users with the Technical user role in large
system landscapes. For example, maintain a separate
communication user for every 10 SAP Customer Check
out applications.
Migrated Indicates whether the user was imported to SAP Customer

Checkout manager via user migration.
Sales Data
Option Description
Color Color used in the SALES screen when this user is logged on
UI Mode Specifies which UI mode is displayed for the user in SAP

Customer Checkout. If a UI mode is not selected for the
user, the UI mode set in the POS system is displayed.
Quick Service
Displays the quick service for the user in SAP Customer

Checkout
Table Management
Displays the table management mode for the user in SAP

Customer Checkout

Option Description
Price List Price list that is assigned to the user. When the user log in to
SAP Customer Checkout, the price list entered here is used
as the default price list.
 Note
Only one price list can be assigned to a user.
If multiple price lists could apply at the same time (for

example, the user and the role assigned to the user have
different price lists), the following order applies:
1. Price lists that are assigned to users take prece

dence over price lists that are assigned to roles or
organizational units.
2. Price lists that are assigned to roles take prece
dence over price lists that are assigned to organiza
tional units.
Employee ID SAP Business One only: Employee ID number in the SAP

Business One system.
Alternative user ID for EFT terminals If SAP Customer Checkout is integrated with an EFT termi
nal, the user name is sent to the terminal during the login
process. Since some EFT terminals can only process nu
meric user names, it is possible to maintain an alternative ID
for the user, which is sent to the EFT terminal in place of the
user name.
Is Salesperson Define this user as a Salesperson (see the SALES screen in

SAP Customer Checkout).
Salesperson ID SAP Business One only: Sales Employee Code from the SAP
Business One system.
Administrative Data
Field Description
Status Shows whether the user is active or not.
Last Login at Date and time when the user last logged in to SAP Customer
Checkout manager.
Last Password Change at Date and time when the user last changed the password.
Password Valid to Date and time the password of this user will expire.

Field Description
Created By Username of the user who created the user in SAP Cus
Created At Date and time when the user was created.
Changed By Username of the user who modified the user in SAP Cus
Changed At Date and time when the user was modified.
Automatic lock
Option Description
Lock time in seconds Locks the screen in SAP Customer Checkout if the user is in
active for the length of time specified.
Logout time in seconds Logs the SAP Customer Checkout user out if he or she is in
active for the length of time specified.
Action after posting Executes the selected action after a sales receipt is posted.
Available actions:
● Without
Does not perform any action
● Lock
Locks the screen in SAP Customer Checkout
● Logout
Logs the user out from SAP Customer Checkout
 Note
Lock time, logout time, and action after posting can also
be specified at POS system and role level. For informa
tion about the validity of these settings, see the SAP
Customer Checkout User Guide.

Personal Info
Option Description
Consent given and maintained Indicates whether the user has given consent for their per
sonal data to be processed.
 Note
This indicator is automatically deactivated if a new value
for the Consent Document Version option is selected.
Assuming that the relevant person has given their con
sent for the new version for the consent document, you
can then reactivate the indicator for consent.
Consent document version Displays the version of the consent document on the proc
essing of personal data for this user. The selection is op
tional.
The Authorizations tab displays all authorizations assigned to this user.
 Note
If a role has been assigned to a user, this role passes all its authorizations on to the user. However, you can
still change individual authorizations manually.
If no role has been assigned to a user, all of the authorization of this user are deactivated, but you can
activate them manually. In addition, for some authorizations you can also define parameters so that you
can modify the permission even further. For example, you can enable a user to give discounts and specify
how much discount to be allowed.
For more information, see Authorizations [page 43].
On the Org. unit assignments tab, you can define SAP Customer Checkout applications and POS groups to be
used by certain users only. This means that users can only log in to and use SAP Customer Checkout
applications to which they are assigned. One user can be assigned to one or more organizational units.
To assign an SAP Customer Checkout application or POS group to a user, perform the following steps:
1. Select the user to assign to the organizational unit, and select the Org. unit assignments tab.
2. Choose Assign.
3. In the Assign dialog, select the respective POS system or POS group, and choose Save.
 Note
When assigning a POS group to a user, you can select the Remove assigned suborganizational units option
to remove all POS systems and POS groups that are below the POS group selected for assignment. The
user will still be able to use the respective organizational unit as the higher POS group is assigned to this
POS system. Disable this option to directly assigned the user to the related organizational units (or the
respective POS group).
 Example
You have the following organizational structure:

● root
○ Merchandise Shop
○ POS1
○ POS2
Assuming that you have a user, User1, and the following POS systems are already assigned to this user:
root, POS1, POS2. When you now assign the Merchandising Shop to this user (User1) and enable the
option Remove assigned suborganizational units, the POS systems POS1 and POS2 that are assigned to
the Merchandising Shop will be removed from the list, and only Merchandising Shop, and root will be
displayed. All direct organizational unit assignments and settings (for example, locked users) are
removed and the higher POS group (Merchandising Shop) is applied.
 Note
To synchronize users managed in SAP Customer Checkout manager with your SAP Customer Checkout
applications, you need to activate Enable central user management in the configuration of your SAP
Customer Checkout application. When this option is enabled, all users (roles and permissions) for your
SAP Customer Checkout applications are managed centrally in SAP Customer Checkout manager.
 Note
If you use the central user management feature in SAP Customer Checkout manager, local user and
role management in the SAP Customer Checkout configuration is deactivated. The "User" tab cannot
be edited, and is read-only.
 Caution
You cannot run Central Drawer Management in SAP Customer Checkout, in parallel with central user
management in SAP Customer Checkout manager.
However, when the Central Drawer Management is activated and SAP Business One is used as an SAP
ERP system, the user and role management concept from the Central Drawer Management is valid.
On the Applications tab, you can control for each application available in SAP Customer Checkout whether the
user is authorized to view and run this application.
 Note
If the user is assigned a role, all application authorizations in this role are passed on to the user. However, it
is possible to revoke the user's authorization for specific applications.
Users not assigned a role are not authorized to view and run any applications: However, it is possible to
manually grant authorizations for individual applications to a user.
For more information, see Applications [page 46].
You can enter the credentials for the user who will communicate with the SAP Event Ticketing target system on
the External credentials tab.

 Note
This tab is relevant only if you wish to integrate SAP Customer Checkout with SAP Event Ticketing, with the
aim of selling tickets in SAP Customer Checkout. For more information, see SAP Event Ticketing
Integration [page 9].
Perform the following steps to add SAP Event Ticketing credentials for a user:
● Choose Add.
● Choose SAP Event Ticketing.
● Enter a user who can communicate with the SAP Event Ticketing system, and a secret.
 Note
You obtain the user secret from your SAP Event Ticketing system. Please look up the API key. For
more information, see the SAP Event Ticketing documentation.
5.3.1.1 Creating a User
Context
You can create new users in SAP Customer Checkout manager.
Procedure
1. Click the Add icon on the lower-left of the screen.

2. Enter the user information.
 Note
Make sure that the entered password fulfills the requirements of the Password Policy described in
Initial Password and Password Policy [page 236].
3. Choose Save.

5.3.1.2 Editing a User
Context
In SAP Customer Checkout manager, you can edit existing users. For example, you may want to change the
password or the language used in the user interface for this specific user.
Procedure
1. Select the user you want to edit, and choose Edit.

2. Edit the user data as needed.
3. To save your changes, click Save.
5.3.1.3 Generating a Barcode
You can generate an encoded string that contains the username and password of a specific user. The string can
be converted into a barcode and then scanned to log into SAP Customer Checkout.
Context
 Note
The barcode can only be used to log into SAP Customer Checkout and not for logging into SAP Customer
Checkout manager.
 Caution
Using this feature can impact application security. Unauthorized persons could gain access to the
application by using the barcode login. It is also possible to decode the username and password from the
string or barcode and use it to gain unauthorized access to the application. If you are using this feature,
disable the autocomplete function of your web browser to prevent it from saving the string as a suggestion.
 Note
On the Users tile, you can use the filter function to find a user using a generated barcode.

Procedure
1. Select the user for whom you want to generate a barcode string.
2. Click Barcode.
3. Enter the user's password, and choose Generate.
The barcode string is displayed in the respective field.
5.3.1.4 Copying a User
You can copy an existing user together with all of that user's rules, permissions, and assigned organizational
units.
Procedure
1. Select the user that you want to copy.

2. Click Copy.
3. Enter the user data (for the new user)..
 Note
You can also select whether you want to copy the rules and permissions and the organizational unit
assignments of the user. If you confirm one or both of these options, all rules, permissions, and
organizational unit assignments of the selected user will be copied to the new user.
4. Choose Save.
5.3.1.5 Changing User Passwords Without Access

Authorization to SAP Customer Checkout manager
Context
In SAP Customer Checkout manager, passwords can be changed even if a user is not authorized to access SAP

Procedure
1. Log in to SAP Customer Checkout manager with your user data.
 Note
The following message appears: "You have no permissions to start an application. Please contact your
administrator."
2. Choose your user name in the upper right corner of the screen and then select Settings.
3. Change your password.
5.3.2 Roles
In the Roles tile, you can manage all of the roles and permissions for users in SAP Customer Checkout
applications. You can also create roles, assign roles to parent roles, assign different permissions to roles, and
edit and delete roles. For roles, you can also specify a lock time, logout time, an action after posting, and a price
list.
 Note
For more information about lock time, logout time, and action after posting, see Users [page 29].
 Note
A price list can be assigned to each role. If a user to whom this role is assigned logs into in SAP Customer
Checkout, the price list assigned to the role is used as the default price list. However, if a price list is already
assigned for the user, the price list of the user is used instead.
 Note
To synchronize roles managed in the SAP Customer Checkout manager with your SAP Customer Checkout
applications, activate the Enable central user management option in the configuration of your SAP
Customer Checkout application. When this option is enabled, all roles and permissions for your SAP
Customer Checkout applications are managed centrally in SAP Customer Checkout manager.
 Note
If you are using central user management in the SAP Customer Checkout manager, you cannot configure
local user and role management in SAP Customer Checkout. The Roles tab is read-only.
 Caution
Central drawer management in SAP Customer Checkout requires central user management via SAP
The Roles tile provides an overview of all roles, general data about a specific role, and information about the
permissions assigned to a role.

On the Role tile, you can do the following:
● Create a role
● Edit a role
● Delete a role
● Refresh all roles
In SAP Customer Checkout manager, you will find the default roles available for use in SAP Customer
Checkout.
Default Roles
SAP Customer Checkout manager delivers the following predefined roles that are transferred to SAP Customer
Checkout:
Default Roles in SAP Customer Checkout Manager

User Role Screens Available
CASHIER SALES, SEARCH
SALESMANAGER SALES, CASH-IN/CASH-OUT, DAY-END CLOSING, CASH

ING-UP, SEARCH
ADMINISTRATOR SALES, CASH-IN/CASH-OUT, Day-End Closing, CASHING-

UP, SEARCH, CONFIGURATION
DATASECURITYOFFICER DATA SECURITY
Roles and Permissions Concept
Each role can access different screens and perform different actions in SAP Customer Checkout and in the
SAP Customer Checkout manager, depending on the assigned permissions.
When you create a new role, you can select a parent role. The parent role passes its permissions on to any new
roles you create. However, you can still decide which permissions are available for each role.
In addition, for some permissions it is possible to define parameters to modify the permissions even further.
For example, when you allow members of a role to give discounts, you can define the maximum discount a user
is allowed to give.
The Permissions table has the following options:
Settings in Permissions Table

Column Description
Protected Resource Name of the protected resource for which permissions can
be granted. For information about system-defined permis
sions, see Authorizations [page 43].

Column Description
Parent role Shows whether the respective permission was granted in the
parent role.
Allowed Sets the permission for the role. If no permission is set (-),
the permission of the parent role is inherited. With Yes and
No, the permission is directly set for the selected role and
overrides the setting in the parent role.
Valid Shows the result derived from the two columns Parent role
and Allowed. Here you can check whether the permission
has been granted. You cannot edit this column.
 Example
A new role has been added to a parent role. The parent
role can cancel sales items on the sales screen. To en
sure that the new role does not inherit this permission,
you can set the Allowed option to No. Result: the permis
sion cancel sales items for the new role is deactivated,
and the entry for Effective is automatically set to NO.
Parameterizable Shows whether a permission can have additional parame

ters. If you select a permission that can have additional pa
rameters, the Permission parameters table is displayed un
der the Permissions table.
System defined Indicates whether the permission was defined by the system
or created manually.
5.3.2.1 Creating Roles
You can create new roles in addition to the default roles if you need to assign customized permissions to your
users.
Procedure
1. Choose the Roles tile and then the "Add" pushbutton.

2. You can assign a name, description, and parent role to this new role. You can also a specify a lock time,
logout time, an action after posting, and a price list.
 Note
For more information about lock time, logout time, and action after posting, see Users [page 29].
3. Edit the General data of this role.

 Recommendation
We recommend that you select a parent role for each role you create. This ensures that the new role
receives all required permissions if the software is updated.
 Caution
You can no longer change the name of a role after you have saved the role.
4. On the Permissions tab, adapt the permissions according to your needs.

5. If you want to add parameters to the permission, do the following:
a. Select the permission.
b. Under Permission parameters, choose New.
c. Select the Template ID, a comparison operator, and a value.
d. Choose OK
6. On the Application tab, adapt the access rights to applications in SAP Customer Checkout manager in line
with your requirements.
5.3.2.2 Editing Roles
You can edit existing roles in SAP Customer Checkout manager to maintain or adjust settings.
Context
 Caution
After the role has been created, the name of the role cannot be changed in SAP Customer Checkout
manager.
Procedure
1. Open the Roles tile in SAP Customer Checkout manager.

2. Select the role you want to edit and click Edit.
3. Edit the General data, the Permissions, or the allowed Applications for the role.

5.3.2.3 Authorizations
The following protected resources are defined in the system.
System-Defined Protected Resources

Protected Resource Description
Allow cash payment above limit Allows the user to accept cash payment above the cash
amount that has been set.
Access SAP Customer Checkout manager Lets the user access SAP Customer Checkout manager - in
cluding all available tiles.
Do time recording punch out without authorization Allows the user to perform a time recording punch-out in
SAP Customer Checkout, without any further approval by a
user who has Approve time recording requests authorization.
Allow adding of payment items Allows the user to add payment options (card payment,
cash, payment on credit, payment by voucher) in SAP Cus
tomer Checkout.
 Note
Users lacking this authorization cannot add payment
items in SAP Customer Checkout for posting the re
ceipt.
Create sales receipt Allows the user to create a sales receipt in SAP Customer
Checkout (and sell articles in the SALES Screen).
Show search screen Allows the user access to the Search screen – including
searching of customers, articles, receipts, vouchers, and so
on.
Show sales screen Allows access to the SALES screen.
Cancel sales items Lets the user cancel sales items on the SALES screen.
Show current cash balance Shows the current cash balance on Cash-in/Cash-out and
on Day-End Closing screen.
Force screen unlock Allows unlocking the screen for other users.
Allow returns Allows the user to return articles and whole receipts on the
SALES screen.
Cancel sale Allows the user to the current sales process on the sales
screen to be reversed. Allows the user to reverse parked and
resumed receipts on the SALES screen.
Can open drawer (no-sale receipt) Allows the user to open a drawer without creating a receipt.
Show cashing-up screen Allows the user to open and edit the Cashing-Up screen.

Top up voucher Allows the user to top up vouchers in SAP Customer Check
out.
Accept expired vouchers Allows the user to accept expired vouchers in SAP Customer
Checkout.
Show day-end closing screen Allows the user to open and edit the Day-End Closing screen.
Using time recording Allows the user to enter time on the "Time Recording"
screen in SAP Customer Checkout. However, the time re
cording request must be approved by a user with the
Approve time recording requests authorization.
Change the unit price Allows the user to change the unit price of sales items on the
Sales screen.
Modify receipts Allows the user to modify or repost receipts outside the
Sales screen
Do time recording punch in without authorization Allows the user to perform a time recording punch-in SAP
Customer Checkout, without any further approval by a user
with Approve time recording requests authorization.
Recovery admin tasks Allows editing of recovery admin tasks that are generally
part of the RAdmin role. RAdmin tasks are particularly rele
vant when you have enabled central drawer management.
 Caution
Users with this authorization have access to the SAP
Customer Checkout configuration screen only, irrespec
tive of whether other authorizations are active.
Show cash-in/ -out screen Allows the user to open the cash-in/cash-out screen.
Can take over "In transit" (ITR) drawers Allows the user to take over drawers that are In transit (ITR).
This authorization is relevant for central drawer manage
ment.
Show settings screen Allows the user to open the Settings screen and edit the set
tings.
Give discount Allows the user to apply a discount on a sales items or the
whole receipt on the Sales screen.
Approve time recording requests Allows the user to approve time recording requests (espe
cially for users with Using time recording authorization).
Create or update customers Allows the user to create and update customers on the
Search screen.
Return a receipt by ID Allows the user to return a receipt by ID in the Quick Service
mode.

Allow selection of sales item Allows the user to select any sales item in Quick Service and
Table Management mode. If this authorization is deacti
vated, the user cannot select sales items and the last sales
item is selected by default.
 Note
This authorization can be combined with the "Cancel
sales items" authorization, to deny or allow users to can
cel any sales item.
Take over table from other user Allows the user to take over tables (including all assigned re
ceipts/sub-tables) from other users.
Move a receipt to another table Allows the user to assign a receipt to a different table.
Change the owner of a bill/table User can transfer an own bill to another user.
Enable creation of sub-tables from another user Allows the user to create receipts/sub-tables at the tables of
other users.
Allow moving a POS system to another POS group Allows the user to move POS systems to other POS groups
directly from SAP Customer Checkout
Manage personal data protection Allows the user to manage personal data and functions and
to block, unblock, and delete business objects
Allow receipt exports from POS system Allows the user to export sales documents for specific time
periods directly from SAP Customer Checkout.
You can also create new authorizations and assign them to a role.
 Note
You need a separate plug-in to use authorizations that have been created manually in SAP Customer
Checkout manager. SAP Customer Checkout only provides the means to connect a plug-in to the
application. Communication between the plug-in, SAP Customer Checkout, and SAP Customer Checkout
manager requires additional development, based on custom requirements.
To create a new authorization and assign them to a role, do the following:
1. Select the role to which you want to add a new authorization, and select Edit.
2. In the Authorizations section, select New.
3. Enter a name for the Protected resource ID and choose whether to grant the authorization.

5.3.2.3.1 Permission Parameters
You can assign additional parameters to a permission, and edit or delete existing parameters that are assigned
to a permission.
 Note
The Permission Parameters option is only displayed for resources that can use parameters and can only be
edited if a permission is created for the parameterizable protected resource directly for the role and the
allowed flag is set to Yes.
This option is only available for the Give Discountpermission, or for a custom permission that you have
created with a separate plug-in.
To edit an existing permission parameter or assign additional parameters to a permission, do the following:
1. Select the role for which you want to edit an existing permission parameter or assign additional
parameters, and select Edit.
2. Select the parameterizable protected resource and in the area below Permission Parameters, select New.
3. Enter a Template ID and a Value, and select Comparison operator.
4. To save your changes, select OK.
5.3.2.4 Applications
On the Applications tab, you can assign or revoke authorizations for applications in SAP Customer Checkout
manager for specific roles.
Users can see and use those applications for which authorization has been granted in the assigned role or for
which authorization has been assigned to the user explicitly.
The following applications can be released for use in SAP Customer Checkout manager.
Data Privacy Management
Change logs In the Change logs application, you can view the logged
changes to business objects.
Configuration In the Configuration application, you can specify which busi

ness objects are logged.
Personal data disclosure In the Personal data disclosure application, you can display
the personal data of an individual. The personal data can be
downloaded as a file.
Blocking and deletion of personal data In the Blocking and deletion of personal data application, you
can be block, unblock, or delete business partners, users,
and loyalty users.

Loyalty Management
Promo codes In the Promotion codes application, you can manage promo
tion codes that are used by loyalty users.
Loyalty users In the Loyalty users application, you can manage loyalty
users.
Loyalty reports In the Loyalty reports application, you can run reports for
transactions related to the loyalty API for a specific time pe
riod.
Loyalty configuration In the Loyalty configuration application, you can manage

configurations for loyalty programs.
Coupons In the Coupons application, you can centrally manage cou

pons purchased by loyalty users or coupons handled as dis
counts.
Point assignments In the Point assignments application, you can assign loyalty
points to loyalty users.
Point of Sales Management
Articles If SAP Customer Checkout manager is used as an SAP back-

end system for SAP Customer Checkout, you can manage
articles in the Articles application.
Article groups In the Article groups application, you can manage article
groups for articles.
Receipts In the Receipts application, you can view all receipts that
have been transferred to SAP Customer Checkout.
Receipt exports In the Receipt exports application, you can export sales re
ceipts for specific periods and organizational structures.
Business object locks In the Business object locks application, you can view locked
business objects. Currently, this only applies to parked re
ceipts currently being used in SAP Customer Checkout.
Code Lists In the Code lists application, you can manage code values.
Vouchers In the Vouchers application, you can manage vouchers.
Drawers In the Drawers application, you can manage cash drawers.

Payment card categories In the application payment card categories, data for payment
card categories (for example, credit cards) can be main
tained. This data is managed for displaying credit card data
in SAP Customer Checkout manager.
Customers If SAP Customer Checkout manager is used as an SAP back-

end system for SAP Customer Checkout, you can centrally
manage customers in the Customers application.
Migrations In the Migrations application, you can import articles with

prices, users, and customers to SAP Customer Checkout
manager.
Monitoring In the Monitoring application, you can view all events that
have been sent to SAP Customer Checkout manager.
Monitoring reports In the Monitoring reports application, you can run reports on
events that have been sent to SAP Customer Checkout man
ager.
Organizational structure On the Organizational structure tile, you can manage the or
ganizational structure of your POS systems.
Price lists If SAP Customer Checkout manager is used as an SAP back-

end system for SAP Customer Checkout, you can centrally
manage price lists in the Price lists application.
Quick selection In the Quick selection application, you can centrally create
and manage quick selections for SAP Customer Checkout.
Drawer contents In the Drawer contents application, you can view all drawer
contents sent to SAP Customer Checkout manager.
Software In the Software application, you can centrally manage and

update versions of SAP Customer Checkout applications.
Tax Rates If articles are managed centrally in SAP Customer Checkout

manager, you can manage the tax rates for these articles in
the Tax rates application.
Sales reports In the Sales reports application, you can – among other
things – run reports on sales, cash balances, and returns.
Sales summaries In the Sales summaries application, you can view all sales
summaries sent to SAP Customer Checkout manager.
Currencies If price lists are managed centrally in SAP Customer Check

out manager, you can use the Currencies application to man
age the currencies that are used in price lists.

Time recordings In the Time recordings application, you can view, among
other things, all working times that were sent to SAP Cus
Time recording exports In the Time recording exports application, you can create and
download statements on working times.
Users In the Users application, you can manage users centrally.
Destinations In the Destinations application, you can manage target sys

tems for transferring data from SAP Customer Checkout
manager.
Dispatcher In the Dispatcher application, you can specify which data is

transferred from SAP Customer Checkout manager to which
target system.
Configuration In the Configuration application, you can – among other

things – manage password policies and proxy settings, as
well as version information about SAP Customer Checkout
manager.
Roles In the Roles application, you can manage roles for users cen
trally.
Sequence numbers In the Sequence numbers application, you can manage se
quence numbers.
Sequence number users In the Sequence number users application, you can assign
sequence numbers to business objects.
5.3.3 Jobs
On the Jobs tile you can centrally manage and monitor various background jobs.
The following background jobs are currently available:
● Sales Summary: Check Consistency: Checks sales summaries that are in "Deviation" status
● Loyalty: Assign Points: Assigns points to all loyalty users
● Monitoring: Delete Entries: Specifies that old monitoring entries are deleted
● Receipt: Repost: Reposts receipts that have not been passed to a destination
● Data Protection: Blocking and deletion of personal data: Enables you to block, unblock, and delete business
partners, users, and loyalty users

● Download: Article label for printing: Download article labels using bar code or QR code data for printing.
The downloaded file is in ZPL format.
 Note
You can filter for which articles and price lists you want to print labels.
The Schedules and Executions tabs contain further information.
● Schedules: Here the system displays all scheduled background jobs. In addition, you can also display
background jobs that have been descheduled.
Field Description
Status Shows the status of the scheduled background job
Job All available background jobs
Type Type of execution (e.g. daily, weekly, monthly)
Next execution Displays the date and time of the next execution
Created at Displays date and time when the background job was
scheduled
Created by User name of the user who created the execution
● Executions: Here you see all jobs that are inactive, active, terminated, and have already been run.
Field Description
Status Displays the background job status
Job All available background jobs
Started at Displays the date and time when the run was started
Finished at Displays the date and time when the run was completed
Results Indicates whether the execution was successful
5.3.3.1 Creating an Execution
You can create a new job that is to be executed.
Context

Procedure
1. In the Jobs tile, choose the Add icon.

2. Select the job that you want to execute and enter the data.
3. Save your changes to execute the job.
5.3.4 Tenants
If your are operating SAP Customer Checkout manager in multi-tenant mode, you can create and manage all
your tenants in the master tenant. Here you can shut down, deactivate, delete, and edit tenants.
Each tenant in SAP Customer Checkout manager has its own database with its own logic.
 Note
This tile is only displayed if you are in the master tenant. If you are logged in to one of the other tenants, the
tile is not displayed.
 Note
For more information on multi-tenant mode, see Using SAP Customer Checkout manager in Multi-Tenant
Mode [page 229]
5.3.4.1 Creating Tenants
Context
You can create new tenants in SAP Customer Checkout manager if you are logged in to the master tenant.
Procedure
1. Click the Add icon on the lower left side of the screen.
2. Enter the tenant data.
 Note
The database driver is the default setting. This is always the same as the master tenant driver.

 Note
In the Connection URL field, you can enter the database name for your tenant.
 Note
Activate the field Automatically create schema (if non-existent) if the database schema with the entered
name is to be created automatically.
 Caution
This function is intended to simplify the setup of the database connection for test purposes. A
database user with system authorizations is required to create the schema. A user of this type has
other authorizations that go beyond the authorization for pure database access and are not
required.
For security reasons, it is recommended that for the connection to an SAP HANA database you
create your own user in the database management system, which only has the required
authorizations for the database connection.
For more information about creating a new user in an SAP HANA database, see Using SAP HANA
Database [page 15].
3. Choose Save.
 Note
Once you have saved your entries, the newly created tenant is in DRAFT status. It may take several
seconds before the tenant status switches to ACTIVE.
5.3.4.2 Editing Tenants
SAP Customer Checkout manager enables you to shut down, deactivate, delete, and edit your tenants.
Context
Procedure
1. Select the tenant you want to edit and choose one of the following options:
a. Shutdown: Tenant is shut down and disabled. The tenant's connection with the database is
deactivated. Scheduled background jobs for the tenant are no longer executed, as the tenant is
disabled completely.

b. Deactivate: Tenant is deactivated and is no longer accessible. Requests from SAP Customer Checkout
to SAP Customer Checkout manager (for example, user or article synchronizations) are not performed
if the respective tenant is deactivated. However, planned background jobs continue to be executed.
When you start up the master tenant, deactivated tenants are not automatically started up.
c. Delete: Tenant entry is deleted from the respective master tenant. The tenant's database is retained.
d. Edit: Here you can edit tenant data, including the tenant name or user name, and the tenant database
password.
5.3.5 Configuration
The Configuration tile contains the Configuration, Destinations, Distribution List, Sequence Numbers, and
Sequence Number Users subtiles.
Tiles
Tile Description
Configuration On the Configuration tile you can define a password policy,

integrate SAP Customer Checkout manager into a third-
party system (to authorize your loyalty users within the Loy
alty API), make proxy settings, or retrieve version informa
tion.
Destinations On the Destinations tile, you can maintain connection data

for other SAP Customer Checkout managers and third-party
systems.
Distribution List On the Distribution List tile, you can define for which SAP
Customer Checkout managers and third-party systems data
is transferred.
Sequence Numbers On the Sequence Numbers tile, you can create and edit se
quence numbers for business objects.
Sequence Number Users On the Sequence Number Users tile, you can assign se
quence numbers to business objects.
5.3.5.1 Configuration
Use the Configuration tile to adjust the settings in SAP Customer Checkout manager.
On the Configuration tile, you can:
● Set or change passwords

● Integrate the SAP Customer Checkout manager application with a third party system to authorize your
loyalty users within the Loyalty API

● Configure various settings for events in your business
The following sections are available on the Configuration tile:
"Configuration" Tile
Section What You Can Do
General Maintain general settings for SAP Customer Checkout man

ager
Security Configure security settings such as password policies for

loyalty users, or specify an identity provider for authorization
of your loyalty users
Proxy Maintain proxy settings
Information View the version number and Java information of SAP Cus
tomer Checkout manager
5.3.5.1.1 General
5.3.5.1.1.1 Basic Configuration Data
Use this section to manage initial configuration settings, such as the name and description of your SAP
Customer Checkout manager application.
Basic Configuration Data
Option Description
Name Name of your SAP Customer Checkout manager application
Description Description of your SAP Customer Checkout manager appli

cation
Active Enable or disable the activation of configuration data. This

field is set to Active by default.
5.3.5.1.1.2 Database Data
This section contains information on the database connected to SAP Customer Checkout manager.

5.3.5.1.1.3 Administrative Data
This section displays administrative data for the SAP Customer Checkout manager
Administrative Data
Option Description
Created by The username of the user who installed the SAP Customer
Checkout manager
Created at Date and time when the SAP Customer Checkout manager
was created
Modified by Username of the user who last modified the SAP Customer
Checkout manager
Modified at Date and time when the SAP Customer Checkout manager
was last modified
5.3.5.1.1.4 Monitoring
Save configurations
Field Description
Save all monitoring pings Enable or disable the option to save all pings from various
SAP Customer Checkout applications in the SAP Customer
Checkout manager.
Enabled: All pings are saved in the SAP Customer Checkout

manager and shown in the Monitoring tile.
Disabled: Only the last ping sent from SAP Customer Check
out is saved in the SAP Customer Checkout manager and
shown in the Monitoring tile.
Delete entries older than (in days) Indicates the time (in days) after which old monitoring en
tries are deleted.

Field Description
Severity Determines the level of importance or relevance of a mes

sage to be sent to SAP Customer Checkout manager from
SAP Customer Checkout.
Possible levels are:
● All
● Debug
● Information
● Warning
● Error
5.3.5.1.1.5 Personal Info
Personal Info
Field Description
Consent Required In SAP Customer Checkout manager, users, customers, and

loyalty users have the Consent given and maintained indica
tor and the Consent document version field to document
whether a person has consented to the processing of their
personal data.
You can enable or disable this option to make the Consent

given and maintained indicator a required entry field for
users, customers, and loyalty users in SAP Customer Check
out manager.
Enabled: When creating and changing users, customers, and

loyalty users, the Consent given and maintained indicator
must be enabled.
 Note
This requires that the affected person has given consent
for the processing of their personal data.
Disabled: When creating and changing users, customers,

and loyalty users, the "Consent given and maintained" indi
cator must not be enabled.
 Note
If, in SAP Customer Checkout manager, you enable the option Consent required, you must also activate the
corresponding function in all connected SAP Customer Checkout applications.

Furthermore, it is essential that you maintain the versions of the consent document identically in SAP
Customer Checkout and SAP Customer Checkout manager.
 Note
If SAP Customer Checkout is connected with SAP Business One and accesses the customer master data
from SAP Business One, the following restrictions apply for the Consent given and maintained and Consent
document version indicators.
If a customer is changed in SAP Customer Checkout, these two indicators are saved locally for the
customer in SAP Customer Checkout. However, they are not saved in SAP Business One or other SAP
5.3.5.1.1.6 Customer Purchase Data
In this section, you can edit the settings for saving customer purchase data.
Customer Purchase Data

Option Description
Default period (in days) Shows the period in days that is used as a default value for
displaying customers' purchased items in SAP Customer
Checkout and SAP Customer Checkout manager.
Default receipt count Shows the number of receipts used by default to display
customers' last purchases in SAP Customer Checkout and
SAP Customer Checkout manager.
Display customer's lifetime gross revenue figures Indicates whether information about the customer's lifetime
gross revenue figures in SAP Customer Checkout and SAP
Customer Checkout manager is displayed.
5.3.5.1.1.7 Generating Coupon Codes
In this section, you can define the Length of coupon codes for coupons created with the Coupons tile.

5.3.5.1.1.8 Table Management: Cleaning Up Temporary Order
Receipts
In this section, you can clean up the background jobs for temporary order receipts for all SAP Customer
Checkout applications running in table management mode.
Option Description
Start hour Start time at which the cleanup job is triggered.
End hour End time until which the cleanup job continues to be
executed.
Interval in seconds Interval at which the cleanup job is executed.
Number of orders in one execution Maximum number of orders per job
5.3.5.1.2 Images
In this section, you can edit the background image for your logon screen in SAP Customer Checkout manager.
You can upload a new image, remove an existing image, or use the standard SAP image.
SAP Customer Checkout manager delivers a background image for the logon screen as standard.
To upload a new background image for the logon screen, choose Upload Image.
To delete an existing background image, choose Remove Image.
The following image formats are supported: PNG, JPG
The maximum screen size is 3MB.
5.3.5.1.3 Security
In this section, you can configure the password policy for your users in the SAP Customer Checkout manager
and for the loyalty users who are registered within the Loyalty API. You can also specify requirements for the
password policy of your loyalty users or maintain identity providers for user verification from external third
party providers.
5.3.5.1.3.1 Password

Password
Option Description
Users Password policies that are assigned to the users of the SAP
 Note
To set the password policies for the users, see Password
Policies [page 59].
Loyalty users Password policies that are assigned to Loyalty API users.
 Note
To set the password policies for Loyalty API users, see
Password Policies [page 59].
Created by During the initial installation and configuration of the SAP

Customer Checkout manager, the password is set automati
cally by the system (without any connection to a user).
Created at Date and time when the password policies were assigned
Modified by Username of the user who modified the password policies

for the SAP Customer Checkout manager.
Modified at Date and time when the password policies were modified for
the SAP Customer Checkout manager.
5.3.5.1.3.2 Password Policies
These are the requirements for setting the Password Policy for users:
Password Policy Configuration
Option Description
Name The name of the user for whom you want to configure the
password policy.
Two user types are currently available:
● default: The users of your mobile application that you

have integrated into the SAP Customer Checkout man
ager application.
● defaultAdmin: The Admin user of SAP Customer Check
out manager

Option Description
Minimum password length (in characters) Displays the minimum length of the password in characters.
The password should have a minimum length of 8 charac
ters.
Maximum validity of password (in days) Displays the maximum validity period of the password, in
days. The maximum validity period of a password is 360
days. To set a password to be valid indefinitely, enter -1.
Maximum failed login attempts before lock The maximum number of failed attempts to log in to the ap
plication before the user is locked out.
Minimum number of changed characters Displays the minimum number of characters that need to be
changed when you enter a new password.
Minimum number of lower case characters Displays the minimum number of lowercase characters
needed for the password.
For example: Latin lowercase letters a, b, c ... z
Minimum number of upper case characters Displays the minimum number of uppercase characters
For example: Latin uppercase letters A, B, C ... Z
Minimum number of numeric characters Displays the minimum number of numeric characters
For example: Westernized Arabic numerals or extended

characters: 0, 1, 2, 3 ... 9
Minimum number of special characters Displays the minimum number of special characters needed
for the password.
Special characters are, for example ! @ # $ % & * ( ) _ + = - |

<>?{}[]~
5.3.5.1.3.3 Identity Providers
The identification of your loyalty users registered through the Loyalty API can also be verified by the SAP Event
Ticketing provider:
To enter details of the identity provider or assign an identity provider to your SAP Customer Checkout
manager, follow these steps:
1. Select the Identity Provider that you want to edit or assign to your application, and choose Edit.
2. Edit the details of the Identity Provider.

Identity Provider Details
Option Description
Name Name of the Identity Provider
Description Description of the Identity Provider
Active Activate/ Deactivate the specific identity provider for the

identification of loyalty users registered in the mobile ap
plication.
URL URL of the identity provider system
Address Service Path Path to the SAP Event Ticketing Address Service
Session Service Path Path to the SAP Event Ticketing Session Service
Customer Service Path Path to the SAP Event Ticketing Customer Service
Company Company name of the Destination Provider
Authorization Type Type used for the authorization of the Identity Provider
Username Key used to communicate with the Identity Provider
Password Password used to communicate with the Identity Provider
5.3.5.1.4 Proxy
To work with SAP Customer Checkout manager, which uses web application services for external
communication, you need to configure the proxy settings. These proxy settings affect all web services that are
deployed on the SAP Customer Checkout manager.
Proxy Configuration
Option Description
Use Proxy Enable or disable the use of the proxy
HTTP Proxy Host Proxy host name
HTTP Proxy Port Port used by the proxy host
HTTPS Proxy Host Proxy host name when using HTTPS
HTTPS Proxy Port Port used by the proxy host for HTTPS

Option Description
Non Proxy Hosts Hosts for which the proxy is bypassed. To enter multiple
hosts, separate them using the pipe ( | ) character.
Created by During the initial installation and configuration of the SAP

Customer Checkout manager, the proxy settings are set au
tomatically by the system (without any connection to a
user).
Created at Date and time when the proxy settings were assigned
Modified by Username of the user who last modified the proxy settings
for the SAP Customer Checkout manager
Modified at Date and time when the proxy settings were last modified for
the SAP Customer Checkout manager
5.3.5.1.5 About
This section contains information on the database, Web server, and other technical details of your SAP
Customer Checkout manager application.
Database Information
Option Description
Vendor Name of database provider
About SAP Customer Checkout manager
Option Description
Release External customer version number
Version Internal version number
Build number Internal build number
Last commit ID ID number of latest commit
 Note
This information is relevant for technical support.

Option Description
Multi-tenancy enabled Indicates whether SAP Customer Checkout manager is be

ing operated in multi-tenant mode
 Note
For more information, see Using SAP Customer Check
out manager in Multi-Tenant Mode [page 229]
Tenant ID ID of tenant logged in to SAP Customer Checkout manager
 Note
If you have activated multi-tenant mode and this field is
blank, you are in the master tenant.
Java version Java version used to run the application
Java runtime name Name of the Java Runtime Environment (JRE) used to run
the application
Java VM name Name of the Java VM used to run the application
System properties Shows all system properties for the installed version of Java
5.3.5.2 Destinations
On the Destinations tile, you can enter connection data from other SAP Customer Checkout managers and
third-party systems.
You can add, edit, and delete destinations. You can also use the Ping function to check whether a destination
can be reached.
The following fields are available on the Destinations tile:
General Data
Field Description
Type HTTP
Communication takes place using HTTP.
Ticketing XMLRPC
Communication takes place using XML-RPC (connection to

SAP Event Ticketing)

Field Description
Subtype Is only available if the type HTTP is selected.
The destination is SAP Customer Checkout manager.
External system
The destination is an external system that can process the

JSON data sent from SAP Customer Checkout manager.
Name Name of the destination
Description Description of the destination
Host Host address of the destination
Path The path for communication at the host address
Ping path Is only available for the subtype external system.
The path for executing the ping at the host address.
Port The port to communicate with the destination
Connection timeout (in seconds) Time available for a connection attempt. If a connection can
not be established within this time period, the connection at
tempt is aborted.
Session service path Is only available if the type Ticketing XMLRPC is selected.
Path to the SAP Event Ticketing Session Service
Order service path Is only available if the type Ticketing XMLRPC is selected.
Path to the SAP Event Ticketing Order Service
Company name Is only available if the type Ticketing XMLRPC is selected.
Name of the Destination Company
User name User name of the technical user that is used to connect to
the destination.
Password Password of the technical user that is used to connect to the

destination.
Status Specifies whether this destination is active and can be se

lected on the Distribution List tile.

Administrative Data
Field Description
Created At Date and time the destination was created
Created By User name of the user who created the destination
Changed At The date and time when the destination was modified
Changed By User name of the user who modified the destination
5.3.5.2.1 Configuring the Destination for SAP Event

Ticketing Integration
Communication between SAP Customer Checkout and SAP Event Ticketing requires the definition of SAP
Event Ticketing as destination in SAP Customer Checkout.
Context
Procedure
1. On the Destinations tile, choose Add to add SAP Event Ticketing.

2. Enter all values required for communication with SAP Event Ticketing:
Option Description
Type Select the SAP Event Ticketing type.
Name Enter a name for your destination; for example: SAP Event
Ticketing
Host Enter the host address of your SAP Event Ticketing sys
tem.
Path Enter interface
Session service path Enter session.php
Order service path Enter order.php
User name Name of technical user used for connecting with SAP
Event Ticketing
Password Password of technical user used for connecting with SAP

Event Ticketing
Status Set the status to active.

3. Save your entries
5.3.5.3 Dispatcher
The "Dispatcher" tile enables you to add, edit, and delete dispatchers. Here you can specify the destination
systems for your business objects.
For each business object to be transferred to a destination system, a separate dispatcher entry in active status
is required.
 Note
As of release 2.0 FP09, SAP Customer Checkout manager supports the transfer of business objects of
"receipt" and "stock overview" type.
5.3.5.3.1 Creating New Dispatchers
Context
Procedure
1. In the Dispatcher application, choose Add.

2. Select a target system for which you want to create new dispatchers.
3. After you have entered the target system, you can determine which business objects are to be transferred
to your target system. Enter the following information:
Field Description
Type The following business objects can be transferred to the

target system:
○ Receipt
○ Stock Overview
Path The path to the end point for receipts/stock overview in

the defined target system.
If an external third-party system is used as a target sys

tem, the path must be set in the dispatcher entry.

Field Description
 Caution
If the dispatcher entry is SAP Customer Checkout
manager, the path must not be adjusted.
Active Specifies whether the business object is to be transferred

to the target system.
 Note
Provided that you have entered all the information for a business object and have set the dispatch
status to Active, the relevant information and transactions of the business object are transferred to the
defined target system automatically in real time.
5.3.5.4 Sequence Numbers
On the "Sequence numbers" tile you define how IDs for certain objects (day-end closings, customers, loyalty
account IDs, loyalty users) are generated in SAP Customer Checkout manager. Each sequence number is
defined by a pattern.
Sequence numbers for customers are used for customers created in SAP Customer Checkout manager.
If central customer management is activated in SAP Customer Checkout, the sequence numbers for
customers in SAP Customer Checkout manager are also used for creating customers in SAP Customer
Checkout.
Sequence Number Settings
Option Description
Name Sequence number name
Number pattern Sequence number pattern. Uses Freemarker-based XSL to

describe how the numbers are generated.
Current sequence Last sequence number that was generated.
Current number Last number that was used in the sequence number.
Increment Size Value by which the number is incremented.
 Note
For further Information on sequence numbers, please see the SAP Customer Checkout Configuration
Guide.

5.3.5.5 Sequence Number Users
On the Sequence Number Users tile, you define which sequence number of which business object is used.
Every business object that requires a sequence number is assigned a sequence number by default.
You can assign additional sequence numbers to a business object and edit or delete existing sequence number
users.
 Note
Sequence number users for which the standard indicator has been activated cannot be deleted.
Multiple sequence numbers can be assigned to a business object, and a sequence number can be assigned to
multiple business objects. If multiple sequence numbers are assigned to a business object, the standard
indicator can be active only for one sequence number.
 Note
The standard indicator determines which sequence number is preselected for the creation of business
objects in SAP Customer Checkout manager. If central customer management is active in SAP Customer
Checkout, the standard indicator also determines, for the customer sequence number user, which
sequence number is used for creating customers in SAP Customer Checkout.
5.3.5.6 Licenses
On this tile, you can manage all licenses for your SAP Customer Checkout applications.
 Note
Only users with the "Administrator" role can display and use this tile.
As of SAP Customer Checkout 2.0 Feature Pack 08, you require a valid license for every SAP Customer
Checkout application and for every SAP Customer Checkout manager. Licensing information is maintained
only in SAP Customer Checkout manager, where this information is then binding.
After every installation, you receive a temporary license that is valid for 28 days starting from the installation
date. Before the temporary license expires, you must request a permanent license key using the SAP License
Key application https://support.sap.com/en/my-support/keys.html . We recommend that you do this as
soon as possible after the installation.
On the Licenses tile, you will find the Details and Assignments areas.
In the Details area, you can see all the important information about your license for SAP Customer Checkout
manager. You can upload and download license key information and view the number of licensed POS systems.
In the Assignments area, you can see all POS systems that are assigned to the respective license. You can
remove one, multiple, or all assignments, or assign a license to a POS group.

5.3.5.6.1 Requesting a License Key
A license is assigned for exactly one SAP Customer Checkout or SAP Customer Checkout manager system.
Prerequisites
Make sure that you have installed SAP Customer Checkout manager successfully. Within the Licenses subtile,
you can find information about the hardware key. You need this to request the license key.
Context
Procedure
1. Go to https://support.sap.com/en/my-support/keys.html .
2. Add a new system, choose the product SAP Customer Checkout, and select the version number.
3. Enter all other data and continue.
4. After you have entered all of the system data, you can now request the license key.
5. In the new window, enter the hardware key of your SAP Customer Checkout manager system and the
number of licenses or devices.
 Note
You require a separate license for every SAP Customer Checkout system.
6. Choose Add.
7. Select the entry and choose Generate to generate the license key.
8. You can now download the license key information.
5.3.5.6.2 Uploading a License Key
After you have downloaded license key information from SAP Service Marketplace, you can upload it to SAP
Context

Procedure
1. In SAP Customer Checkout manager, choose the Configuration tile and then the Licenses subtile.
2. Choose Upload to upload the file containing the license key information.
3. Once the license key has been uploaded, the information in the Details area is adjusted automatically.
 Note
The temporary status changes to Permanent.
The following information is displayed:
Field Description
Hardware key ID of the hardware key of SAP Customer Checkout man

ager
Number of licensed POS systems Total number of POS systems that are actually licensed
according to the license key
 Note
The number denotes the number of devices that you
specified when requesting the license key.
Number of licenses assigned to POS systems Number of POS systems that are already assigned to the
license key
Number of licenses available for assignment Number of POS systems still available for assignment.
Status Status of the SAP Customer Checkout manager license
The following statuses are available:
○ Licensed
○ Over-use: More SAP Customer Checkout licenses
than available are assigned to the license key.
○ Not valid: The hardware key failed to generate or the
hardware has been changed.
○ Expired: The SAP Customer Checkout manager li
cense has expired.
○ Not installed: There is no license available for SAP
Customer Checkout manager. This status occurs,
even if a 32 bit Java version is used.
○ Inactive: License management is deactivated.
Type License type
The following types are available:
○ Temporary
○ Permanent
Installation number

Field Description
System number SAP Customer Checkout manager system number
Database Name of the database to which SAP Customer Checkout

manager is connected
Valid from Date and time from when the SAP Customer Checkout
manager license is valid.
Valid to Date and time up to which the SAP Customer Checkout

manager license is valid.
5.3.5.6.3 Assigning a License to a POS System
Once you have uploaded the license key information to SAP Customer Checkout manager, you can assign a
license to your SAP Customer Checkout application.
Context
Your POS system will operate in the status Temporary License until you assign it a valid license.
Procedure
2. In the Assignments area, you see all the SAP Customer Checkout systems that are integrated with SAP
3. You have the following options:
○ Assign a license to an SAP Customer Checkout application: Select the relevant POS system, choose
Assign, and choose OK to confirm.
○ Assign a license to all SAP Customer Checkout applications: Choose Assign to All and confirm with OK.
All POS systems are assigned to the relevant license key according to the Number of licenses available
for assignment.
○ Assign license to POS group: Choose Assign to POS group, select the respective POS group, and
confirm with OK. All POS systems that belong to the respective POS group are assigned to the relevant
license key.
4. Once you have selected one of the options, the information regarding the assignments of the relevant SAP
Customer Checkout systems is updated. The following information is displayed:
Field Description
Status Displays the licensing status of the POS system.

Field Description

○ Assigned
○ Unassigned: The relevant POS system was assigned
to the license, but the assignment was removed.
○ Not assigned: The relevant POS system has never
been assigned to the license.
POS ID Prefix of POS system
POS group ID Name of the POS group that belongs to the respective
POS system
Hardware key Displays the hardware key of the respective POS system
Assigned from Displays the date and time of the assignment
Assigned by Displays the name of the user who made the assignment
Unassigned from Displays the date and time when the assignment was re
moved
Unassigned by Displays the name of the user who removed the assign
ment
5.3.5.6.4 Unassigning a License from a POS System
You can unassign a license from a POS system.
Context
Procedure
2. In the Assignments area, you can choose the following options:
○ Unassign a single license from a POS system: Select the relevant POS system that you want to
unassign, choose Unassign, and confirm with OK.
○ Unassign all licenses from all POS systems: Choose Unassign from all and confirm with OK.

5.3.5.6.5 Adding or Removing Licenses
You can add or remove SAP Customer Checkout licenses at any time.
If you want to add or remove SAP Customer Checkout licenses, you have to request a new license key with the
relevant number of licenses using the SAP License Key application https://support.sap.com/en/my-support/
keys.html and upload it again to SAP Customer Checkout manager.
Example
You currently have SAP Customer Checkout manager with three SAP Customer Checkout licenses and you
now want to add two additional SAP Customer Checkout licenses, amounting to five POS systems in total.
 Note
Since your previous license key is only valid for three SAP Customer Checkout applications, you have to
request a new license key.
Follow the steps below to add or remove licenses:
2. Select the relevant system for which you want to adjust the number of licenses.
3. Select the relevant license key and choose Edit.
4. In the Number field, you can now enter the new number of licenses or devices.
5. Choose Add.
6. To generate the license key, choose Generate.
7. You can now download the updated license key information.
8. In SAP Customer Checkout manager, you can now upload this license key file in the Licenses subtile within
the Configuration tile.
 Note
The license information is updated.
5.3.5.6.6 Changing Hardware
This section describes how to perform hardware changes.
The hardware on which SAP Customer Checkout manager or the SAP Customer Checkout application is
installed may become damaged or require changes. Such changes also affect the license key.
A distinction is made between:
● Hardware changes on devices on which SAP Customer Checkout manager is installed

● Hardware changes on devices on which SAP Customer Checkout is installed

5.3.5.6.6.1 Changing Hardware for SAP Customer Checkout
manager
The following section describes the steps required to change the hardware on devices on which SAP Customer
Checkout manager is installed. The uploaded license key information is no longer valid for the new hardware.
Context
For example, you have installed SAP Customer Checkout manager on a device and this hardware device is now
damaged, meaning that SAP Customer Checkout manager must be installed on a new device.
Procedure
1. Once you have successfully installed SAP Customer Checkout manager on a new hardware device, you will
find the hardware key in the Licenses subtile within the Configuration tile. You need this to request the new
license key.
3. Select the relevant system for which you want to change the hardware.
4. Select the relevant license key and choose Edit.
5. Continue and choose Edit.
6. In the Hardware key field, you can now enter the new hardware key from your SAP Customer Checkout
manager installation.
7. Choose Add.
8. To generate the license key, choose Generate.
9. You can now download the updated license key information.
10. In SAP Customer Checkout manager, you can now upload this license key file in the Licenses subtile within
the Configuration tile.
 Note
The license information is updated accordingly.

5.3.5.6.6.2 Changing Hardware for SAP Customer Checkout
The following section describes the steps required to change the hardware on devices on which SAP Customer
Checkout is installed. The hardware key for the respective SAP Customer Checkout application must be
changed manually in this case.
Context
For example, you have installed SAP Customer Checkout on a device and this hardware device is now
damaged, meaning that you have to install the POS system on a new device.
Procedure
1. Install SAP Customer Checkout on a new hardware device and make sure that it is connected to SAP
Customer Checkout manager successfully.
2. Log on to SAP Customer Checkout manager and choose the Organizational Structure tile.
3. Select the POS system for which you want to change the hardware key and choose More Information.
4. Choose Edit and enter the respective hardware key manually.
The status of your license for SAP Customer Checkout will be updated with the next license check. A
license check (of the respective POS system to SAP Customer Checkout manager) is executed
automatically every hour.
5.3.5.6.7 SAP Customer Checkout in Offline Mode
This section describes what to do if your SAP Customer Checkout application is not connected with SAP
Customer Checkout manager, or is running in offline mode.
If your SAP Customer Checkout system has no connection with SAP Customer Checkout manager, or if it is run
in offline mode, the license check with SAP Customer Checkout manager fails.
If this status remains for 24 hours, the SAP Customer Checkout logon screen displays the message "No valid
license assigned".
Your SAP Customer Checkout application can remain operational; the user is merely notified. The system is
neither locked nor restricted.

5.4 Point of Sales Management
5.4.1 Organizational Structures
In this tile, you can manage the organizational hierarchy of your company or organization.
The organizational structure contains the following units:
● POS group: a unit that contains POS system units

● SAP Customer Checkout POS system: the application installed on your POS systems
You can keep track of your POS systems and groups, create new POS systems and groups, assign POS systems
to POS groups, move POS systems and groups, see hierarchical dependencies, delete POS systems and
groups, and show the version and build number of each POS system. Furthermore, you can view the assigned
users, quick selections, price lists, and software versions to each SAP Customer Checkout POS system.
 Example
If you are in the Sports and Entertainment field, you might have two primary POS groups, each containing
several POS systems. For example, your primary POS groups may be the following:
● Food and Beverage

● Merchandising
Within the Food and Beverage POS group, you may have POS systems for Food, Soft drinks, Alcoholic
drinks, and so on.
When an SAP Customer Checkout POS system is installed and connected to the SAP Customer Checkout
manager, a new organizational unit is created.
The following information is available for each organizational unit:
Organizational Units
Field Description
Name Name of the organizational unit
ID ID of the organizational unit
 Note
If the organizational unit is a POS system, the ID is taken
from the ID of the POS system.

Field Description
Type Type of organizational unit
Possible types are:
● POS group
● POS system
Version/Build Number Software version of the SAP Customer Checkout POS sys
tem
Select an organizational unit to see tabs with detailed information. The title and displayed tabs change
depending on the type of organizational unit that you selected.
When you select a POS group, the POS Group tab is available:
POS group
Tab Description
POS system Shows details about the respective POS group. For example,
POS group ID, description, and administrative data.
When you select a POS system, the following tabs are available:
POS system
Tab Description
POS system Shows details about the respective POS system, and soft
ware version information. For example, POS system ID, de
scription, administrative data, and software version number.
Users Shows users assigned to the respective POS system.
 Note
This Users tab is for information purposes only, and not
editable.
Quick selections Shows quick selections assigned to the respective POS sys
tem.
 Note
This Quick selections tab is for information purposes
only, and not editable.

Tab Description
Price lists Shows price lists assigned to the respective POS system.
 Note
This Price lists tab is for information purposes only, and
not editable.
Assigned software Shows software versions assigned to the respective POS

system.
 Note
This Assigned software tab is for information purposes
only, and not editable.
The POS system tab contains the subtabs Details and Version with further information about the organizational
unit:
Details Subtab
Field Description
ID ID of the organizational unit
 Note
If the organizational unit is a POS system the ID is taken
from the ID of the POS system.
Name Name of the organizational unit
Description Description of the organizational unit
Location Location of the organizational unit
 Note
This field is only shown when a POS system entry has
been selected.
Version/build number Software version of the SAP Customer Checkout POS sys
tem
Created by Username of the user who created the organizational unit in

Created at Date and time when the organizational unit was created in

Field Description
Modified by Username of the user who modified the organizational unit

in the SAP Customer Checkout manager
Modified at Date and time when the organizational unit was modified in
Version Subtab
Field Description
Version/Build Number Software version of the POS system
Java Version Java version used to run the POS system
System properties System properties for the installed version of Java
The Users tab contains information about the users assigned to the POS system:
Users Tab
Field Description
Username Name of the user used to log in to SAP Customer Checkout

manager.
 Note
Click on the username to go to the respective user ac
count in the Users tile.
Name The user's first and last name.
User locked Shows whether the user is locked in the respective POS sys
tem.
Assigned to Shows the closest POS group or POS system to which the
respective user is assigned.

The Quick selections tab contains information about quick selection configurations assigned to the respective
POS system:
Quick selections Tab
Field Description
Name Name of the quick selection configuration
 Note
Click the quick selection name to go to the respective
quick selection configuration in the POS configuration
tile.
Assigned to Shows the POS group or POS system to which the respec
tive quick selection configuration is assigned.
The Price lists tab shows all of the price lists assigned to the respective POS system:
Price listsTab
Field Description
ID Individual price list ID
 Note
Click on the price list ID to go to the respective price list in the
Price lists tile.
Description Description of the price list
Active Shows whether the price list is active or not.
Synchronize (in PoS) Shows whether the price list is synchronized in the POS system.
Default Shows whether the price list is used as the default price list.
 Note
Only one price list can be marked as the default price list.

Field Description
Default assigned to Shows the closest POS group or POS system that is marked as the
default price list.
 Example
Assuming that you have two price lists (PL1, PL2) and the follow
ing organizational structure: root → Merchandising Shop → POS1
Example 1 - The price lists are assigned as follows:
● PL1:
○ root: default
● PL2:
○ POS1: not default
○ root: default
The following information will be shown in the Price list
details tab for POS1:
Price Lists Details
Default as
ID Default signed to Assigned to
PL1 No - root
PL2 Yes root POS1
Example 2 - The price lists are assigned as follows:
● PL1:
○ root: not default
● PL2:
○ POS1: default
○ root: not default
The following information will be shown in the Price list de
tails tab for POS1:
Price Lists Details
Default as
ID Default signed to Assigned to
PL1 No - root
PL2 Yes POS1 POS1
Assigned to Shows the closest POS group or POS system to which the respective
price list is assigned.

The Assigned software tab contains information about assigned software versions and software installations:
Assigned software Tab
Field Description
Build number Date and time when the software was created
 Note
Click on one of the Build numbers to go to the respective
software version in the Software tile.
Name Name of the software
Assigned version Shows the version number which should run on the respec
tive POS system.
Actual version Shows the version number that is actually running on the re
spective POS system.
Assigned to Shows the closest POS group or POS system to which the
respective software is assigned.
5.4.1.1 Creating New Organizational Units
In the Organizational Structure tile, you can create new organizational units (POS system and POS groups).
Context
 Note
The first time that you connect a POS system with the SAP Customer Checkout manager, the system looks
for a POS system ID in the Organizational Structure tile. If no POS system is found in the SAP Customer
Checkout manager, a new organizational unit entry is created automatically.
Procedure
1. In the Organizational Structure tile, choose Create.

2. Choose the organizational unit type that you want to create.
3. Select the POS group that you want the new organizational unit to be assigned to.
If you don't want to assign the new organizational unit to an existing POS group, choose root.

4. Enter an ID and Name for the organizational unit.
5.4.1.2 Deleting Organizational Units
In the Organizational Structure tile, you can delete POS systems and POS groups.
Context
 Note
You can only delete POS groups that are not referenced by other organizational units.
POS systems that have once been connected with the SAP Customer Checkout manager, cannot be
deleted as a reference is existing for the POS system.
Procedure
1. In the Organizational Structure tile, select the organizational unit (POS group or POS system) that you want
to delete.
2. Choose Delete and confirm the deletion with OK.
5.4.1.3 Moving Organizational Units
You can move organizational units to reflect changes in your organization. For example, you can move POS
groups or POS systems to other POS groups.
Procedure
1. In the Organizational Structure tile, select the organizational unit (POS group or POS system) that you want
to move.
2. Choose Move.
3. Choose the POS group you want the organizational unit to be moved to and confirm with OK.

5.4.2 Time Recordings
The Time Recordings tile lets you centrally check time recordings made from all users in various SAP Customer
Checkout applications.
When a time recording transaction has been performed in SAP Customer Checkout, an entry is created in SAP
Customer Checkout manager with all of the details about the time recording . When you have several SAP
Customer Checkout applications running, and several users within your organization recording their time, the
Time Recordings tile is where you can view them all. You can search, filter, or sort time recording transactions.
 Note
You cannot edit time recording transactions or correct them in the SAP Customer Checkout manager. You
can only view the detailed information. If you want to edit or correct time recording transactions, you can
run a time recording export file that can then be imported into any third-party time tracking system. For
more information, see Time Recordings Export [page 86].
The following details are available in the Time Recordings tile for each time recording transaction:
Time Recording Details
Field Description
Book Status Status level of the time recording transaction sent from SAP Customer
Checkout to SAP Customer Checkout manager.
Possible statuses are:
● Complete
● Critical
● Incomplete
Punch in Date and time when the user punched in to SAP Customer Checkout.
Punch out Date and time when the user punched out from SAP Customer Checkout.
Hours Summary of the time that the user spent on the system.
Hours Decimal Summary of the time that the user spent on the system, in decimal num
bers.
Org Unit Name of the Organizational Unit for which the user created the time record
ing transaction.
Punch in POS ID of the POS system from where the punch in transaction was executed.
Punch out POS ID of the POS system from where the punch out transaction was executed.

Field Description
Username Name and detailed name of the server user in the SAP Customer Checkout
manager.
 Note
Click the Username to go to the respective user.
Punch in supervisor Name of the user who approved the time recording punch in request in SAP
Customer Checkout.
 Note
Click the Punch in supervisor to go to the respective user.
Punch out supervisor Name of the user who approved the time recording punch out request in
 Note
Click the Punch out supervisor to go to the respective user.
Manual punch out Shows whether a manual punch out was performed in the SAP Customer
Checkout manager. Possible statuses are:
● True: The punch out of the respective user was performed manually in
● False: The punch out of the respective user was performed in the re
spective POS system.
Unique Stamp ID Time recording position identifier
5.4.2.1 Performing a Manual Punch Out
Context
If needed, you can perform a manual punch out directly in the SAP Customer Checkout manager. For example,
when a user has forgotten to punch out at the point of sale, and you want punch out for this user.
 Example
A user starts work in the morning and punches in at the point of sale. It might happen that the user leaves
work at the end of the day without punching out . In the SAP Customer Checkout manager system, the
time recording entry will be shown as incomplete. An authorized user with the permissions Using time

recording and either Approve time recording request or Do time recording punch out without
authorization, can perform a manual punch out of the working time on behalf of this respective user. The
benefits of this approach are that the authorized user does not need to log in to the respective POS system
(where the punch in was performed), and the password of the respective user is not needed.
 Note
To perform a manual punch out in the SAP Customer Checkout manager, the user needs the following
permissions:
● Using time recording

AND
● Approve time recording request OR Do time recording punch out without authorization
 Caution
Time recording transactions (punch in and punch out) should be performed manually in the SAP Customer
Checkout application, and not in the SAP Customer Checkout manager. You should only performing a
manual punch out in the SAP Customer Checkout manager in exceptional cases, and by authorized users.
Procedure
1. Select the Time Recordings tile in the SAP Customer Checkout manager.
2. Click the Manual punch out icon of the respective time recording entry.
3. Enter the Punch out POS system, and select a Punch out date.
 Note
If no punch out date has been selected, the current date and time is selected.
You can also select a past date as punch out date.
4. To finish the manual punch out, choose Save.
5.4.3 Time Recordings Export
The Time Recordings Export tile lets you export time recording files that include time recording transactions
performed in various SAP Customer Checkout applications from all users. The time recording export file can be
imported and used in any third-party time tracking system, for example to edit time recording transactions.
You can export new time recording files, download a time recording export file, see an overview of the latest
time recording export files, sort, or filter time recording export files.

The following options are available in the Time Recordings Export tile:
Time Recordings Export Options
Option Description
New Export Exports time recording files generated in the various SAP
History Provides an overview of the latest time recording export files.
The following information is available for time recordings export files:
History Details
Field Description
Description Name of the time recordings export file
Process ID ID of the process that executes a time recording export file
Execution start Displays the date and time when the export of the time re
cording file was completed.
Execution done Displays when the execution of the time recordings export
file was finished.
Execution state Indicates the status of the execution of the time recording
export.
● Idle
● Running
● Canceled
● Finished
Execution result Indicates if the time recording export file was executed suc
cessfully.
● None
● Canceled
● Success
● Fail
● Fatal
Status message Shows the status message.
Download Enables the time recording export file to be downloaded.
Cancel worker Lets you cancel an export process while it's running.

5.4.3.1 Exporting Time Recording Files
Context
If you want to export time recording files for a specific organization, role, or time period, you can do this
centrally in SAP Customer Checkout manager. The export file containing time recordings can be imported into
third-party systems for further editing.
Procedure
1. Select the Time Recordings Export tile in SAP Customer Checkout manager.
2. In the "New Export" section, enter the data for the export file. For example, you can use the Role dropdown
list to restrict the export to users who have a specific role.
 Note
The export file is automatically stored locally in SAP Customer Checkout manager.
When you enter a path for the export file, a copy is stored in the path folder.
You can also specify an executionDate and executionTime in the File field.
3. To run the export, select Start Export.
The status of your time recordings file is shown in the History section.
Once the export is complete, you'll find the file in your local SAP Customer Checkout directory.
5.4.4 Monitoring
The Monitoring tile provides you with an overview of all of the status messages and status information that are
sent from various SAP Customer Checkout applications to SAP Customer Checkout manager.
The SAP Customer Checkout application communicates with SAP Customer Checkout manager to send
regular notifications about the state of each SAP Customer Checkout application. In the Monitoring tile, you
can keep track of the status messages sent from your SAP Customer Checkout applications, see detailed
information about each status message, search, sort, and filter status messages.
 Note
The status messages are displayed in the overview according to the severity that you set in the
configuration of SAP Customer Checkout.

The following information is available for each status message in the Monitoring tile:
Monitoring
Field Description
Severity Level of importance or relevance of a status message
● Information: includes all information sent from the SAP

Customer Checkout application that isn't critical (for
example, starting the application, or logging in)
● Warning: includes information sent from the SAP Cus
tomer Checkout application that requires attention (for
example, a lack of free disc space)
● Debug: includes all information sent from the SAP Cus
tomer Checkout application to analyze coding
● Error: includes information sent from an SAP Customer
Checkout application that contain errors or prevents a
transaction from being performed (for example, failure
of a synchronization job)
 Note
If the Severity is set to Information, Warnings and Errors
are also included and sent to the SAP Customer Check
out manager.
POS system POS system ID used throughout the application
 Note
Click the POS system IDto open the respective organiza
tional structure.
Timestamp Date and time when the status message was sent from SAP
Customer Checkout to SAP Customer Checkout manager

Field Description
Event Group Name of the Event Group assigned to the status message
Possible Event Groups are:
● Start: Starting the SAP Customer Checkout application

● Shutdown: Shutting down the SAP Customer Checkout
application
● System: System-related status messages sent from the
SAP Customer Checkout application
● Configuration Import: Importing a configuration file into
the SAP Customer Checkout application
● Configuration Export: Exporting a configuration file
from the SAP Customer Checkout application
● Customer Synchronization: Performing a customer syn
chronization in SAP Customer Checkout
● Discount Synchronization: Performing a discount syn
● User Synchronization: Performing a user synchroniza
tion in SAP Customer Checkout
● Single User Synchronization: Performing a single user
synchronization in SAP Customer Checkout
● Material Synchronization: Performing a material syn
● Receipt Synchronization: Performing a receipt synchro
nization in SAP Customer Checkout
● Voucher Synchronization: Performing a voucher syn
● Quickselection Synchronization: Performing a quickse
lection synchronization in SAP Customer Checkout
● Update Software Synchronization: Verification process
if a new software version of SAP Customer Checkout is
available. If a new software version is available, the new
version is automatically downloaded.
● Synchronization: Synchronizing the SAP Customer
Checkout application with an SAP ERP system
● Plugin: Connecting a plugin to the SAP Customer
Checkout application
Each event group comprises various events that are as

signed to the status messages. Most of the event groups
consist of the start of an event and the end of an event.

Field Description
Event Name of the Event assigned to the status message. Each

event belongs to an event group (see table below).
Possible events are:
● Start:
○ App start
○ App start completed
● Shutdown:
○ App shutdown
● System
○ App start
○ App shutdown
○ Debug
○ Login
○ Log
○ Logout
○ Ping
○ Update: performing an update of the new software
version in the SAP Customer Checkout application
○ Backup
○ SAP Customer Checkout manager settings
changed
○ Less disk space left
○ New SAP Customer Checkout manager
● Configuration Import
○ Job start
○ Job end
● Configuration Export
○ Job start
○ Job end
● Customer Synchronization
○ Job start
○ Job end
○ Job fetch
○ Job post
● Discount Synchronization
○ Job start
○ Job end
○ Job fetch
○ Job post
● User Synchronization
○ Job start

Field Description
○ Job end
○ Job fetch
● Single User Synchronization
○ Job start
○ User found
○ No user found
● Material Synchronization
○ Job start
○ Job end
○ Job fetch
○ Job post
● Receipt Synchronization
○ Job start
○ Job end
○ Job fetch
○ Job post
● Voucher Synchronization
○ Job start
○ Job end
○ Job fetch
○ Job post
● Quickselection Synchronization
○ Job start
○ Data received
○ No data received
○ Job end
● Update Software Synchronization
○ Job start
○ Job end
○ Job fetch
○ Update available
○ No update available
● Synchronization
○ Job fetch
○ Job post
● Plugin
○ Job start
○ Job end
○ Job fetch
○ Job post
○ Device start (line display)

Field Description
○ Device start (cash drawer)

○ Device start (printer)
○ Device start
○ Device stop
○ Device restart
User Username of the user logged in to SAP Customer Checkout

when the status message was sent to the SAP Customer
Checkout manager.
 Note
If no username appears in the status message, this
means that no user was logged in to SAP Customer
Checkout at the time the status message was sent to
 Note
Click the User to open the respective server account.
POS system Version Software version of the SAP Customer Checkout application
Buildnumber Date and time when the SAP Customer Checkout software
was created
All event groups have several possible events:
Possible Events
Event Name Event Group Description Severity Level
App start Start Starting process of SAP Cus Information

tomer Checkout application
System
has been triggered
 Note
Additional information
about the Java Virtual
Machine, environment
(Base64 decoded), and
internal version is shown
with this event.

App start completed Start Starting process of SAP Cus Information

tomer Checkout application
has finished
App shutdown Shutdown SAP Customer Checkout ap Information

plication is shutting down
System
Debug System Debug message sent from Information

the SAP Customer Checkout
system
 Note
This event might only be
relevant for developers.
Login System A user has logged in to the Information

SAP Customer Checkout
system
Log System Log message sent from the Information

system
 Note
This event contains all of
the information that is
displayed in the cmd
console of the SAP Cus
tomer Checkout system.
Logout System A user has logged out of the Information

system
Ping System Ping message sent from the Information

system

Update System An update of the SAP Cus Information

tomer Checkout system has
been performed
 Note
Additional information,
such as previous soft
ware version, build num
ber, and release version
of the SAP Customer
Checkout system is
shown in this event.
Backup System A backup of the SAP Cus Information

tomer Checkout system has
been performed
Less disc space left System Less disk space is left in the Information
hardware device where SAP
Customer Checkout system
is running
SAP Customer Checkout System Settings for the SAP Cus Information
manager settings changed tomer Checkout manager
have been changed in the
Integration tab of the the SAP
Customer Checkout Configu-
ration screen

New SAP Customer Check System SAP Customer Checkout has Information
out manager connected to a new SAP Cus
system
 Note
The first time you con
nect a POS system to
manager, the system
looks for a POS system
ID in the Organizational
Structure tile. If no POS
system is found in the
manager, a new organi
zational unit entry is au
tomatically created.
Job start Configuration Import Starting process of the event Information

job has been triggered
Configuration Export Debug
Discount Synchronization Error
User Synchronization Warning
Material Synchronization
Receipt Synchronization
Voucher Synchronization
Quickselection Synchroniza
tion
Update Software Synchroni

zation
Plugin

Job end Configuration Import Event job has finished Information
Configuration Export Debug
Discount Synchronization Error
User Synchronization Warning
Material Synchronization
Quickselection Synchroniza
tion

zation
Plugin
Job fetch Customer Synchronization Event job has fetched data Information
from the back-end system to
Discount Synchronization Debug
User Synchronization Error
Material Synchronization Warning

zation
Synchronization
Plugin
Job post Customer Synchronization Event job has posted data Information
from the back-end system to
Discount Synchronization Debug
Material Synchronization Error
Receipt Synchronization Warning
Synchronization
Plugin

User found Single User Synchronization User found in the application Information
that logged in to SAP Cus
tomer Checkout.
 Note
When a user has not
synchronized in SAP
Customer Checkout with
a full user synchroniza
tion and this user logs in
to SAP Customer Check
out, a single user syn
chronization is carried
out.
No user found Single User Synchronization The user who logged in to Information
SAP Customer Checkout was
not found in the back-end
system.
 Note
When a user has not
synchronized in SAP
Customer Checkout with
a full user synchroniza
tion and this user logs
into SAP Customer
Checkout, a single user
synchronization is car
ried out.
Data received Quickselection Synchroniza Quickselection information Information

tion has been successfully sent to
 Note
A new quickselection has
been received from the
back-end system and re
placed the current quick
selection version.

No data received Quickselection Synchroniza Quickselection information Information

tion has not been sent to SAP
Customer Checkout
 Note
There is no new quickse
lection version available.
Update available Update Software Synchroni New software version of SAP Information
zation Customer Checkout is availa
ble
No update available Update Software Synchroni There is no software update Information

zation version of SAP Customer
Checkout available
Device start (line display) Plugin Line display connected to Information

SAP Customer Checkout has
been started
Device start (cash drawer) Plugin Cash drawer connected to Information

SAP Customer Checkout has
been started
Device start (printer) Plugin Printer connected to SAP Information

Customer Checkout has
been started
Device start Plugin Hardware device connected Information

has been started
Device stop Plugin Hardware device connected Information

has been stopped
Device restart Plugin Hardware device connected Information

has been restarted
Select one of the status messages listed in the Monitoring Tile to see tabs with more information.
The General Data tab provides you POS system and event information for the respective status message.

General Data
Field Description
POS system POS system ID used throughout the application
POS system Version Software version of the SAP Customer Checkout application
POS system Buildnumber Date and time when the SAP Customer Checkout software
was created
User Username of the user logged in to SAP Customer Checkout

when the status message was sent to the SAP Customer
Checkout manager
 Note
If no username appears in the status message, it means
that no user was logged in SAP Customer Checkout
when the status message was sent to SAP Customer
Checkout manager.
Severity Level of importance or relevance of a status message that is

sent from SAP Customer Checkout to the SAP Customer
Checkout manager
● Information: includes all information sent from the SAP

Customer Checkout application that isn't critical (for
example, Starting the application, or login)
● Warning : includes information sent from the SAP Cus
tomer Checkout application that requires attention (for
example, a lack of free disk space)
● Debug: includes all information sent from the SAP Cus
tomer Checkout application to analyze the coding
● Error: includes information sent from an SAP Customer
Checkout application that contain errors or prevents a
transaction from being performed (for example, failure
of a synchronization job)
 Note
If Information is set as the Severity, Warnings and Errors
are also included and sent to the SAP Customer Check
out manager.
Timestamp Date and time when the status message is sent from SAP
Customer Checkout to the SAP Customer Checkout man
ager

Field Description
Event Group Name of the Event Group assigned to the status message
(see above).
Event Name of the Event assigned to the status message: each

event belongs to an Event Group (see above).
Description Describes the event sent from SAP Customer Checkout
The Additional Options tab has information about the key and value of the respective status message.
Additional Options
Field Description
Key Key value of the event sent from SAP Customer Checkout
For example: stacktrace, freeMemoryKb, memoryConsump

tion
Value Value assigned to the key of the event sent from SAP Cus
tomer Checkout
5.4.4.1 Deleting Monitoring Entries
In the Monitoring tile, you can also delete entries of status messages.
Context
You can select which entries to delete, either by name, date, or type, or delete all entries.
Procedure
1. In the Monitoring tile select Delete Entries.

2. Select the severity, and the date and time of the entries to delete.
3. Select Delete.

5.4.5 Monitoring Reports
On the Monitoring Reports tile, you can generate reports on warnings and error messages that were sent from
different SAP Customer Checkout applications to SAP Customer Checkout manager.
Using the Monitoring Reports tile, you can determine for which SAP Customer Checkout applications warnings
or error messages occur. You can also display which SAP Customer Checkout applications can currently be
reached.
Choose the Monitoring Reports tile to display monitoring reports or download monitoring reports as a
Microsoft Excel file. You can generate the following monitoring reports:
● All-in-one: Generates a report that comprises all monitoring reports.

● Based on event/event group: Generates a report showing the number of warnings and error messages
broken down by event and event group. You can specify the start and end of the reporting period, filter by
POS group or POS system, and specify which event or event group you want to display.
● Based on log message: Generates a report showing the contents of selected warnings and error messages.
You can specify the start and end of the reporting period, filter by POS group or POS system, and specify
which event or event group you want to display.
● Based on POS system: Generates a report showing the number of warnings and error messages broken
down by POS system. You can specify the start and end of the reporting period, filter by POS group or POS
system, and specify which event or event group you want to display.
● Receipt Gap Identifier: Generates a report on receipt gaps in the selected POS groups or POS systems. If,
when posting a receipt in SAP Customer Checkout, the sequence number ID is interrupted and not
updated continuously, there is a receipt gap in the SAP Customer Checkout manager. You can define the
start and end of the reporting period.
● Article Stock Information: Generates a report on the available stock levels of selected articles and
warehouses.
● Article Transaction History: Generates a report on all receipt and stock transactions of selected articles and
warehouses. You can define the start and end of the reporting period.
● Based on POS system status: Generates a report showing the availability of POS systems. SAP Customer
Checkout can be configured to ping SAP Customer Checkout manager at regular intervals. If SAP
Customer Checkout manager receives the ping signal, it can be assumed that the corresponding SAP
Customer Checkout application is active and reachable.
You can filter by POS group or POS system and select the time interval (in seconds) for determining the
reachability status. For example, for a ping interval of 600 seconds, all SAP Customer Checkout
applications are displayed that have successfully pinged SAP Customer Checkout manager in the last 600
seconds.
 Note
For determining the reachability status, we recommend selecting a time interval larger than the time
interval for sending the ping signal to SAP Customer Checkout. Otherwise, those POS systems that
send their ping signal outside of the time interval selected in SAP Customer Checkout manager appear
as not reachable.

5.4.6 Receipt Exports
On this tile, you can export receipts for certain time periods and organizational structures.
 Note
The receipt export also contains all canceled receipts.
Export Settings:
Field Description
Description Enter a description for the receipt export.
POS group Select POS groups for which you want to export receipts. All
POS systems that are part of the selected POS groups at the
time of the export are included in the export.
POS groups and cash desks cannot be selected at the same

time.
POS system Select all POS systems for which you want to export re
ceipts.
POS groups and cash desks cannot be selected at the same

time.
Date from The period start date for the receipt export.
Date to The period end date for the receipt export.

Field Description
Format Select the data format for the export; the following data for
mats are available:
● JSON
JSON (JavaScript Object Notation) is a data format for
exchanging data between applications.
● IDEA
Data format for the software application IDEA.
● PDF (cash journal)
Cash journal in form readable by humans. Displays a list
of all receipts in the selected timeframe.
● PDF (cash book)
Cash book in form readable by humans. Displays a list
of all receipts and the current cash balance for the se
lected timeframe.
 Note
If the cash balance for the selected start date is not
0, the receipts from the last day-end closing for the
cash journal are also listed.
 Note
You cannot export cash journals if receipts contain
ing multiple currencies were posted in the relevant
cash desk during the selected timeframe.
Start export Choose this to start the data export.
Under the settings for the new export is an overview table displaying all processes for the receipt export. By
choosing the Download button in the relevant column, you can download the receipt export.
History
Field Description
Description Description of the export
Process ID ID of the export process
Execution start Date and time of execution
Execution done Date and time of completion
Execution state Current status of the export process
Execution result Result of the export process

Field Description
Status message Messages and notifications of the export process
Download Allows you to download the corresponding receipt export
Cancel job Allows you to cancel the export process
5.4.7 Vouchers
Vouchers represent a payment method in SAP Customer Checkout. Customers can redeem their vouchers
completely or partially. Even if a voucher has been redeemed, it does not become void. Customers can top up
vouchers at any time within the validity period.
On the Vouchers tile you can manage the vouchers used in SAP Customer Checkout. You can track your
vouchers and edit, create, store, search for, or block a voucher.
The following sections are available on the Vouchers tile:
"Vouchers" Tile
Option Description
Vouchers Displays all vouchers that have been created in SAP Cus
tomer Checkout or directly in SAP Customer Checkout man
ager.
Voucher transactions Provides details about voucher redemptions and topups.
What information is available for vouchers?
Vouchers
Field Description
Voucher ID Unique voucher number
Origin Where the voucher was created, either SAP Customer

Checkout or directly in SAP Customer Checkout manager
Issued at Date and time voucher was created
Valid To Final date the voucher can be redeemed
Status Indicates whether a voucher has already been redeemed.

● Not redeemed
● In use
● Redeemed

Field Description
External transaction ID Receipt ID created by the system when a voucher is sold in

Created By User name who created the voucher, either in SAP Customer
Blocked Indicates whether the voucher was set to Blocked. Blocked

vouchers cannot be redeemed.
Enable voucher topups Allows vouchers to be topped up in SAP Customer Checkout
Current amount Amount of money that can be redeemed with the voucher
Original amount Amount of money originally assigned to the voucher when it

was created
Currency Currency type of the voucher
Sales person ID ID of sales person who created the voucher in SAP Customer
Checkout
Cashier ID ID of the cashier who created the voucher in SAP Customer

Checkout
Voucher Article ID Article ID that is assigned to the voucher in SAP Customer

Checkout from the ERP system
Description Description of the voucher sent from SAP Customer Check

out
Voucher transactions
Field Description
External item ID ID created for each posting
Origin Where the voucher was created, either SAP Customer

Posted on Posting date
External Transaction ID Receipt ID created by the system when a voucher transac

tion is made
ERP transaction ID Document ID in your ERP system
External System ID POS system ID of the SAP Customer Checkout application

that was used to create the voucher transaction

Field Description
Customer ID If a customer was added to the receipt, the customer ID

from SAP Customer Checkout is sent along with the posting
Value Value of the posting
5.4.7.1 Creating a Voucher
Context
Vouchers are usually created by cashiers using the SAP Customer Checkout application. The SAP Customer
Checkout manager also lets you create vouchers centrally that can be used at any POS system of SAP
Customer Checkout.
Procedure
1. On the Vouchers tab, choose New

2. Enter the voucher data.
3. To save the voucher, click Save.
4. After you have saved the voucher, you can add transactions to the voucher.
○ Choose Edit.
○ In the Vouchers Transactions section, choose New.
○ Enter the required data and save your changes.
 Note
The current amount is updated accordingly.

5.4.7.2 Editing a Voucher
Context
SAP Customer Checkout manager lets you to manually edit existing vouchers. For example, you can fix a
problem that has occurred with a voucher in SAP Customer Checkout, or extend the validity date of a voucher.
Procedure
1. On the Vouchers tab, choose a Voucher ID.

2. The voucher details screen opens.
3. To edit the voucher, choose Edit.
 Note
You can edit the customer ID, sales person ID, cashier ID, voucher article ID, and description. You can also
block the voucher so that is no longer accepted in SAP Customer Checkout.
4. To add a new transaction, in the Voucher Transactions section choose New, and enter the required data.
5. To change an existing transaction, on the level of the voucher transaction, choose Details and change the
entries
5.4.7.3 Blocking a Voucher
Context
In the Vouchers section of SAP Customer Checkout manager, you can block vouchers so that they are no
longer accepted in SAP Customer Checkout.
Procedure
1. On the Vouchers tab, select the voucher you want to block by choosing the Voucher ID.
2. Select the Blocked checkbox to block the voucher.
The voucher is marked as blocked in the Blocked column and cannot be used in SAP Customer Checkout.

5.4.7.4 Migrate Vouchers from a File-based Voucher
Module
Context
If you want to switch to the voucher management system in SAP Customer Checkout manager, instead of
using a database file, you can migrate your legacy vouchers.
Procedure
1. Choose an SAP Customer Checkout installation that has the complete set of voucher data.
2. Open the Configuration screen and choose the Integration tab.
3. Open the Voucher subtab and change the voucher module to SAP Customer Checkout manager voucher
module.
4. Open the SAP Customer Checkout manager subtab and in the Webservice endpoint section, enter the
corresponding fields.
5. Open the Synchronization tab and do a voucher synchronization.
 Note
The voucher data is transferred to SAP Customer Checkout manager.
6. To be able to use all vouchers created in SAP Customer Checkout manager, schedule a voucher
synchronization for all of your SAP Customer Checkout installations.
5.4.8 Receipts
In the Receipts tile, you can see an overview and detailed information about receipts that are posted from your
SAP Customer Checkout applications.
When a receipt is posted in SAP Customer Checkout, an entry with all receipt details is created in SAP
Customer Checkout manager. If you have several SAP Customer Checkout applications running, you all
receipts are stored in SAP Customer Checkout manager. You can keep track of receipts, view receipts, sales
items, tax items, and payment item details. You can search for receipts, sort, and filter them.
 Note
You cannot edit receipts in this tile.

The Receipts tile contains the following options:
● Shown receipts: Receipts transferred from SAP Customer Checkout to the SAP ERP system
● Strikethrough receipts: Canceled receipts or receipts not posted from SAP Customer Checkout to the SAP
ERP system
Select an entry to see additional tabs with detailed information about the selected receipt. The displayed tabs
depend on the type of receipt that you have selected.
In addition to the receipt data, customer details assigned to the receipt are also transmitted to SAP Customer
Checkout manager.
The following details are available in the Receipts tile for each receipt entry:
Receipt Options
Field Description
POS system ID POS system ID used in the SAP Customer Checkout applica
tion, where the receipt was created
Rec. ID Receipt ID sent from SAP Customer Checkout
Day-End Closing ID POS system ID of the POS system that has posted the cash
transaction or invoice payment.
Customer Customer ID of the customer assigned to the cash transac

tion or invoice payment
Type Type of receipt
Possible receipt types are:
● Direct sale
● Reserve invoice
● Cash-in
● Cash-out
● Pay-in
● Pay-out
● Cash balancing
● Carryover of remaining amount
● Carryover of remaining amount to follow-on day-end
closing
Business transaction date Date when the receipt was created
Payment gross amount Payment gross amount of the receipt posted in SAP Cus
tomer Checkout
When you select a Direct Sale or Reserve Invoice receipt entry, the Receipt Detail view opens with the following
information about the selected receipt:
● Details
● Sales items

● Tax items
● Payment items
● Purchase orders (optional: only if receipt was posted in table management mode)
● Coupons
● Dispatch status
● Additional fields
When you select a Cash-In, Cash-Out, Pay-In, Pay-Out, Cash Balancing, Carryover or remaining amount, or
Carryover of remaining amount to follow-on Day-End Closing receipt entry, the Receipt Detail view opens with
the following information about the selected receipt:
● Details
● Additional fields
 Note
Duplicates of receipts are rejected and not stored in SAP Customer Checkout manager.
Receipts are not updated in SAP Customer Checkout manager. If you change a receipt in SAP Customer
Checkout that has already been posted in SAP Customer Checkout manager, the change is not posted to
SAP Customer Checkout manager because it rejects duplicate receipts.
Parked receipts in SAP Customer Checkout are not transferred to SAP Customer Checkout manager.
When a strikethrough receipt is selected, the details of the receipt are still shown, even though the receipt is
marked as Cancelled.
You also have the option to export a document as a PDF file.
5.4.8.1 Details
This section of the Receipts tile provides general data, customer data, administrative data, and amount details
about the selected receipt.
Header Data
Field Description
POS system ID POS system ID used throughout the SAP Customer Check
out application from which the receipt was created
Rec. ID Receipt ID sent from SAP Customer Checkout
Day-End Closing ID POS system ID of the POS system that has posted the cash
transaction or invoice payment.

Field Description
Type Type of receipt
Possible receipt types are:
● Direct Sale
● Reserve Invoice
● Cash-in
● Cash-out
● Pay-in
● Pay-out
● Cash balancing
● Carryover of remaining amount
● Carryover of remaining amount to follow-on day-end
closing
Business transaction date Date when the receipt was created
Table ID Displays the table number or name, when SAP Customer

Checkout is operated in table service mode.
Customer count Shows the number of customers belonging to the respective

receipt, when SAP Customer Checkout is operated in table
service mode.
Cashier Name of Cashier assigned to the cash transaction or invoice

payment
Sales person Name of sales person assigned to the cash transaction or in
voice payment
Discount Purpose Code Discount Purpose Code sent from the SAP ERP system
Price List ID ID of the price list in the SAP ERP system
Comment Comment assigned to the receipt in SAP Customer Check

out
Rounding used Shows whether a currency rounding was used in SAP Cus
tomer Checkout.
Rounding level The smallest possible unit to which the currency can be
rounded.
 Example
If each rounded result should be a multiple of 0.05,
maintain the value 0.05.

Field Description
Rounding amount Determines on which level the rounding rules are used in
● Not used: No rounding rule is used.

● Header: The rounding rule is used on the total amount
of the receipt.
● Sales item: The rounding rule is used on each sales item
Status Status of the receipt
Possible receipt statuses are:
● Posted
● Cancelled
● Open
● Parked
POS mode Shows the UI mode in which the receipt was posted in SAP
Customer Checkout.
Possible POS modes:
● Retail
● Quick Service
● Table Service
Customer ID ID of customer assigned to the payment transaction or in

voice payment
Name Name of the customer assigned to the cash transaction or

invoice payment
Type Category of the customer assigned to the cash transaction

or invoice payment
Address Address of the customer assigned to the cash transaction or

invoice payment

Field Description
Petty cash ID Account for cash payments in the currency maintained. If

the cash drawer is configured as an account in the SAP ERP
system, the cash drawer account number is maintained
here.
 Note
This field is only shown when the following types of re
ceipt entries are selected: Cash-In, Cash-Out, Pay-In,
Pay-Out, Cash Balancing, Carryover or remaining
amount, or Carryover of remaining amount to follow-on
Day-End Closing receipt.
Expense amount Amount of payment transaction posted from SAP Customer

Checkout to SAP Customer Checkout manager
 Note
This field is only shown when the following types of re
ceipt entries are selected: Cash-In, Cash-Out, Pay-In,
Pay-Out, Cash Balancing, Carryover or remaining
amount, or Carryover of remaining amount to follow-on
Day-End Closing receipt.
Created At Date and time the receipt was created in SAP Customer
Checkout manager
Created By Username of the user who created the receipt in the SAP
Customer Checkout manager
Changed At Date and time when the receipt was modified in the SAP
Changed By Username of the user who modified the receipt in the SAP
Origin Created At Date and time when the receipt was originally created in SAP
Customer Checkout
Origin Created By Username of the user who originally created the receipt in
Origin Modified At Date and time when the receipt was originally modified in
Origin Modified By Username of the user who originally modified the receipt in

Field Description
Total gross amount Total gross amount of the receipt posted in SAP Customer
Checkout
Cash discount amount Discount amount of the receipt posted in SAP Customer
Checkout
Discount percentage Discount percentage of the receipt posted in SAP Customer

Checkout
Payment gross amount Payment gross amount of the receipt posted in SAP Cus
tomer Checkout
Payment Tax Amount Payment tax amount of the receipt posted in SAP Customer
Checkout
5.4.8.2 Sales Items
This section of the Receipts tile provides information about the sales items assigned to the selected receipt.
 Note
Strikethrough sales items are the ones that are cancelled and were not posted from SAP Customer
Checkout to the SAP ERP system.
Sales Items
Field Description
Number Sales item position identifier
Article ID Article sent from the SAP ERP system
Type Type of sales item
The following article types are possible:
● Sales set
● Standard article
● Voucher
● Special sales item
● Payment for invoice
● Payment for down payment
● Paid down payment
● Credit memo
Description Description of the sales item

Field Description
Quantity Quantity of the sales item
Delivered quantity Determines the delivery quantity of a reserve invoice in SAP

Customer Checkout.
 Note
Only relevant for Reserve Invoice.
UoM Unit of measure used for the sales item
Tax Code Tax code of the sales item sent from the SAP ERP system
Unit Gross Amount Unit gross amount of the sales item sent from the SAP ERP
system
Currency Currency of the sales item
Cash discount amount Discount amount assigned to the sales item in SAP Cus
tomer Checkout
Discount in % Discount in percentage assigned to the sales item in SAP

Customer Checkout
Payment net amount Payment net amount of the sales item sent from SAP Cus
tomer Checkout
Payment Tax Amount Payment tax amount of the sales item sent from SAP Cus
tomer Checkout
Payment gross amount Payment gross amount of the sales item sent from SAP Cus
tomer Checkout
You can view detailed information about the sales item when you select its receipt.
Sales Item Detailed Information
Field Description
Article ID Article sent from the SAP ERP system
Type Type of sales item sent from the SAP ERP system
Description Description of the sales item
Quantity Quantity of the sales item
UoM Unit of measure used for the sales item
Tax Code Tax code of the sales item sent from the SAP ERP system

Field Description
Unit Gross Amount Unit gross amount of the sales item sent from the SAP ERP
system
Discount Purpose Code Discount Purpose Code sent from the SAP ERP system
Customer Return Reason Code Return Reason Code sent from the SAP ERP system
Price List ID ID of the price list in the SAP ERP system
Note Note assigned to the sales item in SAP Customer Checkout
Warehouse Warehouse ID sent from the SAP ERP system
General Ledger Account GL Account assigned to the sales item sent from the SAP
ERP system
Batch Number Batch Number of the sales item sent from the SAP ERP sys
tem
Serial Number Serial Number of the sales item sent from the SAP ERP sys
tem
Discountable Shows whether a sales item is discountable in the SAP ERP

system.
Rounding amount Determines on which level the rounding rules are used in
Rounding levels are as follows:
● Not used: No rounding rule is used.

● Header: The rounding rule is used on the total amount
of the receipt.
● Sales item: The rounding rule is used on each sales item
Base document type Indicates whether this is a "ticket" document/receipt type

from the SAP Event Ticketing system
Base document ID Ticket ID from SAP Event Ticketing system
Base series Description sent by the SAP Event Ticketing system
Voucher ID Voucher ID sent from the SAP ERP system
Status Status of the sales item in the receipt in SAP Customer

Checkout.
● Confirmed
● Cancelled

Field Description
Created At Date and time when the sales item was assigned to the re
ceipt in SAP Customer Checkout manager
Created By Username of the user who assigned the sales item to the re
Changed At Date and time when the sales item was modified in the re
Changed By Username of the user who modified the sales item in the re
Origin Created At Date and time when the sales item was originally assigned to
the receipt in SAP Customer Checkout
Origin Created By Username of the user who originally assigned the sales item
to the receipt in SAP Customer Checkout
Origin Modified At Date and time when the sales item was originally modified in
the receipt in SAP Customer Checkout
Origin Modified By Username of the user who originally modified the sales item
in the receipt in SAP Customer Checkout
Payment gross amount Payment gross amount of the sales item sent from SAP Cus
tomer Checkout
Payment Tax Amount Payment tax amount of the sales item sent from SAP Cus
tomer Checkout
Payment net amount Payment net amount of the sales item sent from SAP Cus
tomer Checkout
Cash discount amount Discount amount assigned to the sales item in SAP Cus
tomer Checkout
Discount Percentage Discount in percentage assigned to the sales item in SAP

Customer Checkout
You can view further information about coupons that are used for the respective sales items within the receipt.
Sales Item Coupon Information
Field Description
Coupon ID Unique identifier of the coupon that was set while creating
the coupon.
Instance ID Unique ID number that is generated as the coupon ID and is

to be used for the respective coupon.

5.4.8.3 Tax Items
This section of the Receipts tile provides information about tax items assigned to the selected receipt.
Tax Items
Field Description
Number Tax item position identifier
Tax Rate Type Code Tax rate type code of the sales item sent from the SAP ERP
system
Business Transaction Amount Business transaction amount used for the tax rate type code
Currency Currency used for the tax rate type code
5.4.8.4 Payment Items
This section of the Receipts tile provides information about the payment items assigned to the selected receipt.
 Note
Strikethrough payment items are ones that are canceled and were not posted from SAP Customer
Checkout to the SAP ERP system (for example, canceled payment items).
Payment Items
Field Description
Number Payment item position identifier
Payment method Payment method
Credit Card Type Credit card type used for the receipt in SAP Customer
Checkout
Amount in Payment Currency Amount in payment currency used for the receipt in SAP
Customer Checkout
Tip amount Tip amount transferred with the document. Tip amounts are
transferred in tip tracing mode only.
Point exchange rate Exchange rate used for the receipt in SAP Customer Check
out
Amount (in EUR) Amount (in EUR) of the receipt

5.4.8.5 Orders
This section of the Receipts tile provides information about order transactions assigned to the selected receipt.
This information is only displayed if the selected receipt has been posted in table management mode in SAP
Customer Checkout.
5.4.8.6 Coupons
This section of the Receipts tile provides information about used coupons (coupons for the loyalty API and
coupons for the Quick Service mode) in the respective receipt.
Coupons
Field Description
Coupon ID Unique identifier that was set while creating the coupon.
 Note
Click the coupon ID to open the respective coupon.
Instance ID Unique ID number that is generated as the coupon ID and is

to be used for the respective coupon.
 Note
This tab is only relevant when using a coupon for Quick
Service mode in SAP Customer Checkout.
5.4.8.7 Dispatch Status
This section of the Receipts tile contains information about the dispatch status of the receipt.
 Note
Receipts are automatically sent to each target system that has an active dispatcher entry. If the transfer
fails, the receipt can be transferred again manually.
The receipt can be transferred again to a single target system. Using the Repost all button, you can transfer the
receipt again to all target systems that have status "Failed".
 Note
Receipts that have been transferred to SAP Customer Checkout manager in the past before an active
dispatcher entry existed cannot be transferred retroactively.

Dispatch Status
Field Description
Name Name of the target system to which the receipt is transfer

red
Changed At Date and time when the receipt was last changed
Status Dispatch status:
Success
The transfer was successful.
Failed
The transfer to the target system failed.
 Note
If a receipt already transferred successfully is reposted,
additional transfer attempts will fail because the receipt
already exists in the target system.
Idle
The receipt is scheduled for transfer.
In Progress
The transfer process is being executed.
Re-Post The receipt is transferred to the target system again.
Dispatch Status Details
Field Description
External ID ID of the transferred receipt
Message Status message of the receiving target system
Created At Date and time of the transmission
Status The dispatch status
5.4.8.8 Additional Fields
This section of the Receipts tile provides information about fields that have been added to a receipt. In SAP
Customer Checkout, it is possible to add additional information to a range of entities (for example Receipt).
These additional fields are usually added using a plug-in. When additional fields have been added to a receipt in
SAP Customer Checkout, you can view them from the Additional Fields tab.

Additional Fields
Field Description
Name Name of the additional field used for the receipt in SAP Cus
tomer Checkout
Value Value of the additional field used for the receipt in SAP Cus
tomer Checkout
5.4.8.9 Export Receipts as PDF
You can export each receipt to SAP Customer Checkout manager as a PDF file.
Context
Procedure
1. Choose the Receipts tile.

2. Select the receipt that you want to export to PDF.
3. In the lower-right corner of the screen, select Export to PDF.
A PDF file containing the selected document is downloaded.
5.4.9 Software
The Software tile lets you centrally manage software versions and installations of various SAP Customer
Checkout applications. You can keep track of your installations, upload or download installation files, delete or
search for SAP Customer Checkout installations, assign organizational units to software versions, and see
additional information about SAP Customer Checkout applications.
Some software versions are marked with a flag icon to show that there is a file attached.
● Flagged (Flag icon): shows software versions that have a file attached
When you select one entry for an SAP Customer Checkout software version entry, you can see tabs with more
information about the software version, organizational unit assignments, installations, and outstanding
installations.
On the Details tab, you can find detailed information about the software version, such as the build number,
version number, or file size.

Details Tab
Field Description
Name Name of the software
Version Version number of the software
Build Number Date and time when the software was created
Internal Version Internal version number of the software
File Size File size of the software
Downloads Number of software downloads
Installations Number of software installations
Created By Username of the user who created the software installation
Created At Date and time when the software installation was created
Modified By Username of the user who modified the software installation
Modified At Date and time when the software installation was modified
The Org. unit assignments tab shows all POS systems and POS groups to which the respective software
version is assigned. You can also manually add an organizational unit to the respective software version so that
this software version to be updated on the POS system and/ or POS group.
Org. unit assignments Tab
Field Description
Organizational unit ID of the POS system or POS group
The Installations tab shows information about the SAP Customer Checkout applications that are running with
the selected software version. This tab points out only single POS systems, and not higher POS groups.
 Note
The information shown is sent directly from the POS system when the respective POS system is
communicating with the SAP Customer Checkout manager.
The POS system is only listed in the Installations tab when the respective software version is installed in this
POS system.
The Outstanding Installations tab shows the SAP Customer Checkout applications that are already assigned
to a software version, but are not yet updated to this software version. For example, this can happen when the
POS system has not yet started.

 Note
To use central update management in your SAP Customer Checkout applications, you have to enable
central software management in the Configuration settings of your POS system, and schedule an update
job.
You have to restart your SAP Customer Checkout application to update the POS system. The POS system
is shown in the Outstanding Installations tab until the software version is updated. After the POS system
has successfully been updated, this POS system will be shown in the Installations tab.
Installations and Outstanding Installations Tab
Field Description
POS system POS system ID used by the software installation
Organization Organizational structure used by the software installation
Location Location used by the software installation
 Note
This information is sent from the SAP Customer Check
out application to the SAP Customer Checkout man
ager.
Last Active Date and time when the software installation was last active
 Note
This information is sent from the SAP Customer Check
out application to the SAP Customer Checkout man
ager.
 Example
Assuming that you have manually created a software version entry for SAP Customer Checkout 2.0
Feature Pack 02, and are using central software management. Your SAP Customer Checkout applications
are still running on version SAP Customer Checkout 2.0 Feature Pack 01, and you want to update them now
to the newer version (SAP Customer Checkout 2.0 Feature Pack 02). In the Org. unit assignments tab,
manually add the respective PoS application. The software version will be updated to the respective SAP
Customer Checkout application depending on the scheduled check for software updates. As long as the
SAP Customer Checkout application has not been updated, there will be an entry in the Outstanding
installations tab for the respective PoS application. Once the SAP Customer Checkout application has been
updated (to version SAP Customer Checkout 2.0 FP02), you will see an entry in the Installations tab for the
respective POS system. The Installations tab lets you verify which SAP Customer Checkout applications are
in fact running with the respective software version.

5.4.9.1 Uploading New Software
Context
In the Software tile, you can upload new software versions of SAP Customer Checkout.
 Note
To upload a new SAP Customer Checkout software version into SAP Customer Checkout manager, you
need to prepare the data in a zip file.
 Recommendation
1. Open the Command Prompt and navigate to the location where your SAP Customer Checkout .exe
file is located.
2. Extract the CustomerCheckout subfolder from the SAP Customer Checkout zip file. To extract the
file, enter the following: SapCustomerCheckout_2_0.exe /
X="<PathnameForExtractedFolder>"
 Note
If you are working with WinRAR, unzip the .exe file of the software version that you want to
upload into the SAP Customer Checkout manager.
3. Choose the CustomerCheckout subfolder and select all files to create a zip file.
Procedure
1. In the Software tile in the SAP Customer Checkout manager, select Add .
2. Attach the zip file that you prepared.
3. To save your changes, select Save . The new software version is displayed in the overview.
5.4.9.2 Downloading Software File
Context
In the Software tile, you can download a software version as zip file.

 Note
This option is only possible for software versions that have a file attached and are marked as flagged in the
overview.
Procedure
1. In the Software tile of the SAP Customer Checkout manager, select the software version you want to
download.
2. Choose Download. The zip file with the selected SAP Customer Checkout software version is downloaded.
5.4.9.3 Detaching Software File
You can detach the updated file from a software version in the Software tile.
Context
 Note
Use this option if you want to free-up storage and for software versions that are no longer used in any SAP
Customer Checkout application.
Procedure
1. In the Software tile, select the software version from which you want to detach the file.
2. Choose Detach File, and select OK. The attached file is removed from the software version.
 Note
When you have detached a software file from a software version, this software version cannot be
assigned to any organizational unit anymore.

5.4.9.4 Deleting Software Version
Context
In the Software tile, you can delete software versions from the SAP Customer Checkout manager.
 Note
This option is only supported for software versions that are no longer used in any SAP Customer Checkout
application.
If you want to delete a software version to free-up storage, you can also detach a software file.
Procedure
1. In the Software tile of the SAP Customer Checkout manager, select the software version you want to delete.
2. Choose Delete and select OK. The software version is deleted from the SAP Customer Checkout manager.
5.4.9.5 Assigning Organizational Units to Software Version
Context
In the Software tile, you can manually assign organizational units (POS systems and POS groups) to a software
version. Once the software version is assigned to an organizational unit or POS group, and central software
management is enabled in the Configuration settings of SAP Customer Checkout (see the SAP Customer
Checkout Configuration Guide), the respective organizational unit will be updated to this software version with
the next check for updates.
 Note
Only software versions that have a file attached can be assigned to an organizational unit or POS group.
Procedure
1. In the Software tile, select the software version to which you want to assign an organizational unit.

2. Choose the Org. unit assignments tab, and select the Add icon .
3. Enter a POS group or POS system.
 Note
When assigning a POS group to a software version, you can Remove sub nodes from all software. If you
select this option, all organizational units that are below the selected POS group will be removed.
Disable this option if you want the software version to also be assigned to all related organizational
units (or the respective POS group).
 Example
○ root
○ Merchandising Shop
○ POS1
○ POS2
Let's say that you have a software version, SAP Customer Checkout 2.0 Feature Pack 01, and root
and POS1 are assigned to this software version. Now you create a new software version, SAP
Customer Checkout 2.0 Feature Pack 02, assign Merchandising Shop to this software version and
enable the option Remove assigned sub nodes. As a result of this, POS1 that is assigned to software
version SAP Customer Checkout 2.0 Feature Pack 01 will be removed. All organizational units that
are assigned to the Merchandising Shop will get the software version SAP Customer Checkout 2.0
Feature Pack 02.
 Note
If you want the respective software version to be assigned to all your organizational units, enter root.
 Note
SAP Customer Checkout does not allow you to assign an organizational unit to two software versions at
the same time . When you assign the organizational unit to a second software version, a dialog window
opens asking you to confirm that you want to force the assignment of the respective organizational
unit.
 Caution
Despite the restriction, in certain cases an organizational unit (POS system) could be assigned to
two software versions at the same time. For example, a POS system can be explicitly assigned to a
software version (SAP Customer Checkout 2.0 Feature Pack 01), and the higher POS group of this
POS system can be assigned to another software version (SAP Customer Checkout 2.0 Feature
Pack 02). In this case, the most specific assignment (SAP Customer Checkout 2.0 Feature Pack 01)
applies.

Examples:
1. Assuming that you have the following organizational structure: root → Merchandise Shop →
POS1
Your software versions are assigned as follows:
○ SAP Customer Checkout 2.0 Feature Pack 01: POS1
○ SAP Customer Checkout 2.0 Feature Pack 02: Merchandise Shop
○ SAP Customer Checkout 2.0 Feature Pack 03: root
In this case, the software version SAP Customer Checkout 2.0 Feature Pack 01 will be
applied to POS1.
2. Assuming that you have the following organizational structure: root → Merchandise Shop →
POS2:
Your software versions are assigned as follows:
○ SAP Customer Checkout 2.0 Feature Pack 02: Merchandise Shop
○ SAP Customer Checkout 2.0 Feature Pack 03: root
In this case, the software version SAP Customer Checkout 2.0 Feature Pack 02 will be
applied to POS2, as this version is the most specific assigned software version, and the
POS system has no direct assignment.
When you assign an organizational unit to a software version, the following rules apply:
○ Software versions can be assigned to the root element of the organizational structure, a POS group in
the organizational structure, or a single or multiple POS systems.
○ If you have multiple software versions running in your organization, the POS systems might also be
assigned to multiple software versions. For example, a POS system might be assigned explicitly to one
software version and also as part of the root element or POS group to another software version.
○ Which software version is applied to the POS system depends on the specificity of the different
assignments.
The following example shows the interaction between Org. unit assignments, Installations, and
Outstanding installations:
Example:
You have a POS system, POS1, and manually assign software version SAP Customer Checkout 2.0 Feature
Pack 01 to this POS system. After you have updated POS1 to this software version, the following
information is shown in the Software tile:
Details
Software version Org. unit assignments Installations Outstanding installations
SAP Customer Checkout POS1 POS1 -

2.0 Feature Pack 01

A new POS system, POS2, has been installed within your organization. You also have a new software
version SAP Customer Checkout 2.0 Feature Pack 02, and manually assign root to this software version.
The following information will be shown in the Software tile:
Details
SAP Customer Checkout root - POS2

2.0 Feature Pack 02

2.0 Feature Pack 01
POS1 will not be shown in the Outstanding installations for software version SAP Customer Checkout 2.0
Feature Pack 02, as this POS system is directly assigned to software version SAP Customer Checkout 2.0
Feature Pack 01.
After POS2 has been successfully updated, the following information will be shown in the Software tile:
Details
SAP Customer Checkout root POS2 -

2.0 Feature Pack 02

2.0 Feature Pack 01
5.4.10 Sales Reports
The Sales reports tile lets you generate sales reports for a specific time period or POS system that were sent
from various SAP Customer Checkout applications in your organization.
 Caution
Sales reports only support the use of a single currency. If SAP Customer Checkout Manager is connected
to an SAP Customer Checkout application that uses multiple currencies, sales reports cannot be used.
Select the Sales Reports tile to view sales reports or download sales report files as a Microsoft Excel file. You
can generate the following sales reports:
 Note
When displaying payment methods in sales reports, SAP Customer Checkout differentiates various types
of credit card payments. The code for credit card types stored in the SAP Customer Checkout applications
is used for breaking down the various types of credit card payments in sales reports.

 Note
If sales reports are not filtered by POS groups or POS systems, the report contains information about all of
the POS systems.
If sales reports are filtered by <root>, the report contains information about all POS systems that are
directly below the <root>. POS groups that are directly below the <root> are ignored, however.
● Cashing-up: generates sales reports from the CASHING-UP screen of your SAP Customer Checkout
applications, which shows the total cash status or number of receipts from the various SAP Customer
Checkout applications. This Cashing-up sales report includes additional sales reports such as Revenue per
cashier, revenue per article group and article, revenue per article, cash balance per POS, revenue per
payment method and POS, and discounts.
● Revenue per article: generates sales reports for revenue per article. For example, you can track the best
and worst seller articles sold in your SAP Customer Checkout applications.
● Revenue per cashier: generates sales reports for revenue per cashier. For example, you can see which of
the cashiers in your organization makes the most revenue.
● Revenue per organization: generates sales reports aggregated by POS group. For example, you have
several POS systems running in your stores and you want to track which of your organizations is making
the most revenue.
● Revenue per POS group and article: generates sales reports aggregated by POS group and article. For
example, you have several POS groups and you want to track which of them is making the most revenue
with which article.
● Cash balance per POS system: shows the cash balance per SAP Customer Checkout application, grouped
by the payment method (for example, card payment, cash, payment on credit, and voucher)
● Revenue per POS system: generates sales reports for revenue per SAP Customer Checkout application.
For example, you can track which of your POS system applications is generating the most revenue and
posting the most receipts.
● Revenue per payment method and organization: generates sales reports for revenue per payment
method and POS group.
● Revenue per payment method and POS: generates sales reports for revenue per payment method and
SAP Customer Checkout application.
● Revenue per article group and article: creates sales reports for revenue per article group and article.
● Payment on credit per customer: Generates sales reports for payments on credit per customer.
● Discounts: generates sales reports for discounts aggregated by the discount reason code and further
information. For example, you can check the number of discounted receipts posted in SAP Customer
Checkout, or the discount type selected in a receipt. Furthermore, you can track the manual price change
for each sales item or the price change within a sales set, and how much of the total revenue is affected by
the used discounts in a receipt.
● Cancelations: Creates sales reports for cancelation transactions in SAP Customer Checkout, grouped by
organization unit and cashier.
● Returns: generates sales reports for returns in SAP Customer Checkout, grouped by organization unit and
cashier.
● All-In-One: creates a sales report that includes all of the other sales reports.
The information displayed in the Sales Reports tile will vary depending on the sales report option you select.

 Note
With SAP Customer Checkout 2.0 Feature Pack 01, you can download sales reports files as Microsoft Excel
files.
However, the Sales Reports tile only displays the following options:
● Revenue per article

● Revenue per cashier
● Revenue per organization
● Revenue per POS
● Revenue per payment method and organization
● Revenue per payment method and POS
● Revenue per article group and article
● Cancelations
● Returns
5.4.10.1 Generating Sales Reports
Procedure
1. In the Sales Reports tile, choose the option for which you want to generate a sales report.
2. Enter or select the Period Start and Period End for the sales report.
3. Select sorting type, POS group, and PoS system for the sales report.
4. Choose Download , or Go, to start generating the sales report.
 Note
For SAP Customer Checkout 2.0 Feature Pack 01, only a limited set of sales reports options can be
generated.
5. A Microsoft Excel file with the selected sales report is downloaded (or shown in the UI).
5.4.11 Tables
On the Tables tile, you can see all transactions of all open (not yet paid) tables of all of your SAP Customer
Checkout applications running in table management mode. You can also use other transactions for open
tables.
For each table transaction performed in SAP Customer Checkout, an entry is created in SAP Customer
Checkout manager with all of the details on the table. If you are using multiple tables in different SAP Customer
Checkout applications, you can view them all on the Tables tile. You can edit, search for, filter, or sort tables.

The following details are available on the Tables tile for each time table:
Field Description
Table ID Number of the respective table
Last table index Technical counter for support purposes
Owner Name of user who created the table in SAP Customer

Checkout
Owner receipt count Displays the number of receipts associated with a given ta
ble
Owner receipt amount Displays the total amount for the receipt associated with a
given table
Open receipt count Displays the number of open receipts associated with a
given table
Open receipt amount Displays the open amount for a receipt remaining to be paid
When you select an entry, you can see more information about the respective table:
You can view general data and an administrative date for the table under Details. Under Receipts you can find all
open receipts associated with the table. In addition, the Move tables, Change owner, and Cancel receipt options
are available here.
5.4.11.1 Editing Tables
In SAP Customer Checkout manager you can edit open (= not yet paid) receipts that are assigned to a table.
Context
You have the following options for open receipts:
● Move tables
● Change owner
● Cancel receipt

:
Procedure
1. Choose the Tables tile.

2. Select the table you want to edit.
3. Go to receipts and choose one of the following options:
Option Description
Move tables Assign a receipt to a different table.
Change owner Assign a receipt to another member of service staff.
Cancel receipt Cancels a receipt.
5.4.12 Articles
In the Articles application, you centrally manage the articles used in SAP Customer Checkout when using SAP
Customer Checkout manager as your back-end system. You can create, edit, and deactivate articles. You can
also create sales sets that are found automatically when posting a sales receipt in SAP Customer Checkout.
You can create the following article types in SAP Customer Checkout manager:
● Standard article: A standard material article with general information and to which a tax code is assigned.
● Generic article: A placeholder material article that groups several standard articles.
 Note
Example: In the food and beverage area, you want to create a generic article beverage. In this context,
beer, juice, soda, and water are all clustered as components in the generic article beverage.
A generic article can consist of standard articles.
● Sales set: A group of standard and/or generic articles that is sold as a separate sales item and contains
general information. A sales set has no tax code assigned.
 Note
Example: In the food and beverage area, you want to create a sales set consisting of a burger and a
drink. In this context, you could offer this sales set to a lower price than the single standard articles.
When using Quick Service mode, the sales set is automatically found and applied to the sales receipt.
To see more information about the article, select an article in the overview on the left side of the screen. The
information changes depending on the article type that you selected.

Articles
Option Description
Details Displays all necessary information about the selected article.
Taxes Displays all information about the tax for the selected article.
Prices Shows the pricelist assignment of the selected article to the

different pricelists.
Discounts Displays the discounts of the selected article that were en
tered via the API interface.
If you have entered a discount for this article via the API in
terface, the discount is adjusted automatically when you se
lect the relevant article in SAP Customer Checkout.
The direct discount is applied to each article of the sales

item.
 Example
In SAP Customer Checkout, you select the following ar
ticles:
● Article price: 20 USD

● Direct discount: 5 USD
● Article price after discount: 15 USD
You now increase the article number to 3.
● Direct discount: 15 USD

● Document price after discount: 45 USD
 Note
For more information, see the SAP Customer Checkout
Manager API Guide.
Warehouses Displays all warehouses and their available inventory, to

which the article is assigned.
 Note
For more information about this, see Assigning or Re
moving a Warehouse to or from an Article [page 142].

Option Description
Components Shows which articles (standard or generic articles) are as

signed to the respective article as a component.
 Note
This tab is only shown for the article types Generic
article and Sales set.
Images Enables you to upload article images that can be used on the
sales screen or for quick selection.
You can see the following information about the selected article on the Details tab:
Details
Field Description
ID Unique article ID. This ID can only be entered when creating

an article. You cannot edit it after the article has been cre
ated.
Article type The following article types are available:
● Generic article
● Sales set
Article group Shows the assignment of the article to the relevant article
group.
Description Description of the article
Short text Articles can have a description as well as a short text. If a

short text has been entered for an article, this text is dis
played on the sales screen in SAP Customer Checkout and
printed on receipts instead of the article description.
Bar code Bar code of the article; used for scanning in SAP Customer
Checkout
Unit of measure Unit of measure of the article
Manufacturer Displays to which manufacturer the article belongs
Characteristic Profile Displays the characteristic profile of the article
Force manual price entry If this option is active, the price is not taken from the price
list but the cashier has to insert it manually.

Field Description
Discountable If this option is active, cashiers are allowed to give a discount

depending from their authorization rights.
Migrated Indicates whether the article was created in SAP Customer

Checkout manager or whether it was migrated from another
back-end or legacy system.
Status Shows if the article is active or inactive.
Hide set components If this option is active, all set components are hidden and
only the set's header article is displayed in the sales item list.
 Note
If this option is activated when SAP Customer Checkout
is operated in quick service or table management mode,
no set components are displayed. In retail mode, set
components are always displayed.
 Note
If this option is activated and all components of a set
have the same tax code, only the set's header article is
printed on sales receipts.
Refund type If the refund type for a specific article is set to Yes, the article
can be refunded in SAP Customer Checkout, even if the user
(currently logged in to the relevant POS system) is not au
thorized to accept returns.
Created At Date and time when the article was created in SAP Customer
Checkout manager
Created By Username of the user who created the article in SAP Cus
Changed At Date and time when the article was last modified in SAP
Changed By Username of the user who last modified the article in SAP
On the Custom Fields tab you can define any values for articles. SAP Customer Checkout manager features
three types of user-defined fields:
● udfString: for user-defined fields for specifying text values

● udfDouble: for user-defined fields for specifying numeric values
● udfBoolean: for user-defined fields that are displayed as checkboxes

On the Taxes tab, you can see which tax code for which country/region is assigned to the respective article.
 Note
Only the tax code is stored in the articles, the tax rate itself cannot be modified there. If you need to modify
the tax rate, you have to modify it in the POS Configuration tile, in the Tax Codes subtab. Any modifications
you have made will be adapted to the tax code that is assigned to the article.
 Note
This tab is only shown for the article type Standard article.
Tax Rates
Field Description
Country/Region Description of the country/region to which the tax code ap

plies
Tax Code ID of the tax code
Description Description of the tax code
Rate Percentage of the tax code
The Prices tab shows to which price list an article is assigned. Articles can be assigned to different price lists.
Prices
Field Description
Price List Name of the price list. Click the price list to open the respec
tive price list details.
Price list type Shows whether the price list includes net or gross prices.
Price The price for the selected article in this price list.
 Note
You cannot assign a price for Generic articles.
The Components tab shows all components that are included in the selected article. Components can be
standard and/ or generic articles.
Components
Field Description
Component Name of the component (article ID)

Field Description
Article type The following article types are available as components:
● Generic article
 Note
A sales set cannot have another sales set included as a
component.
A generic article cannot have another generic article in

cluded as a component.
Description Description of the article
Min quantity Minimum quantity that has to be included
Max quantity Maximum quantity that has to be included
Quantity type code Type code for the quantity type
The Output Locations tab displays the receipt printer by which articles shall be printed.
Output Locations
Field Description
ID Output location ID
Name Output location name
On the Characteristics tab, you can add certain characteristics for articles. In SAP Customer Checkout, you can
search for articles based on these characteristics.
Characteristics
Field Description
ID ID of the characteristic
Description Name of the characteristic
Characteristics Group ID of the characteristics group
Value Value of the characteristic
On the Images tab, you can add images of articles that you can use for quick selection buttons in the POS
configuration, or on the Sales screen.

5.4.12.1 Creating Articles
You can create new articles in SAP Customer Checkout manager.
Procedure
1. On the Articles tile, click Add.
 Note
The article ID can be generated automatically using the selected sequence number or entered manually. To
enter the ID manually, choose the value "manual" in the selection field for the sequence number.
2. Enter all of the relevant article data, and choose one of the following options to proceed:
○ Save the article. Choosing this option activates the article.

○ Save the article as a draft.
○ Create another article. A new window opens where you can enter data for a new article.
○ Cancel all entries.
3. Once you have selected an option, the article with all details is shown in the overview.
When you create a generic article or sales set, you have to go to the Components tab to add components to
the respective article.
 Caution
Components that are added to a generic article or a sales set have to be assigned to the same price list
as the respective generic article or sales set.
 Note
For sales sets, you have to enter the min quantity and max quantity for the respective components.
Especially when you are using Quick Service mode, the values are relevant for the automatic sales
set search. Only positive integer values can be entered. The default value for the min and max
quantity is 1. If no max quantity is entered, SAP Customer Checkout manager uses the same value
as entered in the min quantity field. If no min quantity is entered, SAP Customer Checkout manager
automatically uses the value "1".
You cannot set the following values as the min quantity and max quantity for sales sets:
○ 0
○ negative values
○ values with decimal places
 Note
If you enter a sales set price of 0, the system calculates the total of all individual components. The price
of the set components is not proportionally adjusted.

5.4.12.2 Edit Articles
You can edit existing articles in the SAP Customer Checkout to maintain or adjust any settings.
Context
 Note
You cannot edit the ID of an article after it has been created.
Procedure
1. Open the Articles tile.

2. Select the article you want to edit and choose Edit.
3. Edit the article data as required.
a. On the Taxes tab, you can add, change, or delete a country/region-specific tax code for the selected
article. You can also assign multiple tax codes to an article. However, this is restricted to one per
country/region. To add a new tax code, choose Assign tax.
b. On the Prices tab, you can add the article to one or more price lists. To add the article to a price list,
choose Add price.
c. On the Components tab, you can add the article to one or more components. To add the article to a
component, choose Add component.
4. To save your changes, choose Save.
5.4.12.3 Deleting or Deactivating Articles
Articles can also be deleted or deactivated in the SAP Customer Checkout manager.
Context
 Note
You can only delete articles that are in draft mode.
Migrated articles can only be deleted as long as they are not Synchronized with SAP Customer Checkout.

Procedure
1. Open the Articles tile.

2. Select the article that you want to delete or deactivate.
3. Choose Delete or Deactivate.
4. Confirm the action with OK.
5.4.12.4 Assigning or Removing a Warehouse to or from an

Article
On the Warehouses tab, you can assign warehouses to specific articles. This allows you to check the stocks
available for individual articles in SAP Customer Checkout and SAP Customer Checkout manager. You can also
remove individual storage locations of articles.
Context
Procedure
1. Open the Articles application.

2. Select the article for which you want to assign all warehouses or remove individual warehouses.
3. Choose one of the two options:
a. Choose Assign All to assign all warehouses to the relevant article and confirm your entry.
 Note
With Version 2.0 Feature Pack 09, it is only possible to assign all warehouses. It is not possible to
assign individual warehouses.
b. Select the warehouse you want to remove from the article and choose Unassign.
4. The system displays the assigned warehouses and their available stock.
 Note
The available stock is calculated from the receipt transactions in SAP Customer Checkout and the
stock transactions in SAP Customer Checkout manager.
 Note
You can adjust the respective stocks for individual articles in the Stock Transactions application. For
more information, see Stock Transactions [page 181].

5.4.12.5 Assigning or Removing an Output Location to or
from an Article
Context
Output locations specify which document printer is used to print a specific article or article group. This only
applies to the document type “order”. Output locations can be directly assigned to articles.
Procedure
1. Open the Article tile.

2. Select the article for which you want to assign or remove the output location.
3. Select the Output Locations tab.
○ To assign an output location, choose Assign at the bottom right corner of the screen and assign the
required output location.
○ To remove an assigned output location, choose the "Remove" icon in the relevant row.
5.4.12.6 Copying Articles
Context
Articles can be copied with all of their attributes, such as article group, tax code, price, output locations, and so
on.
Procedure
1. Open the Article tile.

2. Select the article you want to copy.
3. Choose Copy.
4. Enter the new ID and a new description for the article copy.
5. Choose OK

5.4.12.7 Creating an Article for Integration with SAP Event
Ticketing
To enable ticket sales using SAP Customer Checkout, you have to create corresponding articles in SAP
Customer Checkout manager that are linked to the account in SAP Event Ticketing.
Context
Material numbers for tickets you create in SAP Customer Checkout manager consist of the following
components:
● Material Prefix: The material prefix can be defined in the SAP Customer Checkout configuration (under
"SAP Event Ticketing Integration"). For example, you may use the material prefix ET. For more information,
see the SAP Customer Checkout Configuration Guide.
● Account: Account to which tickets are posted in SAP Event Ticketing. Please find more information about
this in your SAP Event Ticketing system.
 Example
In SAP Event Ticketing you own account 123456 for posting tickets. Your material number in SAP
Customer Checkout manager could look as follows: ET123456.
 Note
If you own several ticket accounts in SAP Event Ticketing, create a corresponding number of material
numbers in SAP Customer Checkout manager.
Procedure
1. Choose Add to add a new article.

2. Enter the respective article ID with the material prefix configured in SAP Customer Checkout.
3. Select a tax rate.
Please ensure that the tax rate for the item in SAP Customer Checkout manager is the same as maintained
in SAP Event Ticketing. An article created for integration with SAP Event Ticketing may have several tax
rates. However, if a different tax rate than in SAP Event Ticketing is maintained in SAP Customer Checkout
manager, this may result in an error message.
4. Select a price list for each article.
Pricing information for tickets is derived from SAP Event Ticketing. You do not need to enter an article price
in SAP Customer Checkout manager.
5. Save your entries.
 Caution
As a fallback option, we recommend creating an additional article in SAP Customer Checkout manager.
This article must possess only the material prefix as material ID; for example: ET. If a ticket is added to

SAP Customer Checkout without an SAP Event Ticketing account, the "ET" article is used as a fallback
option, and the receipt can be posted.
5.4.12.8 Adding Images of Articles
You can upload images of articles in SAP Customer Checkout manager. Such images can be used either to
select the article on the SAP Customer Checkout Sales screen, or for quick selections.
Context
Procedure
1. Open the Articles app and select the article for which you want to upload an image.
2. Select the Images tab.
3. Choose Add to upload a new image for the selected article.
4. Select one of the following options and upload the image:
Type Description
Sales screen Displays the image on the Sales screen (in the preconfig-
ured quick selection button of the Article image compo
nent) in SAP Customer Checkout, when this article is se
lected.
For more information, see Assigning a Component to a

Pushbutton [page 176]
Quick selection Displays the image on the quick selection button in SAP
Customer Checkout manager and SAP Customer Check
out.
5. Save your entries by choosing OK.

5.4.13 Price Lists
In the Price List tile, you can manage the price lists to be used in SAP Customer Checkout, when using the SAP
Customer Checkout manager as your back-end system. You can create and edit price lists, assign articles to
price lists, and assign organizational units and POS groups to price lists.
Select a price list to see the following information:
Price Lists
Option Description
Details Displays all necessary information about the selected price

list.
Items Displays all information about the articles assigned to the

selected price list.
On the "Items" tab you can search for or filter articles.
Org. unit assignments Displays all information about organizational units assigned
to the selected price list.
Roles Displays all roles that are assigned to the price list. Roles can
be assigned to a price list or removed from the price list.
Users Displays all users that are assigned to the price list. Users
can be assigned to a price list or removed from the price list.
The Details tab provides the following information:
Details
Field Description
ID The individual price list ID. You cannot edit the ID after the
price list has been created.
Description Name of the price list.
Currency The currency of the price list.
Amount Type Shows whether the price list includes net or gross prices.
Valid from Date as of which this price list is valid
Valid To Date until which this price list is valid

Field Description
Synchronize (in PoS) Enable or disable the synchronization of the respective price
list in the Org. unit assignments
 Note
If the respective price list is not yet synchronized to the
Org. unit assignments, and the field Synchronize (in PoS)
is enabled, a new entry is created in the Sales tab within
the Price Lists subtab of the SAP Customer Checkout
configuration screen.
Active Specify whether the price list is active or inactive.
Created At Date and time when the price list was created in SAP Cus
Created By Username of the user who created the price list in SAP Cus
Changed At Date and time when the price list was last modified in SAP
Changed By Username of the user who last modified the price list in SAP
In the Items tab, you can add, change, or delete the assignment of articles in the respective price list, and view
the following information:
Items
Field Description
Article ID ID of the assigned article. Click the article ID to open the arti
cle.
Article type The following article types are available:
● Generic article
● Sales set
Description Description of the assigned article

Field Description
Sales set Shows the sales set for which the specific price is valid.
 Note
For example, in the food and beverage area, you can cre
ate a sales set consisting of a burger, fries and ketchup.
Within the sales set the ketchup can be sold to a differ-
ent price than as single standard article.
Price Price of the article in the selected price list
 Note
For generic articles, no price is shown.
UoM (Unit of Measure) Unit of Measure of the assigned article
In the Org. unit assignments tab, you can assign POS systems and POS groups to certain price lists, and set a
price lists as default.
Org. unit assignments
Field Description
Organizational unit ID of the POS system or POS group
Default Allow this price list to be used as the default for the respec
tive POS system.
On the User tab page, you can assign users to specific price lists or unassign users from price lists.
On the Roles tab, you can assign roles to specific price lists or unassign roles from price lists.
5.4.13.1 Creating Price Lists
You can create new price lists in the SAP Customer Checkout manager.
Procedure
1. In the Price Lists tile, click Add.

2. Enter the price list data.

5.4.13.2 Editing Price Lists
You can edit existing price lists in the SAP Customer Checkout maintain or adjust any settings.
Context
 Note
After a price list is created, you cannot change the ID.
Procedure
1. Open the Price Lists tile.

2. Select the price list you want to edit and click Edit.
3. Edit the article data as needed.
5.4.13.3 Assigning Articles to Price Lists
In the SAP Customer Checkout manager, you can assign articles to price lists, edit articles already assigned to
price lists, or delete the assignment of articles to price lists.
Procedure
1. Open the Price Lists tile.

2. Select the price list to which you want to assign an article to and click Edit.
3. Choose the Items tab, and click Add item.
4. Select an article from the list shown and enter a Price.
 Note
When adding a standard or generic article to a price list, you can enter a sales set. In this context, the
respective article is sold to the entered price in combination of this sales set.
 Caution
When adding a sales set to a price list, make sure that all article components included in the sales set
are also assigned to this price list.

5.4.13.4 Assigning Organizational Units to Price Lists
You can assign organizational units (POS systems and POS groups) to price lists, set price lists as default price
lists for certain organizational units, or delete assigned organizational units from price lists.
Procedure
1. Open the Price lists tile.

2. Select the price list to which you want to assign an organizational unit, and choose the Org. unit
assignments tab.
3. Click Create to add an organizational unit to the price list.
4. Enter a POS group or PoS system, and save your changes.
 Note
When assigning a POS group to a price list, you can Remove assigned sub nodes. If you select this
option, all POS systems and POS groups that are below the POS group which is selected for
assignment, will be removed. Disable this option if you want the price list to be also assigned to the
related POS system (or the respective POS group)
 Example
○ root
○ Merchandising Shop
○ POS1
○ POS2
Assuming that you have a price list, PL1, and the following assignments to this price
list: root, POS1. When you now assign the Merchandising Shop to this price list (PL1)
and enable the option Remove assigned sub nodes, the POS system (POS1) that are
below the Merchandising Shop in the organizational hierarchy will be removed from the
list, and only Merchandising Shop, and root will be shown. All directly assigned POS
systems and settings (for example, default price lists) are now removed from the list
and the higher POS group (Merchandising Shop) is applied.
 Note
You can set the price list as the default price list of a POS system.
 Note
When you change the price list assignments for an SAP Customer Checkout application, and then
perform an article synchronization, the SAP Customer Checkout system converts a delta

synchronization into a full synchronization. This is only the case when you add or remove a price list
from the SAP Customer Checkout manager, or when you deactivate the option Synchronize (in
PoS). However, when you activate or deactivate the price lists, or change the default settings for
price lists in the SAP Customer Checkout manager, the SAP Customer Checkout system only
performs a delta synchronization, and not a full synchronization.
 Caution
If you do not set a price list to be used as the default price list in your respective organizational unit
and POS group, the local SAP Customer Checkout application takes the first active entry from the
price list configuration settings, and sets it as the default.
5.4.14 POS Configuration
In the POS Configuration application, you can maintain settings for tax rates, article groups, currencies, code
lists, and quick selections in your point-of-sale applications, when using SAP Customer Checkout manager as
your back-end system.
The following tabs are available in the POS Configuration application:
"POS Configuration” Tile
On This Tab What You Can Do
Tax rates Edit tax rates and tax codes used for sales items and articles
in SAP Customer Checkout
Article groups Manage article groups used in SAP Customer Checkout ap
plications
Currency Set currencies used in SAP Customer Checkout
Quick selection Configure the quick selection buttons used in your SAP Cus
tomer Checkout applications In addition, you can configure
the user interface of your SAP Customer Checkout applica
tion flexibly.
Code Lists Manage descriptions for codes used in SAP Customer

Checkout
Payment card categories Edit used payment card categories (for example, credit
cards) in your SAP Customer Checkout applications.
Characteristic Profiles Create and edit characteristic profiles for characteristics and
items that you can use when searching for articles in SAP
Customer Checkout.

On This Tab What You Can Do
Characteristics Create and edit characteristics for articles that you can use
when searching for articles in SAP Customer Checkout.
5.4.14.1 Tax Rates
In SAP Customer Checkout manager, you can define and specify tax codes and tax rates for taxable sales items
and articles. You can display an overview of all your tax codes, create new tax codes, and edit tax codes.
SAP Customer Checkout manager provides predelivered tax codes.
You cannot activate tax codes that have the same tax code for the same country/region with overlapping
validity periods. Use of a tax code for the same tax code and a different country/region is permitted, if the tax
code is inactive.
 Note
Tax codes are not synchronized automatically with your SAP Customer Checkout applications, but have to
be maintained manually in SAP Customer Checkout.
 Caution
You cannot delete a tax code in the SAP Customer Checkout manager. If you do not want a tax code to be
used in articles, you have to deactivate the tax code.
The following information is available for tax codes:
Tax Code
Field Description
Country/Region Country/region to which this tax rate is applied
Type code Tax rate type code used in printed receipts for sales items
and articles
Rate Tax rate in percent
Valid from Date as of which this tax code is valid in the application
Valid to Date until which this tax rate is valid in the application
Description Description displayed on the SALES screen in the Create/

Change Article dialog box for this tax rate
Active Enabled: Tax rate is used in the application
Disabled: Tax rate is not used in the application

5.4.14.2 Article groups
You can maintain article groups for articles and sales items in SAP Customer Checkout manager. You can
create new article groups, and edit article groups.
Article groups are special forms of merchandise category articles that can group together certain articles to
form subgroups.
In SAP Customer Checkout manager, you can see an overview of all your article groups, create new article
groups (for example a hierarchy article), delete, edit, and move article groups.
Select an article group to see subcategories with additional article groups.
 Note
Article groups are not automatically synchronized with your SAP Customer Checkout applications. When
an article is transferred to SAP Customer Checkout, the related article group is also transferred. You don't
have to manually maintain the article group in SAP Customer Checkout.
You assign articles to an article group in the Articles tile in SAP Customer Checkout manager.
The following information is available for article groups:
Article groups
Field Description
ID ID of the article group
Name Name of article group
Refund If you activate this field, the article group can be refunded in
SAP Customer Checkout, even if the user (currently logged
in to the relevant POS system) is not authorized to accept
returns.
5.4.14.2.1 Creating an Article Group
Context
You can create new article groups in the SAP Customer Checkout manager. You can create an article group and
assign additional article groups to the newly created article groups.

Procedure
1. In the PoS Configuration tile of the SAP Customer Checkout manager, choose the Article Groups tab.
2. Choose the Add icon to create a new article group.
3. Enter the article group information.
4. To save the article group, click Save.
5.4.14.2.2 Editing an Article Group
Context
In the SAP Customer Checkout manager, you can edit existing article groups. For example, you may want to
change the name of an article group or create additional subcategories for the article group.
Procedure
1. Select the article group that you want to edit, and choose the Edit icon.
2. Edit the article group information as needed.
You cannot edit the ID of an article group in the SAP Customer Checkout manager.
5.4.14.2.3 Moving an Article Group
Context
You can move article groups in the PoS Configuration tile in the SAP Customer Checkout manager. For example,
you can move an article group to another article group.
 Note
When moving an article group to another article group, all subcategories assigned to this article group are
also moved.

Procedure
1. Select the article group that you want to move, and choose the Move icon.
2. Select the parent article group to which you want to move the article group.
5.4.14.2.4 Deleting an Article Group
Context
You can delete article groups in the SAP Customer Checkout manager.
 Note
You can only delete an article group if no articles are assigned to this article group.
Procedure
1. Select the article group that you want to delete, and choose the Delete icon.
2. Confirm that you want to delete the article group by clicking OK.
The article group is deleted from the SAP Customer Checkout manager.
5.4.14.2.5 Assigning and Removing Output Locations of an

Article Group
Context
Output locations specify which document printer is used to print a specific article or article group. This only
applies to the document type “order”. Output locations can be assigned to article groups.

Procedure
1. Open the POS configuration tile and then the Article groups tile.
2. Open the details of the article group that you want to edit. To open the details, choose the icon for article
group details on the right-hand side of the relevant column.
3. Open the “Output Locations” tab.
○ To assign an output location, choose Assign at the bottom right corner of the screen and assign the
required output location.
○ To remove an assigned output location, choose the "Remove" icon in the relevant row.
5.4.14.3 Currencies
In the SAP Customer Checkout manager, you can maintain multiple currencies that can be used to maintain
prices for articles. You can display an overview of all your currencies, add new currencies, and delete a
currency.
The following currencies are shipped with SAP Customer Checkout:
● EUR
● CHF
● GBP
● PLN
● SEK
● DKK
If you want to use a different currency, you can maintain the currency in the PoS Configuration tile.
 Note
Currencies maintained in the SAP Customer Checkout manager are not synchronized automatically with
your SAP Customer Checkout applications, but have to be maintained manually.
 Caution
You cannot delete a currency that is used in a price list.

5.4.14.3.1 Adding New Currencies
Context
If you want to use a currency that isn't provided out-of-the-box, you can add a currency to the SAP Customer
Checkout manager.
Procedure
1. In the PoS Configuration tile, choose the Currency tab.

2. Choose the Add icon.
3. Enter the international three-letter currency code.
4. To save the currency, click Save.
5.4.14.4 Quick Selections
In SAP Customer Checkout manager, you can configure pushbuttons for quick selection to appear on the
SALES screen of your SAP Customer Checkout applications. For Quick Service and Table Management mode,
you can also configure the Sales screen in SAP Customer Checkout flexibly.
 Note
As of SAP Customer Checkout 2.0 Feature Pack 09, quick selection configuration for Retail, Quick Service,
and Table Service mode is performed centrally in SAP Customer Checkout manager only.
The Quick Selections application is available in SAP Customer Checkout manager within the PoS Configuration
application. Here, you can display an overview of all quick selection configurations, create new quick selection
structures, assign organizational units, roles, and users to a quick selection configuration, upload new quick
selection configurations, and copy, move, edit, or delete a quick selection configuration.
On the right side of the screen, a preview of the quick selection currently selected is displayed. For more
information, see Preview of Quick Selection [page 161].
Select a quick selection structure to display pushbuttons and applications in this structure with more
information. General data, articles assigned to this pushbutton, Extended JavaScript, and extended CSS style
information is located here.
For more information about enabling and using quick selections in SAP Customer Checkout, see the SAP
Customer Checkout User Guide.
As of SAP Customer Checkout 2.0 Feature Pack 09, the SAP Default quick selection is provided at initial
installation of SAP Customer Checkout manager. For more information, see SAP Default Quick Selection [page
160]

The following information is available for each quick selection:
Field Description
Name Name of Pushbutton or Group
The following groups are delivered as standard:
● center: here you can configure the top (main) area of

your quick selection.
● bottom: Here you can configure the lower part of your
quick selection.
● PaymentFX: Here you find preconfigured pushbuttons
with defined special functions for all available payment
options in Sales (cash payment, card payment, voucher
payment, payment on credit, or loyalty points). You can
also select which of the available payment options you
want to display in SAP Customer Checkout. On the
Sales screen in SAP Customer Checkout, these
pushbuttons are located in the lower left area.
● QuickFX: This area includes preconfigured pushbuttons
with special features for common Sales processes
(such as Receipt discount or Receipt printing) and with
components (such as "Customer selection in receipt"
or "Numeric keypad"). On the Sales screen in SAP
Customer Checkout, these pushbuttons are located in
the middle area (to the right of the sales item list).
 Example
If you are working in hospitality, you can use the groups
center and bottom as the higher-level structure - one for
food and the other for beverages:
● center: Configure all pushbuttons for food

● bottom: Configure all pushbuttons for beverages
Row Defines the position (x coordinate) of the pushbutton or

group in the quick selection display area.
When no row is defined, the default row is used. The default

row is 0.
Column Defines the position (y coordinate) of the pushbutton or

group in the quick selection display area.
When no column is defined, the default column is used. The

default column is 0.

Field Description
Type The following types are available:
● Group A collection of pushbuttons. These can contain

articles, texts, functions, or components.
● Articles: A specific article can be stored for the
pushbutton.
● Text: User-defined text modules can be stored for a
pushbutton. For more information, see User-Defined
Text Modules [page 167].
● Feature: The pushbutton can be defined as a special
function, for example, Return Receipt or Park Receipt.
For more information, see Pushbuttons with Special
Features [page 169].
● Component: You can also define elements, such as
Customer selection in receipt, Number pad, or Article
Image, for a pushbutton.
Value The value stored for the pushbutton. This can include an
article ID, a special function, a component, or a user-
defined text module.
If you select a pushbutton or group, you can see more details:
Field Description
Translation key Key for the term to be displayed on the pushbutton.
Horizontal size Defines the width of the display area for this pushbutton.
If no width is defined, the default width is used. Default

width: 1
Vertical size Defines the height of the display area for this pushbutton.
If no height is defined, the default height is used. Default

height: 1
Display option Specifies which pushbutton information is to be displayed

on the screen.
The following options are possible:
● Image Only: The uploaded image of the pushbutton is

displayed on the screen.
● Text Only: The name of the pushbutton is displayed on
the screen.
● Text and Image: The name and the uploaded image of
the pushbutton are displayed on the screen.

Field Description
Extended JavaScript Enables you to extend quick selections using JavaScript.
The code editor supports syntax highlighting.
This field is only relevant when using the retail mode.
Extended CSS style Enables you to extend quick selections using CSS styles
Border top color Border color used for the pushbutton above.
The standard border color above is transparent.
Background color Color used for the pushbutton
5.4.14.4.1 SAP Default Quick Selection
SAP Customer Checkout manager delivers a quick selection template (SAP Default).
The SAP default quick selection is to be used as a template for creating your own quick selection.
The SAP default quick selection includes the following:
● center
● bottom
● PaymentFX
● QuickFX
Each area features preconfigured pushbuttons with special features, articles, or components.
The center area contains preconfigured pushbuttons with special features for receipts (for example: "Cancel
receipt" or "Park receipt"), for individual articles (for example: "Cancel sales item" or "Offer item discount"),
for payments (for example: "No change" or "Card payment"), and for customers (for example: "Create
customer" or "Edit customer"). The area also includes special features for Retail, Table Service, or Quick
Service mode.
The bottom area includes preconfigured pushbuttons for a selection of articles.
The area PaymentFX contains preconfigured pushbuttons with defined special functions for all available
payment options in Sales (cash payment, card payment, voucher payment, payment on credit, loyalty points, or
predefined bank notes).
The QuickFX area includes preconfigured pushbuttons with special features for common Sales processes
(such as Receipt discount or Receipt printing) and with components (such as "Customer selection in receipt" or
"Numeric keypad").
 Note
The SAP Default Quick Selection is only a template and for support and cannot be edited.

5.4.14.4.2 Preview of Quick Selection
A preview is available for processing quick selections.
The preview is displayed automatically on the right-hand side of the screen for the quick selection currently
selected. The preview shows the quick selection in the same way as it would be displayed in the POS system.
 Note
The quick selection preview is available for table management mode and quick service mode, but not for
retail mode.
Changes in the quick selection are immediately applied in the preview. The pushbuttons are shown in the
preview with their labels, defined images, colors, coordinates, and dimensions (height and width). Pushbuttons
that act as an application for showing or hiding other buttons can be used by the user.
If you choose one of the pushbuttons in the preview, the system automatically switches to the detail view of the
pushbutton on the left side of the screen.
5.4.14.4.3 Creating Quick Selections
Context
In the Quick selection application you can create a hierarchical tree structure with pushbuttons and
subsections. You can assign individual articles, functions, components, and user-defined text modules to a
pushbutton. Selecting the pushbuttons adds the corresponding articles, functions, components, or user-
defined text modules to the receipt in SAP Customer Checkout. You can add labels or images to pushbuttons
and position them in the quick selection area. You can also extend the representation and behavior of each
button with CSS styles and JavaScript. In addition, you can flexibly configure the section for payments, the
numeric keypad, and the section for enhanced sales transactions.
Procedure
1. Choose the Quick Selection application.

2. Select Add to create a new quick selection structure for your PoS systems.
 Note
You can also use SAP Default Quick Selection as support and edit it according to your requirements.
For more information, see SAP Default Quick Selection [page 160].
3. Enter the quick selection information and save your entries.

Quick selection
Field Description
Name Name of the quick selection configuration
PoS group Here you can select the PoS group to which you want to
assign the quick selection.
PoS system Here you can select the PoS system to which you want to
assign the quick selection.
4. Your new quick selection is now created. You can configure this as required and create subelements.
5.4.14.4.4 Copying Quick Selections
Context
You can copy quick selection configurations in SAP Customer Checkout manager. When copying a quick
selection configuration, all assigned buttons, groups, features, components, texts, images, and articles are also
copied.
 Caution
POS systems that are assigned to a quick selection configuration are not copied, as only one quick
selection configuration can be assigned to an organizational unit.
 Caution
The system does not display any warning if you copy a quick selection configuration and assign it to an
organizational unit for which a price list or article is unknown. Ensure that the assigned price lists and
articles are maintained in the respective POS system.
Procedure

2. Choose the Copy icon in the quick selection configuration that you want to copy.
3. Enter a name for the new quick selection configuration.
4. Choose Save.

5.4.14.4.5 Editing Quick Selections
In SAP Customer Checkout manager, you can edit the configuration of your quick selection structure and
pushbuttons assigned to the PoS systems.
When you select a quick selection structure or pushbutton, you have the following additional options:
Option Description
Edit general data of the quick selection Here, you can edit general data such as the name, height,
and width, or the format of the quick selection.
Upload or remove an image for the quick selection Here, you can upload an image to be displayed in your quick
selection. If an image has already been uploaded for the
quick selection, you can remove this image.
Add a subelement to the quick selection You can add more pushbuttons and subsections to the
quick selection.
Create a matrix for the quick selection You can create a matrix for the quick selection and enter the
number of columns and rows.
Add SAP default quick selection By default, SAP Customer Checkout manager creates four
quick selection groups (center, bottom, PaymentFx, and
QuickFx) when you add a new quick selection. If you have
deleted one of the four default groups, you can use the Add
Standard option to add the group again.
Change the page ratio of the preview You can choose which page ratio the screen resolution uses
to display the preview. This allows you to simulate how the
quick selection would be displayed in SAP Customer
Checkout with the chosen page ratio.
The following options are possible:
● Resolution 4:3
● Resolution 16:9
● User-defined (an extra window opens, which you can
zoom in and zoom out as desired)
Assign an article, a function, a text module, or a component You can assign the following subelements to a quick
to a quick selection. selection:
● Article
● Feature
● Group
● User-Defined Text Modules
● Component
By selecting the relevant pushbuttons in SAP
Customer Checkout, the corresponding articles,

Option Description
functions, custom texts, or a component can be added

to the receipt.
 Note
For more information, see the following sections:
User-Defined Text Modules [page 167],
Pushbuttons with Special Features [page 169],
Assigning Pushbuttons to an Article [page 175],
Assigning a Component to a Pushbutton [page
176].
Delete all subelements of a quick selection If your quick selection includes one or more subelements,
you can use the Delete All option to remove all underlying
elements.
5.4.14.4.6 Downloading Quick Selections
Context
In the Quick Selection application, you can export the configuration of a quick selection.
Procedure
1. Select the quick selection you want to download and choose Download.
2. The quick selection configuration is downloaded as a JSON file.
5.4.14.4.7 Uploading Quick Selections
Context
In the Quick Selection application, you can import a quick selection configuration.

Procedure
1. Choose Upload and select the JSON file that you want to upload.
2. The quick selection configuration is uploaded to SAP Customer Checkout manager.
5.4.14.4.8 Assigning Organizational Units to a Quick

Selection
Context
In the SAP Customer Checkout manager, you can centrally assign a quick selection configuration to an
organizational unit (POS system and POS group).
 Caution
Only one quick selection can be assigned to an organizational unit. A PoS system cannot have more than
one quick selection assigned.
Procedure

2. Choose the Display icon of each quick selection configuration that you want to assign.
3. Choose the tab for Org. Units.
A tab for assigning organizational units opens, on which all of the POS groups and POS systems assigned
to the quick selection are displayed. You can also add a new POS group or POS system to the quick
selection.
4. Choose the Assign icon.
5. Select the organizational unit to which you want the quick selection to be assigned.
 Note
When you assign a POS group to a quick selection, you can unassign subordinate organizational units. If
you select this option, all organizational units below the selected POS group will be removed. Disable
this option if you want the quick selection to be assigned to the related organizational units (or the
respective POS group).
 Example

○ root
○ Merchandise Shop
○ POS1
○ POS2
 Caution
You cannot assign more than one quick selection configuration to a POS system. If you
assign a quick selection to a PoS system to which another quick selection is already
assigned, you need to save your entries again to remove the current assignment.
You have a quick selection configuration called QuickShop1 with the following assignments:
root, POS1. You create a new quick selection configuration, QuickShop2, assign the
Merchandising Shop organizational unit to this quick selection configuration, and activate
the Unassign subordinate organizational units option. The POS system POS1 is part of the
Merchandising Shop organizational unit. The assignment of POS1 to QuickShop1 is
removed. All POS systems that are assigned to the Merchandising Shop get the quick
selection configuration QuickShop2.
5.4.14.4.9 Assigning Roles and Users to a Quick Selection
Context
In SAP Customer Checkout manager, you can assign central roles and users to a quick selection configuration.
 Note
Only one quick selection can be assigned to a role or user.
Procedure

2. Choose the Display icon of the quick selection configuration to which you want to assign a role or a user.
3. Choose the required tab.
○ Choose Roles to add roles to the quick selection.

○ Choose Users to add users to the quick selection.
The tab for assigning roles or users is opened, which displays all of the roles or users assigned to the quick
selection.

4. Choose the Assign icon.
5. Select the role or user you want to assign.
 Note
If you assign a role or user to a quick selection, no other quick selection can be assigned to this role or
user. If you assign a quick selection to a role or user to which another quick selection is already
assigned, you need to save your entries again to remove the current assignment.
5.4.14.4.10 Deleting Quick Selections
Context
You can delete quick selections or sub-elements of quick selections from SAP Customer Checkout manager.
 Note
If you delete a quick selection configuration, all pushbuttons (subelements) assigned to this configuration
are also deleted.
Procedure

2. Select the quick selection (or sub-element) you want to delete.
3. Choose Delete (or Delete All if you want to delete all sub-elements in a quick selection) and confirm with
OK.
The quick selection or sub-element is deleted from SAP Customer Checkout manager.
5.4.14.4.11 User-Defined Text Modules
User-defined text modules are freely defined texts used for providing sales items with additional information.
These texts can be assigned to buttons on the user interface of SAP Customer Checkout.
If a sales item has assigned text modules, the text module is printed on the purchase order.
User-defined text modules are created in SAP Customer Checkout manager. The modules are provided in the
quick selection in SAP Customer Checkout applications.

 Note
To use user-defined text modules, SAP Customer Checkout has to be operated in table management mode
or quick service mode.
5.4.14.4.11.1 Creating and Editing User-Defined Text Modules
Context
User-defined text modules can be created and edited in SAP Customer Checkout manager.
 Note
You can use a pushbutton to display a keyboard on the user interface instead of the defined text. This
enables you to enter additional information for a sales item directly.
Procedure

2. Create a quick selection in SAP Customer Checkout manager or select an existing one.
3. Add a pushbutton or select an existing one.
4. Enter the desired name for the pushbutton and choose the type Text.
5. Enter the content of the user-defined text module in the Description field.
 Note
Activate the Show keyboard option to display a keyboard when selecting a key.
6. Choose Save.
Results
The user-defined text module becomes available after the next logon to SAP Customer Checkout.

5.4.14.4.12 Pushbuttons with Special Features
Besides pushbuttons for adding articles, other pushbuttons with special features can be added to the quick
selection. Pushbuttons with special features in the quick selection are only supported in quick service and table
management mode.
Each function belongs to a function group that supports certain sales processes.
 Example
For example, the Table Management function group contains functions such as Select Aisle, which are
relevant when SAP Customer Checkout is operated in Table Management mode.
The following features exist in SAP Customer Checkout manager:
Special Features:
Button Description
Add one-time customer Allows you to add a one-time customer to the receipt with
out using master data or creating a master data record.
Opens a dialog for entering the customer data. The cus

tomer data is saved only in the receipt. The printed receipt
contains the customer data entered.
 Note
SAP Customer Checkout provides features for docu
menting whether a person has given their consent for
their personal data to be processed. If the setting
Consent Required is activated in the SAP Customer
Checkout configuration, the Consent given and
maintained indicator is a required entry field.
If the person concerned has given their consent for their

personal data to be processed, select the version of the
consent document and activate the Consent given and
maintained indicator.
Move POS system to POS group Enables the POS system to be moved to a different organiza
tional structure.

Button Description
Apply reduced tax rate A reduced tax rate can be specified for receipts. By choosing
this pushbutton, you can apply the reduced tax rate to all ar
ticles on the receipt (if a reduced tax rate is not defined, the
standard tax rate for the article is used).
 Example
This allows a receipt for meals taken home rather than
consumed in the restaurant to be posted with a reduced
tax rate.
Apply reduced tax rate to sales item A reduced tax rate can be specified for articles. By selecting
a sales item and then choosing this pushbutton, you can ap
ply the reduced tax rate to all articles of the sales item (if a
reduced tax rate is not defined, the standard tax rate for the
article is used).
Apply default tax rate When you choose this button, the standard tax rate defined
in the articles is used for all articles of the receipt.
Apply default tax rate to sales item When you choose this pushbutton, the standard tax rate of
the article is used for the selected article.
Apply tax rate Allows you to change the tax rate type for the receipt.
Cancel receipt Cancels the current receipt.
Cancel sales item Cancels the selected sales item.
Receipt discount Enables you to assign a discount to the whole receipt.
Assign sales person Allows you to assign a sales person to a sales document.
Assign warehouse Allows you to assign a storage location to the sales docu
ment.
Apply tax rate Allows you to change the tax rate type for the sales docu
ment.
Write text note Allows you to add a note to the sales document. This infor
mation is synchronized with the back-end system.
Display header details Shows the header data of a sales document (for example,
general data, tax items, coupons).
Select receipt type (SAP Business One only) Enables the selection for the Sales
and Reserve Invoice document categories.

Button Description
Stock Overview (SAP Customer Checkout manager and SAP Business One
only) Enables you to display stock information for an article.
Coupon Enables you to apply coupons to articles in the sales item list
or to the entire receipt
Print receipt Allows printing of the last sales document.
Split/merge In table management mode, this allows you to split or merge

the sales document when making a payment.
Always split sales items For each article added, a new sales item is created in the
sales item list, even if the list already contains a sales item
with identical articles.
Park receipt Allows the current sales document to be parked.
Resume receipt Allows you to resume processing of a sales document.
Assign loyalty coupon Allows you to assign a loyalty coupon to a sales document.
Assign loyalty account Allows you to assign a loyalty account and a sales document.
Assign sales person to sales item Allows you to assign a salesperson to a sales item.
Assign warehouse to sales item Allows you to assign a storage location to the sales item. In
SAP Customer Checkout manager and SAP Business One,
the warehouse stock for this sales item is reduced accord
ingly for this storage location.
Apply tax rate to sales item Enables you to change the tax rate type for the sales item.
Write text note for sales item Allows you to add a note to the sales item. This information
is synchronized with the back-end system.
Display sales item details Displays details of a sales item (for example, general data,
pricing elements, coupons, sales set components).
Change sales item text Enables the modification of a sales item text.
Assign batch/serial number to sales item (SAP Business One only) Allows you to manually assign a
batch/serial number to a sales item.
Pay exact amount Allows payment of the exact amount in cash.
Create customer Lets you create a new customer.
Edit customer Enables you to edit customers.

Button Description
Create loyalty account for customer Allows you to create a loyalty user for a customer, as long as
the customer does not yet have a loyalty user.
Display Customers Purchased Items Shows the recently purchased purchase items for the se
lected customer.
 Note
The period of purchased items for customers is dis
played based on the settings defined in the configura-
tion under Customer Purchase Data [page 57].
Display Customers Last Purchased Receipts Displays the last purchased receipts for the selected cus
tomer.
 Note
The number of purchased receipts for customers is dis
played based on the settings defined in the configura-
tion under Customer Purchase Data [page 57].
Fetch external Business Object Enables you to retrieve tickets from SAP Event Ticketing. For
more information, see SAP Event Ticketing Integration [page
9]
Customer count When operating SAP Customer Checkout in table service

mode, allows you to enter the number of customers for the
respective table.
Change price list Enables you to change the price list.
Return receipt Allows you to return a receipt.
Return receipt by ID Allows you to return a receipt based on its ID.
Item discount Enables you to assign a discount to the sales item.
Selecting Aisles Allows you to select an aisle when SAP Customer Checkout
is operated in Table Management mode.
Cash payment Allows you to add a cash payment.
Card payment Allows you to add a card payment.
Voucher payment Allows you to add a voucher payment.
Payment by loyalty points Allows you to add a payment with loyalty points.
Payment on credit Allows you to add a payment on credit.

Button Description
Add payment Allows you to add a payment according to defined parame

ters. For more information, see Add Parameters for Pushbut
tons with Special Functions [page 174].
Payout by voucher Allows you to payout money as a voucher.
Remove block after day-end closing Allows you to remove a block during day-end closing when
SAP Customer Checkout is run in central drawer mode.
If you have started day-end closing in a cash desk (CCO1)

and do not end it at this cash desk, then the day-end closing
is not possible at a different cash desk (CCO2). You can use
this function to remove the block.
5.4.14.4.12.1 Creating Pushbuttons with Special Functions
Context
Pushbuttons with special features can be created in SAP Customer Checkout manager.
Procedure

2. Create a quick selection in SAP Customer Checkout manager or select an existing one.
3. Choose Add to create a new pushbutton or choose an existing pushbutton and Edit.
4. Enter the required information (for example, name) for the pushbutton and choose the type Feature.
5. You can now select the relevant function group and function type.
6. Choose Save.

5.4.14.4.12.2 Add Parameters for Pushbuttons with Special
Functions
In SAP Customer Checkout manager, you can create parameters for specific functions. In SAP Customer
Checkout, you can use the defined parameters to flexibly adapt some functions to meet your requirements.
Context
Parameters can be added to a variety of functions, for example, for payment functions, the assignment of
sellers to receipts and sales items, or for discounts.
Procedure
1. Choose the Quick Selectionapplication.

2. Create a pushbutton with special function in SAP Customer Checkout manager, or choose an existing
pushbutton that has a special function.
3. Choose Display to go to the detailed view of the function.
4. Choose the Items application and select the relevant function.
5. Choose Add to create a new parameter for the selected function.
6. Select the name and enter a value for your parameter.
The following parameters can be added for payments:
Name Description
Type The parameter type
Use the following codes for the following payment types:
Payment type Code
Card payment 02
Cash payment 09
Voucher payment 20
Payment on credit 30
Subtype The subcategories of the parameter type, such as the

card type code for a card payment.
Amount The absolute amount of the parameter
Tip Amount The absolute tip amount of the parameter
Currency The international, three-letter currency code
NoAutoPost If this value is set to true, the document is not posted

automatically after the payment is added.

Name Description
If this value is set to false, the document is posted

automatically after the payment is added.
 Example
For example, if you want to create a pushbutton for cash payments of USD 100, enter the following
three parameters in your Add Payment function:
○ Type: 09
○ Amount: 100
○ Currency: USD
 Example
If you want to create a pushbutton to assign a specific seller to a sales item directly, enter the user
name of the seller as a parameter in your function of type Assign Seller to Sales Item. In SAP Customer
Checkout, when the pushbutton is selected, the respective seller is assigned to the sales item
automatically.
7. Choose Save.
5.4.14.4.13 Assigning Pushbuttons to an Article
You can assign an article to a pushbutton. In SAP Customer Checkout manager. When selecting a pushbutton
in SAP Customer Checkout, the corresponding article is added to the receipt.
Context
When you assign an article to the pushbutton, you can select an article provider:
● From the SAP Customer Checkout manager (when using this system as your the back-end system)
● From an External ID (when using an SAP ERP system as the back-end system)
To assign the article to a pushbutton, enter the article ID in the Select Article field.
Procedure

2. Choose Edit for the pushbutton to which you want to assign an article, or choose Add to create a new quick
selection button and assign it to an article.
3. Enter the information for the pushbutton and select the type Article.

4. You can now select one of the following article suppliers:
○ SAP Customer Checkout manager: When using this SAP Customer Checkout manager system as a
back-end system.
○ External ID: When using an SAP ERP system as a back-end system.
5. Enter the relevant article ID in the Article field and save your entries.
 Note
If you select an article from SAP Customer Checkout manager and have stored an image (of type Quick
Selection) for this article, you can use the Image Only or Text and Image display option to use the image
stored for the respective pushbutton. You do not need to manually upload the image again for the
pushbutton.
5.4.14.4.14 Assigning a Component to a Pushbutton
In addition to articles, texts, and functions, you can also assign a component to a pushbutton.
Context
The following component types can be selected:
Type Description
Customer selection in receipt This option allows you to select a customer on the Sales
screen in SAP Customer Checkout that you can add to the
receipt.
Number pad This option displays a numeric keypad on the Sales screen
in SAP Customer Checkout that you can use, for example,
to increase the quantity of a sales item.
Article image When selecting an article on the Sales screen in SAP

Customer Checkout, this option displays the article image
that is stored for the article in SAP Customer Checkout
manager. The relevant article image must be assigned to
the Sales Screen type.
For more information, see Adding Images of Articles [page

145].

Procedure

2. Choose Edit for the pushbutton to which you want to assign a component, or choose Add to create a new
pushbutton and assign it a component.
3. Enter the information for the pushbutton and choose the type Component.
4. Select one of the component types above and save your entries.
5.4.14.5 Code Lists
On the Code Lists tile, you can manage code lists.
In code lists, descriptions of codes that are used during processing and for display purposes in SAP Customer
Checkout manager can be added and edited. Code lists in SAP Customer Checkout manager are not
transferred to SAP Customer Checkout.
 Note
If you add new codes, you need to maintain them both in SAP Customer Checkout manager and SAP
Customer Checkout.
The following fields are available for codes:
Field Description
Value Code value
Description Description of the code value
Active Inactive codes are used for display purposes only.
Default Indicates whether the code list is used as default code list
Changed by Customer This indicator is automatically selected as soon as the code

has been changed by the customer.
Provided by SAP This code is shipped by default with SAP Customer Check
out manager. Codes with this indicator are overwritten again
whenever SAP Customer Checkout manager is updated.
The following code lists can be managed:
Code List Description
Customer Return Reason Code Reasons for the return of articles and receipts. If central re
ceipt management is enabled in SAP Customer Checkout,
and if the user selects a reason for the return, this is sent to
SAP Customer Checkout manager along with the receipt.

Code List Description
Discount Purpose Discount purposes for articles and receipts. If central receipt
management is enabled in SAP Customer Checkout, and if
the user selects a discount purpose, this is sent to SAP Cus
tomer Checkout manager along with the receipt.
Quantity Type Code This code list currently has no effect.
Output Locations Output locations specify which document printer is used to

print a specific article or article group.
Version of the consent for processing personal data The processing of personal data requires the consent of the
person whose data is to be processed. Therefore, users, cus
tomers, and loyalty users have a data field in which the ver
sion of the consent can be saved. The versions of the con
sents can be managed in this code list.
 Note
If a version code is in use, it cannot be deactivated and
the code value cannot be changed.
Manufacturer Name of the manufacturer for articles
5.4.14.6 Payment Card Categories
Data for credit card categories can be defined on this tile.
The data maintained here for credit cards is not sent to SAP Customer Checkout. Credit cards must be
configured locally in each SAP Customer Checkout application.
The credit cards maintained here are used for displaying credit cards in sales reports, day-end closing, and on
the Receipts tile. The assignment takes place for the ERP type code, which must match the ERP type code that
has been configured in SAP Customer Checkout applications.
Credit Card
Field Description
Code Technical code for the unique identification of the credit card
entry.
Type code ERP Type code of the credit card from the SAP back-end system
used.
Is used for the assignment of credit card data.

Field Description
Description Description of the credit card that is displayed in SAP Cus

tomer Checkout manager in sales reports, day-end closings,
and on the Receipts tile.
Credit Card Number Currently has no effect.
General ledger account Currently has no effect.
Visible Currently has no effect.
Active Currently has no effect.
5.4.14.7 Characteristic Profiles
On the Characteristic Profiles tile, you can create and edit characteristic profiles. You can also combine one or
more characteristics.
A characteristic profile is a collection of characteristics.
You can use the characteristic profiles maintained here when searching for articles in SAP Customer Checkout.
5.4.14.7.1 Adding New Characteristic Profiles
You can create new characteristic profiles in SAP Customer Checkout manager.
Procedure
1. Choose Add on the Characteristic profiles tile.

2. Enter the information for the characteristic.
3. To save the characteristic, choose Save.
After you have created the characteristic profile, you add different characteristics for the characteristic
profile on the Characteristics tab. The characteristic profile Shoes, for example, can contain the
characteristics Size and Color. On the Materials tab, you can view articles that are assigned to this
characteristic profile.

5.4.14.8 Characteristics
On the Characteristics tile, you can create and edit characteristics for articles.
An article can have the characteristics Color and Size, for example.
In turn, a characteristic can contain one or more values. The characteristic Color, for example, can have the
values White and Black.
You can use the characteristics maintained here when searching for articles in SAP Customer Checkout.
5.4.14.8.1 Adding Characteristics
You can create characteristics in SAP Customer Checkout manager.
Context
Procedure
1. Choose Add on the Characteristics tile.

2. Enter the information for the characteristic.
3. To save the characteristic, choose Save.
After you have created the characteristic, you can add different values for the characteristic on the Values
tab. The characteristic Color, for example, can have the values White, Black, and Red.
5.4.14.9 Warehouses
By default, SAP Customer Checkout manager provides a feature for centralized warehouse administration.
This enables you to create stock locations, assign articles to specific stock locations, check stock levels for
articles, and transfer articles.
The Warehouse app enables you to create new warehouses and edit existing ones.
You can assign stock locations created in SAP Customer Checkout manager to specific articles (for more
details, see the Articles [page 134] app), in order to generate stock overviews in SAP Customer Checkout.
You can also use stock locations for certain stock transactions (for more details, see the Stock Transactions
[page 181] app).

5.4.14.9.1 Adding New Warehouses
You can create new warehouses in SAP Customer Checkout manager.
Context
Procedure
1. Choose Add in the Warehouses app.

2. Enter the appropriate warehouse data.
3. Choose Save to save the warehouse.
Once you have created the warehouse, you can assign it to specific articles. For more information, see
Articles [page 134]
5.4.15 Stock Transactions
SAP Customer Checkout manager enables you to perform stock transactions. You can correct your warehouse
stocks, receive goods, and withdraw goods from the warehouse.
For more information on warehouse administration, see Warehouses [page 180]
5.4.15.1 Creating Stock Transactions
You can create new stock transactions and add multiple line items to a stock transaction.
Context
Procedure
1. Choose the Stock Transactions tab and then Add.

2. Enter the relevant information and choose one of the following stock transaction categories:
Type Description
Goods Issued Goods have been withdrawn from stock on hand
Receive Goods Goods are added to the stock on hand
Stock Correction Stock on hand is corrected: Goods are either added to or

withdrawn from the warehouse.

4. On the Line Items tab, you can add multiple line items to the respective stock transaction.
5. Choose Add and enter the relevant information:
Field Description
Article Select the article for which you want to perform the stock
transaction.
Warehouses Select the warehouse from which you want to perform the
stock transaction.
Quantity Enter the number to be withdrawn from or added to the

stock on hand.
 Note
After you have created a stock transaction, you are in Draftstatus. To execute the stock transaction,
choose Update.
To check whether your stock transaction has been posted, you can access the available stock levels in the
relevant articles.
5.4.16 Migrations
The Migrations tile enables you import articles, prices, users, customers, and vouchers into SAP Customer
Checkout manager using a CSV file. This may be useful when you have existing data about users, articles,
prices, customers, and vouchers that you want to add to SAP Customer Checkout manager.
You can download the template file for migration and import it to SAP Customer Checkout manager with all
relevant data on articles, prices, users, customers, and vouchers. Furthermore, you can see an overview of the
latest migrations, sort, or filter a migration.
 Note
This tile is only relevant when using SAP Customer Checkout manager as a back-end system.
 Caution
You can only migrate standard articles in the Migrations tile. Generic articles and sales sets cannot be
migrated to SAP Customer Checkout manager.

The following tabs are available in the Migrations tile:
Migrations Tile
On this tab you can...
Articles and price Import articles and prices via a CSV file.
User Import users via a CSV file.
Customers Import customers via a CSV file.
Vouchers Import vouchers via a CSV file.
When you select one of the tabs, the following sections are available:
Migrations Options
Option Description
Download template for migration Executes the download of the template file (csv file) for the
migration.
Select file for migration Executes the import of a CSV file into the SAP Customer
Checkout manager system.
 Note
SAP Customer Checkout manager only supports CSV
files in UTF-8 format.
History Provides an overview of the latest migrations. Furthermore,

you can cancel a migration import process.
The History section contains the following information:
History Details
Field Description
Description Description of the CSV file for migration
Process ID ID of the process that executes the migration
Execution Start Displays the date and time when import started.
Execution Done Displays the date and time when the execution of the migra
tion was finished.

Field Description
Execution State Indicates the status of the import process of the migration.
● Inactive
● Running
● Void
● Finished
Execution Result Indicates if the import process of the migration was success
ful.
● None
● Void
● Success
● Fail
● Fatal
Rows created Shows the number of rows that were created while importing
data into SAP Customer Checkout manager.
Rows updated Shows the number of rows updated while importing data
into SAP Customer Checkout manager.
Rows ignored Shows the number of rows ignored while importing data into
SAP Customer Checkout manager.
Cancel job Lets you cancel a migration process while it's running.
Select a history entry to see the following information:
History Details
Field Description
Status Message Message of the migration process result
Download file Enables you to download the imported CSV file.
 Note
This option is only possible for the Articles and prices
tab.
Created By Username of the user who created the migration in the SAP

Field Description
Created At Date and time when the migration was created in SAP Cus
Changed By Username of the user who modified the migration in the SAP
Changed At Date and time when the migration was modified in the SAP
History Log Details
Field Description
Status Indicates whether the respective line was imported success

fully.
● Success
● Error
● Warning
Description Description of the log message for the respective line
5.4.16.1 Importing Migration Files
SAP Customer Checkout manager lets you migrate articles, prices, users, customers, and vouchers to SAP
Customer Checkout manager system using a CSV file.
Context
 Caution
For special characters " and ; in CSV files, special escape characters are required. To use the special
character ", use the escape character \ as a prefix (example: \"). The special character ; is used within the
CSV files to separate fields from each other. If you want to use the special character ; within a field, you
need to enclose the entire field content with the escape character "" (example: "sample;text").

Procedure
1. On the Migrations tile, select Articles and Prices, Users, Customers, or Vouchers.
2. To download the template for migration, click Download template.
3. In the csv file, enter all relevant data according to the example shown in the template file, and save the file.
 Note
When migrating customers, articles, and prices, you can also enter values for user-defined fields that
are provided during CSV file upload. For further information on user-defined fields, please see the
Configuration Guide for SAP Customer Checkout.
 Note
SAP Customer Checkout manager provides functions for documenting whether a person has given
their consent for their personal data to be processed. If the setting Consent Required is activated in the
SAP Customer Checkout configuration, the Consent given and maintained indicator is a required entry
field when you migrate users and customers.
If the person concerned has given their consent for their personal data to be processed, maintain the
appropriate data for the consent and the version of the consent document in the migration file.
 Note
Examples:
○ Articles and prices:

A00001;100;First Article;EA;N;Y;A;TaxCode;DE;A2;PriceList;1;100.25;EUR
○ Users:
Rob;Robin;ADMINISTRATOR;DE;de_DE;EMP1005;1;FFFFFF;
19181785;N;N;Initial1;Initial1;Y;Y;AssignedPOS;root
In addition, if the csv file that you upload has leading and trailing spaces, they will be trimmed
during the migration. Example:
○ Line contains:
A00001;100; First Article ;EA;N;Y;A;TaxCode;DE;A2;PriceList;1;100.25;EUR
○ As a result when migrating the file:
A00001;100;First Article;EA;N;Y;A;TaxCode;DE;A2;PriceList;1;100.25;EU
○ Customers:
id001;1;Tom;Tomas;;;0002;0004;21-04-1987;EN;01;123;N;
0003;2;1234567;1234567;01501234567;[email protected];AddrId;;;DE;Berlin;12345;Dietmar-
Hopp-Allee;16;;;;;;;;42;;N;Y
 Caution
When migrating articles and prices, you can create standard articles only. Generic articles and
sales sets cannot be migrated into SAP Customer Checkout manager.
When you migrate users, you can assign users to POS groups, and/ or root, not only to POS
systems.

4. Select the csv file that you want to migrate, and choose Execute. Choose one of the update options, and
enter a description.
 Note
The following Update options are available for the migration:
○ Do not update: If you upload data on articles and prices, users, or customers that already exist in
SAP Customer Checkout manager, and you don't want to update the existing data.
○ Update only migrated records: This option allows you to update only articles and prices, users, or
customers that have been migrated to SAP Customer Checkout manager.
○ Update all records: This option enables you to update all records from the file in SAP Customer
Checkout manager.
You can also enter a Description for the migration file.
5. The status of the migrated file is shown in the History section.

Once the migration is completed, you can view articles and prices, users, customers, and vouchers in the
respective tiles.
 Note
Migrated articles and prices, users, or customers can only be deleted from SAP Customer Checkout
manager they have not been Synchronized with SAP Customer Checkout.
5.4.17 Customers
You can manage customers in SAP Customer Checkout manager. You can create, edit, and lock customers.
Customers managed by SAP Customer Checkout manager can be transferred to SAP Customer Checkout
applications. In SAP Customer Checkout you can use customers on the "Sales" screen.
On the "Customers" tile you can filter customers according to various criteria: First name, last name, ID, status,
tax number, consent given and stored, version of the consent document.
 Note
If SAP Customer Checkout is interconnected with another SAP back-end system, you can also use central
customer management in SAP Customer Checkout manager. For more information about the interaction of
central customer management with other SAP back-end systems, see the Configuration Guide for SAP
Customer Checkout.
On the Details tab page, you can see general, administrative, address, contact, and personal data for the
customer.
In the Personal Data area, you can document whether customers have consented to the processing of their
personal data.

Personal Info
Option Description
Consent given and maintained Indicates whether the customer has given consent for their
personal data to be processed.
 Note
essing of personal data for this customer. The selection is
optional.
On the Custom Fields tab you can define any values for customers. SAP Customer Checkout manager features
three types of user-defined fields:
● udfString: for user-defined fields for specifying text values

● udfDouble: for user-defined fields for specifying numeric values
● udfBoolean: for user-defined fields that are displayed as checkboxes
On the Loyalty, Coupons, and History tabs, you can see information about the loyalty user, meaning linked
coupons and loyalty points transactions, if the selected customer is linked to a loyalty account.
On the tab pages Receipts, Articles, and Last Purchases, you can view information on customer purchase data.
There is an overview of all receipts, total sales, and recently purchased items for the respective customer.
5.4.17.1 Creating Customers
Context
You can create customers in SAP Customer Checkout manager.
Procedure
1. Open the Customers tile.

2. Choose the "Create customer" symbol at the lower-left corner of the screen.

 Note
The customer ID can be generated automatically using the selected sequence number, or entered
manually. Select the "manual" value in the sequence number selector to enter the ID manually.
 Note
You can assign a price list and a discount to a customer. In SAP Customer Checkout, these are
automatically retrieved once you select this customer on the Sales screen.
3. Enter the customer data.

4. Choose Save.
5.4.17.2 Editing Customers
Context
Customer details and user-defined fields for customers can be edited in SAP Customer Checkout manager.
Procedure

2. Select the customer you want to edit.
3. Choose Edit at the lower-right corner of the screen.
4. Edit the customer details as required. To edit customer-defined fields, choose the User-Defined Fields tab.
You don't need to switch to edit mode again.
5. Choose Save.
5.4.17.3 Locking Customers
Context
In SAP Customer Checkout manager you can set customers to "locked" status. This status is also transmitted
to SAP Customer Checkout applications during customer synchronization. However, the status has no

influence on the use in SAP Customer Checkout. Customers in "locked" status can be added to documents and
can be used for the "Payment on Credit" payment type.
Procedure

2. Select the customer you want to lock.
3. Select Lock at the lower-right corner of the screen.
5.4.17.4 Activating Customers
Context
You can activate customers with status "locked" or "draft".
Procedure

2. Select the customer you want to activate.
3. Select Activate at the lower-right corner of the screen.
5.4.17.5 View Customer Purchase Data
Context
Customer purchase data, for example, sales history, recently purchased items, and posted receipts for
customers can be viewed in SAP Customer Checkout manager

Procedure

2. Select the customer for which you want to see the purchase data.
3. Choose the tab pages Receipts, Items, and Last Purchases to see further information.
You can search for receipts, and filter and sort receipts.
5.4.18 Central Drawer Management
Please observe the following basic conditions when using central drawer management:
Online Mode
Central drawer management requires SAP Customer Checkout to be connected with SAP Customer Checkout
manager at all times. When a user logs in to SAP Customer Checkout, the application has to call up drawer
data from SAP Customer Checkout manager. All receipts, cash transactions, and day-end closings are
transferred to SAP Customer Checkout manager. User management also requires a connection to SAP
User Management and Receipt Management
Drawer management requires you to activate central user management and central receipt management in
SAP Customer Checkout manager has three applications that are required to work in the "central drawer
management" mode:
● Drawers
● Sales summaries
● Business object locks
5.4.18.1 Drawers
The Cash Drawers application enables you to manage your drawers centrally. This is necessary if you are using
multiple cash drawers in your SAP Customer Checkout application. You can create, edit, or delete new cash
drawers, or modify the drawer status.
Each drawer contains additional tabs with further information: Details and Accounts.

The "Details" tab contains the following information:
Details
Field Description
ID Identifier for the drawer. The drawer ID is displayed on the

drawer selection screen during the logon to SAP Customer
Checkout.
Description Description of the drawer. The drawer description is dis

played on the drawer selection screen when logging in to
Default Users User assigned to this drawer as default user.
When this user logs in to SAP Customer Checkout, the sys

tem automatically displays the drawer assigned as default,
without showing the drawer selection screen.
Status The current status of the drawer. The following statuses are
available:
● Available: Drawer is not in use – it can be taken over by

a cashier.
● In transit: Drawer has been taken over by a cashier who
is currently not logged in.
● In use: Drawer is in use by a user who is logged in.
● Locked: Select this status to prevent a drawer from be
ing used.
POS system ID of PoS system currently or last connected with the

drawer.
User User who last used or is currently using the drawer.
Created At Date and time the drawer was created
Created By User name of the user who created the drawer in SAP Cus
Changed At Date and time the drawer was changed
Changed By Username of the user who last modified the drawer in SAP
The "Accounts" tab contains the following information:
Accounts
Field Description
Account Petty cash for drawer

Field Description
Master account Master account for PoS system
Currency Currency of account
 Note
The accounts, which are configured for drawers in SAP Customer Checkout Manager, are transferred as
accounts for cash sales to other SAP back-end systems, provided that the following prerequisites are met:
● SAP Customer Checkout uses central drawer management of SAP Customer Checkout manager.
● SAP Customer Checkout is also connected to an additional SAP back-end system, which can process
cash sales.
● The cash drawer (for which accounts are configured) is currently in use as cash drawer for the SAP
Customer Checkout application.
5.4.18.1.1 Creating Categories
Context
You have to create a drawer in SAP Customer Checkout manager for each of your company's cash drawers.
Procedure
1. Open the Drawers application.

2. Select the "Add" icon at the bottom left of the screen.
3. Enter the drawer data and fill out all fields flagged with an asterisk (*).
4. Once you have entered all required data you can select one of the following operations:
○ Save
○ Save and new
○ Cancel

5.4.18.1.2 Editing Drawers
Context
You can edit the cash drawers in SAP Customer Checkout manager.
 Caution
Please be careful when manually editing drawer data, as this may trigger an inconsistent system state. Be
particularly careful when making status and/or user changes.
Procedure

2. Select a drawer and choose Edit.
3. Make your changes:
○ On the Details tab you can edit ID, description, and default user.
○ To edit the connected POS system or the current user, select the Details tab and then Change Status.
4. Once you have changed all relevant data you can select one of the following operations:
○ Save
○ Cancel
5.4.18.1.3 Editing Drawer Accounts
Context
You can edit the accounts of existing cash drawers in SAP Customer Checkout manager.
Procedure

2. Select a drawer and open the Accounts tab.

3. On the Accounts tab you can perform the following actions:
○ To add an account, select Add from the lower right corner of the screen.
○ To edit an account, select the "Edit" icon in the corresponding line.
○ To delete an account, select the "Delete" icon in the corresponding line.
5.4.18.2 Sales Summaries
You can use the Sales Summaries application to view day-end closing information from SAP Customer
Checkout applications.
You can check whether all receipts for a day-end closing have been transferred to SAP Customer Checkout
manager and whether they match the posted day-end closing data. You can also display detailed information
for each day-end closing.
The Day-End Closings application displays the following details:
Sales Summaries
Field Description
ID Day-end closing ID
POS system ID of the PoS system
Opened at Date and time the day-end closing was opened
Closed at Date and time of day-end closing
Status Status of day-end closing. The following statuses are possi

ble:
Consistent
All receipts of the day-end closing have been posted in SAP

Customer Checkout manager. The amounts of the day-end
closing also match the totaled amounts of the receipts.
Deviation
Deviations detected for the number of posted receipts or the

totaled amounts of the receipts do not match the amounts
of the day-end closing.
Deviation Accepted
The deviation was accepted by a user.
Deviation accepted by User who accepted the deviation

5.4.18.2.1 Sales Summary Details
You can display detailed data for each sales summary by selecting the required summary.
The details contain the following information:
Sales Summary Details
Field Description
Details Summary of information, e.g. about the number of sales

transactions, totals, etc.
Receipts Overview of all receipts assigned to this sales summary
Cash Transactions Overview of all cash transactions assigned to this sales sum
mary
 Note
Each no-sale receipt (void receipt for opening the cash
drawer) that is assigned to this sales summary is dis
played on the cash transactions tab.
Currency details Overview of currency amounts counted by the cashier at

day-end closing. These are broken down by payment
method and currency.
Drawer Data The drawer data at time of day-end closing in the SAP Cus
tomer Checkout application.
Tips Overview of tips assigned to this sales summary
 Note
Tips are displayed only if SAP Customer Checkout is
running in "Do not record tips" or "Record tips" mode.
Configuration Overview Displays configuration data of the PoS system in which the
day-end closing was performed.
5.4.18.2.2 Checking Sales Summaries
Context
You can only check sales summaries in "Deviation" status.

Procedure
1. Open the Sales Summaries application.

2. Select the sales summary you want to check.
3. Choose Edit at the lower-right corner of the screen.
Results
SAP Customer Checkout manager validates the sales summary and updates its status.
5.4.18.2.3 Accepting Deviations of a Summary Transaction
Context
You can accept deviations only for sales summaries that have "deviation" status.
Procedure
1. Open the Sales Summaries application.

2. Choose the sales summary for which you want to accept the deviation.
3. Select Accept deviation at the lower-right corner of the screen.
Results
SAP Customer Checkout manager updates the sales summary status to "Deviation accepted".

5.4.18.2.4 Late Receipts
Late receipts are receipts that have not yet been transferred to SAP Customer Checkout manager at the time
of day-end closing.
If central drawer management is enabled in SAP Customer Checkout, all data displayed during day-end closing
and on the cashing-up screen is calculated in SAP Customer Checkout manager and transferred to SAP
Customer Checkout for display.
All receipts and cash transactions that were not successfully transferred to SAP Customer Checkout are
therefore not taken into account in day-end closing or when displayed on the cashing-up screen.
These receipts can be transferred to SAP Customer Checkout manager later, for example, by means of receipt
synchronization. However, these are no longer taken into account if the day-end closing or the sales summary
has already been completed at this point. This means that day-end closing or the sales summary shows a
deviation from the real posted receipts or cash transactions.
To be able to trace these deviations later, these late receipts or cash transactions are identified with the
attribute Late.
To view late receipts and cash transactions, open the Sales Summaries application and choose the Receipts tab
or the Cash Transactions tab. Late receipts and cash transactions are identified by a red indicator in the Late
column.
5.4.18.3 Locked Day-End Closings in the Application

Business Object Locks
If central drawer management is enabled in SAP Customer Checkout, day-end closings are locked during
execution for other PoS systems. The locked day-end closings are displayed in the Business Object Locks
application. For more information, refer to section Business object locks [page 200].

5.4.18.4 Troubleshooting for Central Drawer Management
This chapter indicates solutions for problems that may arise when using central drawer management.
5.4.18.4.1 Error Scenario: Cannot log on because the user

with the drawer is already logged on to another
PoS system.
Context
Each change to the drawer status is relayed back to SAP Customer Checkout manager. If the application is
shut down or if the connection with SAP Customer Checkout manager is lost during the logout process from
SAP Customer Checkout, the drawer status change may not be confirmed to SAP Customer Checkout in time.
The user cannot log on to another PoS system until all receipts from the original PoS system have been
successfully transferred to SAP Customer Checkout manager.
To resolve the issue, the user in the original PoS system has to log on and log off successfully once.
However, if this is not possible because a hardware error has occurred (for example, hard disk is defective), you
can adjust the drawer status manually in SAP Customer Checkout.
Procedure
 Caution
Manually adjusting the drawer status can lead to inconsistent data and is to be avoided. When logging off
the PoS system, all drawer data that has not been transferred (for example, sales documents) is
transferred to SAP Customer Checkout manager. If this step is bypassed by adjusting the drawer status
manually, receipts might never be transferred to SAP Customer Checkout manager and will then be
missing during day-end closing.
1. Log in to SAP Customer Checkout manager.

3. Select the drawer.
4. Select Change Status.
5. Select the status In Transit.

Results
It is now possible to log on again with the affected cash drawer.
5.4.19 Business object locks
The Business Object Locks application displays all business objects that are currently locked. Locked business
objects can be unlocked manually.
The following business objects are displayed in this application:
● Parked Receipts
If the Enable central receipt parking option is activated in SAP Customer Checkout, parked receipts are
transferred to SAP Customer Checkout manager. All SAP Customer Checkout applications for which the
"central receipt parking" feature is activated can resume the parked receipts transferred to SAP Customer
Checkout manager.
Once a parked receipt is resumed, it is blocked for other SAP Customer Checkout applications. If the
relevant receipt is parked once again in SAP Customer Checkout, its block is removed.
● Day-End Closings
If central drawer management is enabled in SAP Customer Checkout, day-end closing that has been
started can only be completed or canceled in the same PoS system. During the day-end closing process,
the corresponding business object is locked and displayed in this application.
Once the day-end closing process has been completed or canceled, the lock on the day-end closing is
removed.
If an error occurs during day-end closing in SAP Customer Checkout that prevents the closing (for
example, a hardware error destroys the hard drive), the business object lock can be removed manually to
perform day-end closing in another PoS system.
Select the "Delete" icon next to the block to manually remove blocks in SAP Customer Checkout manager.
 Caution
Once the lock on a parked receipt has been removed manually, the receipt can be resumed and posted by
other PoS systems. Should two different POS systems post the same resumed receipt, one of the receipts
is rejected as duplicate by SAP Customer Checkout manager. This causes a deviation upon cash desk
closing, requiring manual approval.
5.5 Loyalty Management
In loyalty management, all applications that can be used for awarding and processing loyalty points are
summarized.

5.5.1 Coupons
Coupons are a type of voucher for buying special sales items or articles at a reduced price.
On the Coupons tile, you can centrally manage the coupons purchased by your registered loyalty users, or
coupons handled as discounts, in quick service mode. You can display an overview of all your coupons, assign
discount rules to a coupon, and edit, create, find, or cancel a coupon.
When using coupons in SAP Customer Checkout, take the following into account:
● Using coupons for the loyalty API

Loyalty users can buy coupons after collecting a certain number of loyalty points. In SAP Customer
Checkout manager, you can specify the number of loyalty points needed to purchase each coupon. Once
loyalty users have collected the relevant number of loyalty points, they can buy the coupon.
● Use coupons in quick service mode
In quick service mode, coupons can be applied to sales items and to receipts. You can apply coupons only if
the discount rules have been maintained on the Coupons tile.
The following options are available on the Coupons tile:
Coupon Options
Option Description
Sort Lets you sort coupons by the following:
● ID
● Status
● Title
● Valid from
● Valid to
● No
Filter Lets you filter coupons by the following:
● ID
● Status
● Title
● Valid from
● Valid to
Create New Coupon Lets you create a new coupon.
When you select a coupon, additional tabs with detailed information about each of the coupons are displayed:
Option Description
Details Displays general information such as general data, price, val

idity information, and administrative data of the coupon.

Option Description
Articles Shows the articles (from your SAP ERP system) that are as
signed to the respective coupon.
 Note
This tab is only relevant when a coupon is used for the
loyalty API.
Instance IDs Generates valid coupon IDs for the respective coupon to be
used in SAP Customer Checkout.
 Note
This tab is only relevant when you are using a coupon in
quick service mode in SAP Customer Checkout.
Discount rules Enables you to set discount rules to be used for the respec
tive coupon.
 Note
This tab is only relevant when you are using a coupon in
quick service mode in SAP Customer Checkout.
Details Tab
Field Description
ID Unique identifier that is set when the coupon is created
Type Shows the type of coupon to be handled in SAP Customer

Checkout.
The following coupon types are available:
● App: The coupon is used for the loyalty API and loy
alty users can buy the coupon after collecting a cer
tain number of loyalty points.
● Coupon: The coupon can only be used in quick serv
ice mode and is handled as a coupon on a sales item
in SAP Customer Checkout.
Title Name of the coupon

Field Description
Discount purpose code Discount purpose code to be set for the coupon
 Note
This field is only relevant when Coupon has been se
lected as coupon type.
Offline available Specifies whether the coupon can be used when SAP Cus
tomer Checkout application is in offline mode.
Description Description of the coupon
Price in points The number of loyalty points that loyalty users must pay
for the coupon.
 Note
loyalty API.
Coupon can be combined in the receipt Active
The coupon can be applied in combination with other cou

pon types in a receipt.
Inactive
The coupon type cannot be used together with other cou

pon types in a receipt.
Only valid with instance ID Indicates that the respective coupon can only be used
when a valid coupon ID has been generated on the
Instance ID tab.
Usage per instance ID Displays how many times the valid coupon ID can be used.
Allowed purchase per account Displays how many times each coupon can be redeemed
per loyalty user account in SAP Customer Checkout
 Note
loyalty API.

Field Description
Tansaction qty. Indicates how many times the coupon can be redeemed in
total
 Note
loyalty API.
Valid from Earliest date that the coupon can be purchased by loyalty
users
 Note
loyalty API.
Valid to Final date that the coupon can be purchased by loyalty

users
 Note
loyalty API.
Redeemable from Earliest date that the coupon can be redeemed
 Note
loyalty API.
Redeemable to Final date that the coupon can be redeemed
 Note
loyalty API.

Field Description
Status Indicates the status of the coupon. The following statuses

are available:
● Draft: The coupon is still in draft mode and cannot be

used in SAP Customer Checkout, or purchased by
loyalty users.
● Active: The coupon can be used in SAP Customer
Checkout and can be purchased and redeemed by
loyalty users.
● Inactive: The coupon cannot be used in SAP Cus
tomer Checkout or redeemed by loyalty users.
Created by User name of the user who created the coupon in SAP
Created at Date and time when the coupon was created
Changed by User name of the user who modified the coupon in SAP
Changed at Date and time when the coupon was modified
The Articles tab is only relevant when App is set as coupon type.
Articles Tab
Field Description
Article number Article number from your SAP ERP system
Relative Relative discount value to be used for the respective article
Absolute Absolute discount value to be used for the respective article
Instance IDs Tab
Field Description
Instance ID Unique ID that is generated as coupon ID to be used for the

respective coupon
Status Status of the coupon ID

Field Description
User name Username of the user who redeemed the coupon in SAP
Customer Checkout
 Note
This field is only relevant when App is set as coupon
type.
Name Name of the user who redeemed the coupon in SAP Cus
tomer Checkout
 Note
This field is only relevant when App is set as coupon
type.
The Discount rules tab is only relevant when the coupon type is set to Coupon.
Discount rules Tab
Field Description
ID Unique identifier of the discount rule that can be set man

ually
Rule Discount rule to be used when the respective coupon is se

lected in SAP Customer Checkout.
You can specify the discount rules for articles, groups of arti
cles, or receipts, and when doing so, select a discount.
The following discount rule types can be selected and ad

justed as follows:
● 100% for the most expensive article of all article groups

(Relative discount for the most expensive or cheapest
article of all or specific article groups)
● 5% on all articles
(Absolute (in local currency) or relative discount for all
articles that belong to a selection of articles)
● 0.50 discount in local currency on receipt
(Absolute (in local currency) or relative discount on the
receipt)
● 5% on all article groups
(Absolute (in local currency) or relative discount for all
article groups that belong to a selection of article
groups)

5.5.1.1 Creating a Coupon
Context
Coupons purchased from loyalty users and redeemed in SAP Customer Checkout can be created centrally in
SAP Customer Checkout manager. You can also create coupons that can be used in Quick Service mode in SAP
Customer Checkout.
Procedure
1. Choose Create New Coupon.

2. Select the coupon type to be created, and enter the coupon data.
3. To save the coupon, click Save.
5.5.1.2 Editing a Coupon
Context
In SAP Customer Checkout manager, you can manually edit existing coupons. For example, you may want to
change the quantity for sale, extend the validity date, or change the discount rules of a coupon.
Procedure
1. Select the coupon you want to edit, and choose Edit.

2. Edit the coupon data as needed.
 Note
When using the coupon for the Loyalty API, you might want to add an image to your coupon. To add an
image, choose Upload new image and select the image you want to be displayed for the coupon.
3. Click Save.

5.5.1.3 Setting Discount Rules for a Coupon
In quick service mode, coupons can be applied to articles, sales items, and the receipt. Therefore, you need to
set discount rules to be used with the respective coupon.
Procedure
1. Select the coupon for which you want to set a discount rule, and choose the Discount rules tab.
2. Click Create rule.
3. You can enter an ID for the discount rule and select a template to be used.
 Note
You can edit all entries marked in blue.
 Note
When you synchronize a coupon in SAP Customer Checkout, discount rules assigned to a coupon are
also synchronized.
 Caution
You can also deactivate and delete discount rules from coupons. You can also delete discount rules for
a coupon if the coupon is in status ACTIVE.
To deactivate a discount rule, do the following:
1. Select the discount rule that you want to deactivate.

2. Choose Deactivate, and confirm the deactivation with OK.
3. The status of the discount rule will be shown as INACTIVE.
5.5.1.4 Generate an Instance ID for a Coupon
You need to generate valid instance IDs in the SAP Customer Checkout manager to use coupons in SAP
Customer Checkout.
Context
The following two scenarios are possible:
● When using coupons for the Loyalty API, you do not need to generate the coupon IDs manually. When
loyalty users purchase the coupon from the coupon shop, a valid coupon ID is generated by the system.

● When using coupons for the Quick Service mode, you have to generate the coupon IDs manually in SAP
Customer Checkout manager in order to use them in the POS system.
 Note
Before you generate an instance ID to use the coupon in SAP Customer Checkout, make sure that you set a
discount rule for the respective coupon.
Procedure
1. Select the coupon for which you want to generate an instance ID, and choose the Instance IDs tab.
2. Choose Generate, and Execute to proceed.
3. The instance ID is shown in the list and can be used in SAP Customer Checkout.
 Note
In the quick service mode, you will find an entry per coupon ID.
5.5.2 Point Assignments
In SAP Customer Checkout manager, you can centrally assign loyalty points to loyalty users.
Loyalty points can be assigned to loyalty users created in SAP Customer Checkout manager as well as to
loyalty users registered via the loyalty API. You can assign loyalty points for a specific event or reason, display
an overview of the latest loyalty points you have assigned, or cancel the assignment of loyalty points.
The following sections are available on the Point Assignments tile:
Assigning Loyalty Points – Options
Option Description
Assign Loyalty Points to All Users Enables loyalty points to be assigned to all loyalty users reg
istered in the loyalty API and to loyalty users that were cre
ated directly in SAP Customer Checkout manager.
Assigned Loyalty Points Provides you with an overview of the assigned loyalty points

5.5.2.1 Assigning Loyalty Points to All Users
Context
If you want to assign loyalty points to all loyalty users, you can do it centrally in the SAP Customer Checkout
manager. For example, you might assign loyalty points to everyone for special events or campaigns related to
your company.
Procedure
1. In the Assign Loyalty Points to all Users section, enter a reason for the assignment.
2. Enter the number of points.
3. To assign loyalty points to all loyalty users created in SAP Customer Checkout or to all loyalty users
registered via the loyalty API, choose Assign points.
Details
Field Description
Reason Reason for the assignment of loyalty points
Process ID ID of the process executing the assignment of loyalty

points
Execution start Displays the date and time when the loyalty points were
assigned to all loyalty users.
Execution done Shows when the assignment process for loyalty points
was completed
Points Shows the number of loyalty points that you have as
signed for this transaction
Execution state Displays the process status
○ Idle
○ Running
○ Void
○ Completed

Field Description
Execution result Indicates if the loyalty points have been assigned success
fully.
Possible results are:
○ No
○ Void
○ Successful
○ Errors
○ Fatal
Status message Shows the number of loyalty users already processed
Cancel worker Enables the cancelation of the assigned loyalty points
5.5.3 Loyalty Users
Using the Loyalty Users tile, you can manage loyalty users registered via the Loyalty API and loyalty users
created in SAP Customer Checkout. You can keep track of your loyalty users, analyze their history, assign
loyalty points manually to individual loyalty users, and search, lock, or delete a loyalty user.
The loyalty users displayed by SAP Customer Checkout manager are either loyalty users created in SAP
Customer Checkout manager or loyalty users created via the loyalty API.
 Caution
Loyalty users within SAP Customer Checkout manager do not represent the customers stored in your ERP
system or in the SAP Customer Checkout application.
You require authorization for the SAP Event Ticketing system to create the loyalty users registered via the
Loyalty API in the existing ERP system.
For more information about loyalty user authorization, see Security [page 58].
If you are using loyalty management in conjunction with the Loyalty API, loyalty users can register directly via
the loyalty API when creating a new account.
Select the Loyalty Users tile to see an overview of all of the registered loyalty users and detailed information
about each of their accounts. You can also search for loyalty users and sort or filter the list of loyalty users.
The detailed information view of a loyalty user account is divided into the following sections:
Loyalty User Options
Option Description
Details General information on loyalty users, such as the username

and ID

Option Description
Identities Shows the user ID and how loyalty user identification was
authorized
Coupons Overview of coupons purchased and redeemed by loyalty

users
History Overview of the loyalty user’s transactions
Details
Field Description
Public ID Public identification number that is automatically created for

the loyalty user
Loyalty account ID Identification number of the loyalty account that is assigned

to the loyalty user
Barcode Barcode that is automatically generated when the loyalty

user is created
User name E-mail address of the loyalty user
Last name Last name of the loyalty user
First name First name of the loyalty user
Date of birth Date of birth of the loyalty user
App token available Specifies that a loyalty user has already been registered and
has a valid app token.
Leading system Specifies the system in which the loyalty user was created
and is managed.
Possible values:
● SAP Customer Checkout manager

● SAP Event Ticketing
Created by User name of the loyalty user in SAP Customer Checkout

manager who created the user.
 Note
If the loyalty user has been authorized through a third-
party system (SAP Event Ticketing), this field remains
empty.
Created At Date and time when the loyalty user was created

Field Description
Changed By User name of the user who modified the user in SAP Cus
 Note
If the loyalty user has been authorized through a third-
party system (SAP Event Ticketing), this field remains
empty.
Changed At Date and time when the loyalty user was modified
Consent given and maintained Indicates whether the loyalty user has given consent for their
personal data to be processed.
 Note
essing of personal data for this loyalty user. The selection is
optional.
Identities
Field Description
Name of the identity provider Name of the third-party system that has authenticated the
loyalty user. Possible identity provider names are as follows:
● SAP Event Ticketing
 Note
If SAP Customer Checkout manager is used for manag
ing the loyalty users, this field remains empty.

Field Description
Value ● ID of the loyalty user in the third-party system
 Note
ing the loyalty users, this field contains the customer
number.
To subsequently link a customer to a loyalty user, create

a new identity and enter the customer number as the
value.
Value two ID of the ERP system
 Note
ing the loyalty users, this field remains empty.
Coupons
Field Description
Instance ID Instance ID of coupon purchased or redeemed by the loyalty

user
ID ID of coupon purchased or redeemed by the loyalty user
Title Name of coupon purchased or redeemed by the loyalty user
Valid from Validity date from when the coupon can be purchased by the
loyalty user
Valid to Validity date until when the coupon can be purchased by the
loyalty user
Status Indicates whether the coupon has been redeemed
History
Field Description
Transaction Name and ID of the transaction
Date Date and time of the transaction

Field Description
Select an action Generic action description
Possible actions are as follows:
● Create loyalty account

● Redeem coupon
● Purchase coupon
● Redeem points
● Add points
● Add loyalty item
● Bind receipt
● Unbind receipt
ID ref. Internal action ID reference
Created by User name of the user who created the transaction in SAP
Point value Number of loyalty points assigned for this transaction
Value Value displayed depending on the action selected
5.5.3.1 Blocking a User
Context
You can block a loyalty user in SAP Customer Checkout manager if you want to ensure that the user cannot
perform transactions in SAP Customer Checkout such as purchasing coupons, collecting bonus points in SAP
Customer Checkout, or redeeming coupons.
Procedure
1. In Loyalty Users, select the loyalty user that you want to block, and choose Block User.
2. Confirm that you want to block the loyalty user by clicking OK.

Results
The loyalty user is now blocked and cannot perform further transactions within the Loyalty API.
5.5.3.2 Deleting a User
Context
You can anonymize loyalty users. This means that all of the personalized data of this loyalty user is overwritten.
When you anonymize a loyalty user, it is not deleted from the SAP Customer Checkout manager database but
set to "anonymous".
Procedure
1. Select the loyalty user that you want to anonymize and then choose the Delete user icon.
2. Confirm the anonymization of the respective loyalty user by clicking OK.
Results
The loyalty user is now anonymized and can no longer be identified.
5.5.3.3 Correcting Loyalty Points for Individual Loyalty

Users
Context
In SAP Customer Checkout manager, you can correct the number of loyalty points collected by loyalty users.
You can either add or subtract loyalty points.

Procedure
1. In Loyalty Users, select the loyalty user for which you want to edit the number of loyalty points, and then
choose Correct loyalty points.
2. Choose Add or Subtract.
3. Enter the number of loyalty points that you want to add or subtract.
4. Choose OK to save your changes.
5.5.3.4 Linking Loyalty Users to Customers
Loyalty users can be subsequently linked to one or more customers.
Context
On the Identities tab, you can link loyalty users to customer as well as edit or delete links.
To link a loyalty user to a customer, proceed as follows:
Procedure
1. Open the Loyalty Users tile.

2. Select the loyalty user that you want to link to a customer.
3. Choose the Identities tab and then click Add.
4. Enter the customer number of the customer in the Value input field.
5. Choose Save.
Results
The loyalty user is now linked to the customer.

5.5.3.5 Purchasing Coupons for Loyalty Users or Assigning
Coupon Instance IDs to Loyalty Users
In SAP Customer Checkout manager you can purchase a coupon for a loyalty user or assign an instance ID of a
coupon to a loyalty user. In addition, you can return coupons of loyalty users, revoke assignments, or change
the status of a coupon.
1. Open the "Loyalty users" tile.

2. Select the user for whom you want to purchase a coupon or to whom you want to assign an instance ID.
3. Select the Coupon tab and choose one of the following options:
○ Buy: Points for the coupon purchase are deducted from the loyalty user's account.
○ Assign: The coupon instance ID is assigned to the loyalty user. The number of points remains the
same.
4. Enter the relevant information and confirm with Save.
5.5.4 Promotion Code
Promotion codes contain a value in points that can be used by the loyalty users for special marketing or
promotion campaigns within an organization. Loyalty users scan the promotion code and collect loyalty points.
 Note
Promotion codes are only available for loyalty users registered and created via the Loyalty API.
On the Promotion Code tile, you can centrally manage promotion codes that are used by your registered loyalty
users. You can see an overview of all your promotion codes, and you can edit, create, search, or cancel a
promotion code.
You can select different options on the Promotion Code tile:
Promotion Code Options
Option Description
Sort Lets you sort promotion codes by the following:
● Description
● Status
● Valid from date
● Valid to date
● Value in points
● None

Option Description
Filter Lets you filter promotion codes by the following:
● Description
● Status
● Valid from date
● Valid to date
● Value in points
Create new promotion code Lets you create a new promotion code.
The Promotion Code section displays the following details:
Coupons
Field Description
Code ID of the promotion code that can be set manually
 Note
When creating a new promotion code, the system au
tomatically inserts the prefix L in the ID.
 Caution
The barcode of the promotion code is not generated
in the SAP Customer Checkout manager; you create it
with an external barcode generator.
Description Brief description of the promotion code
Value in points Number of loyalty points assigned to the promotion code
Valid from Earliest date from which the promotion code can be re
deemed
Valid to Latest date on which the promotion code can be re

deemed
Quantity per account Displays how many times each promotion code can be re
deemed per loyalty user account
Tansaction qty. Indicates how many times the coupon can be redeemed in
total

Field Description
Status Indicates the status of the promotion code. The following

statuses are available:
● Draft: The promotion code is still in draft mode, and

cannot be used or redeemed by loyalty users.
● Active: The promotion code can be purchased by loy
alty users and redeemed.
● Inactive: The promotion code cannot be used or re
deemed.
● Deleted: The promotion code is deleted and cannot
be activated or edited.
Created by User name of the user who created the promotion code in
Created at Date and time when the promotion code was created
Changed by User name of the user who modified the promotion code
in SAP Customer Checkout manager
Changed at Date and time when the promotion code was modified
5.5.4.1 Creating a New Promotion Code
Context
In the SAP Customer Checkout manager, you can create new promotion codes that can be used and redeemed
by loyalty users to collect loyalty points.
Procedure
1. In the Promotions Code tile, click the Add icon.

2. Enter the promotion code information.
3. To save the promotion code, click Save.

5.5.4.2 Editing a Promotion Code
Context
In the SAP Customer Checkout manager, you can edit existing promotion codes. For example, you may want to
change the quantity for sale or extend the validity date of a promotion code.
Procedure
1. Select the promotion code you want to edit, and choose Edit.
2. Edit the promotion code data as needed.
5.5.5 Loyalty Reports
On the Loyalty reports tile, you generate period-specific reports for transactions in connection with the loyalty
API and loyalty management in SAP Customer Checkout manager. For example, you can generate reports to
check who your top loyalty users are, or which coupons are used in various SAP Customer Checkout
applications, loyalty points transactions, or scan transactions.
On the Loyalty reports tile, you can view reports or download report files (as a Microsoft Excel file). You can
generate the following reports:
● All-in-One: creates an all-in-one report that includes reports on coupons, coupons per time, points, sales
with loyalty users, scans, top loyalty users, and new loyalty users.
 Note
The Maximum number of hits option only refers to reports on top loyalty users.
● Coupon: generates reports for all app coupons that were purchased, redeemed, or returned in SAP
Customer Checkout, or coupons that are open and have not yet been redeemed in SAP Customer
Checkout.
● Coupon per time: generates reports for all app coupons in the specified time period that were purchased,
redeemed, or returned in SAP Customer Checkout, or coupons that are open and have not yet been
redeemed in SAP Customer Checkout.
● Points: generates reports for points by one time tickets, points by season tickets, points by promotion
codes, points by sales, points by coupons, and the amount of overall points.
● Receipts with loyalty users: generates reports for sales receipts where a loyalty user was added to the
receipt.
● Scan: generates reports for scan transactions related to the Loyalty API, for example scan of one-time
tickets, scan of season tickets, or scan of promotion codes.

● Top Loyalty Users: generates reports of your top users, and the amount of points of each loyalty user.
 Note
On this tab, an additional field Maximum number of hits lets you specify the amount of hits that you
want to be shown in the report.
 Caution
Setting a high maximum number of hits can cause performance issues.
● New Loyalty Users: generates reports for the new loyalty users that have been added in a specified time
period.
● Active Loyalty Users: Generates reports for active loyalty users, in the basis of their actions (e.g. regular
purchases, coupon purchases, redeeming coupons, and earning points using tickets).
5.5.5.1 Generate Loyalty Reports
Procedure
1. In the Loyalty Reports tile, choose a loyalty report type.

2. Enter or select the Period Start and Period End for the loyalty report.
 Note
SAP Customer Checkout provides a default period time: Period End is the current date and Period Start
is one prior to the current date.
3. Choose Download (or Go) to start generating the loyalty report.
A Microsoft Excel file with the selected loyalty report is downloaded (or the sales report is shown in the UI).
5.5.6 Loyalty Configuration
In SAP Customer Checkout manager, you can edit the loyalty configurations that are used for processing and
administration in loyalty management. If you are using the loyalty API in conjunction with SAP Event Ticketing,
you can set up events affiliated with your company and define certain actions for loyalty users.
 Example
If your company is in the Sports and Entertainment line of business, and you have integrated a mobile
application for your loyalty users, you can configure a loyalty-point transaction and specify the number of
loyalty points that loyalty users can earn or that can be purchased per ticket.

 Note
To use loyalty management with loyalty users created in SAP Customer Checkout manager, you only need
to maintain the fields in the General Data section. To use the Loyalty API and the connection to SAP Event
Ticketing, you also need to maintain the fields in the SAP Event Ticketing section.
On the Details tab, you can create, activate, deactivate, edit, and delete loyalty configurations. The following
information is available:
General Data
Option Description
Name Name of the loyalty points transaction
Description Description of the loyalty points transaction
Loyalty points per currency unit spent

 Note
This value is only used for the calculation if the remote
standard logic value is set for the points calculation in
Indicates the exchange rate of the currency used in SAP

Customer Checkout for loyalty points.
 Example
In the following example, it is assumed that SAP Cus
tomer Checkout uses euro as the currency. If you select
the value 10 for this field, 10 loyalty points are credited
per euro spent for sales.
Points for registration Displays the amount of loyalty points that are assigned to
loyalty users during registration
Description for registration Description shown when the loyalty user registers to the Loy
alty API
SAP Event Ticketing
Option Description
Season ticket event ID Event ID for which the season ticket is maintained in the SAP
Event Ticketing system
Season ticket default event ID Default booklet event ID in the SAP Event Ticketing system
Overall point cap Maximum number of points that a loyalty user can have.
Points for season ticket Amount of loyalty points that is defined for the purchase of a
season ticket

Option Description
Point cap for tickets Maximum amount of loyalty points that can be collected by
the purchase or scanning of tickets.
 Example
When you have set a Point Cap for Tickets of 900, your
loyalty users cannot collect more than 900 loyalty
points through the ticket scan or by ticket purchase.
Maximum ticket scans per day Displays how many tickets can be scanned per day
Maximum ticket scans per event Displays how many tickets can be scanned per event
Maximum ticket scans per account Displays how many tickets can be scanned per loyalty user
account
Administrative Data
Field Short Description
Status Shows the status of the loyalty configuration
● Active
● Idle
Created by Username of the user who created the loyalty-point transac

tion in SAP Customer Checkout manager
Created at Date and time when the loyalty-point transaction was cre
ated
Changed by Username of the user who modified the loyalty-point trans

action in SAP Customer Checkout manager
Changed at Date and time when the loyalty-point transaction was modi
fied
 Note
Only one loyalty configuration can be set to "Active".
If you are using the SAP Event Ticketing system, you can assign the loyalty configuration to events on the
Events tab. You can create, edit, and delete events.

The following information is available:
Events
Option Description
Event Name of the event
Ticket event ID ID for this event in the SAP Event Ticketing system
Start time Displays the event start date and time
End time Displays the event end date and time

6 Integrate SAP Customer Checkout
Manager with SAP Customer Checkout
In SAP Customer Checkout, you can integrate the SAP Customer Checkout manager application.
 Note
You have to integrate the SAP Customer Checkout manager application into SAP Customer Checkout when
using the voucher management features of SAP Customer Checkout manager.
To use the SAP Customer Checkout manager voucher module, you need to go to your SAP Customer
Checkout system and select the Integration subtab of the Configuration tab. Follow the steps described in
the Integration Guide of SAP Customer Checkout.
After you have set the SAP Customer Checkout manager voucher module in your SAP Customer Checkout
application, do a voucher synchronization to update all vouchers.
 Note
With release 2.0 of SAP Customer Checkout manager, you can only use the voucher management in
SAP Customer Checkout, if you are using the voucher management provided by SAP Customer
Checkout manager. The functionality to collect and redeem loyalty points through SAP Customer
Checkout is not yet supported in version 2.0

226 CUSTOMER Integrate SAP Customer Checkout Manager with SAP Customer Checkout
7 Using SAP Customer Checkout Manager
as the Backend System
With SAP Customer Checkout 2.0 Feature Pack 01, the SAP Customer Checkout manager can also be used as
the back-end system for SAP Customer Checkout.
When using the SAP Customer Checkout manager as the back-end system for your SAP Customer Checkout
applications, you need to perform the following steps:
● Configure and create data in the SAP Customer Checkout manager

● Configure initial settings in SAP Customer Checkout
● Maintain relevant settings in SAP Customer Checkout
 Caution
The SAP Customer Checkout manager cannot replace an SAP ERP system. Functionality is limited in
some areas, for example, financial accounting functions.
7.1 Configure and Create Data in SAP Customer Checkout

manager
To use the SAP Customer Checkout manager as your back-end system, you need to maintain settings for
articles, price lists, tax codes, and currencies, which will be used in your SAP Customer Checkout applications.
For example, you first need to create the articles and price lists in the SAP Customer Checkout manager, in
order to be able to add them into a receipt in your SAP Customer Checkout applications.
For more information, see Articles [page 134], Price Lists [page 146], and POS Configuration [page 151].
7.2 Initial Configuration Settings in SAP Customer

Checkout
When you start SAP Customer Checkout for the first time, you need to configure the SAP Customer Checkout
manager as the back-end system in the initial settings.
Prerequisites
You have the following information:

Using SAP Customer Checkout Manager as the Backend System CUSTOMER 227
● The POS system ID, which has to be applied in the installation. Each POS system must have a unique POS
system ID.
● The service endpoint information of the SAP Customer Checkout manager.
Procedure
1. Start SAP Customer Checkout by double-clicking the SAP Customer Checkout shortcut on the desktop
or by selecting SAP Customer Checkout from the Windows Start menu.
2. In the Initial Configuration screen, enter <4-digit POS system ID>
3. Select the SAP Customer Checkout manager to be used as the type of ERP system for this SAP Customer
Checkout application to communicate with.
4. Enter all relevant service endpoint information for the SAP Customer Checkout manager.
5. Enter and confirm the Password for the Admin user. This is the default user with the ADMINISTRATOR role.
The system sets the same password for the RAdmin user.
6. Enter and confirm the Keyword for processing configuration files.
7. Enter and confirm the Database Password.
8. To finish the initial configuration, choose OK.
7.3 Maintain Relevant Settings in SAP Customer Checkout
Configure additional settings in SAP Customer Checkout, to adapt the application to your requirements.
For more information about the configuration settings in SAP Customer Checkout, see the SAP Customer
Checkout Configuration Guide.
 Note
When the SAP Customer Checkout manager is the back-end system, central receipt management is
activated. All receipts posted in SAP Customer Checkout are sent to the SAP Customer Checkout manager.

228 CUSTOMER Using SAP Customer Checkout Manager as the Backend System
8 Using SAP Customer Checkout manager
in Multi-Tenant Mode
You can operate SAP Customer Checkout manager in multi-tenant mode. This means that an instance of SAP
Customer Checkout manager is installed and functions as master tenant. With this you can administrate
multiple tenants with their own database.
Each tenant has its own database with its own logic.
 Example
Example: You may have three different customers with their own database (= own tenant), but sharing an
instance of SAP Customer Checkout manager.
Potential advantages of multi-tenant mode include:
● Single Apache Tomcat Web server

● Single SAP Customer Checkout manager installation
● Use of multiple tenants with their own database
● Single SAP JVM installation
Using SAP Customer Checkout manager in multi-tenant mode requires the following steps:
● Once-only installation of master tenant in SAP Customer Checkout manager. For more information, see
Initial Configuration of SAP Customer Checkout manager [page 230]
● Configuration of master tenant and creation of required number of tenants. For more information, see
Tenants [page 51]
● Individual login to and configuration of each tenant
● Installation of SAP Customer Checkout and interconnection with the required tenant. For more
information, see SAP Customer Checkout Installation and Update Guide (under "Setting Up the Initial
Configuration") and SAP Customer Checkout Configuration Guide (under "SAP Customer Checkout
manager Integration").
 Note
When using SAP Customer Checkout manager in multi-tenant mode, please note the following:
● The start process for SAP Customer Checkout manager may take more time if you are operating
multiple tenants.
● Database updates are performed at startup.
● Error and default logs for the tenant are stored in the master tenant's log file. The ID of the tenant from
which the log information derives is listed.
● Once you shut down the master tenant, all associated tenants are also shut down.

Using SAP Customer Checkout manager in Multi-Tenant Mode CUSTOMER 229
9 Initial Configuration of SAP Customer
Checkout manager
Context
When you start SAP Customer Checkout manager for the first time, you need to configure some initial settings.
Procedure
 Note
Note that the last part of the URL that you enter is case sensitive. The last part must match the file name
(without the extension) of the .war file.
1. In a Web browser, enter the following URL: <server name>:<port>/ccos (if you used ccos as the .war
file name).
2. On the setup screen that opens, enter some initial configuration data.
3. Select the respective database driver type to be used for SAP Customer Checkout manager:
○ If the selected database driver type is Apache Derby Embedded, proceed as follows:
1. In the Database Connection String box, enter the location of the file system where you want the
Apache Derby database to be created (for example, enter jdbc:derby:%APP_HOME%/
CCOSDB;create=true).
2. Enter a name in the Database Schema Name field, or leave it empty (default).
3. Enter the Database User and Database Password. The embedded database will be created during
system initialization
 Recommendation
○ If the selected database driver type is Microsoft SQL, proceed as follows:

1. In the Database Connection String field, add the server address and database name (for example,
enter jdbc:sqlserver://[server addr]:1433;databaseName=[database name]).
3. Enter the Database User and Database Password.
○ If the selected database driver type is SAP HANA, proceed as follows:
1. Add the server address in the Database Connection String field (for example, enter jdbc:sap://
[server addr]:30015; the port 30015 has the format 3<instance number>15).

230 CUSTOMER Initial Configuration of SAP Customer Checkout manager
3. Activate the field Automatically create schema (if non-existent) if the database schema with the
entered name is to be created automatically.
 Caution
This function is intended to simplify the setup of the database connection for test purposes. A
database user with system authorizations is required to create the schema. A user of this type
has other authorizations that go beyond the authorization for pure database access and are
not required.
For security reasons, it is recommended that for the connection to an SAP HANA database you
create your own user in the database management system, which only has the required
authorizations for the database connection.
4. Enter the Database User and Database Password.

○ If the selected database driver type is JNDI, proceed as follows:
1. Enter the JNDI lookup string in the Database Connection String field.
3. You can leave the Database User and Database Password fields empty.
4. Activate the Multi-Tenant Mode field if you want to use the SAP Customer Checkout manager in multi-
tenant mode.
 Note
For more information on multi-tenant mode, see Using SAP Customer Checkout manager in Multi-
Tenant Mode [page 229]
If you have activated multi-tenant mode, the SAP Customer Checkout manager will start in the master
tenant by default.
5. Enter and confirm the Admin User password for SAP Customer Checkout manager.
The Admin user is delivered with SAP Customer Checkout manager.
For information about requirements for the password policy, see Initial Password and Password Policy
[page 236].
6. Enter and confirm the hash key that is used to encrypt the password of the Database User.
For information about requirements for the hash key policy, see Initial Password and Password Policy [page
236].
7. To confirm your initial settings, choose OK. This process might take a few minutes.
When the initialization is complete, the login page for SAP Customer Checkout manager opens.

Initial Configuration of SAP Customer Checkout manager CUSTOMER 231
9.1 Resetting the Configuration
Context
You can reset the configuration settings of SAP Customer Checkout manager.
Procedure
1. Delete the configuration file that is stored in the config subfolder of your installation (located at
<drive>:\SAP\CustomerCheckout Central Server\config).
2. Restart the Java Application Server.
 Note
If you are using the CMIS repository, you have to delete the repository to reset the configuration. The
repository will be recreated automatically after the setup step is done.
3. In a Web browser, enter the following URL: <server_name>:<port>/ccos (if you have used "ccos" as name
for the .war file).

232 CUSTOMER Initial Configuration of SAP Customer Checkout manager
10 POS Security Regulation 2020 for
Germany
Since December 2019 in Germany, §146a AO was introduced by the law for protecting against manipulations of
digital basic records. As a consequence, as of 1/1/2020, when goods and services are sold, electronic POS
systems (electronic recording systems) in Germany must have a certified technical safety device/entity.
§146a AO includes the following sections, with which all companies must comply:
● Receipt printing obligation: Each POS system must print out receipts.
● Technical safety entity (TSE): Each POS system must be connected to a technical safety entity certified by
the BSI. This means that each receipt is signed to prevent manipulation in the POS system.
● Digital Interface of Cash Management for POS Systems (DSFinV-K): A unified digital cash management
interface for POS systems (structured data export) is necessary, which allows you to export all receipt data
in a specific format.
For more information about the POS Security Regulation 2020 and how to integrate TSEs into SAP Customer
Checkout, see the SAP Customer Checkout Configuration Guide.
In SAP Customer Checkout manager, you can generate a DSFinV-K file. For more information, see Data Export
for DSFinV-K Interface in SAP Customer Checkout manager [page 233]
10.1 Data Export for DSFinV-K Interface in SAP Customer

Checkout manager
SAP Customer Checkout manager enables you to export data for the DSFinV-K interface.
The DSFinV-K interface specifies a type of structured data export in a specific format (IDEA format). This
format is a legal requirement for enabling uniform data processing by tax authorities. For more information on
the DSFinV-K interface, see the SAP Customer Checkout Configuration Guide.
The data export is linked to day-end closing in the respective SAP Customer Checkout application. Before you
export the DSFinV-K file in SAP Customer Checkout manager, ensure that a day-end closing has occurred in
the respective POS.
● Open the Sales Summaries tile.

● Select the required closing and choose Generate DSFinV-K.
● The file download starts.
 Note
The generated .zip file contains a total of 20 documents.
These include the following:
○ 10 files for the single recording module (for example, document header data, line item data, tax
items)

POS Security Regulation 2020 for Germany CUSTOMER 233
○ 7 files for the master data module (at the time of day-end closing, the settings relevant for the
DSFinV-K interface are also exported; for example, tax rates)
○ 3 files for cash desk closing module (summary): This includes aggregated data, such as sales
volumes in cash, on credit card, etc.
○ TSE data (transactions_tse.csv)

234 CUSTOMER POS Security Regulation 2020 for Germany
11 POS Software Certification in Compliance
with NF 525 (France)
To comply with the certification requirements, logged technical events must not be deleted. This necessitates
additional configuration steps in SAP Customer Checkout manager.
Context
During the installation of SAP Customer Checkout manager, a job for deleting obsolete monitoring entries is
created automatically. By default, this daily job deletes all monitoring entries older than a week. The job has to
be configured to prevent any deletion of monitoring entries.
Procedure
1. Select the Configuration app and then the Configuration sub application.
2. In the "General" area, choose Edit.
3. Enter a value of 36500 into the Delete entries older than (in days) field.
4. Choose Save.
The deletion job for monitoring entries is executed with the new value the next time it is run.

POS Software Certification in Compliance with NF 525 (France) CUSTOMER 235
12 Security Guidelines and
Recommendations
This section describes security-related aspects for using the SAP Customer Checkout manager.
12.1 Initial Password and Password Policy
When you start SAP Customer Checkout manager for the first time, the initial configuration screen is displayed
and you have to create a password for the Admin User. Create a strong password. You can also change this
password later in SAP Customer Checkout manager by choosing Settings.
Note the following requirements for the Password Policy of the Admin User account:
● The password should have a minimum length of 8 characters

● The password should not be a dictionary word
● The password should not contain any part of the Admin User name in SAP Customer Checkout manager
● A mixture of the following three character types is an option:
○ Latin uppercase letters A, B, C ... Z
○ Latin lowercase letters a, b, c ... z
○ Westernized Arabic numerals or extended characters: 0, 1, 2, 3 ... 9
 Recommendation
You should not use the same password as for the SAP Customer Checkout application.
For the initial configuration of SAP Customer Checkout manager, you also have to create a hashkey, which used
to encrypt the password of the database user. Again, create a strong password here.
Note the following requirements of the hashkey:
● The hashkey should have a minimum length of 8 characters

● It should not be a dictionary word
● The hashkey should not contain any part of the Admin User name in SAP Customer Checkout manager
● A mixture of the following three character types is an option:
○ Latin uppercase letters A, B, C ... Z
○ Latin lowercase letters a, b, c ... z
○ Westernized Arabic numerals or extended characters: 0, 1, 2, 3 ... 9

236 CUSTOMER Security Guidelines and Recommendations
12.2 Resetting the Admin User Password
If you have forgotten or locked your password to log in to SAP Customer Checkout manager, you can reset your
password.
Context
You can only reset your password on the system where your SAP Customer Checkout manager is running.
Procedure
1. Open your web browser and enter the following URL: http://localhost:<port of the server>/
<path>/recover.html
 Note
Port of the server: Port number that you have set during the installation
Path: Path name to application (name of the .war file)
2. The Recovery Screen opens. Enter the following fields:
Recovery Screen Options
Option Description
Database Password Password of the database management system used for

New Admin Password New password that you want to assign for the Admin User
Confirm new Admin Password Confirmation of the newly assigned password for the Ad
min User
3. To confirm your changes, choose OK.

4. The admin user is now reset and you can log in to SAP Customer Checkout manager.
12.3 User Roles
SAP Customer Checkout manager is delivered with the following user roles by default: ADMINISTRATOR,
CASHIER, and SALESMANAGER

Security Guidelines and Recommendations CUSTOMER 237
If needed, you can create additional user roles in SAP Customer Checkout manager. For more information, see
Roles [page 39].
12.4 Firewall
To secure the SAP Customer Checkout manager application and keep your data safe from unauthorized
access, you can configure the firewall to reject uncertain outside connections or accept only specific incoming
connections.
It is important to configure a firewall because SAP Customer Checkout manager can be integrated with SAP
Event Ticketing. This means that the firewall has to be configured in such a way that an outgoing connection
from the application to SAP Event Ticketing is possible and not rejected (port 80/443).
If you have also integrated a mobile application to SAP Customer Checkout manager, you need to secure the
application for incoming connections. Your firewall has to be configured in such a way that an incoming
connection from outside is possible and not rejected.
Possible incoming connections might be from the following:
● The Loyalty API

● SAP Customer Checkout system
12.5 Auto Logout
SAP Customer Checkout manager has an automatic log out time of ten minutes, after which the Admin User is
automatically logged out if the application is not actively used.
Auto logout is provided by SAP out-of-the-box and cannot be modified.
12.6 Secure Connections
We recommend using content encryption for client-server communications. Enable HTTPS connections on the
application server, where the application is deployed. Check if a secure connection is used by looking at the
protocol in the browser URL. A secure connection starts with https:// instead of http://.
12.7 Virus Scanner
We strongly recommends that you install antivirus software on the application platform operating system.

238 CUSTOMER Security Guidelines and Recommendations
12.8 Software Updates
Context
To protect SAP Customer Checkout manager from vulnerabilities, keep the software and operating system up
to date. To install the Java Application Server, Apache Tomcat Version 8.5 or above is recommended, for the
latest information, see the Product Availability Matrix, under http://service.sap.com/sap/support/pam .
To keep the software up to date, you can download the latest software version from SAP Service Marketplace.
Software updates are provided as a new Web Application Archive for the SAP Customer Checkout manager
application.
Procedure
1. Download the latest version of SAP Customer Checkout manager from SAP Service Marketplace.
2.  Caution
During an update, the SAP Customer Checkout manager cannot be accessed.
Rename the SAP Customer Checkout manager .war file to the same name as your currently installed
application and copy the .war file into the webapps subfolder of your Apache Tomcat server (located in C:
\Program Files\Apache Software Foundation\Tomcat 8.5)
3. Start your updated SAP Customer Checkout manager application.

Security Guidelines and Recommendations CUSTOMER 239
Important Disclaimers and Legal Information
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:
● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such
links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.
Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within
the control or responsibility of SAP.
Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.
Gender-Related Language
We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.

240 CUSTOMER Important Disclaimers and Legal Information
Important Disclaimers and Legal Information CUSTOMER 241
www.sap.com/contactsap
© 2020 SAP SE or an SAP affiliate company. 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 SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.
Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.
SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.
Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.
THE BEST RUN

Guide CCO Server EN

Uploaded by

Copyright:

Available Formats

Guide CCO Server EN

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Guide CCO Server EN

Uploaded by

Copyright:

Available Formats

CUSTOMER

SAP Customer Checkout 2.0 Feature Pack 09

SAP Customer Checkout manager Guide

THE BEST RUN

1 SAP Customer Checkout Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2 What You Can Do with SAP Customer Checkout Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

3 Installing SAP Customer Checkout manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

4 Updating SAP Customer Checkout manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

5 Working with SAP Customer Checkout Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

SAP Customer Checkout manager Guide

7 Using SAP Customer Checkout Manager as the Backend System. . . . . . . . . . . . . . . . . . . . . . 227

8 Using SAP Customer Checkout manager in Multi-Tenant Mode. . . . . . . . . . . . . . . . . . . . . . . 229

9 Initial Configuration of SAP Customer Checkout manager. . . . . . . . . . . . . . . . . . . . . . . . . . . 230

10 POS Security Regulation 2020 for Germany. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

11 POS Software Certification in Compliance with NF 525 (France). . . . . . . . . . . . . . . . . . . . . . 235

12 Security Guidelines and Recommendations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

SAP Customer Checkout manager Guide

SAP Customer Checkout manager Guide

SAP Customer Checkout manager Guide

SAP Customer Checkout manager helps you with:

● Voucher and user management

2.1 Benefits of using SAP Customer Checkout manager

● Manage all vouchers centrally

SAP Customer Checkout manager Guide

2.2 Country/Region Versions and Languages

SAP Customer Checkout manager is available in various languages and countries/regions.

The UI is available in the following languages:

SAP Customer Checkout manager Guide

2.3 Technical Overview

● SAP Customer Checkout manager web application

● Optional: SAP SAP Event Ticketing

SAP Customer Checkout manager Guide

2.3.2 SAP Event Ticketing Integration

SAP Customer Checkout can be integrated with SAP Event Ticketing.

SAP Customer Checkout manager Guide

Hardware Minimum Recommended

Hard disc 64 GB > 64 GB SSD

2.3.4 Operating System Requirements

The following operating systems are supported:

● Microsoft Windows 7 32-bit

For up-to-date information, see the Product Availability Matrix at http://service.sap.com/sap/support/pam

2.3.5 Database Management System Requirements

SAP Customer Checkout manager runs on several database management systems.

The following database management systems are supported:

SAP Customer Checkout manager Guide

● SAP HANA Database 2.0

2.3.6 Software Requirements

The following software is required:

● Database management system

Do not use the embedded Apache Derby database in a production environment.

● Google Chrome web browser

SAP Customer Checkout manager Guide

For up-to-date information, see the Product Availability Matrix at http://service.sap.com/sap/support/pam

SAP Customer Checkout manager Guide

3.1 Preparing the Installation

SAP Customer Checkout manager Guide

For a 64-bit Linux operating system, choose LINUX ON X86_64 64BIT.

Downloading SAPCAR 7.21

For a 64-bit Linux operating system, choose LINUX ON X86_64 64BIT.

Configuration Adjust various configuration settings, such as security or in

For more information, see Using SAP Customer Check

Roles Create and manage roles in SAP Customer Checkout man

Users Create and manage user accounts in SAP Customer Check