CUSTOMER SAP Customer Checkout Server Guide

Transcription

1 SAP Customer Checkout 2.0 Feature Pack 01 Document Version: CUSTOMER

2 Content 1 SAP Customer Checkout Server About this Document What SAP Customer Checkout Server Can Do Benefits of using SAP Customer Checkout Server? Country Versions and Languages Technical Overview....7 Integration with ERP Systems....7 Minimum Hardware Requirements....7 Operating System Requirements Database Management System Requirements....8 Software Requirements How to install SAP Customer Checkout Server? Preparing the Installation Install Prerequisite Software Database management system Java Application Server Initial Configuration of SAP Customer Checkout Server Resetting the Configuration How to update SAP Customer Checkout Server? Working with SAP Customer Checkout Server Getting started Customer Checkout Cockpit Configuration Users Point of Sales Management Organizational Structures Roles Time Recordings Time Recordings Export Monitoring Vouchers Receipts Software Sales reports C U S T O M E R Content

3 Articles Price Lists Point of Sale Configuration Loyalty Management App Users Point Assignments Coupons Promotion Code Loyalty Configuration Integrate SAP Customer Checkout Server with SAP Customer Checkout Using SAP Customer Checkout Server as backend system Configure and Create Data in SAP Customer Checkout Server Initial Configuration Settings in SAP Customer Checkout Maintain Relevant Settings in SAP Customer Checkout Security Guidelines and Recommendations Initial Password and Password Policy Resetting Admin User User Roles Firewall Auto Logout Secure Connections Virus Scanner Software Updates Content C U S T O M E R 3

4 1 SAP Customer Checkout Server 1.1 About this Document If you are working with SAP Customer Checkout and plan to include the SAP Customer Checkout Server, this guide is for you. It shows how to install, configure, and run SAP Customer Checkout Server both from a technical and business viewpoint. You ll also get an overview of SAP Customer Checkout Server, its components, the integration options with SAP Customer Checkout, as well as instructions on how to work with the application. 4 C U S T O M E R SAP Customer Checkout Server

5 2 What SAP Customer Checkout Server Can Do SAP Customer Checkout Server is a web application and another 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. Please note that loyalty users within SAP Customer Checkout Server do not represent the customers stored in your ERP system or in the SAP Customer Checkout application. Additionally, SAP Customer Checkout Server 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 further create and edit coupons for your loyalty users. Vouchers can be created and managed in SAP Customer Checkout Server, and then used in SAP Customer Checkout. The application serves as central platform and enables integration with SAP Event Ticketing. SAP Customer Checkout Server helps you with: Voucher and user management Handling of coupons Assign bonus points to your loyalty users Integration to SAP Event Ticketing 2.1 Benefits of using SAP Customer Checkout Server? Manage all vouchers centrally Handle several organizational units within your company Manage all receipts posted from your SAP Customer Checkout applications centrally Use the SAP Customer Checkout Server as your backend system Track time recordings of all employees within your organization Monitor all your point-of-sale applications to react quickly What SAP Customer Checkout Server Can Do C U S T O M E R 5

6 Update your point-of-sale software versions and installations centrally within the shortest time Generate sales reports for your cash desks and a specific time period Manage loyalty users, promotion codes and coupons centrally Create articles and price lists in a few steps when using the SAP Customer Checkout Server as backend system 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 Versions and Languages SAP Customer Checkout Server is available in various languages and countries. Country Versions Officially, SAP Customer Checkout Server is supported in Germany, Switzerland and Austria (DACH), Great Britain and Ireland. However, if you are a partner or customer of another country, you are free to evaluate the software. If it meets all functional and legal requirements of your country, you can purchase the software in the country version of your choice. Languages The UI is available in the following languages: English German Dutch French Italian Japanese Polish Portuguese (Brazil) Spanish 6 C U S T O M E R What SAP Customer Checkout Server Can Do

7 2.3 Technical Overview When using SAP Customer Checkout Server, the interaction between components works as follows: SAP Customer Checkout Server 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 Server application. It is a point of sale solution that is locally installed on your cash desk and provides views for all sales transactions within a retail or merchandise shop. With the release of SAP Customer Checkout 2.0, all vouchers that have been created and edited in SAP Customer Checkout Server, 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 Server, you have the option to integrate with SAP Event Ticketing to authenticate loyalty users 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 Server provides the interface for integration to SAP Event Ticketing. The integration can be set within the Configuration tab of SAP Customer Checkout Server. Integration with SAP Event Ticketing is supported only in SAP Event Ticketing Minimum Hardware Requirements SAP Customer Checkout Server can only run on a system which fulfills the minimum hardware requirements. These hardware requirements do not include the database server hardware requirements. What SAP Customer Checkout Server Can Do C U S T O M E R 7

8 Table 1: 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 Operating System Requirements SAP Customer Checkout Server runs on several Windows platforms. The following operating systems are supported: Microsoft Windows 7 32-bit Microsoft Windows 7 64-bit Microsoft Windows bit Microsoft Windows bit Microsoft Windows bit Microsoft Windows bit Microsoft Windows Server 2012/ 64-bit Microsoft Windows Server 2012 R2/ 64-bit For up-to-date information, see the Product Availability Matrix at support/pam Database Management System Requirements SAP Customer Checkout Server 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.00 Only Linux Suse SLES11/ X86 64-bit is supported. 8 C U S T O M E R What SAP Customer Checkout Server Can Do

9 2.3.5 Software Requirements To install and run SAP Customer Checkout Server, you need additional software. The following software is required: Java VM Java SE Runtime Environment Version 8 Java Application Server Recommendation We recommend using Apache Tomcat Version 8 to deploy the server. Database management system You can use the embedded Apache Derby database 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 Server: SAP HANA, using SAP Hana JDBC Driver (ngdbc.jar version ) 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 Central Server Web Application Archive and can be selected during the initial setup of the Central Server. For up-to-date information, see the Product Availability Matrix at support/pam What SAP Customer Checkout Server Can Do C U S T O M E R 9

10 3 How to install SAP Customer Checkout Server? This section shows how to install the SAP Customer Checkout Server, and then do the initial technical configuration when you start the software. 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 SAP Customer Checkout download file. Procedure 1. Go to 2. Choose Installations and Upgrades -> By Category -> INDUSTRY-SPECIFIC COMPONENTS -> SAP CUSTOMER CHECKOUT -> SAP CUSTOMER CHECKOUT 2.0 -> SAP CUSTOMER CHECKOUT SVR Install Prerequisite Software Before you start the SAP Customer Checkout Server installation, make sure that the prerequisite software is installed and set up on the system. The following software is required to be able to install the SAP Customer Checkout Server application: Java Application Server A database management system 10 C U S T O M E R How to install SAP Customer Checkout Server?

11 3.2.1 Database management system Using Apache Derby Database When using Apache Derby database, no additional configuration steps are necessary for the installation of SAP Customer Checkout Server. Apache Derby database is a file-based database created automatically by SAP Customer Checkout Server and used in embedded mode. Recommendation Do not use the embedded Apache Derby database in a production environment Using SAP HANA Database Context To install SAP Customer Checkout Server which works with a SAP HANA database, you need 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 to structure the SAP Customer Checkout Server database and enter a name for the schema (for example, CCOS). 3. Use the default user SYSTEM which is automatically created during the SAP HANA installation process as database user. Optional: Creating a new User in SAP HANA Database If you do not want to use the default user account SYSTEM, you can also create a new user in SAP HANA Database. How to install SAP Customer Checkout Server? C U S T O M E R 11

12 Make sure that the new user has the Object Privileges for the newly created db schema (for example, CCOS). To create a new user in SAP HANA Database, you need to follow these steps: 1. Open your SAP HANA database management tool. 2. Extend the folder Security and choose the Users subfolder. 3. Right-click to create a new user and enter the User name. 4. The user details are displayed on the right side and you can enter the necessary details 5. Enter a Password for this User and confirm the password. 6. In the Object Privileges tab, add the newly created db schema (for example, CCOS). 7. Save your changes. Login with the new user to verify if the creation of the user was successful Using Microsoft SQL Server Context When using a Microsoft SQL Server database, you need to create a separate Microsoft SQL Server instance in order to be able to install SAP Customer Checkout Server. If you install Microsoft SQL Server for the first time, we recommend the following options: Feature Selection: Make sure that the following checkboxes are selected: Database Engine Services Management Tools- Complete Collation: SQL_Latin1_General_CP1_CI_AS Authentication mode: Mixed mode 12 C U S T O M E R How to install SAP Customer Checkout Server?

13 Procedure 1. Open the Microsoft SQL Server Management Studio. 2. Create a new database for SAP Customer Checkout Server and enter a name (for example, CCOS). 3. After the new database for SAP Customer Checkout Server 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, CCOS). 6. Use the default user sa which is automatically created during the Microsoft SQL Server installation process as database user. If you are using a 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 Server 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. To create a new user in Microsoft SQL Server, you need to follow these steps: 1. Open the Microsoft SQL Server Management Studio. 2. In the Microsoft SQL Server Management Studio Object Explorer window, extend the folder Security. 3. Choose the Logins subfolder and right-click to create a new login. 4. A new window opens where you can enter the Login details. 5. In the General tab, enter a Login name and select SQL Server authentication. 6. Enter a Password for this login and confirm the password. 7. In the Server Roles tab, select the necessary server roles for this login. Make sure that you have selected the server roles public and sysadmin. 8. In the User Mapping tab, map the user to the respective database that you have newly created (for example, CCOS). 9. Choose OK to save your changes. 10. Select and extend the Security folder of your newly created database (for example, CCOS). 11. Select the Users subfolder, and the login that you have created is displayed as new user. For more information, see the Microsoft documents at How to install SAP Customer Checkout Server? C U S T O M E R 13

14 3.2.2 Java Application Server Recommendation For the installation of SAP Customer Checkout Server, we recommend using Apache Tomcat Version 8. There are two options with regard to the Java Application Server. Installation within the SAP Business One Integration Framework Installation with Apache Tomcat Installation with SAP Business One Integration Framework Context When you are using the SAP Business One Integration Framework, you can deploy SAP Customer Checkout Server within the same web application server and can use the embedded version of Apache Tomcat that is included in your existing SAP Business One Integration Framework installation. We recommend this option only to small customers who do not want to operate an additional server. Procedure 1. Place the SAP Customer Checkout Server.war file that you have downloaded from SAP Service Marketplace to a local folder on your computer and rename the file (for example, CCOS). The file name will be used as the application deployment path on the application server. 2. Copy the SAP Customer Checkout Server.war file into the webapps subfolder of your existing SAP Business One Integration Framework Tomcat server (located in C:\Program Files (x86)\sap\sap Business One Integration\IntegrationServer\Tomcat) Make sure that you have finished the database related prerequisite steps described in section Database management system [page 11], before you do this step. 3. Ensure that your SAP Business One Integration Framework Tomcat server is started before you proceed further. It will take some time before the SAP Customer Checkout Server.war file is extracted. 4. Once the.war file is extracted, you can start the SAP Customer Checkout Server by following the steps described in section Initial Configuration of SAP Customer Checkout Server [page 15]. 14 C U S T O M E R How to install SAP Customer Checkout Server?

15 Installation with Apache Tomcat Context In case you are not using the SAP Business One Integration Framework and the embedded Apache Tomcat server, you can also install the Apache Tomcat server as standalone software. Procedure 1. Go to and download the installation file for Apache Tomcat. 2. To start the installation, double-click the.exe file. 3. Follow the steps described to run the installation. 4. To verify the installation of Apache Tomcat, go to your web browser and open <server name>: Copy the ccos.war file which you have downloaded from the SAP Software Download Center as SAPCUSCHKSVR*.zip file to the webapps subfolder of your Apache Tomcat server (located in C: \Program Files\Apache Software Foundation\Tomcat 8.0). Make sure that you have finished the database-related prerequisite steps described in in section Database management system [page 11], before you do this step. 6. Your Apache Tomcat server has to be restarted before you proceed further. It will take some time before the SAP Customer Checkout Server.war file is extracted. 7. Once the.war file is extracted, you can start the SAP Customer Checkout Server by following the steps described in section Initial Configuration of SAP Customer Checkout Server [page 15]. 3.3 Initial Configuration of SAP Customer Checkout Server Context When you start SAP Customer Checkout Server for the first time, you need to make some initial settings. How to install SAP Customer Checkout Server? C U S T O M E R 15

16 Procedure 1. In a web browser, enter the following URL: <server name>/ccos (if you used CCOS as the.war file name). 2. The setup screen opens, where you need to enter some initial configuration data. 3. Select the respective database driver type to be used for SAP Customer Checkout Server: If the selected database driver type is Apache Derby Embedded, do the following: 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 box Database Schema Name, or leave it empty as default. 3. Enter the Database User and Database Password. The embedded database will be created during system initialization. Recommendation Do not use the embedded Apache Derby database in a production environment. If the selected database driver type is Microsoft SQL, do the following: 1. In the Database Connection String box, add the server address and database name (for example, enter jdbc:sqlserver://[server addr]:1433;databasename=[database name]). 2. Enter a name in the Database Schema Name, or leave it empty as default. 3. Enter the information needed for the Database User and Database Password boxes. If the selected database driver type is SAP HANA, do the following: 1. Add the server address in the Database Connection String (for example, enter jdbc:sap://[server addr]:30015). 2. Enter a name in the Database Schema Name, or leave it empty as default. 3. Enter the information needed for the Database User and Database Password boxes. If the selected database driver type is JNDI, do the following: 1. Enter the JNDI lookup String in the Database Connection String box. 2. Enter the Database Schema Name, or leave it blank as default. 3. You can leave the Database User and Database Password boxes empty. 4. Enter and confirm the Admin User password for SAP Customer Checkout Server. SAP Customer Checkout Server is pre-delivered with the Admin user. For information about requirements for the password policy, see section Initial Password and Password Policy [page 121]. 5. Enter and confirm the hashkey that is used to encrypt the password of the Database User 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). For information about requirements for the hashkey policy, see section Initial Password and Password Policy [page 121]. 6. To confirm your initial settings, choose OK. This process might take a few minutes. 7. Once the initialization is done, the login page for SAP Customer Checkout Server opens. 16 C U S T O M E R How to install SAP Customer Checkout Server?

17 3.3.1 Resetting the Configuration Context You can reset the configuration settings of SAP Customer Checkout Server: Procedure 1. Delete the configuration file that is stored in the config subfolder of your installation (located in C:\SAP \CustomerCheckout Central Server\config). 2. Restart the Java Application Server. If you are using the CMIS Repository, you have to delete the Repository to reset the configuration. The Repository will automatically be recreated after the setup step is done. How to install SAP Customer Checkout Server? C U S T O M E R 17

18 4 How to update SAP Customer Checkout Server? To consume the new features and to protect the SAP Customer Checkout Server from vulnerabilities, keep the web application up to date. To update the SAP Customer Checkout Server, you have to make the new version available to the web application. 1. Download the latest SAP Customer Checkout Server version from the SAP Software Download Center. 2. Rename the SAP Customer Checkout Server.war file that you downloaded the same way as used in your local installation folder (for example, CCOS). 3. Place this file into the webapps subfolder of your local installation. When you are using the SAP Business One Integration Framework, the subfolder is located by default in C:\Program Files (x86)\sap\sap Business One Integration\IntegrationServer \Tomcat. When you are using the Apache Tomcat, the subfolder is located by default in C:\Program Files \Apache Software Foundation\Tomcat 8.0. For more information, see section Java Application Server [page 14]. 4. Once you have updated the file, the upgrade process will take some minutes after you can access the SAP Customer Checkout Server again. 5. Start the SAP Customer Checkout Server in your web browser as usual, and login. When updating from SAP Customer Checkout version 2.0 to version 2.0 Feature Pack 01, the users manually created in the previous version have no roles and permissions assigned. Once you have updated your SAP Customer Checkout Server, make sure to assign a role/ permissions to these users. 6. To make sure your SAP Customer Checkout Server is updated successfully, select the Configuration tile, and choose the About tab. There, you can verify the SAP Customer Checkout Server version. 18 C U S T O M E R How to update SAP Customer Checkout Server?

19 5 Working with SAP Customer Checkout Server 5.1 Getting started When you start SAP Customer Checkout Server, you will see these sections: SAP Customer Checkout Cockpit: Maintain SAP Customer Checkout Server 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 to your application Each section has tiles for specific tasks: Table 2: Customer Checkout Cockpit Tile Configuration Users Adjust various configuration settings to your needs, such as security or integration settings.. Create and manage user accounts in SAP Customer Checkout Server. Table 3: Point of Sales Management Tile Organizational Structures Roles Time Recordings Time Recordings Export Monitoring Provides a view of all cashdesk branches, SAP Customer Checkout applications, and their dependencies. Manage all roles and permissions of your users within various SAP Customer Checkout applications. Centrally check time recordings made from all users in various SAP Customer Checkout applications. Export time recording files that can be imported into any third-party time tracking system. See all status messages and status information that are sent from various SAP Customer Checkout applications to the SAP Customer Checkout Server. Working with SAP Customer Checkout Server C U S T O M E R 19

20 Tile Vouchers Receipts Software Sales Reports Articles Price Lists Point of Sale Configuration Manage vouchers used in SAP Customer Checkout. Centrally check and track receipts created in SAP Customer Checkout. Manage software versions and installations of various SAP Customer Checkout applications. Generate sales reports for various transactions in SAP Customer Checkout within a specific time period. Centrally manage your articles, when using the SAP Customer Checkout Server as your backend system. Centrally manage your price lists, when using the SAP Customer Checkout Server as your backend system. Maintain settings for tax codes, article groups, currencies, and quick selections in your point-of-sales applications, when using the SAP Customer Checkout Server as your backend system. Table 4: Loyalty Management Tile Coupons Point Assignments App Users Promotion Codes Loyalty Configuration Create and edit coupons. Manage bonus points assigned to loyalty users of SAP Customer Checkout Server. Modify the settings for all loyalty users in SAP Customer Checkout Server. Create and edit promotion codes that can be redeemed by loyalty users to collect loyalty points. Create and define various settings for loyalty points for your loyalty users. 5.2 Customer Checkout Cockpit 20 C U S T O M E R Working with SAP Customer Checkout Server

21 5.2.1 Configuration Within the Configuration tile, you can adjust the settings in SAP Customer Checkout Server to your needs. You can do the following: Set or change passwords. Integrate the SAP Customer Checkout Server application with a third party system to authorize your loyalty users within the Loyalty API. Select various settings for events within your business. The following sections are available in the Configuration tile: Table 5: Configuration tile On this section General Security Integration Proxy About You can... Maintain general settings for SAP Customer Checkout Server Configure security settings such as password policies for loyalty users, or determine an identity provider for authorization of your loyalty users Integrate your SAP Customer Checkout Server application with an external third party provider Maintain proxy settings View version number and Java information of your SAP Customer Checkout Server General Basic Configuration Data This section lets you manage settings for your initial configuration, such as the name and description of your SAP Customer Checkout Server application. Table 6: Basic Configuration Data Option Name Name of your SAP Customer Checkout Server application Working with SAP Customer Checkout Server C U S T O M E R 21

22 Option Active of your SAP Customer Checkout Server application Enable/ Disable the activation of the configuration data This field is set to Active by default Number Range Patterns This section lets you specify a pattern for number ranges for your loyalty account ID and loyalty users. Please note that loyalty users have an individual user ID and loyalty account ID. Table 7: Number Range Patterns Option Loyalty Account ID User ID Pattern number range for the loyalty account ID Pattern number range for the user ID of the loyalty user Administrative Data In this section, you will find administrative data to the SAP Customer Checkout Server Table 8: Administrative Data Option Created by Created at Modified by Modified at Username of the user who created (installed) the SAP Customer Checkout Date and time when the SAP Customer Checkout Server was created Username of the user who last modified the SAP Customer Checkout Server Date and time when the SAP Customer Checkout Server was last modified 22 C U S T O M E R Working with SAP Customer Checkout Server

23 Save Configurations Table 9: Save Configurations Field Save all Pings Enable/ disable the option to save all pings from various SAP Customer Checkout applications in the SAP Customer Checkout Server. Enabled: All pings are saved in the SAP Customer Checkout and shown in the Monitoring tile. Disabled: Only the last ping sent from SAP Customer Checkout is saved in the SAP Customer Checkout Server and shown in the Monitoring tile Security In this section, you can configure the password policy for your users in SAP Customer Checkout Server 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 the user verification from external third party providers Password Table 10: Password Option Users Password policies that are assigned to the users of the SAP Customer Checkout Server. To set the password policies for the users, see Password Policies [page 24]. Working with SAP Customer Checkout Server C U S T O M E R 23

24 Option App users Password policies that are assigned to the loyalty API users. To set the password policies for the loyalty API users, see Password Policies [page 24]. Created by Created at Modified by Modified at During the initial installation and configuration of the SAP Customer Cehckout Server, the password is set automatically by the system (without any relation to a user). Date and time when the password policies have been assigned Username of the user who modified the password policies for the SAP Customer Checkout Server Date and time when the password policies were modified for the SAP Customer Checkout Server Password Policies These are the requirements for setting the Password Policy for users: Table 11: Password Policy Configuration Option Name Name of the user you want to configure the password policy Two user types are currently available: default: The users of your mobile application that you have integrated to the SAP Customer Checkout Server application. defaultadmin: The Admin user of SAP Customer Checkout Server Minimum Password Length (in characters) Maximum Validity of Password (in days) Displays the minimum length of the password in characters. The password should have a minimum length of 8 characters. 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 C U S T O M E R Working with SAP Customer Checkout Server

25 Option Maximum Failed Login Attempts Before Lock Minimum Number of changed characters Minimum Number of Lower Case Characters The maximum failed attempts to login to the application before the user is locked out. Displays the minimum number of characters that need to be changed when you enter a new password. Displays the minimum number of lower case 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 upper case characters needed for the password. For example: Latin uppercase letters A, B, C... Z Minimum number of numeric characters Displays the minimum number of numeric characters needed for the password. For example: Westernized Arabic numerals and/or extended characters: 0, 1, 2, Minimum number of special characters Displays the minimum number of special characters needed for the password. Special characters are # $ % & * ( ) _ + = - < >? { } [ ] ~ Identity Providers The identification of your loyalty users registered through the Loyalty API can also be verified by the following external third-party provider: SAP Event Ticketing To enter details of the identity provider or assign an identity provider to your SAP Customer Checkout Server, follow these steps. 1. Select the Identity Provider you want to edit or assign your application, and choose Edit. 2. The Identity Provider details can now be edited. Table 12: Identity Provider Details Option Name Name of the Identity Provider of the Identity Provider Working with SAP Customer Checkout Server C U S T O M E R 25

26 Option Active URL Address Service Path Session Service Path Customer Service Path Company Authorization Type Username Password Enable or disable the activation of the specific identity provider for the identification of your loyalty users registered in the mobile application. URL of the identity provider system Path to the SAP Event Ticketing Address Service Path to the SAP Event Ticketing Session Service Path to the SAP Event Ticketing Customer Service Company name of the Destination Provider Type used for the authorization of the Identity Provider Key used to communicate with the Identity Provider Password used to communicate with the Identity Provider 3. To save your edits, click Save Integration Within SAP Customer Checkout Server, you have the option to integrate more destination providers to adjust the application to your needs. The destination providers are hosted by a separate provider and they communicate with the SAP Customer Checkout Server application to send relevant information. To enter details of the destination provider or assign a destination provider to your SAP Customer Checkout Server, follow these steps. 1. Choose Edit. 2. You can now enter all details to the Destination Provider. Table 13: Integration Configuration Options Option Name Name of the Destination Provider Caution With release 2.0 of SAP Customer Checkout Server, you can only integrate SAP Event Ticketing as Destination Provider to your application. 26 C U S T O M E R Working with SAP Customer Checkout Server

27 Option Active URL Path Session Service Path of the Destination Provider Enable or disable the activation of the specific Destination Provider URL of the Destination Provider system Path to the Destination Provider system Path to the SAP Event Ticketing Session Service This option is only shown when SAP Event Ticketing is selected as Destination Provider. Order Service Path Path to the SAP Event Ticketing Order Service This option is only shown when SAP Event Ticketing is selected as Destination Provider. Company Authorization Type Username Password Company name of the Destination Provider Type used for the authorization of the Destination Provider Username used to communicate with the Destination Provider Password used to communicate with the Destination Provider 3. To save your edits, click Save Proxy To work with SAP Customer Checkout Server, 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 Server. Table 14: Proxy Configuration Option Use Proxy HTTP Proxy Host Enable or disable use of the proxy. Proxy host name Working with SAP Customer Checkout Server C U S T O M E R 27

28 Option HTTP Proxy Port HTTPS Proxy Host HTTPS Proxy Port Non Proxy Hosts Created by Created at Modified by Modified at Port used by the proxy host Proxy host name when using https Port used by the proxy host for https Hosts for which the proxy is bypassed. To enter multiple hosts, separate them using the pipe ( ) character. During the initial installation and configuration of the SAP Customer Cehckout Server, the proxy settings are set automatically by the system (without any relation to a user). Date and time when the proxy settings have been assigned Username of the user who last modified the proxy settings for the SAP Customer Checkout Server Date and time when the proxy settings were last modified for the SAP Customer Checkout Server About This section provides specific information about the SAP Customer Checkout application, version, the Java Runtime Environment used by SAP Customer Checkout Server, the general information about the application and some general functionality. Table 15: About SAP Customer Checkout Server Option Release Version External customer version number of SAP Customer Checkout Server Internal version number of SAP Customer Checkout Server Build Number Java version Java Runtime Name JAVA VM Name Internal build number of SAP Customer Checkout Server Java version used to run SAP Customer Checkout Server Name of the Java Runtime Environment (JRE) used to run the application Name of the Java VM used to run SAP Customer Checkout Server 28 C U S T O M E R Working with SAP Customer Checkout Server

29 Option System Properties Shows all system properties for the installed version of Java Users In the Users tile, you can manage your users of SAP Customer Checkout Server and SAP Customer Checkout. You can create new users, edit, delete, or lock users, assign a role and permissions to users, and assign PoS instances to users. SAP Customer Checkout Server is pre-delivered with the Admin user. In the initial configuration settings, you also have to set the password for this Admin user. Each user account contains further tabs with more information: details, permissions, and assigned PoS instances. The Details tab provides the following information: Table 16: Users Details Option Username Name of the user used to login in SAP Customer Checkout Server The username is case sensitive. Name Role The user's first and last name. Role that is assigned to this user For more information about each of the roles, see section Roles [page 37]. Depending on the role you select to be used for this user, the permissions will be adapted by the respective role. Language Locale Language used on the user interface of the application for this user. Locale used by this user Working with SAP Customer Checkout Server C U S T O M E R 29

30 Option Employee ID Is Salesperson Salesperson ID Color Barcode Secret SAP Business One only: Employee ID number in the SAP Business One system Enable/ disable this user to act as Salesperson (see SALES screen in SAP Customer Checkout) SAP Business One only: Sales Employee Code from the SAP Business One system Color used in the SALES screen when this user is logged in SAP Customer Checkout Alternative login ID for low level login. Example: Can be used for login with magnetic card. Locked Status of the user. Possible statuses are: True: the user cannot log in False: The user can log in Password Locked Password status for the user. Possible statuses are: True: the user cannot log in False: the user can log in This status is set to true if the user exceeded the maximum login fail attempts, which is specified in the password policy. Status Last Login at Last Password Change at Password Valid to Created by Created at Modfied by Modified at Shows whether the user is active or not. Date and time when the user logged in SAP Customer Checkout Server the last time Date and time when the user changed password the last time Date and time until the password of this user is valid Username of the user who created the user in SAP Customer Checkout Server Date and time when the user was created Username of the user who modified the user in SAP Customer Checkout Server Date and time when the user was modified The Permissions tab shows all permissions that are assigned to this user. 30 C U S T O M E R Working with SAP Customer Checkout Server

31 If a role has been assigned to a user, this role passes all its permissions on to the user. However, you can still change individual permissions manually. If no role has been assigned to a user, all permissions of this user are deactivated. You can manually activate them. In addition, for some permissions it is also possible to define paramterers to 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 also section Permissions [page 40]. In the Assigned PoS instances tab, you can define SAP Customer Checkout applications to be used only by certain users. This means that users can only use and log in to SAP Customer Checkout applications to which they are assigned to. One user can be assigned to one or more PoS instances. To assign a SAP Customer Checkout application to a user, do the following steps: 1. Select the user to whom you want to assign the PoS instance, and select the Assign PoS instance tab. 2. Choose Create. 3. In the Create assignment dialog box, select the respective Pos instance, and choose Save. To synchronize users managed in the SAP Customer Checkout Server 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 Server. When using the central user management of the SAP Customer Checkout Server, local user and role management in the SAP Customer Checkout configuration is no longer possible. The User tab cannot be edited, and is read-only. Caution When using the Central Drawer Management in SAP Customer Checkout, the central user management of the SAP Customer Checkout Server cannot run in parallel. You can only run one at a time. 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. Working with SAP Customer Checkout Server C U S T O M E R 31

32 Creating a User Context If needed, you can create further users in SAP Customer Checkout Server. Procedure 1. Click on the Add icon in the left lower part of the screen and add a new user. 2. Enter the user data, and be sure to complete all mandatory fields marked with an asterisk (*). Make sure the entered password fulfills the requirements of the Password Policy described in section Initial Password and Password Policy [page 121]. 3. To create the user, choose Save Editing a User Context In SAP Customer Checkout Server, you can manually edit existing users. For example, you may want to change the password of 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 edits of the user, click Save. 32 C U S T O M E R Working with SAP Customer Checkout Server

33 5.3 Point of Sales Management Organizational Structures In this tile you can manage the organizational hierarchy of your company or organization. The organizational structure contains the following units: Cashdesk Branch: a unit that contains Cashdesk units SAP Customer Checkout Cashdesk: the application installed on your cashdesks You can keep track of your cashdesks and cashdesk branches, create new cashdesks and branches, assign cashdesks to branches, move branches and cashdesks, see the hierarchical dependencies, delete cashdesks and branches, and also show the version and build number of each SAP Customer Checkout cashdesk. Example If you are in the Sports and Entertainment field, you might have two primary cashdesk branches, each containing several cashdesks. For example, your primary branches may be the following: Food and Beverage Merchandising Within the Food and Beverage cashdesk, you may have cashdesks for Food, Soft drinks, Alcoholic drinks, and so on. Once a SAP Customer Checkout cashdesk is installed and connected to the SAP Customer Checkout Server, a new organizational unit is created. The following information is available for each organizational unit: Table 17: Organizational Units Field Name ID Name of the organizational unit ID of the organizational unit If the organizational unit is a cashdesk the ID is taken of the prefix of the SAP Customer Checkout cashdesk. Working with SAP Customer Checkout Server C U S T O M E R 33

34 Field Type Type of Organizational Unit Possible types are: Cashdesk Branch Cashdesk Version/ Build Number Software version of the SAP Customer Checkout cashdesk Once you select an organizational unit, you find more tabs with detailed information about the respective organizational unit. Depending on the type of organizational unit you have selected, the title and tabs displayed change. When you select a cashdesk branch, you will see more information on the following tab: Details: When you select a cashdesk, you will see more information on the following: Details Version The Details tab contains the following information about the organizational unit:. Table 18: Details Field ID ID of the organizational unit If the organizational unit is a cashdesk the ID is taken of the prefix of the SAP Customer Checkout cashdesk. Name Location Name of the organizational unit of the organizational unit Location of the organizational unit This field is only shown when a cashdesk entry has been selected. Created by Created at Username of the user who created the organizational unit in SAP Customer Checkout Server Date and time when the organizational unit was created in SAP Customer Checkout Server 34 C U S T O M E R Working with SAP Customer Checkout Server

35 Field Modified by Modified at Username of the user who modified the organizational unit in SAP Customer Checkout Server Date and time when the organizational unit was modified in SAP Customer Checkout Server The Version tab shows the relevant information about the software version of the SAP Customer Checkout cashdesk. Table 19: Version Field Version/ Build Number Java Version System properties Software version of the SAP Customer Checkout cashdesk Java version used to run the SAP Customer Checkout cashdesk System properties for the installed version of Java Create New Organizational Units In the Organizational Structures tile you can create new organizational units (cashdesk branches and cashdeks). Context The first time you connect an SAP Customer Checkout cashdesk with SAP Customer Checkout Server, the system looks for a cashdesk ID in the Organizational Structures tile. If no cashdesk is found in SAP Customer Checkout Server, a new organizational unit entry is automatically created. Procedure 1. In the Organizational Structure tile of the SAP Customer Checkout Server, choose Create. 2. Choose the organizational unit type you want to create. 3. Select the cashdesk branch you want the new organizational unit to be assigned to. If you don't want to assign the new organizational unit to any existing cashdesk branch, choose root. Working with SAP Customer Checkout Server C U S T O M E R 35

36 4. Enter an ID and Name for the organizational unit. 5. Save your edits Delete Organizational Units In the Organizational Structures tile, you can delete cashdesks and branches. Context Only cashdesk branches that are not referenced by other organizational units can be deleted. SAP Customer Checkout cashdesks that have once been connected with the SAP Customer Checkout Server, cannot be deleted as a reference is existing for the cashdesk. Procedure 1. In the Organizational Structures tile, select the organizational unit (cashdesk branch or cashdesk) you want to delete. 2. Choose Delete and confirm the deletion with OK Move Organizational Units To reflect changes in your organization, you can move organizational units. For example, you can move cashdesk branches or cashdesks to other cashdesk branches. Procedure 1. In the Organizational Structures tile, select the organizational unit (cashdesk branch or cashdesk) you want to move. 2. Choose Move. 3. Choose the cashdesk branch you want the organizational unit to be moved to and confirm with OK. 4. Save your edits. 36 C U S T O M E R Working with SAP Customer Checkout Server

37 5.3.2 Roles In the Roles tile, you can manage all roles and permissions of your users within your SAP Customer Checkout applications. You can also create roles, assign roles to parent roles, assign different permissions to roles, and edit and delete roles. To synchronize roles managed in the SAP Customer Checkout Server 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 roles and permissions for your SAP Customer Checkout applications are managed centrally in SAP Customer Checkout Server. When using the central user management of the SAP Customer Checkout Server, local user and role management in the SAP Customer Checkout configuration is no longer possible. The Roles tab cannot be edited, and is read-only. Caution When using the Central Drawer Management in SAP Customer Checkout, the central user management of the SAP Customer Checkout Server cannot run in parallel. You can only run one at a time. 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. The Roles tile provides an overview of all roles, general data about a specific role, and permissions assigned to a role. The respective UI in the SAP Customer Checkout Server is identical to the UI in the SAP Customer Checkout application for roles. The following options are available in the Role tile: Creating a role Editing a role Deleting a role Refreshing all roles In SAP Customer Checkout Server, you will find the default roles available for use in SAP Customer Checkout. Default Roles SAP Customer Checkout Server delivers the following pre-defined roles that are transmitted to SAP Customer Checkout: Working with SAP Customer Checkout Server C U S T O M E R 37

38 Table 20: Default roles in SAP Customer Checkout Server User Role CASHIER SALESMANAGER ADMINISTRATOR Screens Available SALES, SEARCH SALES, CASH-IN/CASH-OUT, CASH DESK CLOSING, CASHING-UP, SEARCH SALES, CASH-IN/CASH-OUT, CASH DESK CLOSING, CASHING-UP, SEARCH, CONFIGURATION Roles and Permissions Concept Each role can access different screens and perform different actions in SAP Customer Checkout and in the SAP Customer Checkout Server, depending on the permissions assigned to them. 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 permission 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: Table 21: Settings in Permissions table Column Protected resource Parent role Name of the protected resource for which a permission can be granted. For information about system-defined permissions, see Permissions [page 40]. Shows whether in the parent role the respective permission was granted. This column is not editable, because the settings are passed on from 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. 38 C U S T O M E R Working with SAP Customer Checkout Server

39 Column Effective Shows the result that derived from the two boxes Parent role and Allowed. Here you can check whether the permission has been granted. This field is not editable. Example A new role has been added to a parent role. The parent role can cancel sales items in the sales screen. To ensure the new role doesn't inherit this permission, you can set its Allowed option to No. The result: the permission cancel sales items for the new role is deactivated, and the entry for Effective is automatically set to NO. Parameterizable System defined Shows whether a permission can have additional parameters. If you select a permission that can have additional parameters, the Permission parameters table is displayed under the Permissions table. Indicates whether the permission is defined by the system or created manually Creating Roles You can create new roles in addition to the default roles if you require to provide permissions that are customized to your users. Procedure 1. In the Roles tile, click New. You can assign a name, description and parent role to this new role. 2. Edit the General data of this role. Recommendation We recommend to select a parent role for each role you create. This way you ensure that the new role receives all required permissions in case of software updates. Caution Once you enter a name for a role, it's no longer editable. 3. Under Permissions, adapt the permissions according to your needs. Working with SAP Customer Checkout Server C U S T O M E R 39

40 4. 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. 5. Save your edits Editing Roles You can edit existing roles in SAP Customer Checkout Server, if you want to maintain or adjust any settings. Context Caution Once a role is created, the name of the role cannot be edited in the SAP Customer Checkout Server. Procedure 1. Open the Roles tile in the SAP Customer Checkout Server. 2. Select the role you want to edit and click Edit. 3. Edit the General data or Permissions of the role. 4. Save your edits Permissions The following protected resources are defined in the system. Table 22: System-defined protected resources Protected resource Access SAP Customer Checkout Server Do time recording check out without authorization Let the user access SAP Customer Checkout Server - including all tiles available Allow the user to do a time recording check out in SAP Customer Checkout, without any further approval by a user who has the permission Approve time recording requests. 40 C U S T O M E R Working with SAP Customer Checkout Server

41 Protected resource Show search screen Show sales screen Cancel sales items Show current cash balance Force screen unlock Allow returns Cancel sale Can open drawer (no-sale receipt) Show cashing up screen Accept expired vouchers Show cash desk closing screen Using time recording Change the unit price Modify receipts Do time recording check in without authorization Recovery administrator tasks Show cash-in/ out screen Can take over In transit (ITR) drawers Show settings screen Give discount Approve time recording requests Create or update customers Allow the user access to the Search screen including searching of customers, articles, receipts, vouchers, and so on. Allow access to the Sales screen Let the user cancel sales items on the Sales screen Show the current cash balance at cash-in/cash-out and at Cash Desk Closing screen Allow forcing of screen unlock for other users Allow returning articles and whole receipts on the Sales screen Allow cancelling the current sales process on the Sales screen. Allow cancelling parked and resumed receipts on the sales screen. Allow the user to open a drawer without creating a receipt Allow the user to open and edit the Cashing-Up screen Allow the user to accept expired vouchers in SAP Customer Checkout Allow the user to open and edit the Cash Desk Closing screen Allow the user to record time in the Time Recording screen in SAP Customer Checkout, but the time recording request needs approval by a user that has the permission Approve time recording requests. Allow the user to change the unit price of sales items on the Sales screen Allow the user to modify or re-post receipts outside the Sales screen Allow the user to do a time recording check in SAP Customer Checkout, without any further approval by a user that has the permission to Approve time recording requests. Allow editing of recovery admin tasks that are generally part of the RAdmin role. The RAdmin tasks are especially relevant when you have enabled the central drawer management. Allow the user to open the cash-in/-out screen Allow the user to take over drawers that are in state In transit (ITR). This permission is relevant for the central drawer management. Allow the user to open the Settings screen and edit the settings Allow the user to apply discount on sales items or the whole receipt on the Sales screen Allow the user to approve time recording requests (especially for users who have the permission Using time recording). Allow the user to create and update customers on the Search screen. Working with SAP Customer Checkout Server C U S T O M E R 41

42 Protected resource Return a receipt by ID Allow the user to void receipt by ID in the new sales user interface version 2.0 If necessary, you can create new permissions and assign them to a role. To use permissions that have been created manually in SAP Customer Checkout Server, a separate plug-in is necessary. SAP Customer Checkout only provides the means to connect a plug-in to the application. The communication between the plug-in, SAP Customer Checkout and the SAP Customer Checkout Server needs additional development based on the custom requirements. To create a new permission and assign them to a role, do the following: 1. Select the role to which you want to add a new permission, and select Edit. 2. In the Permissions section, select New. 3. Enter a name for the Protected resource ID and choose whether to grant the permission. 4. Save your edits Permission Parameters You can assign additional parameters to a permission, edit, or delete existing parameters that are assigned to a permission. The Permission Parameters option is displayed only 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 available only for Give Discount, or for a custom permission you might create 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 to which you want to edit an existing permission parameter or assign additional parameters, and select Edit. 2. Select the respective protected resource which is parameterizable and in the area below Permission Paramenters, select New. 3. Enter a Template ID and a Value, and select Comparison operator. 4. To save your edits, select OK. 42 C U S T O M E R Working with SAP Customer Checkout Server

43 5.3.3 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 is been performed in SAP Customer Checkout, an entry with all details about the time recording is created in SAP Customer Checkout Server. 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 keep search for time recording transactions, filter, or sort them. Time recording transactions cannot be edited or corrected in the SAP Customer Checkout Server, they are only displayed with all detailed information. In case you want to edit or correct any time recording transactions, you can run a time recording export file. This file can be imported to any third-party time tracking system. For more information, see section Time Recordings Export [page 44]. The following details are available in the Time Recordings tile for each time recording transaction: Table 23: Time Recording Details Field Book Status Status level of the time recording transaction sent from SAP Customer Checkout to SAP Customer Checkout Server. Possible statuses are: Completed Critical Incomplete Check In Check Out Hours Hours Decimal Org Unit Check In PoS Check Out PoS Date and time when the user checked in SAP Customer Checkout Date and time when the user checked out in SAP Customer Checkout Summary of the user's time spent on the system. Summary of the user's time spent on the system in decimal numbers. Name of the Organizational Unit for which the user created the time recording transaction ID or prefix of the SAP Customer Checkout cashdesk from where the check-in transaction was executed ID or prefix of the SAP Customer Checkout cashdesk from where the check-out transaction was executed Working with SAP Customer Checkout Server C U S T O M E R 43

44 Field Username Name and detailed name of the server user in the SAP Customer Checkout Server When you click on the Username, you get forwarded to the respective user. Check In Supervisor Name of the user who approved the time recording check-in request in SAP Customer Checkout When you click on the Check in Supervisor, you get forwarded to the respective user. Check Out Supervisor Name of the user who approved the time recording check-out request in SAP Customer Checkout When you click on the Check Out Supervisor, you get forwarded to the respective user. Unique Stamp ID Time recording position identifier 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 make further changes or 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 a time recording export files. The following options are available in the Time Recordings Export tile: Table 24: Time Recordings Export Options Option New Export Executes the export of time recording files performed in various SAP Customer Checkout applications from all users 44 C U S T O M E R Working with SAP Customer Checkout Server

45 Option History Provides an overview of the latest time recording export files The following information is available for time recordings export files: Table 25: History Details Field Process ID Execution start Execution done Execution state Name of the time recordings export file ID of the process that executes a time recordings export file Displays the date and time when export of the time recordings export file was completed. Displays when the execution of the time recordings export file was finished. Indicates the status of the time recording export execution. Possible statuses are: Idle Running Cancelled Finished Execution result Indicates if the time recording export file has been executed successfully. Possible statuses are: None Cancelled Success Failure Fatal Status message Download Cancel worker Shows the status message of the execution of time recordings export files. Enables the time recordings export file to be downloaded. Lets you cancel an export process before while it's running. Working with SAP Customer Checkout Server C U S T O M E R 45

46 Export Time Recordings Files Context If you want to export time recording files for a specific organization, or time period, you can do it centrally in the SAP Customer Checkout Server. This time recording export file can be included into third party systems which can be used for further editing. Procedure 1. Select the Time Recordings Export tile in SAP Customer Checkout Server. 2. In the New Export section, enter the data for the time recordings export file, and be sure to complete all mandatory fields marked with an asterisk (*). The time recordings export file is automatically stored locally in the SAP Customer Checkout Server. When you enter a path for the time recordings export file, a copy of the time recordings export file is stored in the path folder. 3. To run the export, select Start Export. The status of your time recordings export file is shown in the History section. 4. Once the export is complete, you'll find the file in your local directory for SAP Customer Checkout Monitoring The Monitoring tile provides you with an overview of all status messages and status information that are sent from various SAP Customer Checkout applications to SAP Customer Checkout Server. The SAP Customer Checkout application communicates with SAP Customer Checkout Server 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. Depending on the Severity you set in the Configuration of SAP Customer Checkout, the respective status messages are displayed in the overview. 46 C U S T O M E R Working with SAP Customer Checkout Server

47 The following information is available for each status message in the Monitoring tile: Table 26: Monitoring Field Severity Level of importance or relevance of a status message that is sent from SAP Customer Checkout to SAP Customer Checkout Server Possible levels are: 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 Customer Checkout application that requires attention (for example, a lack of free disc space) Debug: includes all information sent from the SAP Customer Checkout application to analyze the coding Error: includes information sent from a SAP Customer Checkout application that contain errors or prevents a transaction from being performed (for example, failure of synchronization job) If Information is set as Severity, Warnings and Errors are also included and sent to the SAP Customer Checkout Server. Cashdesk SAP Customer Checkout prefix used throughout the application When you select the Cashdesk prefix, you get forwarded to the respective organizational structure. Timestamp Date and time when the status message was sent from SAP Customer Checkout to SAP Customer Checkout Server Working with SAP Customer Checkout Server C U S T O M E R 47

48 Field 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 synchronization in SAP Customer Checkout Discount Synchronization: Performing a discount synchronization in SAP Customer Checkout User Synchronization: Performing a user synchronization in SAP Customer Checkout Single User Synchronization: Performing a single user synchronization in SAP Customer Checkout Material Synchronization: Performing a material synchronization in SAP Customer Checkout Receipt Synchronization: Performing a receipt synchronization in SAP Customer Checkout Voucher Synchronization: Performing a voucher synchronization in SAP Customer Checkout Quickselection Synchronization: Performing a quickselection 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 assigned to the status messages. Most of the event groups consist of the start of an event and the end of an event. 48 C U S T O M E R Working with SAP Customer Checkout Server

49 Field 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 SAP Customer Checkout application) Backup Server settings changed Less disc space left 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 Job end Job fetch Working with SAP Customer Checkout Server C U S T O M E R 49

50 Field 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) Device start (cash drawer) Device start (printer) 50 C U S T O M E R Working with SAP Customer Checkout Server

51 Field 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 Server If no username is maintained to the status message, is means no user was logged in to SAP Customer Checkout at the time the status message was sent to the SAP Customer Checkout Server. When you select the User, you get forwarded to the respective server account. Cashdesk Version Buildnumber Software version of the SAP Customer Checkout application Date and time when the SAP Customer Checkout software was created All event groups have several possible events: Table 27: Possible Events Event Name Event Group Severity Level App start Start, System Starting Process of SAP Customer Checkout application has been triggered Information 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 Customer Checkout application has finished Information Working with SAP Customer Checkout Server C U S T O M E R 51

52 Event Name Event Group Severity Level App shutdown Shutdown, System SAP Customer Checkout application is shutting down Information Debug System Debug message sent from the SAP Customer Checkout system Information This event might only be relevant for developers. Login System Login to SAP Customer Checkout system (a user has logged in) Log System Log message send from the SAP Customer Checkout system Information Information This event contains all information that are displayed in the cmd console of the SAP Customer Checkout system. Logout System Logout of SAP Customer Checkout system (a user has logged out) Ping System Ping message send from SAP Customer Checkout system Information Information 52 C U S T O M E R Working with SAP Customer Checkout Server

53 Event Name Event Group Severity Level Update System Update of SAP Customer Checkout system has been performed Information Additional information, such as previous software version, build number, and release version of the SAP Customer Checkout system is shown in this event. Backup System Backup of SAP Customer Checkout system has been performed Less disc space left System Less disc space left in hardware device where SAP Customer Checkout system is running Server settings changed System Settings for SAP Customer Checkout Server have been changed within the Integration tab of the SAP Customer Checkout Configuration screen Information Information Information Job start Configuration Import, Configuration Export, Discount Synchronization, User Synchronization, Material Synchronization, Receipt Synchronization, Voucher Synchronization, Quickselection Synchronization, Update Software Synchronization, Plugin Starting process of the event job has been triggered Working with SAP Customer Checkout Server C U S T O M E R 53

54 Event Name Event Group Severity Level Job end Configuration Import, Configuration Export, Discount Synchronization, User Synchronization, Material Synchronization, Receipt Synchronization, Voucher Synchronization, Quickselection Synchronization, Update Software Synchronization, Plugin Event job has been finished Job fetch Customer Synchronization, Discount Synchronization, User Synchronization, Material Synchronization, Receipt Synchronization, Voucher Synchronization, Update Software Synchronization, Synchronization, Plugin Event job has fetched data from the backend system to SAP Customer Checkout Job post Customer Synchronization, Discount Synchronization, Material Synchronization, Receipt Synchronization, Voucher Synchronization, Synchronization, Plugin Event job has posted data from the backend system to SAP Customer Checkout 54 C U S T O M E R Working with SAP Customer Checkout Server

55 Event Name Event Group Severity Level User found Single User Synchronization User found in the application who logged in to SAP Customer Checkout. When a user has not synchronized in SAP Customer Checkout with a full user synchronization and this user logs into SAP Customer Checkout, a single user synchronization is carried out. No user found Single User Synchronization The user who logged in to SAP Customer Checkout was not found in the backend system. When a user has not synchronized in SAP Customer Checkout with a full user synchronization and this user logs into SAP Customer Checkout, a single user synchronization is carried out. Data received Quickselection Synchronization Quickselection information has been successfully sent to SAP Customer Checkout Information A new quickselection has been received from the backend system and replaced the current quickselection version. Working with SAP Customer Checkout Server C U S T O M E R 55

56 Event Name Event Group Severity Level No data received Quickselection Synchronization Quickselection information has not been sent to SAP Customer Checkout Information There is no new quickselection version available. Update available Update Software Synchronization New software version of SAP Customer Checkout is available Information No update available Update Software Synchronization There is no software update version of SAP Customer Checkout available Information Device start (line display) Plugin Line display connected to SAP Customer Checkout has been started Information Device start (cash drawer) Plugin Cash drawer connected to SAP Customer Checkout has been started Information Device start (printer) Plugin Printer connected to SAP Customer Checkout has been started Device start Plugin Hardware Device connected to SAP Customer Checkout has been started Information Information Device stop Plugin Hardware Device connected to SAP Customer Checkout has been stopped Device restart Plugin Hardware Device connected to SAP Customer Checkout has been restarted When you select one entry of the status messages listed in the Monitoring Tile, you will find see tabs with more information. The General Data Tab provides you cashdesk and event information for the respective status message. 56 C U S T O M E R Working with SAP Customer Checkout Server

57 Table 28: General Data Field Cashdesk Cashdesk Version Cashdesk Buildnumber User SAP Customer Checkout prefix used throughout the application Software version of the SAP Customer Checkout application Date and time when the SAP Customer Checkout software was created Username of the user logged in to SAP Customer Checkout during the status message was sent to the SAP Customer Checkout Server If no username is maintained to the status message, it means no user was logged in SAP Customer Checkout when the status message was sent to SAP Customer Checkout Server. Severity Level of importance or relevance of a status message that is sent from SAP Customer Checkout to the SAP Customer Checkout Server Possible levels are: 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 Customer Checkout application that requires attention (for example, a lack of free disc space) Debug: includes all information sent from the SAP Customer Checkout application to analyze the coding Error: includes information sent from a SAP Customer Checkout application that contain errors or prevents a transaction from being performed (for example, failure of synchronization job) If Information is set as Severity, Warnings and Errors are also included and sent to the SAP Customer Checkout Server. Timestamp Date and time when the status message is sent from SAP Customer Checkout to the SAP Customer Checkout Server Working with SAP Customer Checkout Server C U S T O M E R 57

58 Field Event Group Event Name of the Event Group assigned to the status message (see above). Name of the Event assigned to the status message: each event belongs to an Event Group (see above). Describes the event sent from SAP Customer Checkout The Additional Options tab has information about the key and value of the respective status message. Each event may have different types of key values. Table 29: Additional Options Field Key Key value of the event sent from SAP Customer Checkout For example: stacktrace, freememorykb, memoryconsumption) Value Value assigned to the key of the event sent from SAP Customer Checkout Delete Monitoring Entries Context In the Monitoring tile, you can also delete entries of status messages. You can select which entries to delete, either by name, date, or type, or delete all entries. Procedure 1. In the Monitoring tile of the SAP Customer Checkout Server, select Delete Entries. 2. Select Severity, and the date and time of the entries to delete. 3. Select Delete. 58 C U S T O M E R Working with SAP Customer Checkout Server

59 5.3.6 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 reload the voucher at any time in the given validity period.. In the Vouchers tile, you can centrally manage your vouchers used in SAP Customer Checkout. You can keep track of your vouchers, edit, create, store, search or block a voucher, if necessary The following sections are available in the Vouchers tile: Table 30: Vouchers Tile Option Vouchers Vouchers transactions Displays all vouchers that have been created in SAP Customer Checkout or directly in SAP Customer Checkout Server. Provides details about redemptions and reloads of any voucher you select. What information is available for vouchers? Table 31: Vouchers Field Voucher ID Origin Issued at Valid to Status Unique number of the voucher Where the voucher was created - either in SAP Customer Checkout or directly in SAP Customer Checkout Server Date and time the voucher was created Final Date that the voucher can be redeemed Indicates if a voucher has already been redeemed. Possible statuses are: Not redeemed Partially redeemed Redeemed External Transaction ID Created by Blocked The receipt ID created by the system when a voucher is sold in SAP Customer Checkout User name of the user who created the voucher, either in SAP Customer Checkout or directly in SAP Customer Checkout Server Indicates whether the voucher was set to Blocked. Blocked vouchers cannot be redeemed. Working with SAP Customer Checkout Server C U S T O M E R 59

60 Field Current amount Original amount Currency Valid to Sales person ID Cashier ID Voucher article ID The amount of money that can be redeemed with the voucher The amount of money originally assigned to the voucher when it was created Currency type of the voucher Validity Date until when the voucher can be redeemed ID of sales person who created the voucher in SAP Customer Checkout ID of the cashier who created the voucher in SAP Customer Checkout Article ID that is assigned to the voucher in SAP Customer Checkout from the ERP system Voucher's description for the voucher send from SAP Customer Checkout Table 32: Voucher Transactions Field External item ID Origin Posted on External Transaction ID ERP Transaction ID External System ID Customer ID Value ID created for each posting Where the voucher was created, either SAP Customer Checkout or directly in SAP Customer Checkout Server Date of the posting The receipt ID created by the system when a voucher transaction is made Document ID in your ERP system Cash desk prefix of the SAP Customer Checkout application that was used to create the voucher transaction If a customer was added to the receipt, the customer ID from SAP Customer Checkout is sent along with the posting. The value of the posting 60 C U S T O M E R Working with SAP Customer Checkout Server

61 Creating a Voucher Context Usually vouchers are created by cashiers using the SAP Customer Checkout application. The SAP Customer Checkout Server also lets you create vouchers centrally that can be used at any cash desk of SAP Customer Checkout. Procedure 1. On the Vouchers tab, choose New 2. Enter the voucher data, and be sure to complete all mandatory fields marked with an asterisk (*). 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. The current amount is updated accordingly Editing a Voucher Context SAP Customer Checkout Server 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, and so on. Procedure 1. On the Vouchers tab, choose a Voucher ID. Working with SAP Customer Checkout Server C U S T O M E R 61

62 2. The voucher details screen opens. 3. To edit the voucher, choose Edit. 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 position level of the voucher transaction choose Details, and change the entries Blocking a Voucher Context In the Vouchers section of SAP Customer Checkout Server, you can also 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. When you select the voucher again, you can undo the block by removing the checkmark Migrate Vouchers from a File-based Voucher Module Context If you used to manage your vouchers with a database file and now want to switch to the voucher management system in SAP Customer Checkout Server, you can migrate your legacy vouchers. 62 C U S T O M E R Working with SAP Customer Checkout Server

63 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. Select the Voucher subtab and change the voucher module to SAP Customer Checkout Server voucher module. 4. Select the Server subtab and in the Webservice endpoint section, enter the corresponding fields. 5. Open the Synchronization tab and do a voucher synchronization. The voucher data is transferred to SAP Customer Checkout Server. 6. To enable to use all vouchers created in SAP Customer Checkout Server, schedule a voucher synchronization for all your SAP Customer Checkout installations Receipts The Receipts tile, you can see an overview of all receipts, and detailed information about them, 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 the SAP Customer Checkout Server. When you have several SAP Customer Checkout applications running, you will find all receipts stored in the SAP Customer Checkout Server. You can keep track of receipts, view receipts, sales items, tax item and payment item details. You can search for receipts, sort, and filter them. Receipts cannot be edited in this tile. When you select the Receipts tile in SAP Customer Checkout Server, you'll see the following options: Shown receipts: receipts transferred from SAP Customer Checkout to the SAP ERP system Striked out receipts: voided receipts or ones not posted from SAP Customer Checkout to the SAP ERP system (for example, cancelled receipts) Once you select a receipts entry, additional tabs with detailed information about the respective receipt are displayed. The title and tabs displayed will 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 the SAP Customer Checkout Server. Working with SAP Customer Checkout Server C U S T O M E R 63

64 The following details are available in the Receipts tile for each receipt entry: Table 33: Receipt Options Field Cash Desk ID Receipt ID Cash Desk Closing ID Customer Type Cashdesk prefix used throughout the SAP Customer Checkout application from which the receipt has been created Receipt ID sent from SAP Customer Checkout Cashdesk ID of the cashdesk that has posted the cash transaction or invoice payment Customer ID of the customer assigned to the cash transaction or invoice payment 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 Cash Desk Closing Business Transaction Date Payment Gross Amount Date when the receipt has been created Payment Gross Amount of the receipt posted in SAP Customer Checkout When you select a Direct Sale or Reserve Invoice receipt entry, you will see the Receipt Detail view and find further information about the selected receipt: Details Sales Items Tax Items Payment Items 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 Cash Desk Closing receipt entry, you will see the Receipt Detail view and find information in the following tabs: Details Additional Fields 64 C U S T O M E R Working with SAP Customer Checkout Server

65 Duplicates of receipts are rejected and not stored in the SAP Customer Checkout Server. Receipts are not updated in SAP Customer Checkout Server. If you change a receipt in SAP Customer Checkout that has already been posted in SAP Customer Checkout Server, the change is not posted to SAP Customer Checkout Server because it rejects duplicate receipts. Parked receipts in SAP Customer Checkout aren't transferred to the SAP Customer Checkout Server. Therefore, parked receipts are not available in the SAP Customer Checkout Server. When a striked out receipt is selected, the details of the receipt are still shown, although the receipt title is marked Void Details This section of the Receipts tile provides general data, customer data, admininistrative data, and amount details about the selected receipt. Table 34: Header Data Field Cash Desk ID Receipt ID Cash Desk Closing ID Type Cashdesk prefix used throughout the SAP Customer Checkout application from which the receipt was created Receipt ID sent from SAP Customer Checkout Cashdesk ID of the cashdesk that posted the cash transaction or invoice payment 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 Cash Desk Closing Business Transaction Date Cashier Date when the receipt was created Name of Cashier assigned to the cash transaction or invoice payment Working with SAP Customer Checkout Server C U S T O M E R 65

66 Field Sales Person Discount Purpose Code Price List ID Comment Rounding Used Rounding Level Name of sales person assigned to the cash transaction or invoice payment Discount Purpose Code sent from the SAP ERP system ID of the price list in the SAP ERP system Comment assigned to the receipt in SAP Customer Checkout Shows whether a currency rounding was used in SAP Customer Checkout. The smallest possible unit the currency can be rounded to. Example If each rounded result should be a multiple of 0.05 maintain the value Rounding Amount Determines on which level the rounding rules are used in SAP Customer Checkout. 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 Void Customer ID Name Category Address Customer ID of the customer assigned to the cash transaction or invoice payment Name of the customer assigned to the cash transaction or invoice payment Category of the customer assigned to the cash transaction or invoice payment Address of the customer assigned to the cash transaction or invoice payment 66 C U S T O M E R Working with SAP Customer Checkout Server

67 Field Petty Cash ID This field is only shown when the following types of receipt 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 Cash Desk Closing receipt. Account for cash payments in the currency maintained. In general, if the cash drawer is configured as an account in the SAP ERP system, the cash drawer account number is maintained here. Amount This field is only shown when the following types of receipt 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 Cash Desk Closing receipt. Amount of the cash transaction posted from SAP Customer Checkout to the SAP Customer Checkout Server Created At Created By Modified At Modified By Origin Created At Origin Created By Origin Modified At Origin Modified By Date and time when the receipt was created in SAP Customer Checkout Server Username of the user who created the receipt in the SAP Customer Checkout Server Date and time when the receipt was modified in SAP Customer Checkout Server Username of the user who modified the receipt in SAP Customer Checkout Server Date and time when the receipt was originally created in SAP Customer Checkout Username of the user who originally created the receipt in SAP Customer Checkout Date and time when the receipt was originally modified in SAP Customer Checkout Username of the user who originally modified the receipt in SAP Customer Checkout Working with SAP Customer Checkout Server C U S T O M E R 67

68 Field Total Gross Amount Discount Amount Discount Percentage Payment Gross Amount Payment Tax Amount Total gross amount of the receipt posted in SAP Customer Checkout Discount amount of the receipt posted in SAP Customer Checkout Discount percentage of the receipt posted in SAP Customer Checkout Payment gross amount of the receipt posted in SAP Customer Checkout Payment tax amount of the receipt posted in SAP Customer Checkout Sales Items This section of the Receipts tile provides information about the sales items assigned to the selected receipt. Striked out sales items are the ones that are void and were not posted from SAP Customer Checkout to the SAP ERP system (for example, cancelled sales items). Table 35: Sales Items Field Number Article ID Type Quantity Sales item position identifier Article ID sent from the SAP ERP system Type of sales item sent from the SAP ERP system of the sales item Quantity of the sales item Delivered Quantity Only relevant for Reserve Invoice: determines the delivery quantity of a reserve invoice in SAP Customer Checkout. UoM Unit of Measurement Code used for the sales item 68 C U S T O M E R Working with SAP Customer Checkout Server

69 Field Tax Code Unit Gross Amount Currency Discount Amount Discount % Payment Net Amount Payment Tax Amount Payment Gross Amount Tax code of the sales item sent from the SAP ERP system Unit gross amount of the sales item sent from the SAP ERP system Currency of the sales item Discount amount assigned to the sales item in SAP Customer Checkout Discount in percentage assigned to the sales item in SAP Customer Checkout Payment net amount of the sales item sent from SAP Customer Checkout Payment tax amount of the sales item sent from SAP Customer Checkout Payment gross amount of the sales item sent from SAP Customer Checkout You can view detailed information about the sales item when you select its receipt. Table 36: Sales Item Detailed Information Field Article ID Type Quantity UoM Tax Code Unit Gross Amount Discount Purpose Code Return Reason Code Price List ID Article ID sent from the SAP ERP system Type of sales item sent from the SAP ERP system of the sales item Quantity of the sales item Unit of Measurement Code used for the sales item Tax code of the sales item sent from the SAP ERP system Unit gross amount of the sales item sent from the SAP ERP system Discount Purpose Code sent from the SAP ERP system Return Reason Code sent from the SAP ERP system ID of the price list in the SAP ERP system assigned to the sales item in SAP Customer Checkout Working with SAP Customer Checkout Server C U S T O M E R 69

70 Field Warehouse GL Account Batch Number Serial Number Discountable Rounding Amount Warehouse ID sent from the SAP ERP system GL Account assigned to the sales item sent from the SAP ERP system Batch Number of the sales item sent from the SAP ERP system Serial Number of the sales item sent from the SAP ERP system Shows whether a sales item is discountable in the SAP ERP system. Determines on which level the rounding rules are used in SAP Customer Checkout. The 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. Voucher ID Status Voucher ID sent from the SAP ERP system Status of the sales item in the receipt in SAP Customer Checkout. Possible statuses are: Confirmed Void Created At Created By Modified At Modified By Origin Created At Date and time when the sales item was assigned to the receipt in SAP Customer Checkout Server Username of the user who assigned the sales item to the receipt in SAP Customer Checkout Server Date and time when the sales item was modified in the receipt in SAP Customer Checkout Server Username of the user who modified the sales item in the receipt in SAP Customer Checkout Server Date and time when the sales item was originally assigned to the receipt in SAP Customer Checkout 70 C U S T O M E R Working with SAP Customer Checkout Server

71 Field Origin Created By Origin Modified At Origin Modified By Payment Gross Amount Payment Tax Amount Payment Net Amount Discount Amount Discount Percentage Username of the user who originally assigned the sales item to the receipt in SAP Customer Checkout Date and time when the sales item was originally modified in the receipt in SAP Customer Checkout Username of the user who originally modified the sales item in the receipt in SAP Customer Checkout Payment gross amount of the sales item sent from SAP Customer Checkout Payment tax amount of the sales item sent from SAP Customer Checkout Payment net amount of the sales item sent from SAP Customer Checkout Discount amount assigned to the sales item in SAP Customer Checkout Discount in percentage assigned to the sales item in SAP Customer Checkout Tax Items This section of the Receipts tile provides information about tax items assigned to the selected receipt. Table 37: Tax Items Field Number Tax Rate Type Code Business Transaction Amount Currency Tax item position identifier Tax rate type code of the sales item sent from the SAP ERP system Business transaction amount used for the tax rate type code Currency used for the tax rate type code Working with SAP Customer Checkout Server C U S T O M E R 71

72 Payment Items This section of the Receipts tile provides information about the payment items assigned to the selected receipt. Striked out payment items are ones that are void and were not posted from SAP Customer Checkout to the SAP ERP system (for example, cancelled payment items). Table 38: Payment Items Field Number Payment Method Credit Card Type Amount in Payment Currency Exchange Rate Amount (in EUR) Payment item position identifier Payment method used for the receipt in SAP Customer Checkout Credit card type used for the receipt in SAP Customer Checkout Amount in payment currency used for the receipt in SAP Customer Checkout Exchange rate used for the receipt in SAP Customer Checkout Amount (in EUR) of the receipt 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 Additonal Fields tab. Information in an additional field is usually added using a plug-in in SAP Customer Checkout. Table 39: Additional Fields Field Name Desciption Name of the additional field used for the receipt in SAP Customer Checkout 72 C U S T O M E R Working with SAP Customer Checkout Server

73 Field Value Desciption Value of the additional field used for the receipt in SAP Customer Checkout 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, and see additional information about SAP Customer Checkout applications. When you select the Software tile, you will find an overview of all SAP Customer Checkout software versions and creation date, and detailed information about each of the software versions. In the overview, software versions may be marked with special icons: Flagged (Flag icon): shows software versions that have a file attached Favorite (Star icon): shows software version that is used as default software for automatic updates When you select one entry for a SAP Customer Checkout software version, you will see tabs with more information about the software version, installations, and outstanding installations. On the Details tab, you will find detailed information about the software version, such as the build number, version number, or file size. Table 40: Details Tab Field Name Version Build Number Internal Version File Size Downloads Name of the software Version number of the software Date and time when the software was created Internal version number of the software File size of the software Number of software downloads Installations Number of software installations Working with SAP Customer Checkout Server C U S T O M E R 73

74 Field Default Release Enable/Disable a software version to be used as default for automatic software updates. Example: When a SAP Customer Checkout application is installed and the central software management option has been enabled in the Configuration settings of SAP Customer Checkout, the application verifies if a newer software version is available. If the software version that is set as Default Release is newer, the SAP Customer Checkout application is updated. Created By Created At Modified By Modified At Username of the user who created the software installation Date and time when the software installation was created Username of the user who modified the software installation Date and time when the software installation was modified The Installations tab shows all relevant information about the SAP Customer Checkout applications that are running with the selected software version. This tab gives information about which software versions are running on each SAP Customer Checkout application. On the Outstanding Installations tab, you will find the SAP Customer Checkout applications that are waiting to be updated with the selected software version. Caution With SAP Customer Checkout release 2.0 Feature Pack 01, the Outstanding Installations tab is not yet supported. In case you have scheduled an automated software update for your SAP Customer Checkout application, but have not yet started the respective application, the software update is still outstanding. Table 41: Installations and Outstanding Installations Tab Field POS Instance Organization POS instance used by the software installation Organizational structure used by the software installation 74 C U S T O M E R Working with SAP Customer Checkout Server

75 Field Location Location used by the software installation Last Active Date and time when the software installation was last active Upload New Software Context In the Software tile, you also have the possibility to upload new software versions of SAP Customer Checkout. To upload a new SAP Customer Checkout software version into SAP Customer Checkout Server, you need to prepare the data in a zip file. Recommendation 1. Open the Command Prompt and navigate to the file where your SAP Customer Checkout.exe file is located that you have downloaded from the SAP Service Marketplace. 2. To extract the file, enter the following: SapCustomerCheckout_2_0.exe / X="<PathnameForExtractedFolder>" If you are working with WinRAR, unzip the.exe file (that you have downloaded from the SAP Service Marketplace) of the software version you want to upload into the SAP Customer Checkout Server. 3. Choose the subfolder CustomerCheckout and select all files to create a zip file. The zip file can be used in the SAP Customer Checkout Server. Procedure 1. In the Software tile of the SAP Customer Checkout Server, select Add. 2. Attach the zip file you have prepared and want to upload. 3. To save your edits, select Save. The new software version is displayed in the overview. Working with SAP Customer Checkout Server C U S T O M E R 75

76 Download Software File Context In the Software tile, you can download a software version as zip file. 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 Server, select the sofware version you want to download. 2. Choose Download. The zip file with the selected SAP Customer Checkout software version is downloaded Detach Software File Context You can also detach the update file from a software version within the Software tile in the SAP Customer Checkout Server. Procedure 1. In the Software tile of the SAP Customer Checkout Server, select the sofware 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. 76 C U S T O M E R Working with SAP Customer Checkout Server

77 Set Software Version as Default Context In the Software tile, you can set a software version to be used as default for automatic software updates. Procedure 1. In the Software tile of the SAP Customer Checkout Server, select the software version you want to set as default. 2. Select Set as Default, and select OK. The software version is now used as default for automatic software updates and marked as favorite in the overview Delete Software Version Context In the Software tile, you can delete software versions from SAP Cusomter Checkin Server. 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 Server, select the sofware version you want to delete. 2. Choose Delete and select OK. The software version is deleted from the SAP Customer Checkout Server. Working with SAP Customer Checkout Server C U S T O M E R 77

78 5.3.9 Sales reports The Sales reports tile lets you generate sales reports for a specific time period or cash desk that were sent from various SAP Customer Checkout applications in your organization. When you select the Sales Reports tile, you can view sales reports or download sales report files (as Microsoft Excel file). The following sales reports can be generated: 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 receips for various SAP Customer Checkout applications. This cashing up sales report includes further 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 who of the cashiers in your organization makes the most revenue. Revenue per Organization: generates sales reports aggregated by the organization units. For example, you have several cashdesks running in your stores and you want to track which of your organizations is making the most revenue. Cash Balance per PoS: shows the cash balance per SAP Customer Checkout application, grouped by the payment account (for example, card payment, cash, payment on credit, and voucher) Revenue per PoS: generates sales reports for revenue per SAP Customer Checkout application. For example, you can track which of your cashdesk applications is generating the most revenue and posting the most number of receipts. Revenue per Payment Method and Organization: generates sales reports for revenue-per-payment method and organization unit. 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. 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. Cancellations: creates sales reports for cancellation 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 an all-in-one sales report (included all above mentioned sales reports). The information displayed in the Sales Reports tile will vary depending on the sales report option you select. With SAP Customer Checkout 2.0 Feature Pack 01, you can download sales reports files (as Microsoft Excel files) for all reports. However, the Sales Reports tile will display only the following options: Revenue per Article Revenue per Cashier 78 C U S T O M E R Working with SAP Customer Checkout Server

79 Revenue per Organization Revenue per PoS Revenue per Payment Method and Organization Revenue per Payment Method and PoS Revenue per Article Group and Article Cancellations Returns Generate Sales Reports Procedure 1. In the Sales Reports tile of the SAP Customer Checkout Server, choose the respective 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 the sorting type and point of sale application for the sales report. 4. Choose Download (or Go) to start generating the sales report. For SAP Customer Checkout 2.0 Feature Pack 01, only a limited set of sales reports options can be generated. 5. The Microsoft Excel file with the selected sales report is downloaded (or shown in the UI) Articles In the Articles tile, you can centrally manage your articles used in SAP Customer Checkout when using the SAP Customer Checkout Server as your backend system. You can create, edit and deactivate an article, if necessary. To see more information, select an article in the overview on the left side of the screen. Working with SAP Customer Checkout Server C U S T O M E R 79

80 The following information about this article can be shown: Table 42: Articles Option Details Taxes Prices Displays all necessary information about the selected article. Displays all information about the tax for the selected article. Shows the pricelist assignment of the selected article to the different pricelists. In the Details tab, you can see the following information about the selected article: Table 43: Details Field ID Article Group Bar Code Unit of Measure Force Manual Price Entry Discountable Migrated Status Created at Created by This is the unique article ID. This ID can only be entered when creatings an article. Is it not editable after the article has been created. The article group shows the assignment of the article to the relevant article group. of the article Barcode of the article, which will be used to scan it at SAP Customer Checkout Unit of Measure of the article If this option is active, the price is not taken from the price list but the cashier has to insert it manually. If this option is active, the cashier is allowed to give a discount depending from his authorization rights. Shows if the article has been created in the SAP Customer Checkout Server or if it has been migrated from another backend or legacy system. Shows the status of the article, if it is active or inactive. Date and time when the article was created in SAP Customer Checkout Server Username of the user who created the article in SAP Customer Checkout Server 80 C U S T O M E R Working with SAP Customer Checkout Server

81 Field Modified at Modified by Date and time when the article was last modified in SAP Customer Checkout Server Username of the user who last modified the article in SAP Customer Checkout Server In the Taxes tab, you can see which tax code for which country is assigned to the respective article. 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 do it within the PoS Configuration tile (in the Tax Codes subtab). Any modifications you made, will be adapted to the tax code which is assigned to the article. Table 44: Taxes Field Country Tax Codes Rate of the country where the tax code is relevant for ID of the tax code of the tax code 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. Table 45: Prices Field Price List Price List Type Price Name of the price list. When clicking on the price list, you get forwarded to the respective price list details. In this field you can see if the price list includes net or gross prices. The price for the selected article in this price list. Working with SAP Customer Checkout Server C U S T O M E R 81

82 Create Articles The SAP Customer Checkout Server lets you create new articles. Procedure 1. In the Articles tile, click Add. 2. Enter the article data, and be sure to complete all mandatory fields marked with an asterisk (*). 3. After entering all relevant data, you can choose one of the following options below to proceed: To save the article (when choosing this option the article is also activated) To save the article as a draft To create another article (a new window opens, where you can enter all article data for a new article) To cancel all entries 4. Once you have selected an option, the article with all details is shown in the overview Edit Articles You can edit existing articles in the SAP Customer Checkout, if you want to maintain or adjust any settings. Context Once an article is created, the ID of this article cannot be edited in the SAP Customer Checkout Server. Procedure 1. Open the Articles tile. 2. Select the article you want to edit and click Edit. 3. Edit the article data as needed. a. In the Taxes tab, you can add, change, or delete a country specific tax code to the selected article. You can also assign multiple tax codes to an article, but one per country. To add a new tax code, click Assign tax. b. In the Prices tab, you can add the article to one or more price lists. To add the article to a price list, click Add price. 4. To save your edits of the article, click Save. 82 C U S T O M E R Working with SAP Customer Checkout Server

83 Delete or Deactivate Articles Articles can also be deleted or deactivated in the SAP Customer Checkout Server. Context Only articles that are in draft mode can be deleted from SAP Customer Checkout. Articles that have once been activated cannot be deleted. Procedure 1. Open the Articles tile. 2. Select the article (in draft mode) you want to delete or deactivate. 3. Choose Delete or Deactivate, depending on the action you want to perform. 4. Confirm the action with OK Price Lists In the Price List tile, you can manage your price lists to be used in SAP Customer Checkout, when using the SAP Customer Checkout Server as your backend system. You can create and edit price lists, and assign articles to price lists. To see more information, select a price list in the overview. The following information about this price list is shown: Table 46: Price lists Option Details Items Displays all necessary information about the selected article. Displays all information about the tax for the selected article. Working with SAP Customer Checkout Server C U S T O M E R 83

84 In the Details tab, you can see the following information: Table 47: Details Field ID Currency Amount Type Valid from Valid to Active Created at Created by Modified at Modified by This is the individual price list ID. Is it not editable after the price list has been created. In this field the name of the price list is shown, this field can be changed. Shows the currency of the price list. In this field you can see if the price list includes net or gross prices. Date as of which this price list is valid Date until which this price list is valid Here you can select if the price list is active (usable) or inactive. Date and time when the price list was created in SAP Customer Checkout Server Username of the user who created the price list in SAP Customer Checkout Server Date and time when the price list was last modified in SAP Customer Checkout Server Username of the user who last modified the price list in SAP Customer Checkout Server In the Items tab, you can add, change, or delete the assignment of articles to the respective price list. The following information is available for Items: Table 48: Items Field Article ID Price UoM (Unit of Measure) ID of the assigned article. When clicking on the article ID, you get forwarded to the respective article details. of the assigned article Price of the article in the selected price list Unit of Measure of the assigned article 84 C U S T O M E R Working with SAP Customer Checkout Server

85 Create Price Lists The SAP Customer Checkout Server lets you create new price lists. Procedure 1. In the Price Lists tile, click Add. 2. Enter the price list data, and be sure to complete all mandatory fields marked with an asterisk (*). 3. Save your edits Edit Price Lists You can edit existing price lists in the SAP Customer Checkout, if you want to maintain or adjust any settings. Context Once a price list is created, the ID of this price list cannot be edited in the SAP Customer Checkout Server. 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. 4. Save your edits. Working with SAP Customer Checkout Server C U S T O M E R 85

86 Assign Articles to Price Lists In the SAP Customer Checkout Server, you can assign articles to price lists, edit already assigned articles to price lists, or delete the assignment of articles to price lists, if necessary. 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 the respective article from the list shown, and enter a Price. 5. Save your edits Point of Sale Configuration Within the Point of Sale Configuration tile, you can maintain settings for tax codes, article groups, currencies and quick selections in your point of sales applications, when using the SAP Customer Checkout Server as your backend system. The following tabs are available in the Point of Sale Configuration tile: Table 49: Point of Sale Configuration tile On this tab Tax Codes Article Groups Currency Quick Selections You can... Maintain tax codes for sales items and articles used in SAP Customer Checkout Manage article groups used in SAP Customer Checkout applications Set currencies used in SAP Customer Checkout Configure the quick selection buttons used in your SAP Customer Checkout applications Tax Codes In the SAP Customer Checkout Server, you can define and specify tax codes for sales items and articles that are liable for taxes. You can see an overview of all your tax codes, create new tax codes, and edit a tax code. SAP Customer Checkout Server provides pre-delivered tax codes, for example for Germany. 86 C U S T O M E R Working with SAP Customer Checkout Server

87 Within the SAP Customer Checkout Server, it is not possible to activate tax codes which have the same tax code for the same country with overlapping validity period. Using a tax code for the same tax code and another country, is allowed when the tax code is inactive. Tax codes are not synchronized automatically with your SAP Customer Checkout applications, but have to be maintained manually in SAP Customer Checkout. Caution Deleting a tax code in the SAP Customer Checkout Server is not possible. If you want a tax code not to be used in articles, you have to deactivate the tax code. The following information is available for tax codes: Table 50: Tax Codes Field Country Type Code Rate Valid from Valid to Active Country for which this tax rate is used Tax rate type code used in printed receipts for sales items and articles. Tax rate in percentage Date as of which this tax code is valid in the application Date until which this tax rate is valid in the application displayed on the SALES screen in the Create/ Change Article dialog box for this tax rate. Enabled: Tax rate is used in the application. Disabled: Tax rate is not used in the application Article Groups In the SAP Customer Checkout Server, you can maintain article groups for articles and sales items handled. You can create new article groups, and edit an article group. Article Groups are special forms of merchandise category articles that can group together certain articles to form subgroups. In the SAP Customer Checkout Server, 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. When selecting an article group, sub-categories with further article groups are shown. Working with SAP Customer Checkout Server C U S T O M E R 87

88 Article groups are not synchronized automatically with your SAP Customer Checkout applications. When an article is transferred to SAP Customer Checkout, the related article group is also been transferred. It is not required to manually maintain the article group in SAP Customer Checkout. The assignment of articles to an article group is handled in the Articles tile in the SAP Customer Checkout Server. The following information is available for article groups: Table 51: Article Groups Field ID Name ID number of the article group Name of the article group Creating an Article Group Context SAP Customer Checkout Server lets you create new article groups. For example, you can create an article group and assign further article groups to the newly created article groups. Procedure 1. In the PoS Configuration tile of the SAP Customer Checkout Server, choose the Article Groups tab. 2. Select the Add icon on the right lower corner of the screen, to create a new article group. 3. Enter the article group data, and be sure to complete all mandatory fields marked with an asterisk (*). 4. To save the article group, click Save. 88 C U S T O M E R Working with SAP Customer Checkout Server

89 Editing an Article Group Context In the SAP Customer Checkout Server, you can manually edit existing article groups. For example, you may want to change the name of an article group or create further sub-categories for the article group. Procedure 1. Select the article group you want to edit, and choose the Edit icon on the right-hand side of the screen. 2. Edit the article group data as needed. Editing the ID of an article group is not possible in the SAP Customer Checkout Server. 3. To save your edits of the article group, click Save Moving an Article Group Context Article groups can also be moved within the PoS Configuration tile in the SAP Customer Checkout Server. For example, you can move an article group to another article group. When moving an article group to another article group, all sub-categories (article groups) assigned to this article group are also moved. Procedure 1. Select the article group you want to move, and choose the Move icon on the right-hand side of the screen. 2. Select the parent article group to which you want to move the article group. 3. To save your edits, click Save. Working with SAP Customer Checkout Server C U S T O M E R 89

90 Deleting an Article Group Context In the SAP Customer Checkout Server, you can also delete article groups. Deleting an article group is only possible if the article group is not used (if no articles are assigned to this article group). Procedure 1. Select the article group you want to delete, and choose the Delete icon on the right-hand side of the screen. 2. Confirm the article group to be deleted by clicking OK. 3. The article group is deleted from the SAP Customer Checkout Server Currency In the SAP Customer Checkout Server, you can maintain multiple currencies which can be used to maintain proces for articles. You can see an overview of all your currencies, add new currencies, and delete a currency, if necessary. SAP Customer Checkout delivers the following currencies by default: EUR CHF If you intent to use a different currency, you can maintain the currency within the PoS Configuration tile. Currencies maintained in the SAP Customer Checkout Server are not synchronized automatically with your SAP Customer Checkout applications, but have to be maintained manually. Caution If a currency is used in a price list, you cannot delete this currency. 90 C U S T O M E R Working with SAP Customer Checkout Server

91 Add New Currencies Context If you intent to use a different currency (and this is not pre-delivered), you can add a currency to the SAP Customer Checkout Server. Procedure 1. In the PoS Configuration tile of the SAP Customer Checkout Server, choose the Currency tab. 2. Select the Add icon on the right lower corner of the screen, to add the currency. 3. Enter the Currency (international three-letter currency code) to be added to the SAP Customer Checkout Server. 4. To save the currency, click Save Quick Selections In the SAP Customer Checkout Server, you can configure quick selection buttons shown in the SALES Screen of your SAP Customer Checkout applications. When using the user interface version 2.0, the configuration of the quick selections has to be maintained in the SAP Customer Checkout Server. Within the quick selections tab in the PoS Configuration tile of the SAP Customer Checkout Server, you can see an overview of all your quick selection configurations, create new quick selection structures, assign SAP Customer Checkout applications to a quick selection configuration, move a quick selection configuration to another, edit a quick selection configuration, and delete a quick selection configuration, if necessary. When you select one quick selection button, you will find tabs with more information such as general data, articles (assigned to this quick selection button), extended javascript, and extended CSS Style. For more information on how the quick selections are enabled and used in SAP Customer Checkout, read the SAP Customer Checkout User Guide. Working with SAP Customer Checkout Server C U S T O M E R 91

92 Creating Quick Selections Context Within the Quick Selections tab of the SAP Customer Checkout Server, you can create a hierarchical tree structure of buttons and subsections. You can assign single articles to a button. Clicking these buttons adds the respective articles to the receipt. Buttons can be labeled, illustrated with icons, and positioned freely in the quick selection area. It is also possible to extend each buttons representation and behavior with CSS styles and JavaScript. Procedure 1. In the PoS Configuration tile of the SAP Customer Checkout Server, choose the Quick Selections tab. 2. Select the Add icon on the right lower corner of the screen, to create a new quick selections structure for your point of sales instances. Depending on the quick selections structure you want to create, you need to set up the sections correctly. When using the user interface version 2.0, you have to consider that you need the following sections: center bottom Example When working in the food and beverage area, and you want to create two separate quick selection sections - one for food and one for beverage - we recommend to set up the following quick selections structure: center: configure all quick selection buttons for food bottom: configure all quick selection buttons for beverage Within each of the section, you can create further buttons or subsections with buttons. 3. Enter the quick selection data, and be sure to complete all mandatory fields marked with an asterisk (*). Table 52: Quick Selection Field Text Name of the quick selection configuration 92 C U S T O M E R Working with SAP Customer Checkout Server

93 Field Color Colour used for the quick selection This field is only relevant when using the user interface version 2.0. Column Defines at what position of the quick selection display area this button is shown (y coordinate). When no column is defined, the default column is used. The default column is 0. Row Defines at what position of the quick selection display area this button is shown (x coordinate). When no row is defined, the default row is used. The default row is 0. Horizontal Size Defines the horizontal size of the display area for this quick selection button. When no horizontal size is defined, the default horizonzal size is used. The default horizontal size is 1. Vertical Size Defines the vertical size of the display area for this quick selection button. When no vertical size is defined, the default vertical size is used. The default vertical size is 1. Extended Javascript Enables to extend the quick selections via Javascript This field is only relevant when using the user interface version 1.0. Extended CSS Style Enables to extend the quick selections via CSS Style 4. To save the quick selection, click Save Editing Quick Selections In the SAP Customer Checkout Server, you can edit the configuration of your quick selection buttons assigned to the point of sales instances. Working with SAP Customer Checkout Server C U S T O M E R 93

94 The following options are possible when selecting a quick selection button: Edit general data of the quick selection Upload or remove an image for the quick selection Add a subnote to the quick selection Assign an article to the quick selection When uploading an image for the quick selection, the Text entered for the quick selection, is not displayed. Only the image is shown in the user interface. When assigning an article to the quick selection, you can select an article provider from which the article should be used. There are two possible options: From the SAP Customer Checkout Server (when using this system as your backend system) From and External ID (when using an SAP ERP system as your backend system) To assign the article to a quick selection, you need to enter the article ID in the Select Article field Assigning PoS Instances to Quick Selections Context In the SAP Customer Checkout Server, you can centrally assign a quick selection configuration to a SAP Customer Checkout application. When the central quickselection management is enabled in your SAP Customer Checkout application, this means that the configuration of your quick selection buttons is not handled locally on your point of sales application, but centrally taken from the SAP Customer Checkout Server. Procedure 1. In the PoS Configuration tile of the SAP Customer Checkout Server, choose the Quick Selections tab. 2. Choose the Assign PoS Instance icon from the respective quick selection configuration. 3. A new tab opens where you can see all organizational units that are assigned to the selected quick selection or add a new organizational unit to the quick selection. 4. Choose the Add icon in the right lower corner of the screen. 5. Select the PoS instance to which you want the quick selection to be assigned. 94 C U S T O M E R Working with SAP Customer Checkout Server

95 6. To save your edits, click Save Moving Quick Selections Context The Quick Selections tab within the PoS Configuration tile lets you move a quick selection configurations. For example, you can move a quick selection header configuration, and quick selection buttons or subsections to other quick selection configurations. When moving a quick selection configuration, all quick selection buttons (subsections) assigned to this configuration are also moved. Procedure 1. In the PoS Configuration tile of the SAP Customer Checkout Server, choose the Quick Selections tab. 2. Select the subsections or buttons of the quick selection you want to move. 3. Choose the Move icon on the right-hand side. 4. Select the parent quick selection you want the quick selection to be moved to and confirm by clicking OK. 5. To save your edits, click Save Deleting Quick Selections Context Quick Selections can be deleted from the SAP Customer Checkout, for example quick selections (or subsections assigned to a quick selection) that are no longer used. When deleting a quick selection configuration, all quick selection buttons (subsections) assigned to this configuration are also deleted. Working with SAP Customer Checkout Server C U S T O M E R 95

96 Procedure 1. In the PoS Configuration tile of the SAP Customer Checkout Server, choose the Quick Selections tab. 2. Select the quick selection (or subsection) you want to delete. 3. Choose the Delete icon on the right-hand side and confirm the deletion by clicking OK. 4. The quick selection is deleted from the SAP Customer Checkout Server. 5.4 Loyalty Management App Users The App Users tile lets you manage loyalty users who are registered through the Loyalty API. You can keep track of your loyalty users: analyze their history, assign bonus points manually to individual loyalty users, search, block or delete a loyalty user, if necessary. Loyalty users shown in SAP Customer Checkout Server are the loyalty users who are registered within the Loyalty API that is integrated with your application. Caution Loyalty users in SAP Customer Checkout Server do not represent the customers in your ERP system or in the SAP Customer Checkout application. To create a loyalty user in the existing ERP system, the authorization of the following third-party system is necessary: SAP Event Ticketing For more information about loyalty user authorization, see section Security [page 23]. Also, a loyalty user can register directly via the Loyalty API while creating a new account. When you select the App Users tile, you will find an overview of all registered loyalty users and detailed information about each of their accounts. You can also use Search to find a loyalty user. And you can sort or filter your loyalty users. The detailed information view of a loyalty user account is divided into these sections: Table 53: App Users Options Option User Details Displays general user data about the loyalty users such as username and ID. 96 C U S T O M E R Working with SAP Customer Checkout Server

97 Option User Identities User Coupons User History Shows the user ID and how the loyalty user identification has been authorized. Provides you with an overview of the coupons that the loyalty user has purchased and redeemed. Provides you with an overview of the user s transaction. What information is available for Loyalty Users? Table 54: User Details Field Public ID Username Last Name First Name Date of Birth App Token Available Number that is automatically generated for the loyalty user address of the loyalty user Last name of the loyalty user First name of the loyalty user Date of Birth of the loyalty user When a loyalty user has already been registered and has a valid App Token. Enabled: Loyalty user has a valid Token. ET Leading Created by Shows whether SAP Event Ticketing is the leading system for the user s data User name of the loyalty user in SAP Customer Checkout Server who created the user. If the loyalty user has been authorized through a third party system (SAP Event Ticketing, Facebook or Twitter), this field remains empty. Created at Date and time when the loyalty user was created Working with SAP Customer Checkout Server C U S T O M E R 97

98 Field Modified by User name of the user in SAP Customer Checkout Server who modified the user. If the loyalty user has been authorized through a third party system (SAP Event Ticketing, Facebook or Twitter), this field remains empty. Modified at Date and time when the loyalty user was modified Table 55: User Identities Field Identity Provider Name Name of the third party system that has authenticated the loyalty user. Possible Identity Provider Names are as follows: SAP Event Ticketing Facebook Twitter With release 2.0 of SAP Customer Checkout, only the authorization via SAP Event Ticketing is supported. Facebook and Twitter is not yet supported with release 2.0. Value Value Two ID of the loyalty user within the third party systems ID of the ERP system Table 56: User Coupons Field Coupon Valid from Valid to State Name of the coupon that has been purchased or redeemed by the loyalty user Validity date from when the coupon can be purchased by the loyalty user Validity date until when the coupon can be purchase by the loyalty user Displays if the coupon has already been redeemed 98 C U S T O M E R Working with SAP Customer Checkout Server

99 Table 57: User History Fieldq Transaction Date Action Name and ID of the transaction Date and time of the transaction 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. Created by Point Value Value Internal action ID reference User name of the user who has created the transaction within SAP Customer Checkout Server Amount of bonus points that has been assigned for the respective transaction Value displayed depending on the action selected Blocking a User Context You can also block a loyalty user within SAP Customer Checkout Server if you want to ensure that the user cannot perform any further transactions in SAP Customer Checkout such as purchasing coupons, collecting bonus points in SAP Customer Checkout or redeeming coupons. Procedure 1. In App Users, select the loyalty user you want to block, and choose Block User. 2. Confirm the Blocking of the respective loyalty user via clicking OK. Working with SAP Customer Checkout Server C U S T O M E R 99

100 3. The loyalty user is now blocked and cannot perform further transactions within the Loyalty API Deleting a User Context In this section you can anonymize loyalty users who have registered through the Loyalty API. To anonymize a user means to overwrite all the personalized data of this loyalty user. Once you have deleted a loyalty user, the loyalty user is not deleted in the SAP Customer Checkout Server database, but set to anonymous. Procedure 1. Select the loyalty user you want to anonymize and click on the Block User icon in the right lower corner of the screen. 2. Confirm the deletion of the respective loyalty user via clicking OK. 3. The loyalty user is now anonymized and cannot be identified anymore Correcting User Bonus Points for Individual Loyalty Users Context In SAP Customer Checkout Server, you can correct the amount of bonus points accumulated by individual loyalty users who have registered through the Loyalty API. You can either add or subtract bonus points. Procedure 1. In App Users, select the loyalty user whose amount of bonus points you want to modify, and then choose Correct User Bonus Points. 2. Choose Add or choose Subtract. 3. Enter the amount of bonus points you want to add or subtract. 100 C U S T O M E R Working with SAP Customer Checkout Server

101 4. Click OK to save your changes Point Assignments In SAP Customer Checkout Server, you have the option to centrally assign bonus points to all your loyalty users who are registered in the Loyalty API. You can assign bonus points for a specific event or reason, see an overview of the latest bonus points you have assigned, or cancel the assignment of bonus points. The following sections are available in the Point Assignments tile: Table 58: Assign Bonus Points Options Option Assign Bonus Points to all Users Assigned Bonus Points Enables the assignment of bonus points to all loyalty users registered in the Loyalty API Provides you with an overview of the assigned bonus points Assign Bonus Points to all Users Context If you want to assign bonus points for specific reasons to all loyalty users, you can do it centrally in the SAP Customer Checkout Server. For example, you might assign bonus points to everyone for special events or campaigns related to your company. Procedure 1. In the Assign Bonus Points to all Users section, enter a reason for the assignment. 2. Enter the amount of points. 3. To assign the bonus points to all loyalty users registered in the Loyalty API, choose Assign Points. Working with SAP Customer Checkout Server C U S T O M E R 101

102 The Assign Bonus Points to all Users section provides these details: Table 59: Field Reason Process ID Execution start Execution done Points Execution state Reason for the assignment of bonus points ID of the process executing the assignment of bonus points Displays the date and time when the bonus points were assigned to all loyalty users. Displays the end date and time when the bonus points have been assigned to all loyalty users Shows the amount of bonus points that you have assigned for this transaction Indicates if the bonus points have already been assigned to the loyalty users. Possible states are: Idle Running Cancelled Finished Execution Result Indicates if the bonus points have been assigned successfully. Possible results are: None Cancelled Success Failure Fatal Status Message Cancel Worker Shows the amount of loyalty users that have already been processed Enables the cancellation of the assigned bonus points 102 C U S T O M E R Working with SAP Customer Checkout Server

103 5.4.3 Coupons Coupons are a type of voucher for buying special sales items or articles at a reduced price. In the Coupons tile, you can centrally manage the coupons purchased from your registered loyalty users or the coupons handled as discounts in the sales user interface version 2.0. You can see an overview of all your coupons, assign discount rules to a coupon, edit, create, search, or cancel a coupon, if necessary. There are the following options to be distinguished when using coupons in SAP Customer Checkout: Using coupons for the loyalty API Loyalty users can buy coupons after collecting a certain amount of bonus points. In SAP Customer Checkout Server, you can determine the number of bonus points needed to purchase each coupon. Once loyalty users have scored the respective amount of bonus points for a coupon, they can buy the coupon. Using coupons for the sales user interface version 2.0 With the sales user interface version 2.0 of SAP Customer Checkout, coupons are handled as discounts and can be applied on sales item level. You can apply discounts only when the discount rules are maintained in the Coupons tile. In the Coupons tile, you can use Search to find a certain coupon. In addition, you can select more options within the Coupons tile: Table 60: Coupon Options Option Sort Lets you sort coupons by the following: ID Status Title Valid from Valid to None Filter Lets you filter coupons by the following: ID Status Title Valid from Valid to Create New Coupon Lets you create a new coupon. Working with SAP Customer Checkout Server C U S T O M E R 103

104 When you select one of the coupons, more tabs with detailed information about each of the coupons are displayed: Table 61: Option Details Articles Displays general coupon information such as general data, price, validity information, and administrative data of the coupon. Shows the articles (from your SAP ERP system) that are assigned to the respective coupon. This tab is only relevant when using a coupon for the loyalty API. Valid coupon ID Generates valid coupon IDs for the respective coupon to be used in SAP Customer Checkout. This tab is only relevant when using a coupon for the sales user interface version 2.0 in SAP Customer Checkout. Discount rules Enables you to set discount rules to be used for the respective coupon. This tab is only relevant when using a coupon for the sales user interface version 2.0 in SAP Customer Checkout. Table 62: Details Tab Field ID Unique identifier of the coupon that is set while creating the coupon 104 C U S T O M E R Working with SAP Customer Checkout Server

105 Field Type Shows as of which type the coupon to be handled in SAP Customer Checkout. The following coupon types are possible: App: When App is selected as type, the coupon is used for the loyalty API and app users can buy the coupon after collecting a certain amount of bonus points. Coupon: When Coupon is selected as type, the coupon can only be used for the sales user interface version 2.0 and is handled as a discount on a sales item in SAP Customer Checkout. Title Discount purpose code Name of the coupon Discount purpose code to be set for the respective coupon This field is only relevant when Coupon has been selected as coupon type. Offline available Price in Points Enable/ disable the coupon to be used when SAP Customer Checkout application is in offline mode. Brief description of the coupon The number of bonus points that loyalty users must pay for the coupon. This tab is only relevant when using a coupon for the loyalty API. Only valid with coupon ID Quantity per coupon ID Indicates that the respective coupon can only be used when a valid coupon ID has been generated in the Valid coupon ID tab. Displays how many times the valid coupon ID that has been generated can be used. Working with SAP Customer Checkout Server C U S T O M E R 105

106 Field Quantity per Account Displays how many times each coupon can be redeemed per loyalty user account in SAP Customer Checkout This tab is only relevant when using a coupon for the loyalty API. Quantity for Sale Displays how many times the coupon can be redeemed in total This tab is only relevant when using a coupon for the loyalty API. Valid from Earliest date that the coupon can be purchased by loyalty users This tab is only relevant when using a coupon for the loyalty API. Valid to Final date that the coupon can be purchased by loyalty users This tab is only relevant when using a coupon for the loyalty API. Redeemable from Earliest date that the coupon can be redeemed This tab is only relevant when using a coupon for the loyalty API. Redeemable to Final date that the coupon can be redeemed This tab is only relevant when using a coupon for the loyalty API. 106 C U S T O M E R Working with SAP Customer Checkout Server

107 Field Status Indicates the status set for the coupon. Possible statuses are: 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 purchased and redeemed by loyalty users. Inactive: The coupon cannot be used in SAP Customer Checkout, or redeemed by loyalty users. Created by Created at Modified by Modified at User name of the user who created the coupon in SAP Customer Checkout Server Date and time when the coupon was created User name of the user who modified the coupon in SAP Customer Checkout Server Date and time when the coupon was modified The Articles tab is only relevant when App is set as coupon type. Table 63: Articles Tab Field Article number Relative Absolute Article number from your SAP ERP system Relative discount value to be used for the respective article Absolute discount value to be used for the respective article Table 64: Valid coupon IDs Tab Field ID Status Username Unique ID number which is generated as coupon ID to be used for the respective coupon Status of the coupon ID Username of the user who redeemed the coupon in SAP Customer Checkout This field is only relevant when App is set as coupon type. Working with SAP Customer Checkout Server C U S T O M E R 107

108 Field Name Name of the user who redeemed the coupon in SAP Customer Checkout This field is only relevant when App is set as coupon type. The Discount rules tab is only relevant when Coupon is set as coupon type. Table 65: Discount rules Tab Field ID Rule Unique identifier of the discount rule that can be set manually Discount rule to be used when the respective coupon is selected in SAP Customer Checkout. You can set a discount amount in percentage, and also maintain the discount rule for a specific article or article groups. The following discount rule types can be selected and adapted in the following: 100% for the 1 most expensive article of all article groups 5% on one of all article Creating a Coupon Context Coupons purchased from loyalty users and redeemed in SAP Customer Checkout can be centrally created in SAP Customer Checkout Server. Furthermore, you can create coupons that can be used in the sales user interface version 2.0 of SAP Customer Checkout. 108 C U S T O M E R Working with SAP Customer Checkout Server

109 Procedure 1. Choose Create New Coupon. 2. Select the coupon type to be created, and enter the coupon data. Be sure to complete all mandatory fields marked with an asterisk (*). 3. To save the coupon, click Save Editing a Coupon Context In SAP Customer Checkout Server, 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. When using the coupon for the loyalty API, you might want to add an image to your coupon. To add an image to the specific coupon, choose Upload new image and select the image you want to be displayed for the coupon. 3. To save your edits of the coupon, click Save Assign an Article to a Coupon This field is only relevant when App is set as coupon type. You can assign the coupon to a certain article from your ERP system. Or you can assign them to items that are not listed as article in your ERP (for example, money can t buy articles) but that must be processed and redeemed via your ERP system. Coupons can be created for articles with relative or absolute discounts. Working with SAP Customer Checkout Server C U S T O M E R 109

110 Procedure 1. Select the coupon you want to assign an article to, and choose the Articles tab. 2. Click Add, to assign an article to the coupon. 3. Enter the respective article number from your ERP system and give a relative or absolute discount. You can add more articles to the coupon. For example when using an article with various sizes, you can assign the coupon to more than one article. 4. To save your edits, click Save Set Discount Rules for a Coupon When using the sales user interface version 2.0, discounts can only be applied to articles and sales items via coupons. 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. Enter an ID for the discount rule and select a template to be used. 4. To save your edits, click Save. All blue marked options of the discount rule are editable. In case you want change any of the options (discount percentage, article or article group the discount rule to be applied to), you can select the respective option and change the data as needed. Save your edits. Caution You can also delete discount rules from coupons (only coupons that are in status DRAFT), if needed. Once a coupon has been activated, discount rules cannot be deleted. 110 C U S T O M E R Working with SAP Customer Checkout Server

111 Generate Valid Coupon ID for a Coupon In order to use coupons in SAP Customer Checkout, valid coupon IDs need to be generated within the SAP Customer Checkout Server. Context Depending on the usage of the coupon within SAP Customer Checkout, the following two scenarios are possible: When using coupons for the loyalty API, the coupon IDs do not need to be generated manually. Once the loyalty users purchase the coupon via the coupon shop, a valid coupon ID is generated by the system. When using coupons for the sales user interface version 2.0, the coupon IDs have to be generated manually in the SAP Customer Checkout Server in order to use them in the point-of-sale application. Before you generate a valid coupon ID to use the coupon in SAP Customer Checkout, make sure to set a discount rule for the respective coupon. Procedure 1. Select the coupon for which you want to generate a valid coupon ID, and choose the Valid coupon IDs tab. 2. Choose Generate, and Execute to proceed. 3. The valid coupon ID is shown in the list and can be used in SAP Customer Checkout. In the SALES user interface version 2.0, you will find an entry per coupon ID Promotion Code Promotion Codes contain a value in points that can be used by the loyalty users for special marketing or promotion campaign within an organization. Loyalty users scan the promotion code and collect loyalty points via the code. In 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, if necessary. You can use Search to find a certain promotion code. You can select different options within the Promotion Code tile: Working with SAP Customer Checkout Server C U S T O M E R 111

112 Table 66: Promotion Code Options Option Sort Lets you sort promotion codes by the following: Status Valid from Date Valid to Date Value in Points None Filter Lets you filter promotion codes by the following: 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 provides these details: Table 67: Coupons Field Code ID of the promotion code that can be set manually When creating a new promotion code, the system automatically creates a L in front of the ID. Caution The barcode of the promotion code is not generated in the SAP Customer Checkout Server, but has to be created by an external barcode generator. Value in Points Valid from Valid to Quantity per Account Brief description of the promotion code Amount of loyalty points assigned to the promotion code Earliest date when the promotion code can be redeemed Final date when the promotion code can be redeemed Displays how many times each promotion code can be redeemed per loyalty user account. 112 C U S T O M E R Working with SAP Customer Checkout Server

113 Field Quantity for Sale Status Displays how many times the promotion code can be redeemed in total Indicates the status set for the promotion code. Possible statuses are: 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 loyalty users and redeemed. Inactive: The promotion code cannot be used or redeemed. Deleted: The promotion code is deleted and cannot be activated or edited. Created by Created at Modified by Modified at User name of the user who created the promotion code in SAP Customer Checkout Server Date and time when the promotion code was created User name of the user who modified the promotion code in SAP Customer Checkout Server Date and time when the promotion code was modified Creating a New Promotion Code Context In the SAP Customer Checkout Server, 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 of the SAP Customer Checkout Server, click on the Add icon in the left lower corner of the screen. 2. Enter the promotion code data, and be sure to complete all mandatory fields marked with an asterisk (*). 3. To save the promotion code, click Save. Working with SAP Customer Checkout Server C U S T O M E R 113

114 Editing a Promotion Code Context In the SAP Customer Checkout Server, you can manually edit existing promotion codes. For example, you may want to change the quantity for sale or extend the validity date of a promition code. Procedure 1. Select the promotion code you want to edit, and choose Edit in the left lower corner of the screen. 2. Edit the promotion code data as needed. 3. To save your edits of the promotion code, click Save Loyalty Configuration This section is of particular importance, when you have a Loyalty API integrated to the SAP Customer Checkout application. In SAP Customer Checkout Server, you can create loyalty-point transactions for loyalty user accounts from the Loyalty API, which is integrated to SAP Customer Checkout Server. Loyalty points let you to set up events that are related to your business, and define specific actions for loyalty users to perform. Example When you are working in the Sports and Entertainment area and have integrated a mobile application for your loyalty users, you can configure a loyalty-point transaction and determine an amount of loyalty points that loyalty users can earn or the number of loyalty points that can be purchased by ticket. On the Details tab, you can create, activate, deactive edit, and delete loyalty-point transactions, if necessary. The following information is available: Table 68: Loyalty Configuration Option Name Name of the loyalty points transaction of the loyalty points transaction 114 C U S T O M E R Working with SAP Customer Checkout Server

115 Option Season ticket event ID Season ticket default event ID Points for season ticket Point cap for tickets Event ID for which the season ticket is maintained in the SAP Event Ticketing system Booklet default event ID in the SAP Event Ticketing system Amount of loyalty points that is defined for the purchase of a season ticket 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. Points for registration Exchange rate for points Displays the amount of loyalty points that are assigned to loyalty users for their registration Displays the exchange rate in points: Example When your default currency is EUR and you have set a Point Exchange Rate of 5, for every EUR of their purchase loyalty users will get 5 loyalty points. for registration Maximum ticket scans per day Maximum ticket scans per event Maximum ticket scans per account Status shown when the loyalty user is registering to the Loyalty API Displays how many tickets can be scanned per day Displays how many tickets can be scanned per event Displays how many tickets can be scanned per loyalty user account Shows the status of the loyalty-point transaction. Possible statuses are: Active Inactive Created by Created at Username of the user who created the loyalty-point transaction in SAP Customer Checkout Server Date and time when the loyalty-point transaction was created Working with SAP Customer Checkout Server C U S T O M E R 115

116 Option Modified by Modified at Username of the user who modified the loyalty-point transaction in SAP Customer Checkout Server Date and time when the loyalty-point transaction was modified Only one loyalty-point transaction (action) can be set to Active). On the Events tab, you can assign loyalty-point transactions to events (while using the SAP Event Ticketing system). You can create new events, edit, and delete events, if necessary. The following information is available: Table 69: Events Option Event Ticketing event ID Name of the event ID for this event in the SAP Event Ticketing system 116 C U S T O M E R Working with SAP Customer Checkout Server

117 6 Integrate SAP Customer Checkout Server with SAP Customer Checkout In SAP Customer Checkout, you can integrate the SAP Customer Checkout Server application. Especially when using the voucher management of SAP Customer Checkout Server, you will need to integrate the SAP Customer Checkout Server application into SAP Customer Checkout. To use the Central-Server voucher module that SAP Customer Checkout Server provides, you need to go to your SAP Customer Checkout system and select the Integration subtab of your Configuration Tab. Follow the steps described in the Integration Guide of SAP Customer Checkout. After you have set the SAP Customer Checkout Server voucher module in your SAP Customer Checkout application, do a Voucher synchronization to update all vouchers. With release 2.0 of SAP Customer Checkout Server, you can only use the voucher management of the application with SAP Customer Checkout. The functionality to collect and redeem loyalty points through SAP Customer Checkout is not yet supported with version 2.0 Integrate SAP Customer Checkout Server with SAP Customer Checkout C US TO M E R 117

118 7 Using SAP Customer Checkout Server as backend system With SAP Customer Checkout 2.0 Feature Pack 01, the SAP Customer Checkout Server can also be used as backend system for SAP Customer Checkout. When using the SAP Customer Checkout Server as backend system for your SAP Customer Checkout applications, the following steps are relevant: Configure and create data in the SAP Customer Checkout Server Initial configuration settings in SAP Customer Checkout Maintain relevant settings in SAP Customer Checkout Caution The SAP Customer Checkout Server cannot replace any SAP ERP system (for example, in regards of the financial accounting function), as the functionalities are very limited. 7.1 Configure and Create Data in SAP Customer Checkout Server To use the SAP Customer Checkout Server as your backend system, you need to maintain the respective 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 Server, in order to be able to add them into a receipt in your SAP Customer Checkout applications. For more information, see sections Articles [page 79], Price Lists [page 83], and Point of Sale Configuration [page 86]. Caution Customers cannot be created in the SAP Customer Checkout Server. 118 C U S T O M E R Using SAP Customer Checkout Server as backend system

119 7.2 Initial Configuration Settings in SAP Customer Checkout When you start SAP Customer Checkout for the first time, you need to maintain the SAP Customer Checkout Server as backend system in the initial settings. Prerequisites You'll need the following information: The cash desk prefix, which has to be applied in the installation. Each cash desk must have a unique cash desk prefix The service endpoint information of the SAP Customer Checkout Server 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 the <4-digit cash desk prefix>. 3. Select the SAP Customer Checkout Server to be used as the type of ERP system for this SAP Customer Checkout application and to communicate with. 4. Enter all relevant service endpoint information for the SAP Customer Checkout Server. 5. Enter and confirm the Password for the Admin user (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 All further settings can be configured in SAP Customer Checkout, to adapt the application to your requirements. For more information on the configuration settings in SAP Customer Checkout, see the SAP Customer Checkout Configuration Guide. Using SAP Customer Checkout Server as backend system C U S T O M E R 119

120 When using the SAP Customer Checkout Server as backend system, the central receipt management is activated. All receipts posted in SAP Customer Checkout are sent to the SAP Customer Checkout Server. 120 C U S T O M E R Using SAP Customer Checkout Server as backend system

121 8 Security Guidelines and Recommendations In this section you will find all security-related aspects for using of SAP Customer Checkout Server. 8.1 Initial Password and Password Policy When you start SAP Customer Checkout Server for the first time, the initial configuration screen is displayed and you have to enter a password for the Admin User. Enter a strong password. You can also change this password later in SAP Customer Checkout Server. To do that, choose Settings. 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 Server 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, Recommendation You should not use the same password as for the SAP Customer Checkout application. For the initial configuration of SAP Customer Checkout Server, you also have to enter a hashkey, which used to encrypt the password of the database user. Again, enter a strong password here. 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 Server 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, Security Guidelines and Recommendations C US TO M E R 121

122 8.2 Resetting Admin User In case you have forgotten or locked your password to login to SAP Customer Checkout Server, you have the option to reset your password. Context The reset of your password can only be done on the system where your SAP Customer Checkout Server is running. Procedure 1. Open your web browser and enter the following URL: of the server>/ <path>/recover.html 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 will be displayed and you need to enter the following fields: Table 70: Recovery Screen Options Option Database Password New Admin Password Confirm new Admin Password Password of the database management system used for the SAP Customer Checkout Server New password that you want to assign for the Admin User Confirmation of the newly assigned password for the Admin User 3. To confirm your changes, choose OK. 4. The admin user is now reset and you can login to SAP Customer Checkout Server. 8.3 User Roles SAP Customer Checkout Server is delivered with the following user roles by default: ADMINISTRATOR, CASHIER, and SALESMANAGER 122 C U S T O M E R Security Guidelines and Recommendations

123 If needed, you can create further user roles in SAP Customer Checkout Server. For more information, see section Roles [page 37]. 8.4 Firewall To secure the SAP Customer Checkout Server 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. The configuration of a firewall is especially important because SAP Customer Checkout Server has the possibility to be integrated with SAP Event Ticketing. This means 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 Server, it is also relevant to secure the application with regard to 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 8.5 Auto Logout SAP Customer Checkout Server has an auto logout time, after which the Admin User is automatically logged out if the application is not actively used. The auto logout time is ten minutes. The auto logout is automatically provided by SAP and cannot be modified. 8.6 Secure Connections In general, it is recommended to use content encryption for client-server communications. So you should 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 has to start with instead of Security Guidelines and Recommendations C US TO M E R 123

124 8.7 Virus Scanner SAP strongly recommends that you install antivirus software on the application platform operating system. 8.8 Software Updates Context To protect SAP Customer Checkout Server from vulnerabilities, keep the software and operating system up to date. SAP Customer Checkout Server runs with Apache Tomcat version 8 or later. SAP recommends that you use the latest version of Apache Tomcat 8 or later. To keep the software up to date, you can supply the latest software version of SAP Service Marketplace. Software Updates are provided as new Web Application Archive for the SAP Customer Checkout Server application. Procedure 1. Download the latest version of SAP Customer Checkout Server from SAP Service Marketplace. 2. Caution During an update, the SAP Customer Checkout Server cannot be accessed. Rename the SAP Customer Checkout Server.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.0) 3. You can now start your updated SAP Customer Checkout Server application as usual. 124 C U S T O M E R Security Guidelines and Recommendations

125 Important Disclaimers and Legal Information Coding Samples Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP intentionally or by SAP's gross negligence. Accessibility The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does not apply in cases of wilful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP. Gender-Neutral Language As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible. Internet Hyperlinks The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency (see: Important Disclaimers and Legal Information C US TO M E R 125

126 go.sap.com/registration/ contact.html 2016 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 index.epx for additional trademark information and notices.