Manual Retail SAP 1

ADMINISTRATOR'S GUIDE | PUBLIC
15-04-16
SAP RETAIL EXECUTION 3.5 Administrator Guide

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

Content
1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1 History of Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2 SAP Retail Execution 3.3.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
1.3 About this Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.4 Related Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.5 Further Useful Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.6 Important SAP Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2 SAP Retail Execution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
2.2 Key Benefits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.3 Technical System Landscape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.4 Compatibility Matrix for Release Versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3 Installations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.1 General Installation Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
SAP Notes for Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Information Available in SAP Service Marketplace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Further Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.2 Installation Matrix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.3 Client Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Installing the App on an iOS Device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Installing the App on an Android Device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4 Configuration & Customizing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

4.1 SAP Mobile Platform Server Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
MBO Deployment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Maintain Additional Configurations for Connection Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Configuring SAP Mobile Platform Server Performance Properties. . . . . . . . . . . . . . . . . . . . . . . . . . 26
Enforcing Password Policy for Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Maintain Lock Timeout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Network Edge Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.2 Relay Server Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.3 CRM Add-On. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

2 PUBLIC Content
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Programs and Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Business Add-Ins. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Implementation Guide (IMG). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.4 ERP Add-On. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Programs and Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Business Add-Ins. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Implementation Guide (IMG). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4.5 Data Download. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Configuration and Customizing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Criteria for Data Download. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Additional Settings for Delta Download. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Push Alerts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Synchronization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
4.6 Device Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Application Provisioning with Afaria. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
User Creation and Authorization Assignment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Trusted RFC Connection from SAP ERP to SAP CRM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
5 Extensibility Using Augmentation Framework. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
6 Security Framework. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
6.1 Before you Start. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
6.2 Technical System Landscape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
6.3 User Administration and Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
6.4 User Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
6.5 Authorizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
6.6 Network and Communication Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
6.7 Communication Channel Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
6.8 Network Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
6.9 Data Storage Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
6.10 Other Security Relevant Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
7 Operations Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
7.1 Data Consistency. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
7.2 Support Desk Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
7.3 Remote Support Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
7.4 Problem Message Handover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
8 Features and Functions Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Content PUBLIC 3
8.1 Device Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67
8.2 Schedule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
8.3 Visits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Visits Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Surveys. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Activity Journals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
8.4 Customers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
‘Prospect’ Customer Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Marketing (Campaigns and Promotions). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
(iPad ONLY) Customer Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Customer Accounts Classification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88
Other Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Contact and Communication Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
8.5 Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
8.6 Sales Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Key Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Offline Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Product Proposals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
8.7 Returns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
8.8 Dashboard (Account and Employee). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
8.9 Other Allied Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
(Android Only): Lazy Load List for All Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Print Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Preferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Attachments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Alerts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
9 Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
10 Limitations and Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

10.1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
11 Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
11.1 DCN Specific APIs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
11.2 Additional Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

4 PUBLIC Content
1 Introduction
1.1 History of Changes
The Administrator’s Guide is regularly updated in SAP Service Marketplace at http://service.sap.com/instguides

.
 Caution
Make sure you have the latest version of the Administrator’s Guide by checking the SAP Service Marketplace
immediately before starting the installation.
The following table provides an overview of the most important changes that were made in the latest versions.
Document Version Important Changes
2.3 This is the latest version of the Administrator's Guide valid for SAP Retail Execution 3.3.0. Refer to
the Upgrade Guide for 3.3.0 for detailed information on the new features.
2.2 This version of the Administrator’s Guide is valid for SAP Retail Execution 3.2.0. Refer to the Upgrade
Guide for 3.2.0 for detailed descriptions on the upgrades.
2.1 The document updated with new features implemented for SAP Retail Execution 3.1.0. Refer to the
Administrator’s Guide for 3.1.0 version for further details.
2.0 The second version of the Administrator’s Guide published for SAP Retail Execution 3.0. The guide
updated with information and details that are specific to the 3.0 release.
 Note
For enhancements specific to 3.0, refer to the Upgrade guide for Retail Execution 3.0
1.0 Initial version of the Administrator's Guide for SAP Retail Execution 2.1.
 Note
The documentation for product release versions prior to 2.1 are available as separate TICM
guides. Refer to the documentation for respective release versions of Retail Execution in SAP
Service Marketplace.

Introduction PUBLIC 5
1.2 SAP Retail Execution 3.3.0
The SAP Retail Execution 3.3.0 is a software product release supported on Apple iOS 8.0 onwards and Android 4.0+
[(Ice Cream Sandwich (4.0) to Jellybean (4.3)].
 Caution
Retail Execution 3.3.0 is supported only on devices running on iOS 8.0.
 Caution
GooglePlay : Only the latest version (3.3.0) of the app is available on the GooglePlay. Go to the SAP Service
Marketplace to download and install previous versions of SAP Retail Execution.
SAP Retail Execution 3.3.0 is available in the following languages:
● English
● German
● French
● Italian
● Turkish
● Japanese
● Korean
● Russian
● Simplified Chinese
● Spanish
● Portuguese
● Polish
● Norwegian
● Finnish
● Swedish
● Thai
● Danish
● Romanian
● Dutch
● Czech
1.3 About this Document
This document is the central starting point for the implementation of SAP Retail Execution 3.3.0. You can find
implementation information as well as security and operation information in this document.

6 PUBLIC Introduction
 Note
You can find the most current version of this document on SAP Service Marketplace at http://service.sap.com/
instguides. We strongly recommend that you use the document available here. The guide will be updated
regularly.
1.4 Related Information
For more information about implementation topics not covered in this guide, see the following content on SAP
Service Marketplace:
Content Location on SAP Service Marketplace
Master Guide for SAP ERP 6.0 http://service.sap.com/instguides SAP Business Suite
Applications SAP ERP SAP ERP 6.0 Installation
Installation Guide for SAP ERP 6.0 http://service.sap.com/instguides SAP Business Suite
Applications SAP ERP SAP ERP 6.0 Installation
Solution Operations Guide for SAP ERP 6.0 http://service.sap.com/instguides SAP Business Suite
Applications SAP ERP SAP ERP 6.0 Operations
Security Guide for SAP ERP 6.0 http://service.sap.com/instguides SAP Business Suite
Applications SAP ERP SAP ERP 6.0
Application Operation Guide CRM 7.0 http://service.sap.com/instguides SAP Business Suite
Applications SAP CRM SAP CRM 7.0
Security Guide for SAP Customer Relationship Management http://service.sap.com/instguides SAP Business Suite
7.0
Applications SAP CRM SAP CRM 7.0
Latest versions of installation and upgrade guides http://service.sap.com/instguides
General information about SAP Retail Execution http://service.sap.com/quicklink
Released platforms and technology-related topics such as http://service.sap.com/platforms

maintenance strategies and language support
To access the Platform Availability Matrix directly, enterhttp://
service.sap.com/pam
Network security http://service.sap.com/securityguide
High Availability http://www.sdn.sap.com/irj/sdn/ha

Introduction PUBLIC 7
Performance http://service.sap.com/performance
Information about Support Package Stacks, latest software http://service.sap.com/sp-stacks

versions and patch level requirements
Information about Unicode technology http://www.sdn.sap.com/irj/sdn/i18n
1.5 Further Useful Links
The following table lists further useful links in SAP Service Marketplace.
Content Location on Service Marketplace
Information about creating error messages http://service.sap.com/messages
SAP Notes search http://service.sap.com/notes
SAP Software Distribution Center (software download and or http://service.sap.com/swdc

dering of software)
SAP Online Knowledge Products (OKPs) – role-specific Learn http://service.sap.com/rkt

ing Maps
1.6 Important SAP Notes
You must read the following SAP Notes before you start the installation. These SAP Notes contain the most recent
information on the installation, as well as corrections to the installation documentation.
Make sure that you have the up-to-date version of each SAP Note, which you can find on SAP Service Marketplace
at http://service.sap.com/notes.
SAP Note Number Title
2132727 SAP Retail Execution 3.3.0 Release Note

8 PUBLIC Introduction
2 SAP Retail Execution
2.1 Introduction
The SAP Retail Execution business solution addresses the business needs of Consumer Products (CP) companies
by enabling delivery of the SAP Business Suite to a wide array of mobile devices and platforms. The key processes
in this solution offer advanced mobile solutions for effective Retail Visit Management.
A retail visit can be defined as a set of activities that a sales representative performs within a retail store, activities
designed to help the CP manufacturer sell its brands/products better in the retail store. For a merchandiser the key
activities include conducting an audit to check stocks, verifying if the agreed planograms are being honored by the
retailer and check if the retailer is handling any promotional agreements such displaying material at the point of
sale, running feature ads, setting up display locations and merchandising products appropriately within those
locations.
This SAP Retail Execution Administrator's Guide provides a central starting point for the technical implementation
of the business scenarios for SAP Retail Execution 3.3.0.
2.2 Key Benefits
Key Business Benefits
● Improves sales effectiveness in the retail channel by executing relevant store visits.
● Provides immediate awareness of relevant customer information.
● Improves overall sales decision-making with access to timely data.
● Increases ROI on trade spending by ensuing effective execution in the retail stores.
Key IT Benefits
● Mobilize the workforce on SAP applications thus avoiding costly integration costs for bespoke applications.
● Supports heterogeneous devices through a single, highly scalable mobile platform.
● Enforces enterprise-class security.
● Enables easy deployment, support, and management.

SAP Retail Execution PUBLIC 9
Security
● Data security built in at multiple levels using the SAP Mobile Platform. The Control Center provides a single
administration console. This enables you to centrally manage, secure, and deploy data applications and
devices.
● Device user involvement is not required and you can maintain the authorization methods that you have already
defined.
● Data is secure at the enterprise level connecting to SAP Mobile Platform and through the Relay Server, as well
as at the device level. The Relay Server allows servers and devices to connect without requiring changes to
your existing corporate firewall configurations and policies.
● Encryption built into the transport layer, which uses asynchronous and synchronous technologies, ensuring
that all in-transit data is secure. There is no further need for VPN or SSL security.
Data Flow and Synchronization for Online and Offline Access
● Mobile users can work online and offline, thus maximizing productivity. The message queuing architecture of
the mobile application allows the mobile workforce to be productive online as well as offline.
● In the offline working mode, the mobile application stores data in a queue on the device. When the device goes
back online, the messages can be synchronized to the back-end and processed accordingly.
● Similarly, when a device goes online, any messages from the back-end that have been queued (while the device
was offline) can be processed when a synchronization is triggered from the device.

10 PUBLIC SAP Retail Execution
2.3 Technical System Landscape
The end-to-end solution comprises of the following components from the SAP landscape and Sybase landscape as
depicted in the graphic below:
SAP Retail Execution 3.3.0 : Architecture Overview
● Mobile Application
● Device Management (Afaria)
● SAP Mobile Platform
○ SAP Mobile Platform (Version 2.3 SP05 PL01)
○ System Management Tools
○ Afaria Server (Client Version 6.60.6057.0)
○ Relay Server (Version 12.0.1)
● SAP Business Suite – SAP CRM 7.0 SP8 or EhP1 with SAP Retail Execution CRM Add-on ( MOB_CRM 100 SP13)
● SAP Business Suite – SAP ERP 6.0 SP15 with SAP Retail Execution ERP Add-on ( MCRMRERP 200 SP13)
● SAP Business Warehouse 7.0
The following software components are either mandatory or optional, as indicated below, for the technical
implementation of SAP Retail Execution

Component Mandatory Optional
SAP CRM 7.0 SP08 or EhP1 X
SAP Retail Execution CRM Add-On X
SAP ERP 6.0 SP15 X
SAP Retail Execution ERP Add-On X
SAP Mobile Platform 2.3 SP05 PL01 X
Afaria X
Relay Server X
 Recommendation
SAP recommends to use Relay
Server as it is tested by SMP and
supported by SAP.
SAP Business Warehouse 7.0 X
Application Architecture
The mobile application consists of 3 key layers:
UI LAYER – This layer renders the interface with which the end user interacts. The functions and controls in this
layer will depend on the device type and on the native controls available in this environment.
APPLICATION BUSINESS OBJECT (ABO) LAYER – The business functionality within the application is encoded in
this layer. Functionally this will be similar between the different platforms but given the SDK/run time differences
on each of the devices, the coding will be in different programming languages.
MOBILE BUSINESS OBJECT (MBO) LAYER – The core data model needed to design business processes and
relationships between these entities are modeled within this layer. Additionally this layer also represents the model
used for synchronizing data with the back-end systems. For example, it determines the database tables (and the
fields/values) that need to be extracted. Similarly the MBO model is also used to trigger create and/or update of
data in the back-end.
2.4 Compatibility Matrix for Release Versions
The following table displays the compatibility matrix for various release versions of Retail Execution, SMP server
and other components in the system landscape.

App Release SMP Server SAP CRM CRM Add-On SAP ERP ERP Add-On
Version
3.3 SUP 2.3 SP05 PL01 CRM 7.0 SP8 OR Ehp1 MOB_CRM 100 SAP ERP 6.0 MCRMRERP 200
SP13 SP15 SP13
 Caution
OR
Patches 10683, 10703 ERP6.02SP05
and 10710 must also
OR ERP 603,
be implemented.
SP04
OR ERP 604,
SP02
OR ERP 605
3.2 2.3 SP04 7.0 SP8 or higher OR MOB_CRM 100 SAP ERP 6.0 MCRMRERP 200
EhP1 or higher SP08 SP15 SP09)
OR
ERP6.02SP05
OR ERP 603,
SP04
OR ERP 604,
SP02
OR ERP 605
3.1 SUP 2.2 SP02 CRM 7.0 SP8 OR Ehp1 MOB_CRM 100 ERP 6.0 SP15 MCRMRERP 200
SP06 SP07
3.0 SUP 2.2 SP02 CRM 7.0 SP8 OR Ehp1 MOB_CRM 100 ERP 6.0 SP15 MCRMRERP 200
SP03 SP04
App Release iOS Devices iOS SW Ver Android Devi Android SW Ver Afaria Relay SAP BW
Version sion ces sion Server
3.3.0 iPad and iOS 8.0 on Android Android 4.0+ [(Ice Client Ver 12.0.1 7.0
iPhone wards Phone and Cream Sandwich sion
Tablet (4.0) to Jellybean 6.60.6057.0
(4.3)].
3.2 Patch 02 iPad and iOS 7.0 ONLY Android Android 4.0+ [(Ice Client Ver 12.0.1 7.0
iPhone Phone and Cream Sandwich sion
(4.3)].

3.2 Patch 01 iPad and iOS 7.0 ONLY Android Android 4.0+ [(Ice Client Ver 12.0.1 7.0
(4.3)].
3.2 iPad and iOS 7.0 ONLY Android Android 4.0+ [(Ice Client Ver 12.0.1 7.0
(4.3)].
3.1 I Pad, I Phone iOS 6 & iOS 7 Android Android 1, 2 & 3 Client Ver 12.0.1 7.0
with REX 2.1 Phone and sion
functionality Tablet 6.60.6057.0
and UI Frame
work
3.0 iPad; iPhone iOS 6 , iOS 7 Android Android 1, 2 & 3 Client Ver 12.0.1 7.0
with 2.1 func compatibility Phone and sion
tionality and would be Tablet 6.60.6057.0
UI framework available end
of Oc

3 Installations
3.1 General Installation Information
3.1.1 Introduction
This section of the guide provides instructions on how to install the SAP Retail Execution. It provides notes on all
the steps and settings relevant for the deployment of the app. For specific instructions on how to configure the
application, see the relevant Post Installation sections. Before you start the installation, ensure that you have read
all the necessary information from this guide including SAP Notes for the Installation and Information Available in
SAP Service Marketplace.
3.1.2 SAP Notes for Installation
You must read the following SAP Notes before you start the installation. These SAP Notes contain the most recent
information on the installation, as well as corrections to the installation documentation.
Make sure that you have the up-to-date version of each SAP Note, which you can find on the SAP Service
Marketplace at http://www.service.sap.com/notes
SAP Note Number Title
2132727 SAP Retail Execution 3.3.0 Release Note
3.1.3 Information Available in SAP Service Marketplace
Information on the following areas is available in the SAP Service Marketplace.
Description Internet Address
SAP Notes http://www.service.sap.com/notes
Security http://www.service.sap.com/security
Installation Information http://www.service.sap.com/instguides
Software Download http://www.service.sap.com/swdc

Installations PUBLIC 15
3.1.4 Further Documentation
In addition to this document, you need the following documents to install and operate SAP Retail Execution.
Description Internet Address
Information on Sybase products http://www.sybase.com
Information on Sybase product documentation http://help.sap.com/mobile-platform
3.2 Installation Matrix
3.2.1 Introduction
This section provides installation instructions to create the infrastructure for SAP Retail Execution mobile
application.
 Note
For information about the minimum hardware requirements for each component, see the appropriate
installation guides.
The following table provides the implementation sequence on each respective server:
SAP Business Suite Component Server
1 SAP CRM 7.0 EHP1 or higher OR To download the software and for detailed information, refer to the following links:
SAP CRM 7.0 SP08 or higher
● http://www.service.sap.com/swdc Installations and Upgrades Browse
our Download Catalog SAP Application Components SAP CRM SAP CRM
7.0
● http://www.service.sap.com/crm-inst SAP Business Suite Applications
SAP CRM SAP CRM 7.0
● http://www.service.sap.com/instguides SAP Business Suite Applications
SAP CRM SAP CRM 7.0

16 PUBLIC Installations
2 Installation of CRM Add-On for Install the Add-On MOB_CRM 100 SP13. To download the software and for detailed in
Retail Execution 3.3.0 formation, refer to the following links:
 Note  Note
The minimum recommended It is recommended to use the latest patch for fresh installations.
SP is specified in this docu
Download the Add-On installation tool before installing the Add-On software from
ment. A higher available SP
Service Marketplace. Refer to the documentation in the following path for more
is recommended for new
information: http://help.sap.com/saphelp_nw04/helpdata/en/
Customers implementing the
49/3e896728ab2222e10000000a42189d/frameset.htm
solution.
our Download Catalog SAP Mobile Solutions SAP Retail Execution MOB
RETAIL EXEC CRM INT

● http://www.service.sap.com/crm-inst
● http://service.sap.com/instguides SAP Business Suite Applications SAP
CRM
3 SAP ERP 6.0 SP15 To download the software and for detailed information, refer to the following links:
OR ERP6.02 SP05 ● http://www.service.sap.com/swdc Browse our Download Catalog SAP
OR ERP 603, SP04 Application Components SAP ERP SAP ERP 6.0
OR ERP 604, SP02 ● http://www.service.sap.com/erp-inst SAP Business Suite Applications
OR ERP 605 SAP ERP SAP ERP 6.0
● http://www.service.sap.com/instguides SAP Business Suite Applications
SAP ERP SAP ERP 6.0
4 Installation of ERP Add-On for Install the ERP Add-On MCRMRERP 200 SP13 for the ERP application back-end sys
Retail Execution 3.3.0 tem To download the software and for detailed information, refer to the following
links:
 Note
It is recommended to use the latest patch for fresh installations.
our Download Catalog SAP Mobile Solutions SAP Retail Execution MOB
RETAIL EXEC ERP INT

○ http://service.sap.com/erp-inst
○ http://service.sap.com/instguides SAP Business Suite Applications
SAP ERP
SAP Mobile Platform Server

1 Installation of SAP Mobile Platform 2.3 SP05 PL01 For more information, refer to product documentation for
the following topics:
 Caution
● http://help.sap.com/mobile-platform SAP Mobile
The following patches 10683, 10703 and 10710 for SMP
Platform 2.3 SP05
2.3 SP05 MUST also be implemented.
● Provisioning with Afaria
● SQL Anywhere 12.0.1 Relay Server
2 Deployment of Mobile Business Objects (MBO) on SMP You can find the MBO package in the download catalog in
server SAP Service Marketplace using the following path:http://
service.sap.com/swdc Installations and Upgrades
Browse our Download Catalog SAP Mobile Solutions
SAP Retail Execution Mobile MOB_RETAIL_EXEC_MBO
3.3 Client Installation
3.3.1 Introduction
The following information describes the process for installing the Retail Execution mobile app on iPad and Android
client devices.
3.3.2 Installing the App on an iOS Device
Prerequisites
Device is connected to a wireless cellular network / a wi-fi network / via ActiveSync to the computer. Download the
application from the iTunes app store.
 Note
If you have already registered the device or if you use Afaria or any other device management capabilities, then
you do not need to recreate these steps. Refer to the section on Provisioning with Afaria for detailed
information.
Procedure
1. Tap on Setup to maintain the connection settings required to connect to the SMP server.

2. If provisioning through Afaria is not available, the following details need to be maintained
The Retail Execution application can be installed in a single domain or in more than one domains. If the
application is installed on more than one domains, the security configuration settings will identify the domain
that must be selected. Further, the connection to the SAP Mobile Platform (SMP) can be a direct connection or
through a Relay Server. The application setup details are therefore segregated as follows
Direct Connection : Maintain the following details:
○ Server name (IP Address of the SMP server)
○ User Name (SMP user name)
○ Password
Set Advanced Settings to ON
○ Server Port
SMP port
○ Secure Connection
Set this to On (recommended in a productive environment)
 Note
The direct connection details will suffice if a VPN connection is used to access the SAP Mobile Platform
server.
Connection using Relay Server :

If your connection is routed through a Relay server, the following details will need to be maintained:
○ Server name (IP Address of the Relay server)
○ User Name (SMP user name)
○ Password
Set Advanced Settings to ON
○ Server Port
Relay server port
○ URL Prefix
○ Farm ID
Relay server MBS Farm ID
○ Security Domain
If the application has been installed in more than one security domains, then the specific domain
identification must be maintained here.
Set this to ON (recommended in a productive environment)
3. Maintain an App Passcode (device password)
The user is prompted for the application login credentials.
4. Enter the SAP CRM login credentials.
 Note
If the login credentials are validated, the application is initialized and the synchronization with the back-end
servers is initiated. The user is expected to wait until the synchronization process is complete (the interface
message text Synchronizing is displayed on the device) before running the application.
Scenario for Aftaria Set-Up

If Afaria is implemented within a corporate network, the application will be installed using Afaria setup (pushed to
the device). In this scenario, all the connection details will be populated by Afaria and the user will have to maintain
only the login credentials (user name and password).
Uninstalling the Application
1. Hold your finger on the application that you wish to uninstall until the icons on your home screen begin to
shake or wiggle. This is the same action you take to move or rearrange home screen icons in an iOS device.
2. Tap on the indicator X in the top left corner of the application you with to delete the application.
 Note
It is always recommended to first unsubscribe to the application and then uninstall the app from the device.
if user happens to delete the application without unsubscribing to it, then the user has to be manually
removed from the SCC.
3.3.3 Installing the App on an Android Device
Device is connected to a wireless cellular network / a wi-fi network / via ActiveSync to the computer. Download the
application from the GooglePlay store.
1.  Note
If you have already registered the device or if you use Afaria or any other device management capabilities,
then you do not need to recreate these steps. Refer to the section on Provisioning with Afaria for detailed
information.
Procedure
1. Tap on Setup to maintain the connection settings required to connect to the SMP server.
2. If provisioning through Afaria is available, then the Afaria login screen appears. The device user is expected
to maintain the Afaria login and password and the SMP registration and password (if required).
3. If provisioning through Afaria is NOT available, then the device user must tap on Setup Connection to
maintain the following details:
If the Retail Execution application is installed on a single domain, the application ID will point to the default
domain. However, if the application is installed on more than one domains, the security configuration settings
will identify the domain that must be selected. Further, the connection to the SAP Mobile Platform (SMP) can
be a direct connection or through a Relay Server. The application setup details are therefore segregated as
follows:
Direct Connection
○ Server name (IP Address of the SMP server)
○ SMP User Name
○ Password
○ Server Port
SMP Port

○ SMP Activation Code
Set it to ON (recommended in a productive environment)
Relay Server Connection Details:
○ Server name (IP Address of the MBS server)
○ SMP User Name
○ Password
○ Server Port
Relay Server Port
○ SMP Server Company ID (Farm ID)
Relay Server ID
○ SMP Activation Code
○ URL Prefix
Relay Server URL Prefix
Set this to On (recommended in a productive environment)
4. Maintain an App Passcode (device password)
The user is prompted for the application login credentials.
5. Enter the SAP CRM login credentials.
 Note
If the login credentials are validated, the application is initialized and the synchronization with the back-end
servers is initiated. The user is expected to wait until the synchronization process is complete (the interface
message text Synchronizing is displayed on the device) before running the application.
Uninstall the Application
1. From the Settings, select Apps.

2. Select SAP Retail Execution and tap on Uninstall.
3. Confirm Uninstall.
 Note
Use the file explorer application on the device to confirm if application and all its files/folders have been
removed from the device. If there are any files remaining on the device, delete them manually.
 Recommendation
It is always recommended to first unsubscribe to the application and then uninstall the app from the device.
if user happens to delete the application without unsubscribing to it, then the user has to be manually
removed from the SCC.

4 Configuration & Customizing
4.1 SAP Mobile Platform Server Configuration
4.1.1 Introduction
4.1.2 MBO Deployment
4.1.2.1 Introduction
The MBO deployment involves the following steps:
1. Selecting a domain (OR creating a new domain) to deploy the MBO package.
2. Create Connections (OR use the connections provided )
3. Create security configuration that you will need to specify during deployment.
4. Deploy the MBO package on SMP server.
5. After you have deployed the MBO package, change or create connection templates.
This is used for authenticating the user at the time of registration.
4.1.2.2 Identify a Domain (Select Existing or Create New)
Prerequisites
The SMP 2.3 SP05 PL01 server has already been installed.
Procedure
1. Select an existing domain or create a new domain to deploy the MBO package.

22 PUBLIC Configuration & Customizing
4.1.2.3 Use Existing Connections OR Create New Connections
Connections are required for deploying the MBO package. You can:
● Use existing connections for deployment.

● OR Create new connections for the deployment.
 Note
If you have to create new connections (to deploy the MBO package), create the connection to CRM at SAP
Control Center using the following path: Domain Connections New Connection Pool The
connection pointing to CRM back-end system should be defined based on the respective SAP template for
these systems.
4.1.2.4 Define Security Configuration
1. The security configuration for SAP Retail Execution is maintained in the SAP Control Center (SCC) on the SMP.
You will need to specify the security configuration when deploying the MBO package on SMP server.
 Note
For further information, refer to the SAP Mobile Platform 2.3 SP05 PL01 documentation for Security
Configurations and Assigning a Security Configuration to a Domain.
 Recommendation
○ It is recommended to use the http basic security provider or Certificate Security Provider. Refer to
the SMP 2.3 SP05 PL01 documentation for these topics.
○ If http basic security provider is used, then it is recommended that a separate ABAP server is
configured for authentication. A NetWeaver Mobile server can also be used for this purpose.
Set-up the ABAP servers to issue and receive the logon ticket (MYSAPSSO2). For detailed information,
see Using Logon Tickets (link enclosed)http://help.sap.com/saphelp_nw70ehp2/helpdata/en/
f8/18da3a82f9cc38e10000000a114084/content.htm
 Caution
If you do not use the SSO mechanism, then the Username and Password of the CRM or ERP
system and that of the authenticating Http server (can be any Http server including CRM/ ERP
server) must be the same. Additionally, a trust relationship should be established between the
back-end systems (SAP CRM and SAP ERP) and the authenticating system
○ If certificate security provider is used, then client certificate (X.509 certificate) must be provided to the
client application to authenticate the device. Additionally you have to configure the ABAP back-end
servers (link enclosed: http://help.sap.com/saphelp_nw70ehp1/helpdata/en/a8/
d9d53a9aa9e933e10000000a114084/content.htm) and SAP Mobile Platform server to accept this
client certificate.

Configuration & Customizing PUBLIC 23
4.1.2.5 Deploy the MBO Package on SMP Server
Prerequisites
In order to deploy, you must:
● Download the MBO package (located in the SAP Service Marketplace) to your local machine.
● Extract the jar file to a folder in your local machine.
 Note
The MBO package for Retail Execution 3.3.0 is available under the following path in the SAP Service
Marketplace: http://service.sap.com/swdc Installations and Upgrades Browse our Download Catalog
SAP Mobile Solutions SAP Retail Execution Mobile MOB RETAIL EXEC MBO
Procedure
1. To deploy the jar file contained in the MBO package (that you have downloaded from the SAP software
download catalogue), perform the following steps:
1. In SAP Control Center (SCC), Go to Domain Default Packages .
2. In the Packages section, click on Deploy.
The deployment wizard appears.
3. Browse your local machine for the deployment file (jar file that you extracted from the MBO package) and
set the Deployment Mode to ‘Update’.
4. Click on Next to proceed with the deployment.
5. In the deployment wizard ‘Select a domain and a security configuration for the package’, screen, the domain
is defaulted in this screen. Here, select the appropriate security configuration (Prerequisite : You have
already defined security configuration as explained in section 4.2).
6. In the next screen (Perform role mapping screen) that appears, simply click on Next to proceed with the
deployment.
7. In the deployment wizard 'Server connection ' screen, you can:
○ Either
Use standard settings and click on Next to continue with the deployment.
 Note
If you use standard settings, go to Connections in SAP Mobile Platform Cluster and in the tab for
Connections, update the properties for connection pool name (CRM_local), to point the
connections to the CRM system in your landscape.
○ OR
Select the Endpoint connections (CRM system connections that you have defined using steps
mentioned in section 4.2) for each of the MBOs.
 Note
In the deployment wizard, EMBEDDED ENDPOINT is selected as the default endpoint connection.
Select CRM_local as the endpoint connection for all the MBOs. In addition, select the Apply

connection changes to operations checkbox for each MBO. Make sure that you have applied the
connections for all MBOs.
○ Select the checkbox for ‘Apply Connection Changes to Operations’ (bottom of the screen) and proceed
to the next step.
2. Click on Next to view the deployment Summary.
3. In the deployment summary screen, click on Finish to start the deployment.
4.1.3 Maintain Additional Configurations for Connection

Templates
A connection template is created as default for each application created on SMP. You can change templates
provided for the standard application or create new connection templates. After the MBO package has been
deployed, the following additional settings must be maintained for the connection templates:
 Note
All connection templates must be created with the default application identifier : retailex
The configurations that you define for the templates are used for authenticating the user at the time of
registration.
 Caution
If multiple domains are defined in the system landscape for Retail Execution, then for each domain, separate
security configuration and application template ID must be created.
 Note
For detailed information on refer to the documentation for SAP Mobile Platform 2.3 SP05 PL01 OR in the
following path: SAP Mobile Platform 2.3 SP05 Developer Guide : Windows and Windows Mobile Object API
Applications Client Object API Usage Application APIs Connection Properties.
● Connection
○ Farm ID
MBS Farm ID
○ Server Name
Relay Server IP Address
○ Server Port
Relay Server Port
○ Synchronization Server Host
Relay Server IP Address
○ Synchronization Server Port
Relay Server Port
○ Synchronization Server Protocol
Https
○ Synchronization Server URL Suffix

Maintain the value : /ias_relay_server/client/rs_client.dll/(enter the RBS Farm ID here)
● Device Advanced
○ Relay Server URL Suffix
Maintain the value : /ias_relay_server/client/rs_client.dll/%cid%/tm
● Capabilities
 Recommendation
Set the Application Supports Password Policy to True.
4.1.4 Configuring SAP Mobile Platform Server Performance

Properties
The JVM heap size of the SMP server influences the performance of the server. In the SMP server configuration,
you must configure the minimum heap size and maximum heap size. The default is 512M, you can increase it based
on machine size (where SMP is residing).
For detailed information, refer to the documentation in the following link: http://help.sap.com/mobile-platform
SAP Mobile Platform 2.3 SP05 System Administration 2.3 SP05
4.1.5 Enforcing Password Policy for Application
The password protection and enforcement can be done on the SAP Mobile Platform.
 Recommendation
SAP recommends that at least three of the eight characters in the password comply with the password
protection policy. The policy states that the eight letter password must have a combination of upper case and
lower case letters, numeric values and special characters.
Quick guide for making the application secure
Step1 SMP Security Administration
Step2 Password/login attempts from Afaria Configuration
Step3 Configure PIN protection on SMP
Step4 Lock the device in case of inactivity.
 Note
Customers are recommended to use Afaria for securing personal information on the client.

4.1.6 Maintain Lock Timeout
The idle time for device application can be defined in the SMP Control Center at the connection template level.
Perform the following steps:
1. In the SMP Control Center,, select Applications in the SMP Platform Cluster (menu on the left hand side of the
screen).
2. Click on the tab for Application Connection Templates.
3. Click on the checkbox next to the application connection template that you have selected for registering users
on SMP server.
4. Click on the tab for Properties.
5. The dialog screen for Template appears. In this screen, click on Password Policy and maintain values for the
following properties:
○ Enabled : True
○ Lock Timeout : time in seconds
 Note
The default Lock Timeout is set to 0 in SMP Control Center. Android Only: If the Lock Timeout is set to
0 or no value is maintained, then 20 seconds will be considered as the default Lock Timeout. A non-
zero value is recommended. iOS Only: If the default Lock Timeout is set to 0, then the app will prompt
for a password immediately.
4.1.7 Network Edge Authentication
Retail Execution supports Network Edge authentication and the Network Edge security feature can be configured in
the SMP landscape for additional security authentications. For detailed information, refer to the product
documentation for SMP 2.3 SP05 for the topic Single Sign-On Integration Across Client Applications.
 Note
Network Edge authentication for X-509 certifications (Single Sign On) is not supported for SAP Retail
Execution.
4.2 Relay Server Configuration
After you have installed the Relay Server, you have to configure the server. For detailed information on installing
Relay Server, refer to product documentation (http://help.sap.com/mobile-platform ) for SMP 2.3 SP05 for the
topic Installing a Relay Server.
 Note
1. You must use the Relay Server setup available in the download zip available in the software download
catalog of SAP Service Marketplace.

2. Two Farms (one each for RBS and MBS) must be maintained on Relay Server.
Network Edge Authentication
SAP Retail Execution supports Network Edge authentication. The Relay Server can be configured and protected
using Network Edge authentication, If this feature is implemented, then for a connection made through a secured
communication to a network Edge protected Relay Server, the user is prompted to provide the Network Edge
Password.
4.3 CRM Add-On
4.3.1 Introduction
You need to have installed the SAP CRM Add-On MOB_CRM 100 SP13 (OR higher) for Retail Execution.
 Caution
SAP recommends that you use a minimal system landscape for test and demo purposes only. For performance,
scalability, high availability, and security reasons, do not use a minimal system landscape as your production
landscape.
4.3.2 Programs and Reports
4.3.2.1 /MAC/VISIT_ACT_REL_CREATE
This report can be executed after the visits and activities have been created using the visit plan in CRM Web Client
UI. This report determines assignment of activities with the visits and subsequently, these activities appear part of
the assigned visit on the device application.
The report has capability to run as scheduled task and process as background report (use Transaction SM36). The
results can be seen at transaction SLG1 for object /MAC/RETAIL and sub-object ACTREL.
The report offers the following features:
● Reads the Retail Execution configuration to determine the visit transaction type and all the mandatory /
optional activity types that have been configured.
● Considers start and end time of visit
 Note
Start time must be set in the future.

● Considers the employee responsible and customer as option; If value for Customer is not provided, then the
report considers all the customers in the user‘s visit plans.
● Determines retail visit of type mentioned in the Customizing. It then identifies all the activities which are within
the start plan and start end date of the retail visit and sets the follow-up GUID of the same.
4.3.2.2 Activities Mass Generation
Use
A new report /MAC/MASS_GEN_ACTIVITIES is provided to create a batch job for generating many activities at a
time and also assign them to open visits. The report uses an existing activity template for generating multiple
activities. The activities can be generated for a specific customer, a target group or a customer hierarchy. Detailed
explanation for how the parameters are used in the report is documented in the sections given below:
Template ID
This is the ID of an activity created as Template. All other activities generated using the report will have the
following data copied from this template
● General Data
○ Description
○ Process Type
○ Category
○ Priority
● Status
● All partners except store/customer
● Sales org. data
Frequency, Date-From, Date-To
These values are used to calculate the number of activities that are going to be generated and also their planned
completion periods.
One of the following frequencies can be selected to run the report.
● Monthly
● Weekly
● Once
Date-From and Date-To
This duration is considered to arrive at the number of visits that must be generated for each frequency.
Planned Completion Date Type
 Example
One activity will be generated if Frequency=Monthly, Date-From=1-Jan-2015 and Date-To=1-Feb-2015(the

value is derived by Date-From by Date-To in months.
Similarly, four activities will be generated if Frequency=Weekly, Date-From=1-Jan-2015 and Date-To=1-

Feb-2015 (the value is derived by dividing the Date-From by Date-To in weeks.

Customer, Target Group, Customer Hierarchy
In the Customer field, specify the ID of the customer for whom you need to generate activities. You can also specify
multiple customers. Note that the same number of activities will be generated for each of the customers.
 Example
Frequency=Monthly
Date-From=1-Jan-2015
Date-To=1-Feb-2015
Customers = 1234 and 5678
RESULT: Two activities (one each for each customer) will be generated.
Target Group:
If you specify a target group, the activities will be generated for all customers in the specified target group.
Customer Hierarchy
To generate activities for multiple customers, you can also specify the node ID in a customer hierarchy. All
customers in below that node will be considered.
Create Links
Set this flag to assign visits to the newly generated activities. For assignment, the system determines visits with
same customer and whose planned dates overlap with the planned completion dates of the generated activity.
Valid scenarios are where:
● Planned completion Period’s end date of activity lies in Planned dates of visit.
● Planned completion Period’s start date of activity lies in Planned dates of visit.
● Planned Completion Period of activity lies in Planned Period of visit.
● Planned period of visit lies on Planned Completion Period of activity.
Create Only Linked Activities
Set this flag to determine that activities be generated only if which visits are found in system. If this flag is set, the
report does not generate any unassigned activities.
Test Run
This flag is set by default and it is recommended to set this flag in order to view the changes before they are
executed.
More Information
The frequently asked questions (FAQ's) for visit assignment are listed in this section:
1. If multiple visits are found for the given criteria

The activity is assigned to the first visit that meets the required criteria.
2. If same visit classifies the criteria for multiple activities that are created during a single run. For example, this
may occur when planned period for a visit is greater than the duration for which report is run.

A visit will only be assigned once to an activity. Therefore, a visit is assigned to the first activity (in the report
run) that meets the required criteria.
3. If you need to assign multiple activities of same type to a visit
Multiple runs of the same report can be used to assign multiple activities of same type to a visit.
4.3.2.3 Alerts Generation
In addition to the standard interface message texts created for the application user interface, additional alerts can
be defined if required. For each alert, specify the priority, category for the alert, validity dates etc. Most importantly,
the recipients for the alerts can be specified (individual customers, a territory, customer hierarchy or target group).
Some examples of alert types are:
● Delayed delivery for a store

● Product recall messages
● Price Changes for a store
● CRM Alerts - based on survey qualification
● Upcoming promotion alert from CRM
A new report /MAC/RSFM_ALERT_GEN is provided to implement this feature. Alerts can be implemented only at the
sales organizational level.
Customizing : The required Alert Category Profiles must be defined in the IMG Activity Define Push Alert
Categories. Refer to the documentation for the IMG activity for more details.
 Note
The alerts are directly sent to SMP and are not maintained in the backend CRM system. Therefore you cannot
delete the alerts from the backend CRM system. The alerts will be automatically deleted from the device when
the validity expires. Note that you maintain the VALID_TO date & time while creating the alerts.
4.3.2.4 Initial Download
Run this report /MAC/RS_INITIAL_DOWNLOAD for initial download of the business objects listed below:
 Recommendation
Define a percentage allocation of processes between background job run and dialog processes. The report for
initial download will then consider only the processes allocated for background run. If you do not define such an
allocation, system may get locked due to unavailability of any processes (as all processes get blocked for the
job run).
● Activity
● Sales Order
● Business Partner
● Business Partner Hierarchy

● Products
● Target Group
● Marketing Projects
● Listing
Maintain the following details to run the report.
1. Select the business object for which the initial download report must be run.
2. Specify the block size for each business object.
3. Enter sales organizational unit, division, channel etc. (for org. unit specific data download)
4. Specify the profile name for which you want to execute the program.
In the IMG Customizing for DCN, you can define multiple DCN profiles (each for a different package, domain or
RFC destination). The report can be executed for one DCN profile at a time.
5. (Mandatory) Parallel processing group that will be used to run the initial download.
6. Number of work processes for the parallel processing group.
7. Click on the Generate icon on the header bar to execute the report.
4.3.2.5 Initial Download Report for Activity Survey-Journal

Download
Execute this initial download report /MAC/RS_SVY_JRNL_DOWNLOAD to download survey and journal template
data from backend to SMP.
 Recommendation
It is recommended to run this report as a regular scheduled background job. The frequency of this scheduled
background job should be able to correctly capture any modifications being made to survey and journal
templates in the SAP CRM backend.
 Caution
In SAP Retail Execution, inconsistencies may occur in journal determination, often in the scenarios where
business partner hierarchy governs journal determination. This happens when there is mismatch in the planned
and actual execution dates for a visit; This is because journal determination in Retail Execution is based on
Planned Date while in SAP CRM, the same is based on the Actual Execution Date of the visit. It is therefore
recommended to run this report with a regular frequency to ensure the correct set of survey and journal
templates are available when creating visits.
 Note
New Customizing settings can be maintained for survey templates BUT existing Customizing must be available
to ensure the correct determination of the templates on the device.
Enter the following details to execute the report:
1. Select the business object (Survey Template OR Journal Template) for which the report will be run.
2. Enter sales organizational unit, division, channel etc., (for org. unit specific data download).
3. Specify the DCN profile name relevant for this program.

4. Specify the block size for the data to be replicated to SMP.
4.3.2.6 Account Specific Listings Relationship Determination
Run the report /MAC/RS_BP_LST_RELN_DETER whenever you create new listings for a specific sales organization.
In the earlier approach, an online call was made to retrieve the listings. In the new approach, listings are retrieved
using parallel processing and the data is stored in a database table in SMP. . This report deletes the existing entries
and fills the database table /MAC/RSC_DCN_LST (also used in the function module /MAC/
RSFM_DCN_PRODUCT_LIST) with the new listings thus improving the performance and lead time to fetch listings.
For a given sales organization, all the business partners will be retrieved and the listing GUIDs will be fetched for all
these business partners.
Maintain the following details to execute this report:
1. Sales data such as organizational unit, division and channel.

2. The DCN profile name relevant for this program. In the IMG Customizing for DCN, you can define multiple DCN
profiles (each for a different package, domain or RFC destination). The report can be executed for one DCN
profile at a time.
3. Specify the block size for the data to be replicated to SMP.
4. (Mandatory) Parallel processing group that will be used to run the initial download
4.3.3 Business Add-Ins
All Business Add-Ins provided for SAP Retail Execution belong to the enhancement spot /MAC/RS_ES in CRM
component (CRM-MSP-REX). You can use the BAdIs of this enhancement spot to enhance the standard functions
that are available as part of the CRM side of the SAP Retail Execution.
Use this Business Add-In to enhance the standard functions that are available in CRM Activity Management as part
of the Retail Execution functionality for Mobile Business Applications. The interface methods in this BAdI allow you
to add new fields (custom fields) using the customer enhancement structures.
 Note
All Business Add-Ins provided for Retail Execution are assigned to the Retail Execution Customizing IMG
structure in transaction code SPRO.

4.3.4 Implementation Guide (IMG)
Customizing settings must be defined in the CRM system for SAP Retail Execution using the following path:
SPRO Customer Relationship Management SAP Retail Execution (Mob App) Refer to the detailed
documentation provided in the IMG structure for each corresponding IMG activity step.
4.4 ERP Add-On
4.4.1 Introduction
To enable customers to take advantage of their ERP installations on smart devices, you need to install Add-On
MCRMRERP 200 SP013 (or higher) on SAP ERP 6.0 or SAP ERP SP15 or higher. This Add-On package consists of the
following configuration:
 Caution
We strongly recommend that you use a minimal system landscape for test and demo purposes only. For
performance, scalability, high availability, and security reasons, do not use a minimal system landscape as your
production landscape.
4.4.2 Programs and Reports
4.4.2.1 (ERP) /MRE/RS_INITIAL_DOWNLOAD : Report for

Initial Download
Run this report for initial download of sales orders:
 Recommendation
Define a percentage allocation of processes between background job run and dialog processes. The report for
initial download will then consider only the processes allocated for background run. If you do not define such an
allocation, system may get locked due to unavailability of any processes (as all processes get blocked for the
job run).
Maintain the following details to run the report.
1. Select the business object (sales orders) for which the initial download report must be run.
2. Specify the block size for sales orders download.
3. Enter sales organizational unit, division, channel etc. (for org. unit specific data download)

4. Specify the profile name for which you want to execute the program.
4.4.3 Business Add-Ins
All Business Add-Ins provided for SAP Retail Execution belong to the enhancement spot /MRE/ES_SD in ERP
component.. You can use the BAdIs of this enhancement spot to enhance the standard functions that are available
as part of the ERP side of the SAP Retail Execution.
Use this Business Add-In to enhance the standard functions that are available in ERP as part of the Retail Execution
functionality for Mobile Business Applications. The interface methods in this BAdI allow you to add new fields
(custom fields) using the customer enhancement structures.
 Note
All Business Add-Ins provided for Retail Execution are assigned to the Retail Execution Customizing IMG
structure in transaction code SPRO.
4.4.4 Implementation Guide (IMG)
Define the Customizing settings in the SAP ERP system for SAP Retail Execution. Access the IMG structure in
Transaction SPRO SAP Customizing Implementation Guide SAP Retail Execution (Mob App) Refer to the
documentation in the IMG structure corresponding to each IMG activity step.

4.5 Data Download
4.5.1 Introduction
Data is downloaded to the device either as part of initial download (after device subscription) or as delta or online
download when app is running on the device. The pattern for initial and delta download can be classified as follows:
● Using Data Change Notification: This is valid only for objects supported with the for DCN and is relevant only
for initial data download.
● Hybrid: This may involve data download using DCN or On demand depending on the requirement of business
logic.
○ Direct download via SMP AND
○ On-demand download from backend or via SMP
 Note
In Hybrid scenarios, the required calculations are first performed in the backend system. Further data for
the device is selected from SMP based on this calculated information.
● On Demand
When a specific sync request is made from the device. Note that the objects for delta sync must be selected in
the device Preferences.
Download Support Objects Supported Pattern for Download
DCN ● Activities Backend to SMP and from SMP to device

● Surveys and Journal Templates
● Sales Order
● Product Master
● BP Hierarchy
● Target Groups
● Marketing Projects
● Listing
● Alerts
 Note
Unlike other business objects,
data for alerts is sent to the de
vice from SMP without need for a
specific sync from the device.
Hybrid ● Valid products for user by Listing and One of the following:
Territory
● Backend to SMP and from SMP to device
● Business Partners
● Partly directly from backend to device and partly
via SMP

On Demand ● Customizing On-demand download directly from Backend to Device
● Product Proposal
● Trade Assets
● Attachment Details
● Offline Pricing
● Item Proposal
4.5.2 Configuration and Customizing
4.5.2.1 Data Change Notification (DCN)
4.5.2.1.1 Introduction
The Data Change Notification (DCN) feature uses Regular DCN to replication-based synchronization (RBS) and
message-based synchronization (MBS) clients.
 Note
Refer to documentation for the topic Data Change Notification Data Flow in the portal http://help.sap.com/
mobile-platform SAP Mobile Platform 2.3 SP05
4.5.2.1.2 Configuration
This section lists the set-up steps in detail:
 Recommendation
Authentication and Authorization for DCN User : The DCN user must be authenticated successfully and must
also have the required authorizations to make DCN calls. In the security configuration maintained for the
application package in SMP, necessary authorizations must be provided for the DCN user, for whom a remote
function call (RFC) connection has been created in the back-end systems.
1. Authorization Settings in SMP:

Define the following to maintain authorization settings in SMP
1. Authorize the user with SMP rights to make the DCN calls using the following authorizations:
○ SMP Administrator
○ SMP Domain Administrator
○ SMP DCN User
○ SMP Push User

 Note
Make sure that the login name of the user with SMP administrator rights has naming convention as
user@admin. For example, supAdmin@admin.
2. Login Authorized for making DCN calls: In the back-end logical system, Go to transaction code SM59 and
define the following:
1. HTTP connection to External Server
2. Make sure the connection type is set to 'G'
3. For this connection :
1. In the tab for Technical Settings, set the Target Host to IP Address of the SMP Server and the Service
No. as the HTTP Port of the SMP Server.
2. In the tab for Logon & Security, in the section for Logon, enter the same logon details (user name and
password) whether you have used the SMP admin user or the pre-configured login module (provider
type) for maintaining the authorizations for the calls. This login module has the necessary
authorization to make the calls.
You must consider the following information while maintaining the user name:
○ username@Admin if you have used the administrator rights.
○ Only the UserName if you have used the pre-configured login module
3. Connection Profile in IMG : Maintain a connection profile for making DCN calls to the back-end logical system.
You can define this connection profile in the IMG Activity : Maintain configuration for Change Notifications.
In this configuration settings, you define the connection parameters for communication between the back-end
system and the SAP Mobile Platform (SMP) for the feature for change notification and push alerts. Maintain
the following settings for the connection profile.
1. Connection profile for change notifications. You will also need to maintain the following details for each
target server:
1. Name of the domain created in SAP Mobile Platform (SMP) for Retail Execution for the valid
application release version
2. Name of the package deployed in SMP for Retail Execution.
 Note
The package for SAP Retail Execution 3.3.0 is sapRex:3.3.
3. The HTTP connection to external servers (in this case, a connection to SMP server) is maintained. The
connections are maintained in transaction code SM59.
2. Assign the connection profile to sales organization, distribution channel and divisions. The sales
organization determines all the calculations that must be made on the SMP server when an initial or delta
download is requested from the client device.
3. You must set the flag for Active to allow data download to the devices.
4. Test Connection : You must test the connection after performing the configurations listed above to perform
data transfer.
5. Enable Delta Flow of Data to SMP : In the transaction SMQR in the backend SAP CRM and ERP systems,
check if the * Queue is registered. If this setting is not defined, then CN* queue must be registered to enable
delta flow of data to SMP.
6. Optional : If you modify standard MBOs or create new MBOs, you must maintain the required details in the IMG
activity Standard Settings for Data Change Notifications. Refer to the detailed documentation in the following
section.

OPTIONAL (IMG Setting) : Standard Settings for Data Change Notifications
 Note
Maintain these settings only if you are adding new MBOs that use DCN as a data flow mechanism.
This Customizing step includes settings delivered in the standard system for Retail Execution for Data Change
Notifications. Any modifications that you have defined to the MBO model must be reflected in the settings in
this IMG steps.
The following settings are maintained in this Customizing:
1. Objects Supported for DCN (the business objects supported in Retail Execution for implementing the DCN
framework).
2. Sub-Objects Supported for DCN (represent the objects dependent on the parent business objects). In the MBO
model, an MBO structure is maintained for each sub-object.
3. MBOs in Standard System (lists all the MBO structures provided in the standard system for Retail Execution.
You can add new MBO structures or modify existing ones.)
4. Define MBO Sets (In the standard system, MBO sets are defined for each valid version of the application.
Application specific additions and modifications are therefore reflected in the MBO sets.
 Example
For example, the MBO_PKG_SET_3.0 contains the MBO structures for Alerts). Similarly, the MBO set
MBO_PKG_SET_3.1 contains the MBO structures for Alerts and Activities.
5. Assign MBOs to MBO Sets (in this step, you assign the following to a DCN object:
○ Sub-objects and corresponding MBO structures
○ Hierarchy level of the sub-object in the schema of the MBO model (for maintaining the upsert sequence).
The following example demonstrates how the hierarchy level is defined and interpreted:
Parent Object Sub-Object Child Object Hierarchy Level
Activity Header 1
Partner 2
CE Fields 3
Notes 2
CE Fields 3
6. Assign MBO Sets to packages – In this step, you must assign all the relevant MBO sets to valid package name
(maintained in SMP server for the corresponding version of Retail Execution). This assignment, along with the
DCN connection profile (based on SMP target server maintained in the IMG) will determine the data to be
moved to the SMP server.

4.5.3 Criteria for Data Download
4.5.3.2 (DCN) Visits and Activities (including all associated

objects and To Do’s)
Replication to ● Transaction type and transaction category

SMP ● Date profile in Customizing where all activities that have started or have a start date in future are consid
ered for replication to SMP
● All activities valid for the device user
 Note
Activity Customizing is the same across all Sales areas.
Replication to ● If the user belongs to any partner functions for a transaction which belongs to this maintained transaction
Client type & category and is in status ‘I002, 1003, 1004, 1005, 1007, 1008. In summary, following Customizing is
validated:
○ Transaction type and category
○ Partner Function
○ Status
● Activity dates: Either of the following dates must fall within the date profile maintained for the activity
download profile
○ Planned Date
○ Completion Date
○ Planned Completion Date

4.5.3.3 (DCN) Surveys
Replication to 1. The following data is considered for replication of survey templates to SMP:
SMP
 Note
Surveys with only upto three subsections are supported. To support more than three subsections,
the user must turn on the ‘Use HTML’ option in the Preferences settings on the device.
○ Based on the sales organization (in the DCN Profile), all survey templates for a set of activities se
lected (Based on the IMG Customizing for the transaction type, category) and the sales organiza
tion selection provided in the report.
○ All the surveys and survey templates determined in the back-end (based on the Customizing crite
ria and for the surveys assigned to visits in the backend), will be replicated to the device. This
download also considers the standard survey determination criteria maintained in SAP CRM and
also the validity of the target groups for data download to the device.
Replication to All survey templates replicated to SMP will be downloaded to the device.
Client
 Note
The survey templates valid for the sales organization of the device user or belonging to the target group
of the business partner will only be displayed for the user.
4.5.3.4 (DCN) Journal Templates
Replication to All journal templates valid for the date type profile, transaction type, transaction category will be replicated
SMP to SMP. sales area forwhich have users sales area or no sales area will be sent to devicethat meet the follow
ing criteria are validated:
● Set to status Release.

● Belong to the Transaction type – Transaction category set defined in Customizing
● Belong to the same Days Profile as the Activities selected for download.
● Belong to the sales organization maintained in the DCN profile.
● For journals that are determined by target group or business partner hierarchy, the validity of these tar
get groups and business partner hierarchy (including the validity of the specific hierarchy node for the
current business partner in the hierarchy) will be considered for the offline determination of these jour
nals on the device. If the checks on the validity fail, then the journal templates will not be determined for
the visits.

Replication to All templates that have users sales area or no sales area will be sent to device.
Client
 Note
For offline determination of journal templates to activities in the device, the following criteria are consid
ered:
● Target group
● BP hierarchy
● Validity at the time of sync to backend
● Frequency check
4.5.3.5 (DCN) Sales Orders
Replication to SMP ● Valid in the date range maintained in the Days profile for Sales Documents
● All sales orders with a Posting date
Replication to Client All sales orders which are:
● Account based on relationship category or territory where that account is part of the sales or
der partner functions Customizing
● Document date or valid date of sales order is within the date range maintained in Sales docu
ments Customizing
4.5.3.6 (DCN) Business Partner
Replication to Business partners can be Accounts or Employees.

SMP
● Accounts
○ Role Profile – where BPs of certain roles are only download
● Employees
○ Employee relationship Category

Replication to ● BP download based on relationship
Client ○ Customer
○ User should be related to the customer based on the Relationship category and valid today
○ For replication of accounts detailed information, Customer should be part of sales area to
which device user is assigned
○ Account team
○ All BP’s for the customer who belong to the Relationship category maintained in selection cri
teria in Customizing replicated to the device
○ Contacts
○ Contact relationship category maintained at the selection criteria in Customizing considered
for replication of contacts to device. If no Customizing is available, then all contacts valid for
relationship category BUR001 considered for replication
● BP based on Territory (Hybrid) download based on Territory: All BP data replicated from backend to
SMP based on ‘Territory’
○ Customer – On demand request made from device to SMP and then forwarded to backend. All Cus
tomers for the user’s territory and where the user is the ‘Employee Responsible’ are replicated to
SMP. Direct replication of BP GUIDS from backend to device while the BP data is fetched from SMP.
○ Account Team : The Account team for user’s territory and for the Customers where user is ‘Em
ployee Responsible’ along with corresponding account team (and based on selection criteria from
Customizing) replicated to the device.
○ Contacts : Contacts for user’s territory and the contacts for Customers where user is ‘Employee Re
sponsible’ (and based on selection criteria in Customizing) replicated to the device
○ User : Directly based on the data fetched for Employee GUIDS from SMP
● Employee (Hybrid) – Employee represents Device user along with the sales team.
○ Territory : Hybrid approach
○ Sales Area : Hybrid Approach : On demand request made from device sent to backend to fetch list
of sales team GUIDS that are directly replicated from backend to the device. The data for sales team
is replicated from SMP. Criteria considered for replication include the download profile for account
(employee download criteria and the sales area to which user is assigned)
 Caution
SAP Retail Execution currently does not support assignment of an employee to multiple sales
organizations.
4.5.3.7 (DCN) Business Partner Hierarchy
Replication to BP Hierarchy considered only for determination of journal & marketing projects and not displayed on the de
SMP vice.
Replication to All business partners coming from either territory or relationship category and the corresponding Hierarchies
Client to which they belong are replicated to the device.

4.5.3.8 (DCN) Products
Replication to ● The product download profile valid for the sales area of the device user (if no product download profile
SMP assignment to sales area is available, then the product download profile set as default will be considered.
Replication to Download can be based on : Listings OR Territory along with or without Journals.
Client
● Territory (Hybrid)
○ All products belonging to the user’s territory are replicated to device. In addition, product sales area
data, sales area notes, set types and attachments are downloaded to client based on the sales area
of the user.
● Listings – (Hybrid)
○ Listings are based on BP’s. Once the BPs are downloaded based on relationship category or Terri
tory accordingly the products assigned to the BPs are downloaded to device
● Journals
○ Products Assigned to user's activities
○ Journal templates valid for download to device
4.5.3.9 (DCN) Target Groups
Replication to SMP Target groups for all business partners in the given sales area considered for replication to SMP
Replication to Client All BPs coming from either territory or relationship category and the corresponding Target groups
to which these BPs belong are replicated to the device.
4.5.3.10 (DCN) Marketing Projects
Replication to
 Note
SMP
Only Top n Lists and Marketing Projects are supported
● All marketing projects of future

● All Marketing projects in status ‘Released’

Replication to Data meeting the following criteria will be replicated to the device:
Client
● All valid Customers for employee responsible (Direct / Target Group / Hierarchy)
● All marketing projects set to status Released.
● Belonging to Days Profile
● All short-term marketing projects (Criteria for Short term : If in the CRM Customizing for Condition
Generation Types, no details are maintained for the assignment of condition generation type to the Cam
paign Determination Condition Type.
4.5.3.11 (DCN) Listings
Replication to SMP For the given sales area (in the DCN profile), all the list procedures are read and the assigned listing
types and the assigned listing for these listing procedures are considered for download to SMP.
Replication to Client For all the accounts valid for employee responsible, listed products listing information replicated to
the device.
4.5.3.12 (DCN) Returns
 Note
Returns are downloaded along with Sales Order; however, unlike Sales Orders, returns are downloaded only
from ERP system.
Replication to For all relevant standard client Customizing, returns for list of valid business partners for employee respon
Client sible, belonging to the days profile and assigned as either a Sold-To or a Ship-To (in the Customizing step:
Assign Data Download Profile to Sales Documents), will be replicated to the device.
4.5.3.13 (On Demand) Product Hierarchy
Replication to Business partners and their BP hierarchy for the Sales area of the device user will be replicated to the SMP.
SMP
Replication to The BP hierarchy for all the device user’s Customer accounts replicated to the device.
Client

4.5.3.14 (On Demand) Product Categories
The following criteria are applicable for download of product categories to the device:
● Sales organization of the device user and the hierarchy level maintained in the Customizing for product
hierarchy level profile ( Retail Execution Define Download Profiles Product Category Hierarchy Level
Profile ) will be considered to replicate product categories to the device.
● Only the base categories of the product hierarchy (as defined in the Customizing of CRM 'Sales' application
and maintained in the master data for each product) assigned to the product are considered for download.
Sales categories and other categories assigned to the product are not downloaded.
● The table below illustrates how product categories are downloaded to the device:
Base Category Level as in CRM Customizing AND Hierarchy Download Result

Level in Retail Execution
If Base category level is Lower than all hierarchy levels in Re No downloads are possible
tail Execution
If Base category level is Same as hierarchy levels in REX The same hierarchy level considered for download of prod
uct categories to the device
If Base category level is same or lower than atleast one of Hierarchy level in Retail Execution that is same or lower than
the hierarchy levels in Retail Execution base category level considered for download of product cat
egories to the device
If Base Category Level is higher than all Hierarchy Levels in The highest of the hierarchy levels in Retail Execution con
Retail Execution sidered for download of product categories to the device.
 Example
Base category level maintained for the Product Hierarchy Levels Assigned to Product Category Level considered for
Product (in the CRM Customizing) 'Product Hierarchy Download Profile' Download of Product Categories
in Customizing for Retail Execution
1 2 None
2 2 2
3 2 2
2 1 and 3 1
4 1 and 2 2
4 1 and 3 3

4.5.3.15 (On Demand) Competitor Products
Replication to All competitor products of type Material or Service replicated to the device.
Client
4.5.3.16 (On Demand) Product Proposals
Replication to Schema related products for the schema maintained in the Customizing replicated to the device. Addition
Client ally, the following criteria will also need to be validated
1. All valid Customers for employee responsible (Direct / Target Group / Hierarchy)
2. All marketing projects (TopnList, Listed products and Promoted products) set to status Released
3. Belonging to Days Profile
4. All short-term marketing projects (Criteria for Consideration as Short term : If in the CRM Customizing
for condition generation types, no details are maintained for the assignment of condition generation
type to the Campaign Determination Condition Type.
4.5.3.17 (On Demand) Item Proposals
Replication to Cli All item proposals belonging to the sales area of the employee responsible and the date profile for sales
ent orders will be replicated to the device.
4.5.3.18 (On Demand) Offline Prices
Replication to Product price information when Offline price data in the ERP System set to Active in the Customizing for
Client Define Device Settings and meeting either of the following criteria, replicated to the device:
1. Condition Technique: For valid Business Partners and for the valid products, read the relevant condition
table and data replicated to the device.
2. Price list replicated to the device.

4.5.3.19 (On Demand) Dashboard
Replication to Dashboard data (employee and Account analytics) replicated to the device based on the query maintained in
Client the Customizing.
 Caution
Only simple BW queries with one characteristic and multiple key figures are supported for Retail Execu
tion.
4.5.3.20 (On Demand) Trade Assets
Replication to Client Based on the Customizing for Trade Assets Maintenance (ERP), relevant data will be replicated to the
device.)
● Functional Location Active : Trade assets at the specified functional location only will be replicated to
device if this flag is selected. If the flag is not set, then all trade assets for the specific Customer will
be replicated to the device.
● Equipment Category : If the flag for 'Equipment Category' is set ONLY THEN trade asset details will
be replicated to device.
● Partner Function : Where the Accounts of the user belong to the partner function specified in the
Customizing for Organizational Attributes.
4.5.3.21 (On Demand) Print
Replication to Templates maintained (for CALENDAR, SALES ORDER, RETURNS) in the CRM and ERP for print settings, re
Client plicated to the device.
4.5.4 Additional Settings for Delta Download
4.5.4.1 CRM - Delta Download with DCN using BDOCs
Delta download for CRMis performed using the MBDOCs provided for all the business objects supported for data
transfer using DCN. The following section lists the relevant details required to execute delta download.
 Note
The MBDoc information is used to identify the corresponding DCN enabled object and subsequently the delta
information for the object is sent to SMP.

For delta download using DCN, execute the transaction SMW3FDCUST and choose Maintain Entries to specify the
following for each DCN object.
 Caution
The flow context can either be MO1 or MO2. If the flow context of the bdoc is MO1, map delta FM to MOA and if
the flow context is MO2, then map it to MOB.
Business Object BDOC_Type Context Counter FNAME ACTIV
Activities / Sales BUS_TRANS_MSG MOA/MOB next sequence no in /MAC/ X

Orders the system for RSFM_DCN_ONEOR
BDOC_TYPE FCTXT DER_DELTA
MOA
Business Partner BUPA_MAIN MOA/MOB next sequence no in /MAC/ X

the system for RSFM_BP_MAIN_D
BDOC_TYPE and ELTA
context MOA
BUPA_REL MOA/MOB next sequence no in /MAC/ X

the system for RSFM_BP_RELATI
BDOC_TYPE ON_DELTA
Marketing Projects MKTPROF_MSG MOA/MOB next sequence no in /MAC/ X

(for Business Part the system for RSFM_BP_DELTA_
ner) BDOC_TYPE MKT_ATTR
Business Partner BUHI_MAIN MOA/MOB next sequence no in /MAC/ X

Hierarchy the system for RSFM_BP_HIERAR
BDOC_TYPE CHY_DELTA
Products Product_mat MOA/MOB next sequence no in /MAC/ X

the system for RSFM_PRODUCTS_
BDOC_TYPE DELTA
Target Group TG_MSG MOA/MOB next sequence no in /MAC/ X

the system for RSFM_DCN_TRGT_
BDOC_TYPE GRP_DELTA
Marketing Projects MKTPL_MKTELEM MOA/MOB next sequence no in /MAC/ X

the system for RSFM_DCN_MKTPR
BDOC_TYPE OJECT_DELTA
Listing PPR MOA/MOB next sequence no in /MAC/ X

the system for RSFM_DCN_LISTI
BDOC_TYPE NG_D
Attachments

CRM_DOC_MBDOC MOA/MOB next sequence no in /MAC/ X
the system for RSFM_DCN_ATTAC
BDOC_TYPE and HMENT_DELTA
context MOA
4.5.4.2 ERP - Delta download of based on BTEs
 Caution
The Parent Object MUST FIRST BE EDITED for attachments to be considered for DELTA download (when
attachments are added/modified/deleted from existing sales orders) to SMP. No limitations apply in CREATE
scenario.
The following steps must be performed to fetch delta for ERP objects.
1. Execute the transaction SM30 and maintain entries for the table TBE31
2. Enter the following values and save.
Event Country ISO Code Application Indicator Function module
00501014 /MRE/
RSFM_DCN_SALESORDER_DE
LTA
4.5.5 Push Alerts
Push alerts execute EIS (Enterprise Information System) operations and therefore need to be secured. In order to
secure the DCNs, the communication channel as well as the event request made by SMP server must be secured.
This mechanism also secures DCN User Setup and DCN Authentication.
 Note
Maintain the required configuration for DCN (as described above) to use the feature for push alerts.
Refer to the documentation for Securing EIS Operations: DCN and Push (relevant for SAP Mobile Platform 2.3
SP05) in http://help.sap.com/mobile-platform .

4.5.6 Synchronization
4.5.6.1 Initial Sync
 Caution
Background sync (both Initial Sync and Delta Sync) is not supported in Retail Execution. The users can navigate
in the application, but cannot create or modify in the application. Additionally, Background activity on the
device on any other application on the device is also not supported.
Initial Sync : Synchronization is an extremely critical feature of Retail Execution as the application can be used both
in online and offline modes. After the initial login to the application, a synchronization is performed to initialize the
application on the device and for data to be replicated to the device. The duration of the initial sync will depend on
the data load from the back-end systems. It is important that the initial sync is complete before the user starts the
application. Any interruption to the sync will result in incomplete data setup on the device.
Initial synchronization is segregated into three stages:
● synchronization with CRM system

● synchronization with ERP system
● synchronization for Attachments
 Note
Make sure the device is connected during and until the synchronization process is complete. Disconnecting
the device will also abruptly stop the synchronization process.
 Caution
Synchronization of attachments will consume more time. Therefore, the application prompts the device
user with the following options:
○ Continue
If the user selects this option, the initial sync will complete the download of attachments to the device.
○ Not Now
If the user selects this option, the attachments will be downloaded on-demand, that is when the user
taps on an attachment.
 Caution
The user is allowed 30 seconds time to stop or continue with attachments sync. If the user does not select
an option in 30 seconds timeframe, the system continues to sync the attachments.
 Caution

4.5.6.2 Delta Sync
The application offers various options to perform DELTA sync with the back-end systems. The performance of
synchronization will depend on the SMP servers as well as the synchronization preferences maintained on the
device.
 Caution
Because of caching in the SMP servers, any Customizing changes in the back-end systems will consume more
time in getting replicated to the device.
Delta sync can be performed for the following objects:
● Customers
 Note
Delta sync for Customers also includes the sync for Customer and Employee Analytics
● Visits
● Promotions
● Products
● Customizing
● Target Group
● BP Hierarchy
● Survey Templates
● Trade Assets
● Sales Documents
● Offline Pricing
4.5.6.3 Few Dependencies in Synchronization
The dependencies listed in this section are critical in the application and must be noted:
Background Sync not Supported
Background activity on the device or use of any other app on device is not supported when synchronization is in
progress.
No Creation or Modification Allowed During Initial or Delta Sync
Only navigation is possible when initial or delta sync is in progress. No creation and modification are allowed. If
users attempt to create or modify when sync is in progress, the application may crash.

Initial Synchronization of Attachments
Initial synchronization of attachments may consume more time. The user is therefore provided with an option to
continue with the initial sync or stop the synchronization of attachments. The user can download attachments on
demand (tap on an attachment to download and view the attachment).
Synchronization of Product Attachments
If initial synchronization for Attachments is interrupted, then product attachments waiting to be synchronized will
be processed in queue and considered for synchronization when an on-demand synchronization is performed for
one or more product attachments.
Synchronization of Visits with Unsynced Contacts
iOS Only: Visits created on the device using contacts local on the device (not yet synced with the backend) MUST
BE SYNCED TWICE. The first sync will be used to sync the contacts and generate unique identification for the
contact in the backend and assign them to the visit on the device. The second sync will be used to sync the visit
itself.
Android Only: Visits cannot be created using contacts that are local on the device (not yet synced with backend).
The contacts on the device must first be synced with the backend to make them valid for use in visits.
Only Products and Promotions WITH Description Considered for Download to

Device
Products and promotions created with a description will be considered for download from backend to the device.
 Caution
Products and promotions without description WILL NOT be considered for download to the device.
4.6 Device Management
4.6.1 Application Provisioning with Afaria
Use
With the following steps you can provide application provisioning with Afaria. The usage of Afaria is optional but it
gives you an advantage in managing and securing all your mobile applications and devices including critical

enterprise data. For more information about Afaria, see the information on Sybase products at http://
www.sybase.com Products Mobile Enterprise Afaria.
 Recommendation
For more information about Communication Encryption when you are using Afaria for application provisioning,
see section on Communication Channel Security.
Prerequisites
You have followed the installation instructions for the topic Provisioning with Afaria in the product documentation
for SMP 2.3 SP05
In addition, you are familiar with the Afaria documentation. To access the Afaria documentation, log on to the
Mobile Enterprise Technical Support (METS) at http://www.sybase.com Products Mobile Enterprise Afaria
Technical Info Technical Support
After installation, you have to enter your app in Afaria MDM. For information on how to proceed on Afaria
Administrator Console and create an Afaria portal application package, see the documentation for Afaria.
Features
In the configuration profile (for the respective platforms) of the Afaria administration console, the general data and
the configuration data for applications compiled with the Afaria Static Link Library must be maintained. The
following table lists the provisioning properties that can be configured for Retail Execution and the format in which
these need to be configured. Customers can choose to use all or only few of these properties.
 Caution
1. Each of the properties listed in the table must be maintained in separate lines in the configuration setup.
2. The format of these values must be the same as mentioned in the table below. Note that Retail Execution
does not use all or the same provisioning parameters as in the standard Afaria setup.
Provisioning Properties for iOS and Android
Properties (as Description Format to Configure Properties in Re Example

in Afaria) tail Execution
Servername The server name for the CONNECT_SERVER_PROP_ID CONNECT_SERVER_PROP_ID:

machine (IP address of the 10.11.12.13
server) that hosts the SAP
Mobile Server or Relay
Server if this is used.

(iOS ONLY) CONNECT_USERNAME_PROP_ID CONNECT_USERNAME_PROP_ID:shiv
Username
Serverport The server port number CONNECT_PORT_PROP_ID CONNECT_PORT_PROP_ID:123

for SAP Mobile Server. The
default is 5001.
Companyid The company or farm ID CONNECT_FARMID_PROP_ID

you entered when you reg
istered the device in SAP
Control Center, in this
case, 0 (zero).
URL prefix The URL suffix is a pattern CONNECT_URLPREFIX_PROP_ID

that is used internally by
SAP Mobile Platform when
constructing URLs as part
of the correct path to con
nect to SAP Mobile Server.
By default, you do not
need to set this property;
the client auto-detects the
correct path when con
necting directly to SAP
Mobile Server, or when
connecting to SAP Mobile
Server via the Relay Server
using its default settings.
 Note
Only use when the ad
ministrator sets
something other than
the default path and
URL suffix for the Re
lay Server.
protocol This property indicates CONNECT_PROTOCOL

whether to use a secure
connection , this property
accepts a Boolean value ,
possible values that can be
supplied are “YES” , “NO”

Security Con This property accepts a CONNECT_SECURITY_CONFIGURATI
figuration string value , customers ON_ID
can provide the name of
security configuration as
its value.
4.6.2 User Creation and Authorization Assignment
 Note
It is important that you understand the user concept in the mobile system landscape. To obtain an overview of
the user concept in the mobile system landscape, see the section on User Administration and Authentication.
● You have to create users on the application back-end system. For more information, see User
Management.
● You need to decide about your preferred mechanism for user authentication. This decision influences user
management and has to match the corresponding settings when registering the application on SAP Mobile
Platform.
● Mobile application users need dedicated authorizations in the application back-end system.
4.6.3 Trusted RFC Connection from SAP ERP to SAP CRM
A trusted RFC connection must be defined from SAP ERP to SAP CRM using the login credentials of the current
user. These settings can be defined in Transaction Code SM59 ABAP Connections Create a New
Connection In the same path, go to the Logon & Security tab and set the flag for 'Current User' to ensure that
these settings are active for the current user.

5 Extensibility Using Augmentation
Framework
 Note
For the benefit of implementation, a separate Extensibility Customizing Guide is available for SAP Retail
Execution 3.3.0 in the SAP Service Marketplace. Note that there are differences in the extensibility Customizing
implementation in various devices (iPhone, IPad, Android Phone and Android Tablet).
From release version 3.3. onwards, you can configure and implement multiple XML files in the Retail Execution
extensibility framework using UI Augmentation framework. Multiple XMLs can be used to support the following
scenarios:
● Multiple release versions of Retail Execution that use the same backend systems (CRM and ERP).
● Assignment to different sales areas. The Business Add-In implementation that you create must use sales area
data as filter criteria to select the valid XML for a user. Three new fields IV_SALES_ORG, IV_DIS_CHANNEL,
IV_DIVISION have been added to the method /MAC/RS_BADI_GET_CLNT_XML and interface /MAC/
RS_BADI_IF_CLNT_XML in the Business Add-In. You need to create the necessary logic to implement this
method with these fields.
The complete UI for the iOS and Android applications can be modified using the extensibility framework provided in
Retail Execution. The extensibility is designed using Augmentation framework. For supported documents for
extensibility, refer to the Extensibility Customizing guide and the SAP Note numbers 1918860 (for IOS) and
1932680 (for Android).

Extensibility Using Augmentation Framework PUBLIC 57
6 Security Framework
6.1 Before you Start
The SAP Mobile Platform provides the technology to build SAP Retail Execution. The solution uses the SMP and its
development model to expose CRM and ECC functionality. SAP Retail Execution integrates with the SAP CRM back-
end and SAP ECC back-end for business functionality. Business logic still resides in the back-end servers.
SAP Retail Execution is built using ABAP functionality (RFC Function Modules) on the CRM and ECC server. To
enable the business scenarios, the solution leverages three main components: SAP Mobile Platform, SAP CRM
Server and SAP ERP Server. Hence, the corresponding Security Guides of the components also apply in
implementation of SAP Retail Execution.
For a complete list of the available SAP Security Guides, see SAP Service Marketplace at the following location:
http://www.service.sap.com/securityguide
Fundamental Security Guides
Scenario, Application or Component Most Relevant Sections or Specific Restrictions

Security Guide
SAP CRM Security in Detail SAP Security Guides SAP Business Suite Applications SAP
CRM Security Guide for SAP Customer Relationship Management 7.0
SAP ERP Security Security in Detail SAP Security Guides SAP Business Suite
Applications SAP ERP SAP ERP 6.0 Security Guides
Security for iPad http://www.apple.com/iphone/business/integration Refer to the section on Secure

your Data.
Security for Android http://source.android.com/tech/security
SAP Mobile Platform 2.3 SP05 PL01 http://help.sap.com/mobile-platform SAP Mobile Platform 2.3 SP05
Afaria Data Security Manager for Afaria docs are available to customer and partners at the Mobile Enterprise Technical
Windows Support (METS) website. (link: http://frontline.sybase.com/support/login)
6.2 Technical System Landscape
The following figure introduces a possible Network topology which is secured by different firewalls.

58 PUBLIC Security Framework
Overview of the Network Security for SAP Retail Execution
6.3 User Administration and Authentication
Mobile applications provide access to back-end functions from outside the corporate network. This results in
additional challenges, such as how to authenticate the user via the mobile device. The following topics include
information about the user administration and authentication that specifically applies to Retail Execution.
● User Management:This topic describes the user management concept and lists the tools used for user
management and the types of users required.
● User Authentication and Single Sign-On: This topic describes the authentication options that mobile
applications support and how they are integrated with SAP Single Sign-On mechanisms.

Security Framework PUBLIC 59
6.4 User Management
6.4.1 Introduction
To use SAP Retail Execution, the following user types are required:
● Administrator:
Administrators are internal users who have the task of operating on the SAP NetWeaver ABAP and configuring
the Retail Execution app using the standard ABAP implementation guide (IMG) Customizing.
● Mobile User:
In SAP Retail Execution scenario, the mobile device user is a business partner that represents an Employee
Responsible for one or more Customers.
There are two options to authenticate the mobile device user:
● User ID and Password

● X-509 Certificates
SAP recommends using the X-509 certificates for authentication. Please follow the online documentation for
setting up SAP Mobile Platform Server for accepting X-509 certificate.
To use a user ID and password, the SAP Mobile Platform Server security configuration for security provider (HTTP
Basic Security Provider) can be used. For details on how to use the security configuration, refer to the SAP Mobile
Platform documentation to create security configuration and assigning the security configuration to a domain for
the application.
SAP recommends the following for Retail Execution.
● Configuring a separate ABAP server solely for authenticating the mobile user. A NetWeaver Mobile server, if
available, can also be used for this purpose.
● Using an SSO mechanism provided by using an SSO cookie. The cookie with name MYSAPSSO2 is provided in
the standard system. A trust relationship must be defined between each of the back-end systems (CRM and
ERP) and this authenticating system.
● Setting a password for the authenticating server that is different from the passwords for CRM and ERP
systems. This will ensure that the risk to the back-end system is minimized when the authenticating server
password is compromised.
● Using a strong initial back-end password for the authenticating server. A strong password can be generated by
the administrator using transaction SU01. For more information refer, refer to the documentation in the
following path: http://www.help.sap.com SAP NetWeaver SAP NetWeaver 7.0 Including Enhancement
Package 1 Application Help AP Library Instructions for using the application SAP NetWeave SAP
NetWeaver by Key Capability Security Identity Management User and Role Administration of AS ABAP
Administration of Users and Roles User Administration User Administration Functions Creating and
Editing User Master Records Logon Data Tab Page
● Not using an initial password on the mobile device. For changing the initial password, users can log on to the
authenticating ABAP server and follow the dialog for changing the password. The changed password can then
be entered on the mobile device.

6.5 Authorizations
The SAP Retail Execution users the authorization concept provided by SAP NetWeaver. Therefore, the
recommendations and guidelines for authorizations, as described in the SAP NetWeaver AS Security Guide ABAP,
also apply.
The SAP NetWeaver authorization concept, is based on assigning authorizations to users based on roles. For role
maintenance, use the profile generator (transaction PFCG) when using ABAP technology.
 Note
Since most of the business functions of SAP Retail Execution use the CRM and ERP objects, the ABAP
authorization concept must be referred to. For more information on how to create roles, see SAP Library
documentation for Role Maintenance.
Standard Authorization Objects
Authorization Object Field Value Description
S_RFC RFC_NAME List of RFC function groups Needed to allow access to my

that are used by SAP Retail Ex business functionality in the
ecution is given below this ta back-end that is accessed via
ble. an RFC.
Never assign full authorization

to this authorization object.
S_TABU_DIS DICBERCLS /MAC IMG maintenance) the SAP

Retail Execution Scenario on
the CRM back-end.
S_TABU_DIS DICBERCLS /MRE Needed to allow access to

configure (IMG maintenance)
the SAP Retail Execution Sce
nario on the ERP back-end.
List of function groups to be maintained in S_RFC:
CRM function groups:
● /MAC/ITEM_PROPOSALS
● /MAC/RETURNS /MAC/RSFG_ACT
● /MAC/RSFG_ANALYTICS
● /MAC/RSFG_BP
● /MAC/RSFG_COMMON
● /MAC/RSFG_CUSTOMIZING
● /MAC/RSFG_DCN

● /MAC/RSFG_DCN_BP
● /MAC/RSFG_DOC
● /MAC/RSFG_MARKETING
● /MAC/RSFG_PRICING
● /MAC/RSFG_PRINT
● /MAC/RSFG_PRODUCTS
● /MAC/SALESORDERS
● /MAC/TRADE_ASSETS
ERP function groups
● /MRE/TRADE_ASSETS
● /MRE/ITEM_PROPOSALS
● /MRE/CUSTOMIZING_UTIL
● /MRE/SALESORDERS
● /MRE/SALESDOCUMENTS
● /MRE/RETURNS
6.6 Network and Communication Security
Your network infrastructure is extremely important in protecting your system. Your network needs to support the
communication necessary for your business needs without allowing unauthorized access. A well-defined network
topology can eliminate many security threats based on software flaws (at both the operating system and
application level) or network attacks such as eavesdropping. If users cannot log on to your application or database
servers at the operating system or database layer, then there is no way for intruders to compromise the machines
and gain access to the back-end system’s database or files. Additionally, if users are not able to connect to the
server LAN (local area network), they cannot exploit well-known bugs and security holes in network services on the
server machines. The network topology for the SAP Retail Execution Solution is based on the topology used by the
SAP NetWeaver platform, SAP Mobile Platform (with Sybase Afaria). Therefore, the security guidelines and
recommendations described in the SAP NetWeaver Security Guide and SAP Mobile Platform also apply to the SAP
Retail Execution.
6.7 Communication Channel Security
Communication Channel Protocol Used Type of Data Transferred
Replication Client to Relay Server HTTPS All application data
SAP Mobile Platform to Relay Server HTTPS All application data
SAP Mobile Platform server to CRM/ERP RFC All application data relevant for business
logic

SAP Mobile Platform server to CRM/ HTTPS Push Alerts
ERP2
RFC connections can be protected using Secure Network Communications (SNC). HTTPs connections are
protected using the Secure Sockets Layer (SSL) protocol.
 Recommendation
SAP strongly recommends using secure protocols (SSL, SNC) whenever possible.
Communication Encryption
SAP Retail Execution
Set up the SAP Mobile Platform to use the Https protocol for Synchronization to enable encrypted
communications. And instruct the users to use Https as network protocol in the communication setting on the
application. This settings option is available in the section on application Setup when the user launches the
application for the first time.
More Information
For more information, see sections Transport Layer Security and Web Services Security in SAP Library for SAP
NetWeaver on SAP help portal at the following path:http://help.sap.com/nw702 and in SAP Library, choose
Administrator’s Guide SAP NetWeaver Security Guide .
For more information about how to set up secure communication channels, see SAP Library of SAP NetWeaver
Gateway 2.0 SP02 on SAP help portal at the following path: http://help.sap.com/nwgateway20 and in SAP
Library, choose SAP NetWeaver Gateway Security Guide Network and Communication Security Encrypted
Communication Channels. .
For more information about how to set up the communication between the mobile device and SAP Mobile Platform
and relay server, see the product documentation for SAP Mobile Platform 2.3 in the following path:http://
help.sap.com/mobile-platform
6.8 Network Security
It is recommended to run the SAP Retail Execution Scenario in network zone as recommended in the SAP Mobile
Platform security guide.

6.9 Data Storage Security
SAP Retail Execution data is stored at different storages depending on the kind of data and the usage of data.
SAP Database
The device database of Retail Execution is already encrypted. To implement additional security measures, use the
passcode policy of SMP. For further information, refer to section 4.1.4 of this document.
File System
SAP Retail Execution scenario for iPad stores information for application customizing like CEClass Names and
status metadata in the file system of the mobile device at the application root directory.
 Note
● It is recommended that PIN protection is enforced from the SMP.

● The user of the device is recommended to use the feature provided by the device to lock the device in case
of inactivity.
6.10 Other Security Relevant Information
Overview on the users and default passwords from the application perspective
The SAP Retail Execution does not provide any default users and passwords to use the client application. The
mobile user has to register his user ID and password (when the device is connected first time after application
installation), to be able to subscribe to the data.
Message Encryption
For more details, please read the SAP Mobile Platform security guide.

7 Operations Information
7.1 Data Consistency
For Retail Execution, the data is stored in the corresponding SAP Business Suite back-end ERP and CRM systems.
Data consistency is checked there using the usual procedures.
7.2 Support Desk Management
Support desk management enables you to set up an efficient internal support desk for your support organization
that seamlessly integrates your end users, internal support employees, partners and SAP Active global support
specialists with an efficient problem resolution procedure. For support desk management, you need the
methodology, management procedures and tools infrastructure to run your internal support organization
efficiently.
7.3 Remote Support Setup
SAP support needs to be able to work remotely to achieve the highest efficiency and availability. Therefore, all
required support tools must be remotely accessible for SAP support. For more information on how to set up remote
connections, see the SAP Support Portal on SAP Service Marketplace at the following path: http://
www.service.sap.com/access-support Available Connection Types.
 Recommendation
For SAP back-end systems, the following connection types are a good starting point:
● HTTP Connect - URL Access

● R/3 Support
● Connection types enabling the access to the operating system.
● For SAP Mobile Platform Control Center, you should activate HTTP URL access as a minimum.

Operations Information PUBLIC 65
7.4 Problem Message Handover
When creating a message, you need to distinguish between back-end application related issues and issues with the
mobile components. For the back-end related issues, use the standard application component hierarchy. and
related technology components have been assigned to new component hierarchies as follows:
MOB-SUP SAP Mobile Platform
MOB-APP Mobile Applications (refer to the sub-component defined for

the relevant application).
MOB-AFA Afaria
MOB-APP-REX Retail Execution Backend
CRM-MSP-REX-IPH Retail Execution for iOS
CRM-MSP-REX-AND Retail Execution for Android

66 PUBLIC Operations Information
8 Features and Functions Overview
8.1 Device Settings
The following settings can be defined in the Preferences section (application menu option in Android and Global
Access Menu toolbar in iPad)
● (iPad and iPhone Only) Calendar Settings in Preferences

○ Device events on REx Calendar
If you set this switch to ON, device events will be displayed in the schedule for Retail Execution. However, in
order to refresh the schedule with device events, the device user must exit the application and re-login to
the application.
○ Visits on device calendar
When you set this switch to ON, the visits in the schedule for Retail Execution will be replicated to the
device calendar.
 Note
Only visits from the current date and time of defining these settings will be displayed in the device
calendar. Whenever a delta sync is performed (for any objects), the device calendar will be refreshed
with visits prior to the current date and time.
 Caution
In addition to setting the checkbox for 'Visits on device calendar', the following settings MUST be
defined to enable visits on device calendar:
1. On your iOS device, Turn Off the Calenders in the following path: Settings Mail, Contacts,
Calenders Accounts Active email account Calenders
 Caution
When the device calendar is turned off, an alert is displayed with two options : 'Delete from My
iPhone/iPad' and 'Cancel'. You must select 'Delete from My iPhone/iPad'. Your native device
calendar is now deleted.
2. Now turn on the calendar again. An alert is displayed to the user asking whether device calendars
must be retained or deleted. Select 'Keep on My iPad', and then select 'Keep' in the next alert.
3. Exit 'Settings'
4. Go to Calendars on the device and tap on 'Calendars' on the calendar toolbar.
 Note
If your device is already synced with the backend, duplicate entries will appear in the calendar.
Delete all REX events in the calendar.
5. Go to Settings General Reset Reset Location & Privacy.

Features and Functions Overview PUBLIC 67
6. Close the device calendar.
7. Login to the Retail Execution application and in the device preferences, select the checkbox for
'Visits on device calendar'.
 Caution
If the checkbox is already set to 'ON', it needs to be turned off and then turned on again.
8. Open the calendar in Retail Execution application. All Retail Execution events and appropriate
alerts will now be displayed in the calendar.
● Search Criteria
Search criteria for following business objects can be defined here:
○ Customer
iPad Only
○ Phone
○ Partner/Customer ID
○ Customer
○ Address
○ Email
Android Only
○ Customer ID
○ Name
○ Store Address
○ Mobile
○ E-mail
○ Phone
iPhone Only
○ Customer ID
○ Customer
○ Address
○ Phone
○ Email
○ Products
iPhone Only
○ Product ID
○ Product Description
○ GTin
○ EAN/UPC Code
Android Only
○ Product ID
○ Description
○ UoM
iPad Only
○ Product ID
○ GTIN
○ Description

68 PUBLIC Features and Functions Overview
○ iPad and iPhone Only : Trade Assets
○ Description
○ Serial Number
○ iPad and iPhone Only : Promotions
○ ID
○ Descriptions
○ iPhone Only : Visit
○ Process Type
○ Activity ID
○ Duration
○ Customer
○ Priority
○ Activity Category
○ Type
○ Status
○ Planned End
○ Address
○ Description
○ Planned Start
○ Actual Start
○ Actual End
○ Reason
○ Mandatory
○ iOS Only : Audit
○ Product ID
○ GTIN
○ Description
○ Category
○ iPhone Only : Sales Orders
○ Created Date
○ Status
○ Sold-To
○ Partner ID
○ Total
○ Document Type
○ iPhone Only :Returns
○ Partner ID
○ Document Type
○ Return ID
○ Reason
○ Created Date
○ Sold-To
○ Status
○ iOS Only :Return Items
○ Description

○ Reason
● General
Settings for sending error logs (including maximum size for log file). Other options in this section include
Change Password and alert for visits.
● Synchronization
Synchronization on/off switches for various entities such as products, visits, Customizing, Sales Documents,
Customers, etc.
● Search
Search settings for Customer, Products and additionally (iOS Only) : Promotions and Trade Assets.
 Note
iPhone Only: The search settings are also used in displaying the fields in the list.
● Attachments
Time frame for downloading attachments to the device and the number of on demand attachments that are
permissible on device.
● Calendar
Settings to display personal settings on the Retail Execution schedule and visits on device calendar.
● Password Change
The password from the SAP CRM back-end login credentials can be changed. The password must however first
be changed on the CRM Server before changing it on the device.
● Unsubscribe
Unsubscribes the user from the application and deletes all local data on the device. To re-login, a new user
must be created in the SMP server.
● iOS Only : Questionnaire
Copy Previous Journal Turn on this indicator if you want to use the feature to copy previous visit journals to a
new visit.
● iPad Only
Use HTML: Specify the format in which questionnaires are to be displayed. If you set HTML to ON, the surveys
will be displayed in html format. You can turn off this switch if you want native formats to be used for displaying
surveys and questionnaires.
Use Matrix View for JournalsTurn on this indicator to display journals in matrix view.

8.2 Schedule
The schedule is the center stage for all visit related planning. It offers many integrated features. Some of them are:
Map Overview
 Note
Android Only:
 Note
Android Maps
A licensed agreement with Google is required to use the feature for Maps. Further, you need to retrieve a client
id and encryption key (with help from Google's team). These fields (GoogleMapKey(for clientid) and
GoogleMapEncryptionKey(for encryption key) need to be included in the commonconfiguration.xml ( CRM
System Mime Repository REX XMLS Android . For detailed information, see https://
developers.google.com/maps/documentation/business/clientside/
● Displayed in the Day view of the schedule.

● Pointers for visit locations.
● Option to view directions for visit location.
Free Global Search
A free global search (in the application menu) runs on the entire application. For example, a search can be executed
using a Customer name, an Identification or even description of a visit. The results of search are filtered to display
only those objects for which matching entries are found.
To Do’s
Some characteristic features of To Do’s are:
● Can be created in the SAP CRM back-end system or on device. If created on the back-end servers, the
Employee Responsible, cannot be changed on the device. If created on the device, activity partners can be
assigned for a To Do. Activity partners are however not mandatory for To Do’s.
● Created for Transaction Type To Do in CRM back-end server.
● Independent of Visits or any other objects.
● When To Do’s are complete, the internal status is set to Completed.

● To Do’s in the various devices:
○ iPad : A button (with tick mark) available on the navigation bar below the menu bar.
○ iPhone: Icon for To Do’s on the toolbar in the application menu.
○ Android : A separate item in the application menu for To Do’s.
Drop Pins on Map
These are pointers on map for Customer locations.
 Note
iOS Only: Apple maps are used for implementing the feature.
Android Only: Geocode server implementation required for this feature.
Day View
iPad Only: Tab screen for Day view displayed in the schedule.
Android Only : An icon to display day view in the schedule.
Print : Print option for the Day view is only available in Android smartphone)
Week View
Android Only : Icon to display promotions assigned to the device user.
iPhone Only : Week view is displayed in the Schedule when the device is in the landscape mode.
iPad Only : Drag and Drop Visits : In the List View (Split view), The drag & drop action appears n Blue color if the
reschedule is possible and Red color if the action is not permissible. The following drag and drop actions are
possible in the list view:
iPad Only Favorite Customers : Star icon displays the favorite customers (customer groups) created by the user.
A tap on one of the customer groups displays all the customers in that customer group, in addition to the list of
Customers for the user.
Month View
Displays the calendar for the whole month and the dates on which visits are scheduled are marked with a dot. If
more than one visit exists, then parallel bars will be displayed to represent the visits on the calendar.

List View
Lists all visits for each day of the month.
Create New Visits
Icon for creating new visits from the schedule.
iOS Only : Recent
The list of recent business objects (Visits, Customers, Sales Orders and Returns, Products) accessed recently is
displayed in this global access menu option.
Unassigned Visits
Unassigned visits are displayed in the schedule.
iPad Only: In the Week View / Split View
iPhone Only : A button for Unassigned activities on the toolbar.
Android Only: Icon for displaying unassigned visits is available in all the views in the schedule.
All-Day Visits and Events in Retail Execution Device Calendar
You can create all-day events (including all-day events spanning over many days) in the Retail Execution device
calendar. To do this, you must select the flag for the Allday indicator for all-day events when creating or
rescheduling a new visit. Note that if you turn on this indicator, the start and end time for the visit are disabled.
Android Only: The new all-day events will be displayed in blue color but will follow the standard color palette
maintained for Retail Execution calendar events once the status changes to In-Process (until the status is set to
Completed.
8.3 Visits
8.3.1 Visits Overview
Visits in SAP Retail Execution represent activities in SAP CRM. Therefore, in the IMG Customizing, a mapping is
defined between the Retail Execution specific device transaction types and device transaction keys to CRM

Activities and Categories. It is with this assignment that visits created in Retail Execution are maintained in SAP
CRM.
Retail Execution supports the following device transaction keys and these device transaction keys have been
delivered with certain UI paradigms. You are required to consider these UI paradigms before defining the
Customizing for visits.
● Retail Visit
Represents plain visit template for Retail Execution.
● Promotion Compliance
Supports surveys without images
● Planogram Check
Supports both surveys and images
● Retail Audit
Supports all product audits but without surveys
● Competitor Audit
Supports all products but without surveys
● Task
● To Do
 Example
If you need to use both surveys and images, you must map a transaction type and category to device
transaction key : Planogram Check. And if you need to add products to a visit for performing a store audit, you
must use device transaction key Retail Audit.
You can, for example, use Product Audit and create multiple entries such as shelf audit, store audit etc. All these
device transaction types will have the UI functionality supported for Product Audit.
The following terminology definitions are provided for clarity in understanding the Implementation Guide
Customizing settings:
Term Explanation
Device Transaction Key Represents the UI paradigm supported by Retail Execution. You
must select a device transaction key that will support the in
tended business process.
Device Transaction Type Represents the Text and Numerical representation defined in
the Customizing. You assign this device transaction type to a
CRM transaction type.
Transaction Type Represents the CRM transaction type
Transaction Category Represents the CRM transaction category
IMG Customizing for Visits
1. Select a device transaction key supported in Retail Execution.

2. For this selection, maintain a text description to reflect the intended business process for which it is created.
Also maintain a numeric code for this text description.
3. Select this combination of device transaction type + device transaction key and assign it to a CRM transaction
type and CRM transaction category.
Result : This mapping will determine:
● The UI for the visit template on the client application.

● The CRM transaction type that is used to read the visit data and synchronized to the back-end CRM system.
Check-In and Check-Out
The Check-In and Check-Out buttons record the start time and completion time of a visit respectively. The
Customizing for Visit and Activity Timestamps in the IMG captures the actual start time and end time for visits.
 Note
The respective flags for Visit and Activities timestamps must be set in the Customizing activity Define
Organizational Attributes, to ensure that the actual start and end time for activities within a visit too get
recorded.
Check-In using GPS
Check-in using Global Positioning Systems (GPS) proceeds as follows:
● Accuracy of location is determined using cellular data or internet connection (if cellular data is not available
● If both cellular data and internet connectivity are not available, the app prompts the user to choose to wait (5
seconds for iOS and 20 seconds for Android - configurable for Android in the preferences) until the GPS
location is determined. The user is allowed to check-in without having to wait until the GPS location is
determined. The visit is not checked-in if the user chooses to wait until GPS location is determined.
(iPad and Android Only) QR Code and Bar Code Scanning for Starting a Visit
A third-party scanning tool can be used to scan the Customer QR codes during Check-In / start of a visit. It enables
tracking of the actual start time for a visit. The QR code and Barcode data for Customer accounts are maintained in
the back-end SAP CRM system. The time when the device user scans the barcode, is recorded as the start time for
visits. The barcode is encoded along with the Check-In button. The application user can scan the barcode / QR
code to start the visit or simply use the Check-In button.
 Note
The required implementation considerations exist for using a third-party scanning tool. The standard system
for Retail Execution supports bar code scanning using the third-party application Zxing. Refer to the following
websites for more information on this application: http://code.google.com/p/zxing and http://
zxing.appspot.com

 Note
Standard system for SAP Retail Execution supports the feature for QR code scanning with a default BAdI
implementation. To use the feature for bar codes, a separate implementation of the BAdI must be created.
(iPad and Android Tablet ONLY) Journal Matrix View
In product audits, the parameters for the audit can be displayed in a matrix view.
iPad Only : Use the button (beside the button for Exceptions) to toggle between normal and matrix view mode.
Android Tablet Only: The journal is by default set to the matrix view mode and cannot be changed.
 Note
Journal matrix view is not supported in the standard application for iPhone and Android phone. However, in the
Android phone, this feature can be enabled using extensibility (refer to the Extensibility Customizing Guide for
Retail Execution).
Visit Contacts
A list of contacts for the Customer account are displayed in this section. The user can use the ‘+’ icon to add
further contacts to the visit. The Visit contacts and the respective contact and communication details are displayed
in this section. Notes can be created in the back-end or on the device. Marketing attributes can be assigned for the
contacts in the CRM back-end system and these can be edited on the device.
 Caution
If the user selects a contact that is local on the device, then the visit must be synchronized twice; first to
sync the contact with the backend and subsequently to sync the visit itself.
Cancelling a Visit
A menu option is available for cancelling visits. When a visit is cancelled, the status for the visit and its assigned
activities is changed to Cancelled. This status is reflected in the Activities tab screen for all the activities. This status
update is performed during synchronization and these visits and activities will no longer be available on the device.
As a result, the visit description in the schedule changes to red color indicating a cancelled visit. The status
Cancelled is also updated for all activities in a visit. The following steps are performed in the back-end systems
before a visit is cancelled:
● Flag for Cancel is set to True in SAP CRM.

● A check performed to determine if follow-up activities exist for the visit. If follow-up activities are found for a
visit, the status for the activities is also set to Cancelled. before updating the status of the visit to Cancelled.

(iOS Only) Parties Involved
In the basic details for visit, ll the partner functions in the same role to which the device user is assigned (and based
on the Customizing settings for the download profile) are displayed under 'Parties Involved'.
GPS Tagging of Visits
Global Positioning System (GPS) location services can be utilized to view Account locations and track progress of
visits. To use this feature, the GPS services on device must be enabled and in the Retail Execution IMG Activity
Define Organizational Settings, the flag for GPS Tracking Visit must be selected.
 Note
If you have implemented the logic in the method /MAC/RS_BADI_BP_FILL_GEOCODING to fill the fields
LATITUDE and LONGITUDE [Interface /MAC/RS_BADI_IF_BP in BAdI /MAC/RS_BADI_DEF_BP] to save the
geo-location attributes, then the geo-attributes (latitude and longitude) of location for each customer are
captured and stored in the back-end CRM servers and are not displayed on the device.
Execution of Tasks
Tasks can be created in the back-end systems or on the device. In the CRM back-end system, Tasks must be
created using the transaction type Tasks. On the device, new tasks can be created on the device and synchronized
with the back-end systems. Further, any existing tasks can be added to Visit and later marked complete when the
Visit is Checked-In.
 Note
In the IMG for Retail Execution, a separate transaction type is available for Tasks under Map CRM Activities to
Retail Execution Visits and Activities
Priority for Visits
Visit Priority (in addition to the Status), can be maintained in the back-end SAP CRM servers. The priority will be
displayed only if it has been maintained during visit creation.
 Note
Android edition Only : For new visits created on the device, the priority can be specified during visit creation.

Reassignment of Visits
Visits can be reassigned to other users in the same Sales organization (all employees displayed under ‘Parties
Involved’). The reassignment updates the visit with the new Employee Responsible.
 Caution
Reassignment of visits does not reassign the activities assigned to the visit.
Rescheduling for Visits
Existing visits can be rescheduled to another date. iPad Only : Apart from the menu option, Visit reschedule is
possible with the drag and drop feature in the List View (icon with three lines and a star) available in the Week View
of the schedule. Android Only : An icon on the toolbar is available for visit rescheduling.
iPhone Only : Visit reschedule possible using the menu option Reschedule Visit using the actions icon on the
toolbar or by modifying the dates. The application allows rescheduling even in scenarios where conflicting visits
exist. An alert is displayed to the device user informing that conflicting visits exist in the rescheduled time.
Trade Assets Maintenance
Following details are displayed in the Assets section
● Address
● Installed On
● Manufacturer
● Model
● Part Number
● Serial Number
● Functional Location ID and Description
● Icon for Creating Service Request
Promotion Calendar
A graphical presentation of the promotions planned for a Customer over a period of time is displayed in the tab
screen Promotions. Following details are displayed:
● Promotion ID and Type

● Available Discounts
● Attachments specific to promotions or campaigns or both
● Products, product categories and product groups

 Note
iPhone Only: Promotions are listed and not displayed in a calendar. This is due to device size constraint.
Notes
This section displays the notes created for the visit. Additional notes can be created for the visit on the device. The
last five notes created for the visit can be displayed on the device.
Attachments
Attachments created for the visit and all its activities, To Do’s, journals etc., are maintained in the Binder section in
Visit details.
Duplicate Visit
The menu option for Duplicate creates a copy of the visit with the same details for Customer, Start and End time,
Customer, Category and Reason. These details can be modified in the duplicate visit.
Creation of New Sales Orders and Returns
New sales orders and returns can be created for a Customer from the Visit screen.
Customer Contacts
Customer Account contacts are displayed in the Contacts section. The communication details for contacts can be
edited here. New contacts can be added for the Customer account of the visit.
 Caution
If contacts that are local on the device (not yet synced with the backend) are assigned to a visit, then the visit
will need to be synced twice. First to sync the contact (this generates a unique ID for the contact that is
displayed on the device). Second to sync the visit itself.

Display Customer Overview
The Customer Information section displays information such as open orders for the account, next visit scheduled
date and preferred visiting hours. It is possible to navigate to the Customer details screen from this section.
8.3.2 Activities
Activities constitute the core functions that must be performed during a visit. Few characteristics of activities in
Retail Execution are:
● In the SAP CRM back-end system, activities must be defined as Follow-up (actions) for a visit.
● On the device, the list of possible activities for a visit is determined by various text descriptions defined in the
IMG activity Map CRM Activities to Retail Execution Visits and Activities.
● Priority of an activity created in the CRM back-end system determines whether an activity is mandatory or
optional on the device. If priority is set to Very High, the activity is considered mandatory. When a visit is
completed, a valid check is performed to determine if the mandatory activities have also been completed. If
this check fails, a visit Check-Out is not allowed.
● If priority is any other value (except very high), the device user is allowed to select an activity as mandatory or
optional.
● Surveys or questionnaires can be assigned to activities.
 Note
Templates or questionnaires tagged to activities can be created in the IMG Customizing for SAP CRM and
assigned to transaction types (specific to Retail Execution). For example, for product audit or planogram
compliance specific survey templates can be assigned to these transaction types in the IMG for SAP CRM.
 Caution
To design more than three sub-sections for surveys, native HTML format must be set for surveys. To do
this, go to Preferences Questionnarire Use HTML.
● In SAP Retail Execution, the template and design have been created separately for various transaction types.
● Start and end time for activities can be recorded independent of the visits. To enable this feature, both the visit
and activity timestamps must be selected in the IMG activity Define Organizational Attributes.
● Only those activities that are not already part of the visit will be available for selection for creating activities.
● All activities can only be edited in the Check-In mode.
8.3.3 Surveys
Survey templates can be assigned to activities. The following Customizing must have been maintained in SAP CRM
IMG path SAP Customer Relationship Management Transactions Settings for Activities Questionnaires
for questionnaires:
● Define Questionnaires

● Define Determination for Questionnaires : Business Activity
 Note
(iPad Only) : Surveys with only upto three subsections are supported. To support more than three subsections,
the user must turn on the ‘Use HTML’ option in device settings in Preferences.
Since the surveys are determined for transaction types, they are displayed for each activity of the relevant
transaction type. Surveys can also be determined for a business partner group or even at the sales organization
level. SAP Retail Execution considers the following criteria for displaying surveys on device:
● Sales organization of the user

● Transaction types
 Note
Surveys must be saved and marked as Done in order to complete the activities they are assigned to.
 Caution
Offline determination of surveys using target groups: If survey determination is done using target group, then
the validity of the target group will be considered for offline determination of surveys for visits and activities. If
the checks on the validity fail, then the surveys will not be determined for the visits.
8.3.4 Activity Journals
Activity journals can only be created in the back-end CRM system. They are independent sub-objects for visits. In
SAP Retail Execution, you create activity journal templates for a template type and assign them to Follow-up
activities.
Assigning products to journal templates : Products can be added to the journal templates. These products will be
listed for the activity journals in a visit.
 Caution
If no journals are added to an activity of type Audit, then the Activity will only be displayed in the Overview tab
screen and will not be available for editing in the Activities tab screen.
Sorting Products in Product Audits
The '+' icon within a product audit can be used to sort display of products using GTIN, (iPad ONLY) Product ID,
Product Description and Category (iPhone Only).

Product Audits and Exception Reports
The device user can generate reports for any product-specific deviations observed during a visit. The criteria for
the product exceptions are maintained in the Customizing. The button for Exceptions, available in the screens for
Retail Audit and Competitor Audits, can be used to display exception reports. The report lists the exception values
as well as the Customers where the audit compliance has failed. (deviated from the exception values maintained in
the Customizing). The products and fields corresponding to the exception are highlighted.
 Note
Exceptions can only be generated in a visit Checked-In mode.
Customizing: Required Customizing can be maintained in the IMG activity Define Criteria for Product Audit
Exception Reports.
Checks Performed on Activity Journals
1. The Done button to mark the activity journal complete must be used to mark an activity journal complete. This
button determines in the back-end CRM system if the activity journal must be considered for frequency of
redetermination.
2. Mandatory activity journals are valid only for the period for which they are created. The journals existing in pre
or post validity period will not be determined for visits.
 Note
Even for a visit reschedule, only those journals existing within the reschedule date will be replicated to the
device.
3. If activity journals are determined for a frequency, the activity journals with the same frequency (and with the
same Transaction type) cannot be created for any other visits within the time frame as the specified frequency.
 Note
If mandatory activity journals with the same Transaction type are determined more than once within the
same time frame, then after synchronization, the activity journals will not be created for the visit in the
CRM back-end system.
4. An activity with a mandatory activity journal cannot be set to complete if the journal itself is not set to
complete.
5. Journal template types can be determined for a business partner hierarchy and will be replicated to the device
for all Customer accounts in the hierarchy.
6. In visits download, activity journals are replicated for the visits on the device based on the target group of the
Customer account.
7. If products having UPC or GTIN numbers are assigned to a journal, the same information will be displayed on
the device for the products listed in the journal.
8. If journals are mandatory and additionally,
○ There are no products or a product category assigned, no error will be displayed during checkout. However
it should be noted that a journal without products is not a valid business scenario.

○ The products assigned to the journals have no mandatory fields, a message will be displayed during
checkout prompting the user to fill the journal. Once the user navigates to and closes the journal, it will be
considered as filled and a subsequent checkout will be successful.
○ The products assigned have mandatory fields, then two messages will be displayed during the checkout.
The first message prompts the user to fill the mandatory journal and the second message prompts the
user to fill the mandatory fields for the products.
 Note
The journal fields have to be filled before the visit can be checked out.
9. If journals are not mandatory,

○ The checkout will proceed without any errors.
○ But if the products assigned to the journal have mandatory fields, then a red colored bar is shown on the
screen and two messages will be displayed. One message prompts the user to fill the mandatory journal
and then retry checking out. The second message prompts the user to complete the mandatory product
fields within the journal.
Mandatory Activities Displayed on Top of List of Activities
In the activities list view screen, mandatory activities and sub-activities (surveys and journals) will be displayed at
the top followed by the other activities.
Copy Previous Journal Data to Journals in a New Visit
You can copy previous journal data to a new visit provided the following criteria are fulfilled:
● The transaction type and customer of the new visit should match that of the visit from which journals are
copied.
● One of the previous visits (for this transaction type) is completed. If this criteria is not met, then the journals
data of the previous visit will not be copied to the journal of the new visit.
Offline Determination of Journals using Target Group and Business Partner

Hierarchy
The determination of journals using target group and business partner hierarchy is now enabled in offline mode
also. The validity of journals determined using target groups and business partner hierarchy (including that of the
hierarchy node for the current business partner) will be considered for offline determination of these journals on
the device. If the checks on the validity fail, then the journals will not be determined for the visits.

(iPad Only) Marking Activities as Complete
For all visit level activities, surveys and journals, auto save is enabled. Therefore, the internal status is set to
completed when user exits after completing the activity. However, all activity level surveys and journals have to be
explicitly marked as completed using the Done button.
Suggested Orders in Activities
All suggested orders for a Customer will be displayed in the Activities section of all visits for that Customer.
8.4 Customers
8.4.1 Introduction
The scenario for Customers covers all the Retail-specific characteristics that may be required to manage Account
relationships. Few important features in this scenario are listed in this section:
8.4.2 ‘Prospect’ Customer Account
A prospect Customer account can be created from the Customer landing page. The device user can maintain the
contact and communication details as well as any additional notes. The details of a prospect are only for
notification to the backend and the prospect does not appear in the list after a synchronization is performed with
the backend.
 Note
The required Customizing must be maintained in the Retail Execution IMG activity Maintain Client Device
Settings for Customers.
8.4.3 Marketing (Campaigns and Promotions)
Marketing Project (Promotions and Campaigns)
In the Promotions tab screen, the promotion details are displayed. These include Promotion ID, Products (and
respective categories) for which the promotion is valid, discounts for the products in the promotion and the start
and end dates or promotion.

For a Customer account, marketing promotions can be created in the CRM back-end system and products
assigned to these promotions. The products can be assigned at the individual Product level or for a Category or
Target group. Additionally, attachments can also be created for these promotions. This information is displayed in
the promotion calendar in the tab screen for Promotions. Note that information relating to promotions can only be
displayed and cannot be modified on the device.
Customizing : In the IMG activity Define Product Proposal, the marketing project types (campaigns or trade
promotions or even both) must be selected that are required for defining marketing activities.
Short Term Proposals : SAP Retail Execution considers only short term marketing projects for download to the
device. Marketing projects are considered short term If in the CRM Customizing for condition generation types, no
details are maintained for the assignment of condition generation type to the Campaign Determination Condition
Type.
Marketing Attributes
The marketing attribute sets created in the SAP CRM back-end systems are displayed on the device. In the Edit
mode, the values for the attribute sets can be updated. Marketing attributes can be maintained for Customer
accounts as well as for contacts within accounts.
Customizing : Marketing attributes (in SAP CRM) are created to capture marketing specific information for
business partners. In the IMG for Retail Execution, following settings must be defined for marketing data to be
replicated to the device:
● Define Account and Contact (marketing) attribute sets and assign them to attribute profiles in the IMG Activity
Define Data Selection Criteria.
● Assign these Attribute Set Profiles to Account download profiles in the IMG activity Assign Selection Criteria to
Download Profiles.
 Note
Eventually, the account download profile assignment to Sales Organization will determine the available
marketing attribute sets at the organizational level.
 Caution
For surveys created using marketing attributes, you can specify if the attribute type is Person or Organization.
However, the marketing attributes will be updated only if the attribute type of the marketing attribute is the
same as that of the activity partner. For example, if you choose to add a marketing attribute of type
Organization, then the marketing attribute will be updated only if the activity partner (in the activity) is of type
Organization.
Identify Customer Trade Promotions Using Target Groups
Trade promotions are usually defined for a single customer, a target group or for a customer hierarchy. Therefore,
when a search is performed for the Customer’s trade promotions, target groups will be scanned to display the valid
Trade Promotions (TPMs) on the device.

Customizing : The required target groups must be created in the IMG Customizing for SAP CRM and relevant
Customers assigned to these target groups.
Promotion Calendar
A graphical presentation of the promotions planned for a Customer over a period of time, is shown in the tab screen
Promotions. The following details are displayed in the promotion calendar:
● Promotion ID and Type

● Available Discounts
● Attachments specific to promotions
● Products, product categories and product groups
Customizing : In the IMG Customizing activity Define Settings for Trade Assets Maintenance , following settings can
be defined :
● Set the flag for Functional location active If trade assets are maintained at the customer location.
● Select the equipment category to which the trade assets may belong.
● Service request types that can be used to create service requests for the trade assets.
 Note
iPhone Only : Promotions are only listed and not displayed in a calendar. This due to device size constraints.
Notes
The notes added for promotions in the backend system will be displayed on the device.
8.4.4 (iPad ONLY) Customer Groups
Customer groups feature enables users to group customers based on specific criteria such as favorite customers,
platinum customers, etc. Users can use these groups in the week view to drag and drop customers and create a
visit or even navigate to the Customer overview page.
 Note
The filters functionality for Customer Groups is supported using filter criteria defined in the backed CRM
Customizing (IMG activity : Define Filters for Business Partners). This should not be confused with filters feature
available in the device object list page for respective objects which is supported with UI defined standard filter
criteria shipped with the standard application.

Customizing Required in Backend CRM for Customer Groups:
In the IMG activity Define Filters for Business Partners, you can define the following:
1. Define filters and maintain required Customizing values for each filter.
 Note
You can define multiple filters for each supported MBO.
 Caution
Filters (supported from backend) is only supported for Business Partners. Even for Business Partners, the
feature is applicable only for the following MBO’s:
○ BusinessPartnerAddressMBO
○ BusinessPartnerClassificationMBO
○ BusinessPartnerMarketingAttributeMBO
○ BusinessPartnerMBO
2. Define Multiple Filter Profiles but only one filter profile can be set to Active.
3. Assign the active filter profile to a sales organizational unit.
Define Filters and maintain the following relevant values for each filter:
Customizing Field Entry Notes
Value Key Any text or numeric entry
MBO Name Only the following MBO’s are supported

for filters:
● BusinessPartnerAddressMBO
● BusinessPartnerMarketingAttribu
teMBO
● BusinessPartnerMBO
Filtering Field Filtering Field that can be selected using Filtering Field that can be selected using
F4 help on the field F4 help on the field
FilterGroup ID Any random number

 Caution
Marketing Attributes MBO : Each
marketing attribute set will must
have two customizing row entries,
One for Attribute and other for corre
sponding Attribute set. Both the fil-
tering fields (for attribute set and at
tribute name) should have the SAME
filtering group ID

Filtering Field Description Description associated with the filtering
field is defaulted here
Option Select an option based on filter value
Low Value Low value must be specified for the “OP

 Example
TIONS’ that you specify for filtering val
● MBO : BusinessPartnerMBO
ues.
● Filtering Field : City
● Option : Equal Low Value : Delhi
 Example
● MBO : MarketingAttributesMBO
● Filtering Field : ATTRIBUTE_SET
● Option : Equal
● Low Value : Technical key of the
marketing attribute set
High Value Specify the higher limit if you have se

lected ‘OPTION’ that specifies a range of
filtering values (such as ‘Between’).
8.4.5 Customer Accounts Classification
Classification
Classification attributes include values such as the sales organization, division, channel, etc. Both criteria and
attributes are displayed in the application. The account classifications are set as filters to retrieve a required set of
Customers.
 Note
In Retail Execution, account categories can be grouped into a single Account Classification Profile, that can be
used for maintaining attributes and criteria for a large set of Customers.
Customizing : The following Customizing settings need to be maintained for this feature:
1. In the IMG for SAP CRM, Define account classification categories and assign classification attributes and
criteria to the categories in the following IMG path SAP CRM Master Data Business Partner Define
Account Classification
2. In the Retail Execution IMG activity Define Data Selection Criteria, account classification profiles can be defined
and the classification categories defined in SAP CRM be assigned to these profiles. Multiple categories can be
grouped in a single classification profile.
3. Finally, In the IMG activity Assign Data Selection Criteria to Download Profiles, account classification profiles
must be assigned to download profiles for accounts. This assignment determines the account classifications
available for a Customer account.

iPad Only : Account Groups (Favorite Customers)
The logic on Filters has been used to enable this feature in Retail Execution. The device user can create various
Customer groups for criteria other than the standard filters for Customer Accounts (Near Me, Visits Planned and
Marketing Attributes).
 Note
The Customer account groups appear for selection under 'Customers' in the calendar Week view / Split View
(icon beside the Today button on the right hand side of the screen).
8.4.6 Other Features
Geocode Feature : 'Near Me'
In Retail Execution, geocodes are used for locating drop pins (for Customer locations) on map and also for locating
the Customers 'Near Me' feature. 'Near Me' defines the radius that must be considered to retrieve the list of
Customer accounts within that radius. It is used as a filter to select a set of Customers.
iOS Only : From Retail Execution 3.0.16 (patch release) onwards, Apple Maps are used to implement the 'Near Me'
and 'Drop Pins' features ; no separate implementation and configurations are required.
 Caution
The Client device will use Apple maps ONLY IF Customizing for geocodes is NOT defined or defined as
Zero.
Android Only : The standard system for Retail Execution provides a default implementation for BAdI
method /MAC/RS_BAdI_BP_FILL_GEOCODING in the Business Add-In implementation /MAC/RS_BAdI_DEF_BP.
Additionally, you need to define the required settings for geocode server. Refer to the Appendix for details on how
to define the Geocode settings.
Account Factsheet
The Generate Factsheet menu item is available in the Customer account overview. Factsheet can be generated only
if device is in an online mode. The generated fact sheet will be displayed as an attachment in the Binder tab screen.
 Note
The pdf factsheet is different for the different user roles in SAP CRM; Therefore, to ensure that the user has
access to the account factsheet on the device, users must be assigned to specific roles in the Organizational
model using transaction PPOMA_SAP CRM.
The factsheet is generated at runtime using an RFC enabled API.: /MAC/RSFM_BUPA_GEN_FACTSHEET

 Caution
Each time the user triggers factsheet generation for a single Customer, all the factsheets generated in the
past will be refreshed and generated again.
Asset Maintenance
If trade asset details are maintained for a Customer in the ERP back-end systems, the same will be displayed in the
Assets section. The details that are displayed include the Asset ID and address, asset type, Installation details,
manufacturer details, and model number. If Service requests exist, the relevant details (Asset/Equipment for which
the service request is created, the functional location id and address) will be displayed.
 Note
If the flag for Functional Location Active is set in the Customizing, then the trade assets available at the
specified functional location will be downloaded for the Customer. If this flag is not set, then all the trade assets
for the Customer will be downloaded to the device.
Service Request Type for Trade Asset — A menu option is available to create service requests for existing trade
assets.
Dashboard : Account Analytics
The graphs and pie charts based on queries defined in SAP Business Warehouse are displayed in the Analytics tab
screen.
Customizing
1. The relevant queries for the analytics must be defined in SAP Business Warehouse.
2. A reference to these queries and other relevant settings must be defined in the IMG activity Define Dashboard
Settings.
iPad Only : Alerts in Customer Overview
The alerts issued for the Customer account are displayed in red color.

Binder for Attachments
In order to display the required attachments for a Customer account, the following Customizing settings must be
defined:
1. In the IMG activity Define Data Selection Criteria, the business partner hierarchy level profiles can be defined. It
is important to maintain the hierarchy level of the folder from where a search is executed for retrieving
attachments.
 Note
The hierarchy level will be traversed bottom up considering the top node as level Zero.
2. In the IMG activity : Assign Selection Criteria to Download Profiles, the attachment BP hierarchy level extraction
profile must be assigned to the default account download profile.
 Caution
(iOS Only) Logo Size : The size of each Customer account logo must not exceed 3 KB.
(iOS Only) Logo Dimension : A standard size 32 X 32 is recommended for Customer logos. If the image size
being uploaded is smaller or larger than the recommended size, then the image will be adjusted to fit the
recommended size.
8.4.7 Contact and Communication Details
 Note
In the device, Retail Execution supports 3 types of partner function and for which the partner function category
is hardcoded in the application business login. The three partner functions are Activity partner, Contact and
partner functions for ‘My Team’. Therefore, IMG Customizing for partner function extraction profiles must be
one of the above mentioned partner function types.
● Activity partner: All accounts downloaded to device are available for selection.
● Contact : Relationship category displayed in the device.
● Account Team :
For Contacts, the relationship category is displayed on the device. For Activity Partner and Account Team, the
partner functions will be displayed as selection values for 'My Team'.
(iOS Only) Account Team
The employees belonging to the sales organization of the device user and displayed as ‘Parties Involved’ in the Visit
will be displayed as ‘Account Team’ in the Customer landing screen.

Communication Details
The Customer communication details (phone number and E-mail ID) can be updated on the device.
Contacts
New contacts can be created and even notes can be maintained for each contact. Further, images can be attached
to the contacts in the back-end system that will be displayed for the contact on device.
 Caution
If a new contact has been created on the device and assigned to a visit, then the user is expected to sync
twice; first sync is used to sync the contact and the second to sync the visit itself.
Contact Function
An additional selection field is available to add a new function to a contact. You can add two functions for a contact
in Retail Execution. The list of values for the field will come from Customizing maintained in the backend system.
Business Hours
If the preferred visiting hours for a Customer account are maintained in the SAP CRM back-end system, the same
will be displayed on the device.
8.5 Products
8.5.1 Introduction
The products list screen displays a list of products with their IDs, description and GTIN numbers. In Retail
Execution, master data for products is only available for display and cannot be edited. Following sets of data are
displayed for Products:
Product Classification
Products can be classified (as in SAP CRM) as categories and brands. In the product details screen, these appear in
the section Sales Categories.

Customizing The following settings Customizing in the IMG for Retail Execution :
● In the IMG activity Define Download Profiles, product hierarchy profiles must be defined and hierarchy levels of
products be assigned to these profiles.
● In the IMG activity Assign Download Profiles to Bus. Objects and Sales Org, the product hierarchy profiles must
be assigned to product download profiles. These settings will determine the product hierarchy levels that must
be considered for display on the device.
Product Identification Attributes
This feature can be used in scenarios where the identity of products needs to be highlighted, for example in
scenarios for promotions and campaigns.
Online Search for Products
If a search for products is initiated when the device is in online mode, the search is first initiated on all products on
the device, irrespective of the Customer account. If the device search does not yield the results, then the 'Search on
Server' option is displayed. The device user can tap on this option to trigger an online search on the back-end
system to retrieve products and their master data.
 Note
Products displayed must belong to the sales organization of the device user.
Search for Products using Bar Code
Barcode of a product can be scanned to search for the product in the products list.
Product Filters
Product search can be filtered based on the following criteria:
● Listing (based on Customer-Product relationship defined in the SAP CRM back-end system).
● Category (sub-category or brand of products)
● Marketing Attributes (values specific to a single or a set of products).
Customizing : The following settings must be defined for filtering and classifying products:
● In the IMG activity Assign Download Profiles to Bus. Objects, maintain the product hierarchy level profiles that
must be considered for downloading product master data to the device.
● In the IMG activity Define Data Selection Criteria, define product attribute set profiles and assign product
attribute sets to the profiles.

● In the last step, assign the product attribute set profiles to product download profiles.
Extended Criteria for Product Downloads
Products can be downloaded by sales organization, territory or listing.
Customizing: In the sub node IMG Customizing activity : Assign Download Profiles to Bus. Objects and Sales Org,
the appropriate value (download products by sales organization, listing or territory) can be specified.
Product Attachments
Images (for Product identification) and Media files (for product promotions) can be created in the CRM back-end
server and displayed on the device.
Synchronization of Product Attachments : If initial synchronization for attachments is interrupted, then product
attachments waiting to be synchronized will be processed in queue and considered for synchronization when an
on-demand synchronization is performed for one or more products attachments.
Customizing : The relevant attachment types profiles must be defined and further assigned to the product
download profile.
 Note
Product Images : The products list screen also displays the image of a product next to the identification if an
image has been set as default in the backend system. In Retail Execution, for replication to device, the flag
PRD_DEF_IMG (in the structure ET_PRDS_IMG in API : /MAC/RSFM_GET_PROD_DETAILS) is set if default image
is available. To enable this setting, the following criteria are considered:
In the Documents tab screen for a product, right click on the document/image and then click on Properties. In
the dialog box that appears:
● In the Properties tab screen, if Default Document is set to Yes

● In the Log.Doc.Properties tab screen, if the Document type is set to BDS_IMAGE (the attachment is an
image)
Product Images (Android Only) : To be considered as a default image, an image must be saved as an
attachment for the product with the naming convention PRDIMG_xyz.xyz where XYZ.XYZ represents the
image name and extension type.
Notes for Products
The single / multi-line texts maintained for products in the back-end are displayed (no edit possible) for the
product. In the SAP CRM back-end, following types of notes can be maintained for products:
● Basic Text
● Inspection Text

● Internal Note
Customizing : The relevant attachment types must be defined for downloading notes and these must be assigned
to the selected product download profiles.
8.6 Sales Orders
8.6.1 Introduction
 Note
REX supports sales documents only for the following categories: SALES_ORDER_CATEG0RY - 'C' and
RETURNS_CATEGORY - 'H'. BADI implementation can be created . Sales orders must be created only for
these categories
Sales orders can be created in both SAP CRM and SAP ERP backend systems or on the device. SAP Retail
Execution supports product price calculations both in the online and offline mode. The Sold-To, Ship-To and Order
Type, Pricing Date and Request Date are required to create a sales order.
 Note
After synchronization, the sales orders created on device will be routed to SAP ERP system via SAP CRM
system using the RFC destination maintained in the IMG activity Maintain Device Settings.
 Note
When a sales order is being created, the global access menu will be disabled (irrespective of whether order
confirmation is required or not using signature capture), and the user can access global access menu only after
confirming the sales order. Therefore, the user can either Save or Cancel the order to exit. This is because it is
not advisable to save an interim sales order and move to global access menu
8.6.2 Key Features
Selection of Products
Products can be selected using one of the following five options:
● Quick Order (iOS Only)

● Past Orders
● TopnList
● My Proposals
● Search for products
● Scan bar code of products

Item Category Selection for Product Items
A new field for Item category is now available for item selection in sales orders. You can select a valid item category
for an item from the list displayed in the selection field. Change an item category only if you need to change the
category determination from the backend system. If no item category selection is made in the device, the item
category determination from the backend system will be valid.
Configuration: Note that you must have enabled the flag for Enable Changing Item Category in Sales Order under
Transaction SPRO (SAP Reference Implementation Guide for CRM) Customer Relationship Management SAP
Retail Execution Sales Orders Maintain Client Device Settings for Sales Orders Settings for Order Creation .
 Note
The valid item categories for a transaction type are maintained under Transaction SPRO (SAP Reference
Implementation Guide for CRM) Customer Relationship Management Transactions Basic Settings Define
Item Category Determination Retail Execution selects the following values for this Customizing: Transaction
Type, Item Category Group and Item Category.
If Alternate Item Category values are maintained in the above Customizing, they are also downloaded to the
device. The Item Category field on the device will display all allowed item categories in the selection field help.
The user can select any of these values as the item category.
iPhone ONLY: You can also enable search for order items using item category. You must select the field
ItemCategory under Preferences Search Settings Items Item Category . Note that in iPad, no such setting
is available in the Search Settings. However, if the required Customizing is maintained in Retail Execution, the field
for item category will be displayed in sales orders.
Online Product Search
If the device is online, then an online product search can be triggered to add products to sales orders. The search
initially runs on all products on the device (irrespective of the Customer account). If search on device does not yield
any results, the 'Search on Server' option is displayed. The device user can tap on this option to perform an online
search and download the required products and their master data.
 Note
Products displayed must belong to the sales organizational unit of the device user.
Replacement Product
The descriptions for a replacement product will be displayed in sales order after an order is synced (if they have not
already been downloaded during the product master data download). Note that the mapping for substitute
products must have been maintained in the base customizing activity in SAP ERP system and transported to the
SAP CRM system.

 Note
item level details for substitute products are displayed in the sales order. However, the product master data for
substitute products is not displayed in Retail Execution.
Online Scenario for Price and Discount Calculations
 Note
Sales order item discounts can be of the following three types namely A (Percentage based), B (Value based)
and C (Discount/UoM based). Note that all three discount types are supported on device for online price
calculation. However, for offline price calculation, only type C (Discount/UoM based) is considered.
The Online calculations in the ERP system consider the following Customizing settings in the ERP system.
1. Pricing procedures defined in the IMG activity Define Data Selection Criteria.
2. Price calculation relevant settings in the IMG activity Define Organizational Attributes.
The price and discount calculations are as follows:
● First step involves the condition type determination using the Customizing setting in the IMG activity Define
Organizational Attributes. Amongst the two manual condition types, one can be maintained in percentage.
terms and another in actual terms. (both condition types cannot be maintained in the same value terms).
● Second step involves summation of the online discounts (originally available for the selected products) and the
manual discounts maintained on the device (condition type 1 and condition type 2).
Header and Order Level Summary View
On Finalize and confirmation of the sales order, the confirmed sales order displays the following details:
Sales Order : Header Level Summary: Lists the default price profiles and their respective values:
● Gross Price
● Net Price
● Surcharge
● Discount
● Tax amount
Sales Order : Item Level Summary lists the following details:
● Discount prices (per unit of measure) calculated and displayed for the sales order.
● Total net price
● If the icon for Delivery Schedule is in Blue Color, a tap on the icon displays quantity available and expected date
of delivery
● If the icon for Delivery Schedule is in Grey Color, it implies that the products are not available for delivery.

Item Proposal
An item proposal can be created on the device or in the SAP ERP back-end system. Item proposal details include
material, quantity and header details including validity period. For replication to the device, the validity of item
proposal must lie within the validity of sales order.
Following checks are determined for item proposals:
● If no validity is maintained for the item proposals, all proposals for the device user will be displayed in My
Proposals.
● If validity is maintained for the item proposals, all proposals that are valid as on the sales order created date will
appear for selection in My Proposals.
Item Statuses
In addition to the Order header statuses (Overall Status, Rejection Status and Delivery Status), item level statuses
such as Delivery Status and Overall Status are displayed in the sales order.
Two Manual Discounts Per Sales Organization
In addition to the standard discounts maintained for the products, the device user is allowed to maintain two
manual discounts (one each in percentage and value terms). Note that both the discounts cannot be maintained in
absolute percentage or absolute value terms.
Customizing : In the ERP IMG Customizing for sales organization (IMG Activity : Define Settings at Organizational
Level, you must specify item manual condition type 1 and 2 (both percentage and actual values are permitted on
both conditions).
iPad Only : Quick Order
This feature can be used to quickly create a sales order if the required product ID's are known to the user.
Purchase Order Number
A free text field is provided for Purchase Order in the sales order header section. This field can be modified both on
the device as well as in the backend system and the updates will be visible after a delta sync is performed.

Delivery Schedule
The delivery schedule of sales orders can now be downloaded and viewed on device. If the delivery schedule is
available, the icon will appear in blue and a tap on this icon displays the expected delivery date and number of items
available.
 Note
The delivery schedule is displayed only when delivery of items is not possible in a single shipment.
Requested Date
The requested delivery date is displayed in the sales order header section.
iOS ONLY: In iOS devices, you can enable search for sales orders using the requested date. To do this, you must
select the field Requested Date under device Settings Preferences Search Settings Sales Orders
Replacement Product
he descriptions for a replacement product will be displayed in sales order after an order is synced (if they have not
already been downloaded during the product master data download). Note that the mapping for substitute
products must have been maintained in the base customizing activity in SAP ERP system and transported to the
SAP CRM system.
 Note
The item level details for substitute products are displayed in the sales order. However, the product master data
for substitute products is not displayed in Retail Execution.
Signature Capture
This feature for sales orders can be enabled or disabled on the device.
 Note
When a sales order is being created, the global access menu will be disabled (irrespective of whether order
confirmation is required or not using signature capture), and the user can access global access menu only after
confirming the sales order. Therefore, the user can either Save or Cancel the order to exit. This is because it is
not advisable to save an interim sales order and move to global access menu.

Attachments
Attachments can be created for sales orders. Most importantly, the signature captured on sales order confirmation
also appears as an attachment in the relevant tab screen for attachments.
Notes
Notes can be maintained for sales orders using Customized note types. For each sales order, one note type can
only be used once for creating a note.
 Caution
For sales orders created in the back-end system:
● Notes created from the Header Menu using the path GoTo Header Texts will be replicated to the
device and shown for sales orders on the device.
● Notes created using the icon Services for Object (on the menu bar) will NOT be replicated to the device
and will hence NOT be shown for sales orders on the device.
Duplicate Sales Order
When the menu option Duplicate is used, a copy of the existing sales order template is created. The new sales order
will be created for the same Sold-To user as in the original order.
Cancel Order
The Cancel Order menu option is available if the user, at any point of time, wishes to cancel the sales order. The
status of the sales order on the device will be set to Completed. In the sales orders list, an additional comment
Nothing Rejected is displayed for the order. The updated order status will also be reflected in the ERP system after a
sync is performed.
 Caution
A sales order can be canceled only if :
1. It exists only on the deivce and has not been synced with the backend.
2. Synced but failed to get created in the backend due to a sync error.
Print
The menu option for print can be used to print the sales order document.

Customizing : The relevant MIME folders must be created and the print templates stored in these folders. In the
IMG activity Maintain Print Settings, the location of the mime folders and templates must be maintained.
E-mail
The device user can use the E-mail option to promptly send the sales order document created in the visit location,
for processing in the back office.
8.6.3 Offline Scenario
Price List
Retail Execution uses the SAP CRM price list feature for calculating the offline prices on device. The price list can be
maintained with the list of prices for a value pair of Product-Customer..
 Note
The table for price list is created on the device during initial sync. In the Customizing for Offline Pricing
Conditions, if the Price List option is set, then the price list is updated in the table and used for offline price
calculations.
Discount Calculation in Offline Mode
 Caution
and C (Discount/UoM based). For offline price calculation, only type C (Discount/UoM based) is considered
but all three discount types are supported on device for online price calculation.
When simulating an order in an offline mode, the discounts that must be considered will depend on the
Customizing defined in the IMG activity : Maintain Conditions for Offline Pricing. in the CRM back-end system.
Customizing : Maintain the required settings in the IMG Activity : Maintain Conditions for Offline Pricing
Retail Execution supports the offline pricing scenarios for the following price types:
● Condition Type : If this pricing type is selected, the following values can be maintained:
○ Base Price condition and Value or the condition table
○ Discount condition and Discount condition table
● Price List Type: If this pricing type is selected, the following values can be maintained :
○ Price list type
○ Value for Price

○ Value for Discount
 Note
The relevant Customizing for pricing procedures must have already been defined in the SAP CRM specific
Customizing settings.
Price Simulation
Price simulation is allowed only if the flag for Simulation Req is set in the ERP MG activity : Define Organizational
Attributes.
 Caution
Exceptions Occurring during Sales Order Simulation:
Exceptions reported during sales order simulation will be displayed on the device. The exceptions will be
displayed until the time the sales order simulation is complete.
Calculation for and Display of Free Goods
Free goods for a product can only be created in the SAP ERP back-end systems. For example, some products
selected during sales order creation may be associated with marketing promotions and may have free goods
associated with them. In the products list, the free goods created are displayed in a different color. When the price
simulation happens, the value of the free goods is considered using one of the following approaches:
● Inclusive
The price of the free goods will be deducted from the net price and shown on the device. An indicator is marked
for the net price to show that free goods calculations have been considered.
● Exclusive
A separate line item is created and relevant calculations are displayed for the free goods.
8.6.4 Product Proposals
Product proposals can be created in the CRM backend system and displayed on the device for selection. The
product proposals created in the back-end servers can be assigned to an individual Customer account or to a
customer segment.
Retail Execution supports the following method schema for selecting products :
● TopnList
● Marketing Projects (Campaigns and Promotions)
● Custom Schema

 Note
The standard system for Retail Execution supports only the scenarios for short-term promotions with a status
set to Released.
Short Term Proposals Only short-term proposals are considered for download to device. Proposals are
considered short term if, for a given condition generation type, no details are maintained in the assignment of
the Condition generation type to Campaign Determination Condition Types. All proposals that meet the above
mentioned criteria will be downloaded to the device.
Customizing
1. Define Product Proposals in the IMG for SAP CRM

2. In Retail Execution IMG Activity : Define Product Proposal, define the following settings:
1. Assign the required method schema and set the ones that you require as Default.
2. Assign the method schema to Sales Organization and specify the marketing project type (Campaign or
Promotions) valid for these schema.
8.7 Returns
This section covers the scenario of product returns that a sales representative may encounter during retail visits.
The Return Type, Reason for Return, Created Date and Sold-To can be maintained for a return.
The following features are possible for returns:
● Create new returns and confirm the same.

Signature capture is required on confirmation of a return (if the ‘Signature Req’ flag is set in the Customizing).
The captured signature is stored as an attachment for the return.
● Add products using search or barcode functions
For each product return that is created, the relevant unit of measure and quantity can also be specified.
● Create notes
● Display attachments
● Print a Return
● E-mail the return template.
8.8 Dashboard (Account and Employee)
8.8.1 Introduction
The dashboard for analytics displays the graphs and pie-charts for queries defined in the SAP Business Warehouse
system. The analytics feature is available for Account and Employee Responsible.
The queries will be displayed on the device based on the sales organization of the user. Four chart types (bar chart,
pie chart, column chart and line chart) are supported for each query. It is possible to define the default chart type

for each query in the Customizing for the query in the BW. When Synchronization is performed on the device, these
settings for the queries will be used to download the BW content for the queries. The chart can be zoomed on the
device. It is possible to send the charts by E-mail.
 Caution
Only One simple BW query with one characteristic and multiple key figures is supported for SAP Retail
Execution.
Implementing Dashboard Analytics in Retail Execution
The dashboard display in Retail Execution requires the following configuration:
1. Define the required query and info provider in the BI system.

2. Establish connections (remote function calls or RFC connections) between BI system and SAP CRM system
3. Retrieve the BI info provider and query details to SAP CRM system
4. In the Customizing, maintain the configurations required to connect the query to the dashboard display in
Retail Execution.
Define the InfoProvider and Query in the BW System
In the BI system, define the following for the Retail Execution dashboard:
1. InfoProvider
2. BI query
 Note
The query ID that you define must be in the format 0CRMBPKPI/ZCRMBPKPI_Q002 where the first part
0CRMBPKPI represents the InfoProvider and the latter part ZCRMBPKPI_Q002 represents the query ID For
detailed information, see the documentation for SAP Business Warehouse.
Define RFC Connection in SAP CRM system
Go to transaction SM59 and choose HTTP Connection to External Server to maintain a remote functional call (RFC)
connection with BI system.
Execute the BI Query in SAP CRM System
1. Go to transaction RSRT1
2. Enter the query ID that you have defined for dashboard in Retail Execution.
3. Execute the query
The details of the query are retrieved in the CRM system. Run the following function modules to verify if the
requested BI data has been retrieved in the SAP CRM system:
○ For General BI query - /MAC/RSFM_GET_BI_QUERY_RESULTS
○ For Customer Specific BI Query -- /MAC/RSFM_GET_BI_QUERY_RES_CUS
○ For Query Filter -- /MAC/RSFM_SET_BI_QUERY_FILTER
4.
Define Configuration Settings in Retail Execution Customizing

Define the required configuration in Retail Execution under Transaction SPRO (SAP Implementation Guide
Reference IMG for CRM) Customer Relationship Management SAP Retail Execution Mob App Define
Dashboard Settings .
1. RFC Destination : Specify the RFC destination to the BI system that you have defined in transaction SM59
2. Define Filter Value : Specify the filter values that you have used to maintain the query in the BI system,
3. BI Query
1. Specify the query details such as ID, name and description, ID of the info provider to which the query is
assigned and the type of chart to be displayed in the dashboard
2. Maintain the mapping (for each query) between the query filter defined in BW system and the one that you
have maintained in Retail Execution Customizing step Define Dashboard Settings Define Filter
Values .
 Caution
The order of the filter values that you maintain in this step must be the same as maintained in the BW
system.
4. Activate Queries for Sales Org:

Specify the mapping between Query ID and sales organization. This mapping will determine the query that will
allowed for a user. You can therefore define various queries in BI system for different dashboard requirements
of multiple sales organizations in your system. In this step, you can assign the queries to the relevant sales
organizations.
5. Define Account Dashboard per Sales Org
For customer account analytics, assign the relevant queries to the sales organizations. This assignment will
determine the dashboard bar charts and graphs for customer analytics.
8.9 Other Allied Features
8.9.1 (Android Only): Lazy Load List for All Objects
When displaying the list of objects for Visits, Customers, Sales Orders, Returns and Products (all objects in the
master list except the Schedule), the lazy load list ensures that only the first twenty objects are loaded and
displayed in the list. As the user scrolls further down in the screen, the remaining objects are loaded and displayed
in the list.
 Note
A new tag NumberofRecordsForLazyLoad has been included in the demo UI configuration XML file. For
detailed information on the lazy load configuration, refer to the Extensibility Guide for SAP Retail Execution. By
default 25 records will be considered as default # of record. User can maintain any valid integer value between
25 to 500. 25 will be considered If value is <=25. 500 will be considered if value is >= 500. If user maintain non
integer value or not maintained at all then default value(25) will be considered.

8.9.2 Print Function
The print function is possible for the following Retail Execution business objects. Note that the required
customizing must be maintained in the customizing activity 'Define Print Settings.. For more information, refer to
the documentation for this IMG activity Define Print Settings.
● (Android Only) Calendar (Day View)

● Sales Orders
● Returns
Print Template
You can add the following fields using the print template:
● doc_number,doc_type ,doc_date
● soldTo, shipTo, soldToID
● gross_value, discount, net_value, surcharge, tax_amount, total, currency
● req_date_h, price_date, overall_status, delivery_status, rejection_status, ord_reason
It is also possible to add partner function fields using the print template. To do this, the required fields must be
maintained in the print template as described in the example below:
<h1 align = "center"> Partner Details <h1> <table border="1" align="center"> <tr bgcolor="#9acd32"> <th>Partner
ID</th>
<th>Partner Name</th> <th>Partner Function</th> <th>Partner Address</th> </tr> <xsl:for-each

select="data/partner_Details">
<tr> <td> <xsl:value-of select="partner_ID"/> </td> <td> <xsl:value-of select="partner_name"/> </td>
<td> <xsl:value-of select="partner_function"/></td>
<td><xsl:value-of select="partner_address"/></td> </tr> </xsl:for-each>/xsl:for-each></table>
 Caution
Irrespective of whether default templates (provided in the Standard System) or Customer designed templates
are used for the print function, the path to the folders in the MIME repository must be MANUALLY maintained
in the Customizing activity Define Print Settings
8.9.3 Preferences
The client side preference settings for the application can be defined in Preferences
● General

Settings for sending error logs (including maximum size for log file). Other options in this section include
Change Password and alert for visits.
 Caution
It is recommended to change the Password in Online mode when the device is connected with the back-end
systems. The password can be changed when the device is Offline as well. However, if this change is not
reflected in the login credentials of the SAP back-end systems, synchronization with the back-end systems
will fail.
● Synchronization
Synchronization on/off switches for various entities such as products, visits, Customizing, sales documents,
customers, etc.
● Search
Search settings for Customer, Products and (iOS Only) : Promotions and Trade Assets.
● Attachments
Time frame for downloading attachments to the device and the number of on demand attachments that are
permissible on device.
● Calendar
Settings to display personal settings on the Retail Execution schedule and visits on device calendar.
● Password Change
The password from the SAP CRM back-end login credentials can be changed. The password must however first
be changed on the CRM Server before changing it on the device.
● Unsubscribe
Unsubscribes the user from the application and deletes all local data on the device. To re-login, a new user
must be created in the SMP server.
● iOS Only : Questionnaire
Format in which questionnaires are to be displayed. If you set HTML to ON, the surveys will be displayed in html
format. You can turn off this switch if you want native formats to be used for displaying surveys and
questionnaires.
8.9.4 Attachments
It is possible to maintain a hierarchy structure for folders to maintain attachments in the CRM back-end system.
The folder structure can include a hierarchy of substructures. When the attachments are downloaded to the device,
the complete hierarchy is not considered for the download. Only the immediate parent folder will be considered
during data download. This function ensures that separate folders can be maintained for attachments belonging to
different business objects.
 Caution
(iOS Only) : The size of attachments for Customer accounts logos must not exceed 3KB. Further, for
performance considerations, size of a single attachment must not exceed 7.5 — 10 MB.
(iPad Only) : The recommended dimension of a Customer account logo is 32 x 32. If the dimension of the
image being uploaded is smaller or larger than the recommended size, then the image will be adjusted to
fit the recommended size).
(Android Only) : For performance reasons, the size of image attachments must not exceed 3 MB and the
size of text attachments must not exceed 32KB.

Attachments for Customer Account
For Customer account attachments, it is possible to maintain the hierarchy level from which a search must be
performed for retrieving attachments and downloading them to device.
 Note
If in the device Preferences, the 'Download attachments' is set to 'Today' and no visits are scheduled for
today, then no attachments will be downloaded to the device after a sync. However, Customer LOGO and
photos of Contacts will be downloaded
Use of Attachment Types : Every attachment created in SAP Retail Execution will be assigned to an attachment
type in order to identify the usage of the attachment in the application. The following attachment types are
provided in the standard system for Retail Execution: Attachment Type Usage FLOORPLAN Identifies the image to
be a floorplan image. PLANOGRAM Identifies the image to be a planogram. PHOTO Identifies the image to be a
photo. LOGO Identifies the image to be a logo. PROMO Identifies the image to be a promo
BP Hierarchy for Attachments Download
Attachments will be downloaded only for the Business Partner whose node level is maintained in the Customizing
and until the hierarchy level maintained in the Customizing. Further, for the node levels maintained, the
attachments will be downloaded for the BP only if the BP is part of Pricing hierarchy downloaded from backend
system. To download attachments of BP's that are at higher hierarchy level than the level maintained in the
Customizing, BADI implementation has to be done.
8.9.5 Alerts
iPad Only : A red button in the bottom navigation bar in the application displays the alerts and messages that have
been pushed to the device user using data change notification (DCN).
iPhone Only An icon on the toolbar in the application menu displays the landing page for Alerts and Messages.
Android Only: 'Alerts' and 'Messages' are two separate options in the application menu.
 Note
For more information on how to set-up alerts, refer to the relevant IMG Customizing (CRM system) and the
configuration using DCN.

9 Troubleshooting
Business and technical errors are displayed under Messages. For business errors, you can navigate to the relevant
business object and make required corrections. Click on a business error to navigate to the business object for
which the error was reported.
Error Source Solution
Command to tRFC/ This error can appear in any one of the following Contact your Basis team to fix the connection is
qRFC: Execute LUW scenarios: sues with SMP or to modify the details for commu
again nication channels.
● When executing the alert generation report
● Initial sync run from backend to SMP For initial or delta sync, the system will retry to
● Delta sync run from backend to SMP sync with SMP after the predetermined time set in
SMP. If the connection issues are resolved by then,
Cause
the sync (initial or delta) will go through success
A network or connection problem has occurred in fully. However, if the issue is not resolved, the sys
SMP. View the details of the error in the SLG1 logs tem will keep trying after each gap of the predeter
(for issues with initial and delta sync). For alerts, mined time and the sync objects will remain in
the error message will be displayed on the system, queue.
in the screen for alert generation report.
Synchronization of If you are using 3.1.9 MBO, then it is recommended

devices failed to delete the old App and install the recent App
from the App Store.
App crash when sync When Initial or delta sync is in progress, no modifi-
is in progress cations or creations are allowed; user can only nav
igate between different screens in the application.
No creation or modification is allowed for other ap
plications on the device.
Connection dropped Http communication error on device

due to lack of net
work activity)
Partner Determina
tion Error for Visit
MES This message is raised in the backend when the

SAGE_TYPE_X_TEXT SUP server destination (DOMAIN + Package + RFC
Destination) maintained in SPRO is not reachable

Troubleshooting PUBLIC 109
Http Communication This is because the CRM SSO certificate is not To download both CRM and ERP backend data, you
error trusted by the ERP System. can :
1. Define a trusted connection between CRM and

ERP system (in the ERP IMG activity 'Define
General Settings', maitain the CRM RFC desti
nation and then define the trusted connection
settings in the ABAP system)
2. OR remove the SSO cookie attribute in the se
curity configuration in SCC.
Define the following settings:
1. In the ERP Customizing, make sure, the

trusted setting is set in the ERP system / A
second option is to remove the SSO cookie -
this will enable data download for both CRM
and ERP.
2. In the Security Configuration in SCC, 'Edit Pro
vider' screen, remove the SSO cookie attribute
(value 'MYSAPSSO2' for the property 'SSO
Cookie Name')

110 PUBLIC Troubleshooting
Android Only Uninstall any previously installed Retail Execution
app from your device and reinstall to reproduce the
Application failed to
error scenario.
install due to different
application signature If the error recurs, then,
1. Go to Menu Preferences Debug
Screen . In this Debug screen, you must per

form the following steps:
○ Mail the database encryption key to the
system administrator or upload in mes
sage
○ Export the database. To do this,
1. Click on 'Export Database'.
2. Explore the folder sdcard/
Download folder in your device
 Note
The folder by default is named
'Download' but will appear as
'sdcard' if you are using an
sdcard.
3. A new folder with the name

com.sap.rex will be created along
with the timestamp.
4. Zip the folder and send it to the sys
tem administrator in an IT ticket or
as a mail attachment.

Troubleshooting PUBLIC 111
10 Limitations and Restrictions
10.1 Introduction
● User assignment to single sales org

Retail Execution supports assignment of only one organizational unit for a user. Assignment to multiple sales
organizations is not supported.
● Discount Calculations for Sales Order Items:
and C (Discount/UoM based). Note that all three discount types are supported on device for online price
calculation. However, for offline price calculation, only type C (Discount/UoM based) is considered.

112 PUBLIC Limitations and Restrictions
11 Appendix
11.1 DCN Specific APIs
The following APIs have been provided to support the DCN :
● /MAC/RSFM_CREATE_ACT_RESULT – Create Visit / Activity / Task / To Do

● /MAC/RSFM_UPDATE_ACT_RESULT – Update Visit / Activity / Task / To Do
● /MAC/RSFM_DCN_PRODUCT_LIST
● /MAC/RSFM_DCN_TRGT_GRP_DELTA
● /MAC/RSFM_get_bp_prd_listing_i
● /MAC/RSFM_PRODUCT_DELTA
● /MAC/RSFM_DCN_ACTIVITY_DELTA
● /MAC/RSFM_DCN_ATTACHMENT_DELTA
● /MAC/RSFM_DCN_ATTACHMENT_DELTA
● /MAC/RSFM_DCN_BP_LIST
● /MAC/RSFM_DCN_CUST_ACC_PROD
● /MAC/RSFM_DCN_LISTING_DELTA
● /MAC/RSFM_DCN_MKTPROJECT_DELTA
● /MAC/RSFM_DCN_ONEORDER_DELTA
● /MAC/RSFM_DCN_PRD_ONLINE_SRCH
● /MAC/RSFM_DCN_SALESORDER_DELTA
● /MAC/RSFM_DCN_SO_ATCHMNT_DELTA
11.2 Additional Information
Android Only : Enabling New Languages in Retail Execution
 Note
This section explains how to setup languages for Retail Execution that are not supported in the standard
application.
Option 1
1. Make sure translations are available in the required language for all strings included in res/values/
strings.xml.
2. Create a new folder in the 'res' folder and copy the translated labels in this folder.

Appendix PUBLIC 113
3. Recompile the application to enable the new language.
4. Change the device locale to the location relevant for the language.
Option 2
1. Make sure translations are available in the required language for all strings included in the Strings.xml file in
the following location: res values strings.xml
2. Include the labels in uiconfiguration.xml at start inside the 'strings' tag
3. Rename the uiconfiguration to the 32UIAconfiguration_Android.xml
4. Upload the file at CRM mime repository in the following location: SAP Public REX Android
5. Sync customizing in device and change locale to the new language. Note that all labels appear in the new
language. Make sure the cache period for customizing cache group in Sybase control center is 0.

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

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

Important Disclaimers and Legal Information PUBLIC 115
www.sap.com/contactsap
© 2018 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.
Some software products marketed by SAP SE and its distributors

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

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

additional trademark information and notices.
THE BEST RUN

Manual Retail SAP 1

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Manual Retail SAP 1

Uploaded by

Copyright:

Available Formats

ADMINISTRATOR'S GUIDE | PUBLIC

SAP RETAIL EXECUTION 3.5 Administrator Guide

THE BEST RUN

2 SAP Retail Execution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

4 Configuration & Customizing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

SAP RETAIL EXECUTION 3.5 Administrator Guide

5 Extensibility Using Augmentation Framework. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57

8 Features and Functions Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

SAP RETAIL EXECUTION 3.5 Administrator Guide

10 Limitations and Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

SAP RETAIL EXECUTION 3.5 Administrator Guide

1.1 History of Changes

The Administrator’s Guide is regularly updated in SAP Service Marketplace at http://service.sap.com/instguides

Document Version Important Changes

SAP RETAIL EXECUTION 3.5 Administrator Guide

Retail Execution 3.3.0 is supported only on devices running on iOS 8.0.

SAP Retail Execution 3.3.0 is available in the following languages:

1.3 About this Document

SAP RETAIL EXECUTION 3.5 Administrator Guide

1.4 Related Information

Content Location on SAP Service Marketplace

Applications SAP ERP SAP ERP 6.0 Installation

Applications SAP ERP SAP ERP 6.0 Installation

Applications SAP ERP SAP ERP 6.0 Operations

Applications SAP ERP SAP ERP 6.0

Application Operation Guide CRM 7.0 http://service.sap.com/instguides SAP Business Suite

Applications SAP CRM SAP CRM 7.0

Latest versions of installation and upgrade guides http://service.sap.com/instguides

General information about SAP Retail Execution http://service.sap.com/quicklink

Released platforms and technology-related topics such as http://service.sap.com/platforms

Network security http://service.sap.com/securityguide

High Availability http://www.sdn.sap.com/irj/sdn/ha

SAP RETAIL EXECUTION 3.5 Administrator Guide

Information about Support Package Stacks, latest software http://service.sap.com/sp-stacks

Information about Unicode technology http://www.sdn.sap.com/irj/sdn/i18n

1.5 Further Useful Links

Content Location on Service Marketplace

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

SAP Notes search http://service.sap.com/notes

SAP Software Distribution Center (software download and or­ http://service.sap.com/swdc

SAP Online Knowledge Products (OKPs) – role-specific Learn­ http://service.sap.com/rkt

1.6 Important SAP Notes

SAP Note Number Title

2132727 SAP Retail Execution 3.3.0 Release Note

SAP RETAIL EXECUTION 3.5 Administrator Guide

2.2 Key Benefits

Key Business Benefits

SAP RETAIL EXECUTION 3.5 Administrator Guide

Data Flow and Synchronization for Online and Offline Access

SAP RETAIL EXECUTION 3.5 Administrator Guide

SAP Retail Execution 3.3.0 : Architecture Overview

SAP RETAIL EXECUTION 3.5 Administrator Guide

SAP CRM 7.0 SP08 or EhP1 X

SAP Retail Execution CRM Add-On X

SAP ERP 6.0 SP15 X

SAP Retail Execution ERP Add-On X

SAP Mobile Platform 2.3 SP05 PL01 X

SAP Business Warehouse 7.0 X

The mobile application consists of 3 key layers:

2.4 Compatibility Matrix for Release Versions

SAP RETAIL EXECUTION 3.5 Administrator Guide

SAP RETAIL EXECUTION 3.5 Administrator Guide

SAP RETAIL EXECUTION 3.5 Administrator Guide

3.1 General Installation Information

SAP Software Distribution Center (software download and or http://service.sap.com/swdc

SAP Online Knowledge Products (OKPs) – role-specific Learn http://service.sap.com/rkt