MCF_ADMIN_GUIDE_1_5

Administrator's Guide for SAP for UtilitiesDocument version: 1.5 2015-06-11

SAP Multichannel Foundation for Utilities and Public Sector

CUSTOMER

Document History

CautionBefore you start the implementation, make sure you have the latest version of this document. You can find the latest version at the following location:service.sap.com/utilities .

The following table provides an overview of the most important document changes.

Table 1Version Date Description1.40 2015-03-13 Fourth Version

2CUSTOMERCopyright;

SAP Multichannel Foundation for Utilities and Public SectorDocument History

Content

1 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.1 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2 Installation of SAP Multichannel Foundation for Utilities and Public Sector . . . . . . . . . . . . . . . . 11

3 Configuration of SAP CRM System as Leading System Scenario . . . . . . . . . . . . . . . . . . . . . . . . 143.1 Configuring the SAP Gateway Hub System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

SAP NetWeaver System Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 SAP Gateway Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Maintain System Aliases for the SAP IS-U and SAP CRM Systems . . . . . . . . . . . . . . . . . . . . . . . . 15 Register Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Create PFCG Role for Service User in SAP Gateway Hub System . . . . . . . . . . . . . . . . . . . . . . . . . 16 Create PFCG Role for Reference User in SAP Gateway Hub System . . . . . . . . . . . . . . . . . . . . . . . 17 Create Service User in SAP Gateway Hub System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Create Reference User in SAP Gateway Hub System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Set Service User in SICF Node for Public OData Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Activate the SICF Nodes for Private and Public SAPUI5 Template Applications . . . . . . . . . . . . . . . 19

3.2 Configuring the SAP CRM System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Create PFCG Role for Service User in SAP CRM System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Create PFCG Role for Reference User in SAP CRM System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Activate BC-Sets in SAP CRM System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Create Service User in SAP CRM System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Create Reference User in SAP CRM System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

3.3 Configuring the SAP IS-U System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Create PFCG Role for Service User in SAP IS-U System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Create PFCG Role for Reference User in SAP IS-U System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Create Service User in SAP IS-U System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Create Reference User in SAP IS-U System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Activate BC-Sets in SAP IS-U System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

3.4 Set Up B2C User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Maintain URL for User Account Activation (Mandatory) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Maintain Number Range Interval for User Self Service (Mandatory) . . . . . . . . . . . . . . . . . . . . . . 26 Maintain RFC Destinations for User Replication (Mandatory) . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Maintain User Category (Mandatory) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Verify User Request (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Define Notification Process for User Request Management (Optional) . . . . . . . . . . . . . . . . . . . . . 27 Implement User Management (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Define Handler for User Management Notification (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 User Request Cleanup (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

3.5 Quick Testing of OData Services CRM_UTILITIES_UMC and ERP_UTILITIES_UMC . . . . . . . . . . . . . . 29

4 Configuration of SAP IS-U System as Standalone Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . 304.1 Configuring the SAP Gateway Hub System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

SAP Multichannel Foundation for Utilities and Public SectorContent

CUSTOMERCopyright; 3

SAP NetWeaver System Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 SAP Gateway Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Maintain System Alias for the SAP IS-U System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Register Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Create PFCG Roles for Service User for SAP Gateway Hub System . . . . . . . . . . . . . . . . . . . . . . . 32 Create PFCG Roles for Reference User for SAP Gateway Hub System . . . . . . . . . . . . . . . . . . . . . 32 Create Service User in SAP Gateway Hub System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Create Reference User in SAP Gateway Hub System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Set Service User in SICF Node for ERP_UTILITIES_UMC_URM . . . . . . . . . . . . . . . . . . . . . . . . . . 34

4.2 Configuring the SAP IS-U System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Create PFCG Role for Service User in the SAP IS-U System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Create PFCG Role for Reference User in the SAP IS-U System . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Create Service User in the SAP IS-U System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Create Reference User in the SAP IS-U System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Activate BC-Sets in SAP IS-U System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

4.3 Set Up B2C User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Maintain URL for User Account Activation (Mandatory) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Maintain Number Range Interval for User Self Service (Mandatory) . . . . . . . . . . . . . . . . . . . . . . . 37 Maintain RFC Destinations for User Replication (Mandatory) . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Maintain User Category (Mandatory) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Verify User Request (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Define Notification Process for User Request Management (Optional) . . . . . . . . . . . . . . . . . . . . . 39 Implement User Management (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Define Handler for User Management Notification (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 User Request Cleanup (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

4.4 Quick Testing of OData Services ERP_UTILITIES_UMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Quick Testing of OData Services ERP_UTILITIES_UMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

5 Configuration of SAP Self-Service for Utilities Mobile App . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415.1 Working Example of How to Set Up SAP Self-Service for Utilities Mobile App . . . . . . . . . . . . . . . . . . . 415.2 Additional Setup Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

6 Application Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446.1 SAP Gateway Service Model Development in SAP CRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446.2 SAP Gateway Service Model Development in SAP IS-U . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446.3 SAP Gateway Service Model Extensibility in SAP CRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456.4 SAP Gateway Service Model Extensibility in SAP IS-U . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476.5 Batch Operations for OData Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486.6 Consuming OData Batch Request from SAP UI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506.7 Error Message Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506.8 SAP Multichannel Foundation for Utilities and Public Sector Solution Monitoring . . . . . . . . . . . . . . . . 526.9 SAP Multichannel Foundation for Utilities and Public Sector Management . . . . . . . . . . . . . . . . . . . . 536.10 Sample SAP UI5 Application Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

UMCUI5 Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 UMCUI5 Public Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Log Out Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

6.11 Sample SAP UI5 Mobile Application Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 SAP Gateway Service Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 UMCUI5_MOBILE Public Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 UMCUI5_MOBILE Foundation Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

4CUSTOMERCopyright;


6.12 Applying Custom Themes to Mobile Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Applying a Custom UI Theme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Specifying the Path to a Custom UI Theme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Creating a Custom Theme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

6.13 Configuring Outage in SAP Multichannel Foundation for Utilities and Public Sector . . . . . . . . . . . . . . 60 Configuring Visual Business for OData Entity Outage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Consuming Visual Business Services from the User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Creating an Outage Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Configuring Outage Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

6.14 Retrieving Channel Information in SAP Multichannel Foundation for Utilities and Public Sector . . . . . . 63

7 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647.1 Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647.2 Technical System Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657.3 Security Aspects of Data, Data Flow, and Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667.4 User Administration and Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677.5 User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677.6 Integration into Single Sign-On Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707.7 Authorizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707.8 Session Security Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737.9 Network and Communication Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747.10 Communication Channel Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747.11 Network Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757.12 Internet Communication Framework Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757.13 Data Protection and Privacy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 767.14 OData Services Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777.15 Other Security-Related Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777.16 Security-Relevant Logging and Tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

8 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 808.1 Related Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80



6CUSTOMERCopyright; SAP Multichannel Foundation for Utilities and Public Sector

1 Getting Started

1.1 Getting StartedAbout this DocumentThis document is a single source of information for the implementation of SAP Multichannel Foundation for Utilities and Public Sector. It contains implementation, security and operation information only for SAP for Utilities. You can find the Administrator's Guide for public sector at help.sap.com/industries under SAP for Public Sector.This document is divided into the following main sections: Introduction with references to related documents and relevant SAP Notes Installation information Security information Application Operations information

NoteYou can find the most current version of this document on SAP Service Marketplace at help.sap.com/umc .We strongly recommend that you use the document available there. The Guide will be updated according to updates of the software.

Related InformationFor more information about implementation topics not covered in this Guide, see the following content on SAP Service Marketplace:Table 2Content Location on SAP Service Marketplace

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

General information about SAP Multichannel Foundation for Utilities and Public Sector

service.sap.com/utilities

Sizing, calculation of hardware requirements such as CPU, disk and memory resource with the Quick Sizer tool

service.sap.com/quicksizer

Released platforms and technology-related topics such as maintenance strategies and language support

service.sap.com/platformsTo access the Platform Availability Matrix directly, enter service.sap.com/pam

Network Security service.sap.com/securityguide

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

Performance service.sap.com/performance

SAP Multichannel Foundation for Utilities and Public SectorGetting Started


Content Location on SAP Service Marketplace

Information about Support Package Stacks, latest software versions and patch level requirements

service.sap.com/sp-stacks

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

SAP Notes search service.sap.com/notes

SAP Software Distribution Center (software download and ordering of software)

service.sap.com/swdc

SAP Online Knowledge Products (OKPs) role-specific learning maps

service.sap.com/rkt

Related GuidesYou can find more information about the relevant applications in the following documents:Table 3Title Location

Master Guide SAP Netweaver 7.0 service.sap.com/installNW70See the Master Guide under the Planning section

Technical Operations for SAP NetWeaver help.sap.com/netweaverSee the Guide under SAP Netweaver 7.4 System Administration and Maintenance Technical Operations for SAP NetWeaver

SAP NetWeaver Gateway Security Guide help.sap.com/nwgateway

SAP NetWeaver Gateway Technical Operations Guide help.sap.com/nwgateway

Important SAP NotesYou must read and implement the following SAP Notes before you start the installation. These SAP Notes contain the most recent information, and are prerequisites for installing SAP Multichannel Foundation for Utilities and Public Sector.Make sure that you have the current version of each SAP Note, which you can find on SAP Service Marketplace at service.sap.com/notes .Table 4SAP Note Number Title

1942072 SAP NetWeaver Gateway 2.0 Support Package Stack Definition

1964240 * User Self Service: Check Password Security Policy Fixes

1988794 * User Self Service Enhancement: Resetting Password Using Email ID of the User

2000713 * User Self Service - User is Unable to Change the Password

8CUSTOMERCopyright;


SAP Note Number Title

2004762 * User Self Service: Reset Credentials with auto generated password

2025549 * User Self Service: Improving the Error Message Shown to End User

2028105 * User Self Service: Short Dump While Checking Password

NoteAll the SAP Notes marked with an asterisk are required only if you have installed IW_BEP SP08 or the corresponding SAP_GWFND Support Pack.

RecommendationYou are recommended to implement the following SAP Notes. Additionally, they may prove useful when using the SAP Multichannel Foundation for Utilities and Public Sector solution.

Table 5SAP Note Number Title

1509851 ICF logoff service with redirectURL

853878 HTTP WhiteList Check (security)

1.2 OverviewThe figure below shows an overview of the technical system landscape for SAP Multichannel Foundation for Utilities and Public Sector.



Figure 1: The technical system landscape for SAP Multichannel Foundation for Utilities and Public Sector

Two add-ons that group business processes in SAP ERP and SAP CRM for Utilities for OData consumption are UMCERP01 and UMCCRM01. A sample SAPUI5 template is hosted on SAP Gateway. The user interface application communicates with the SAP Gateway using OData protocol. The SAP Gateway dispatches the calls to specific back end systems.

10CUSTOMERCopyright;


2 Installation of SAP Multichannel Foundation for Utilities and Public Sector

Installation SequenceThe following tables provide the implementation sequence:Table 6SAP for Utilities

1. Installation of SAP for Utilities, based on SAP ERP 6.0 Enhancement Package 4 or higher, SAP CRM 7.0 or higher, SAP NetWeaver 7.0 Enhancement Package 1 or higher

For more information, see SAP Service Marketplace Installation & Upgrade Guides Industry SolutionsIndustry Solution Guides SAP for Utilities

SAP for Utilities contains several business scenarios. Each scenario requires a different technical system landscape and installation sequence. For SAP Multichannel Foundation for Utilities and Public Sector, you should choose from one of the following business scenarios: Selling of Energy Supply Products (E-Services) Selling of Energy Supply Products (Interaction Center) Selling of Energy Supply Products (Key Account Management) Selling of Utility Services

For all of the listed scenarios, both the SAP ERP and SAP CRM Servers are required. It is also necessary to have an additional SAP Gateway Server. It is further necessary to install additional components of the Servers mentioned above. The following table provides the implementation sequence:Table 7SAP ERP Server

1 as part of the installation of SAP for Utilities

Installation of SAP ERP 6.0 EHP4 (or higher) Utilities/Waste and Recycl./Telco

For more information, see service.sap.com/erp-inst SAP ERP 6.0 Planning .

2 Installation of IW_BEP SP08 on SAP ERP 6.0 EHP4 or higher

NW 7.40 SAP ERP 6.0 EHP7 onwards, installation of SAP_GWFND 740 SP06 is required instead of IW_BEP

See help.sap.com/nwgateway and choose SAP NetWeaver Gateway Developer Guide OData ChannelAdvanced Features User Self Service .For more information on compatibility of the different SAP Gateway components, see SAP Note 1942072

3 Installation of Add-On UMCERP01 For more information, see service.sap.com/erp-inst SAP ERP Add-Ons .

SAP Multichannel Foundation for Utilities and Public SectorInstallation of SAP Multichannel Foundation for Utilities and Public Sector


Table 8SAP CRM Server

1 as part of the installation of SAP for Utilities

Installation of SAP CRM 7.0 or higher For more information, see service.sap.com/crm-inst SAP CRM SAP CRM 7.0 Enhancement Package X Plan .

2 Installation of IW_BEP SP08 on SAP ERP 6.0 EHP4 or higher

NW 7.40 SAP ERP 6.0 EHP7 onwards, installation of SAP_GWFND 740 SP06 is required instead of IW_BEP

See help.sap.com/nwgateway and choose SAP NetWeaver Gateway Developer Guide OData ChannelAdvanced Features User Self Service .For more information on compatibility of the different SAP Gateway components, see SAP Note 1942072

3 Installation of Add-On UMCCRM01 For more information, see service.sap.com/crm-inst SAP CRM Add-Ons .

Table 9SAP Gateway Server

1 For SAP NetWeaver versions prior to NW 7.40, installation of GW_CORE SP04 and IW_FND SP04 are required.For NW 7.40 SAP_GWFND SP06 component is needed

For more information, see http://help.sap.com/nwgateway under SAP NetWeaver Gateway Installation Guide Installation Prerequisites .For detailed information on compatibility of the different SAP Gateway components, see SAP Note 1942072

2 Installation of SAPUI5 related Add-Ons: UISAPUI5 SP08 or higher, UI_INFRA SP08 or higher.

NoteUISAPUI5 and UI_INFRA can be delivered within the same Add-On (SAP_UI). In this scenario, SAP_UI SP08 or higher must be installed.If the package SAP_UI 740 or higher is already installed in the system, then the UISAPUI5, UI_INFRA are already a part of it and do not require explicit installation.

For more information, see help.sap.com/nw under User Interface Add-On for SAP NetWeaverMaster Guide Software Units .



SAP Gateway ServerOptional UI5 components: UI5_731 SP05 for Team Provider and other UI5 components depending on the UI implementation approach

3 Installation of Add-On UMCUI501

Hardware SizingA sizing guide for SAP Gateway is available on the SAP Service Marketplace at service.sap.com/sizing and under Sizing Guidelines. You can also refer to the Sizing Guides for SAP CRM for ISU and SAP ERP. The Quick Sizer tool can also be used to come up with a rough estimation regarding hardware calculations for the system landscape.



3 Configuration of SAP CRM System as Leading System Scenario

In order to configure your SAP CRM system as a leading system scenario, certain roles, users and activations need to be maintained in the system. The following sections provide you with instructions on how to set up SAP CRM as the leading system.

3.1 Configuring the SAP Gateway Hub System

3.1.1 SAP NetWeaver System SettingsTo allow proper authentication for online users, it is necessary to set correct Application Server (AS) profile parameters related to HTTP Security Session Management on AS ABAP. This can be done in transaction SICF_SESSIONS.For more information, see the SAP Application Help at help.sap.com under SAP NetWeaver SAP NerWeaver Platform Security Information Security Guide User Administration and Authentication User Authentication and Single Sign-On .To check HTTP Session Management settings, run transaction SICF_SESSIONS. Sample values for HTTP session parameters are: login/create_sso2_ticket = 2 login/accept_sso2_ticket = 1 login/ticketcache_off = 0 login/ticket_only_by_https = 1 icf/user_recheck = 1

NoteDepending on your session security configuration, these parameters may differ.

3.1.2 SAP Gateway ActivationProcedureIn order to check whether SAP Gateway is activated, do the following:1. Use transaction SPRO in the system.2. Navigate to SAP NetWeaver Gateway OData Channel Configuration Activate or Deactivate SAP

NetWeaver Gateway .


SAP Multichannel Foundation for Utilities and Public SectorConfiguration of SAP CRM System as Leading System Scenario

3.1.3 Maintain System Aliases for the SAP IS-U and SAP CRM Systems

An SAP system alias maps the following together: A logical RFC destination pointing to an SAP business system A Web service provider system pointing to the same SAP business system The software version of that SAP business system; the supported versions are shipped by SAP and cannot be

changed

Procedure

In order to create system aliases for the SAP ERP and SAP CRM systems proceed as follows:1. In transaction SM59, create trusted RFC connections to the appropriate systems.2. On the Logon and Security tab pages for these RFCs, select the Current User check box.3. Use transaction SPRO and open the SAP Reference IMG.4. Navigate to SAP NetWeaver Gateway OData Channel Configuration Connection Settings Manage

SAP System Aliases .5. Create system aliases for the SAP ERP and SAP CRM systems.

3.1.4 Register ServicesOData Channel implementations retrieve the data from an SAP Business Suite system, which is a back end system. You can use the OData Services that have already been defined by SAP; alternately, you can redefine the OData Services according to your requirements. Once an OData Service has been defined in the back end system, the Service must be registered or activated on the SAP Gateway system.

Procedure

In order to register services in SAP NetWeaver Gateway Hub system, proceed as follows:1. In transaction /IWFND/MAINT_SERVICE, choose the Add Service option.2. Select the system alias of the SAP CRM system and select Get Services.3. Add the following services:

CRM_UTILITIES_UMC CRM_UTILITIES_UMC_URM CRM_UTILITIES_UMC_PUBLIC_SRV USERMANAGEMENT ERP_UTILITIES_UMC ERP_UTILITIES_UMC_PUBLIC_SRV



4. Select a package in the customer namespace for the objects that will be created during the registration of the services.

5. Select the system alias of the SAP ERP system and select Get Services.6. Add service ERP_UTILITIES_UMC.7. Select a package in the customer namespace for the objects that will be created during the registration of the

services.

NoteIn the context of SAP Multichannel Foundation for Utilities and Public Sector, we enhanced the originally delivered SAP NetWeaver Gateway service USERREQUESTMANAGEMENT by adding Utilities-specific business logic validation (business agreement ID and business partners E-mail address are used for user request validation). CRM_UTILITIES_UMC_URM replaces the original USERREQUESTMANAGEMENT service.

8. For each registered service, select ICF Node pushbutton and then select Configure (SICF).9. For additional security, navigate to the Logon Data tab page, and adjust the security parameters as

necessary, for example, the SSL parameter.

3.1.5 Create PFCG Role for Service User in SAP Gateway Hub System

To execute the User Self Service, the system needs to be setup with users and authorizations for those users. This is a mandatory step as the scenario does not work if the users do not have the required authorizations. In this step, a PFCG role must be created to grant access authorizations to relevant business processes and then assigned to the Service User. This ensures that the user can perform the related tasks when using the services for SAP Multichannel Foundation for Utilities and Public Sector.

Procedure

1. In transaction PFCG, create a new role ZUMC_SRV_USR using the templates /IWFND/RT_GW_USR, /IWBEP/RT_USS_SRVUSR.

NoteAdd additional required authorization objects /IWFND/SRV, S_SECPOL and S_TCODE.

2. For authorization object S_SERVICE and authorization field SRV_NAME (program, transaction or function module name), you must ensure that the following entries exist:Table 10Program ID Object Type Object Name

R3TR IWSG CRM_UTILITIES_UMC_URM

R3TR IWSG CRM_UTILITIES_UMC_PUBLIC_SRV

R3TR IWSG ERP_UTILITIES_UMC_URM



Program ID Object Type Object Name(in SAP ERP standalone)

R3TR IWSG ERP_UTILITIES_UMC_PUBLIC_SRV

NoteThe name of the authorization role is provided as an example only. You can choose any other name in the customer namespace.For the object names to show up in the F4 Help, you must register and activate the OData Services mentioned in the preceding table in transaction /IWFND/MAINT_SERVICE and then execute the service in the SAP NetWeaver Gateway client. For more information, see Register Services [page 15].If you need to use a custom password security policy for the reference user, additional authorization object S_SECPOL must be added to the role.

3. For authorization objects that do not have predefined values for authorization fields in the templates, you must ensure that values relevant to the current business scenarios are provided.

4. Check Customizing in transaction SPRO under the path SAP NetWeaver Application Server System Administration Users and Authorizations Set Customizing Switch in Table PRGN_CUST .If CHECK_S_USER_SAS is specified as YES, the authorization object S_USER_SAS must be manually added to the PFCG role for the Service User.

3.1.6 Create PFCG Role for Reference User in SAP Gateway Hub System

To execute the User Self Service, the system needs to be set up with users and authorizations for those users. This is a mandatory step as the scenario does not work if the users do not have the required authorizations. In this step, a PFCG role must be created to grant access authorizations to relevant business processes and then assigned to the Reference User. This ensures that the user can perform the related tasks when using the services for SAP Multichannel Foundation for Utilities and Public Sector.

Procedure

1. In transaction PFCG, create a new role ZUMC_REF_USR using the /IWBEP/RT_USS_INTUSR template.2. For authorization object S_SERVICE and authorization field SRV_NAME (program, transaction or function

module name), you must ensure that the following entries exist:Table 11Program ID Object Type Object Name

R3TR IWSG CRM_UTILITIES_UMC

R3TR IWSG ERP_UTILITIES_UMC

R3TR IWSG USERMANAGEMENT



NoteThe name of the authorization role is provided as an example only. You can choose any other name in the customer namespace.For the object names to show up in the F4 Help, you must register and activate the OData Services mentioned in the preceding table in transaction /IWFND/MAINT_SERVICE and then execute the service in the SAP NetWeaver Gateway client. For more information, see Register Services [page 15].


3.1.7 Create Service User in SAP Gateway Hub System

Procedure

To execute the User Self Service, the system needs to be set up with users and the required authorizations for those users. Additionally, the users have to be created and maintained through SAP NetWeaver ABAP AS User Management, using transaction SU01. A Service User is a standard SAP user of User Type Service created in the SAP Gateway Hub and also in the SAP Business Suite System with the IWBEP add-on. A Service User should be able to access the OData Service /IWBEP/USERREQUESTMANAGEMENT.1. In transaction SU01, create user UMC_SRV_USR.

NoteThe name of the user is provided as an example. You can use any other name of your choice but you must make sure that the same name is maintained for the service in transaction SICF.

2. On the Logon Data tab page, specify the users type as S - Service.3. On the Roles tab page, assign the previously created role ZUMC_SRV_USR.

3.1.8 Create Reference User in SAP Gateway Hub System

Procedure

To execute the User Self Service, the system needs to be set up with users and the required authorization for those users. Additionally, the users have to be created and maintained through SAP NetWeaver ABAP AS User Management, using transaction SU01. A Reference User is a standard SAP user of User Type Reference created in the SAP Gateway Hub and also in SAP Business Suite System with the IWBEP add-on. This user is used by the user management service as a template to create other users in the system.1. In transaction SU01, create user UMC_REF_USR.




2. On the Logon Data tab page, specify the users type as L - Reference.3. Specify the alias for the user as UMC_REFERENCE_USER.4. On the Roles tab page, assign the previously created role ZUMC_REF_USR.

3.1.9 Set Service User in SICF Node for Public OData Services

In order to execute the CRM_UTILITIES_UMC_URM service, a Service type user must be set up in the ICF node of CRM_UTILITIES_UMC_URM.

ProcedureIn order to set the service user in the ICF Node for CRM_UTILITIES_UMC_URM, proceed as follows:1. In transaction SICF, find the node /default_host/sap/opu/odata/sap/crm_utilities_umc_urm.2. Under Logon Data, specify logon settings for the SAP Gateway Hub system for the service user:

Client: SAP Gateway Hub system client User: UMC_SRV_USR Password: UMC_SRV_USR users password

3. Disable Cross-Site Request Forgery (CSRF) for CRM_UTILITIES_UMC_URM ICF node since the service is executed in the context of the service user. In order to disable CSRF validation in the Service Data tab page of the ICF node, select GUI Configuration and add parameter ~CHECK_CSRF_TOKEN with value 0.

For the OData Service CRM_UTILITIES_UMC_PUBLIC_SRV, you can set the service user in the same way as described above.

NoteYou must omit setting the parameter ~CHECK_CSRF_TOKEN with value 0 for CRM_UTILITIES_UMC_PUBLIC_SRV.

3.1.10 Activate the SICF Nodes for Private and Public SAPUI5 Template Applications

Once you have installed the Application Server ABAP (AS ABAP), all Internet Communication Framework (ICF) services are available in an inactive state for security reasons. After the installation, you have to decide which services are required to be activated for the applications you want to use. Moreover, after installing the SAP



Multichannel Foundation for Utilities and Public Sector application, all service nodes must be activated in the SICF tree.

Procedure

In order to activate the SICF nodes for private and public SAPUI5 template application, proceed as follows:1. In transaction SICF, find the following nodes:

/default_host/sap/bc/ui5_ui5/sap/umcui5 /default_host/sap/bc/ui5_ui5/sap/umcui5_mobile /default_host/sap/public/bc/ui2 /default_host/sap/public/bc/ui5_ui5 /default_host/sap/public/bc/icf/logoff

2. Right click on the nodes and select the Activate Service option.If you need to change security settings for the login procedure of UMCUI5 Web application, select the Logon Data tab page and adjust the options as necessary. By default the user is authenticated in the system using a user alias (Internet user). Further configuration can be carried out on the Error Pages Logon Errors System LogonConfiguration .

3.2 Configuring the SAP CRM System

3.2.1 Create PFCG Role for Service User in SAP CRM SystemTo execute the User Self Service, the system needs to be set up with users and authorization for those users. This is a mandatory step as the scenario does not work if the users do not have the required authorizations. In this step, a PFCG role has to be created to grant access authorizations to relevant business processes and assigned to the Service User. This ensures that the user can perform the related tasks when using the services for SAP Multichannel Foundation for Utilities and Public Sector.

Procedure

1. In transaction PFCG, create a new role ZUMC_SRV_USR using the templates /IWBEP/RT_USS_SRVUSR and SAP_CRM_UMC_SRV.


R3TR IWSG CRM_UTILITIES_UMC_URM

R3TR IWSG CRM_UTILITIES_UMC_PUBLIC_SRV






3.2.2 Create PFCG Role for Reference User in SAP CRM System

To execute the User Self Service, the system needs to be set up with users and authorization for those users. This is a mandatory step as the scenario does not work if the users do not have the required authorizations. In this step, a PFCG role has to be created to grant access authorizations to relevant business processes and assigned to the Service User. This ensures that the user can perform the related tasks when using the services for SAP Multichannel Foundation for Utilities and Public Sector.

Procedure

1. In transaction PFCG, create a new role ZUMC_REF_USR using the templates /IWBEP/RT_USS_INTUSR and SAP_CRM_UMC_ODATA.

2. For authorization object S_SERVICE and authorization field SRV_NAME (program, transaction or function module name) you must ensure that the following entries exist:Table 13Program ID Object Type Object Name

R3TR IWSG /IWBEP/USERMANAGEMENT

R3TR IWSG CRM_UTILITIES_UMC





4. If you create your own services, you must add the authorization objects you have used to the role of the Reference User. Additionally, you must include entry of your service to the authorization object S_SERVICE as mentioned above.

5. Add authorization object S_RFCACL for trusted RFC authorizations to the PFCG role ZUMC_REF_USR.

3.2.3 Activate BC-Sets in SAP CRM System

To be able to execute contract management related entities in SAP Multichannel Foundation for Utilities and Public Sector, the system requires some specific Customizing that is delivered through BC-Sets. This is a mandatory step as the scenario does not work if the Customizing is done incorrectly.In this step, the following BC-Sets need to be activated using transaction SCPR20: CRM_IU_UMC_IR_CATEGORY CRM_IU_UMC_ISR CRM_IU_UMC_PR_PROCESS CRM_IU_UMC_SETTING

3.2.4 Create Service User in SAP CRM System

To execute the User Self Service, the system needs to be set up with users and the required authorization for those users. Additionally, the users have to be created and maintained through SAP NetWeaver ABAP AS User Management, using transaction SU01. A Service User is a standard SAP user of User Type Service created in the Gateway Hub and also in SAP Business Suite System with the IWBEP add-on. A Service User should be able to access the OData service/IWBEP/USERREQUESTMANAGEMENT_0001.

Procedure

1. In transaction SU01, create user UMC_SRV_USR.





3.2.5 Create Reference User in SAP CRM SystemTo execute the User Self Service, the system needs to be set up with users and the required authorization for those users. Additionally, the users have to be created and maintained through SAP NetWeaver ABAP AS User Management, using transaction SU01. A Service User is a standard SAP user of User Type Reference created in the Gateway Hub and also in SAP Business Suite System with the IWBEP add-on. This user is used by the user management service to create users in the system.

Procedure1. In transaction SU01, create user UMC_REF_USR.



3.3 Configuring the SAP IS-U SystemThe SAP IS-U system needs to be configured in the same way as the SAP CRM system.

3.3.1 Create PFCG Role for Service User in SAP IS-U SystemTo execute the User Self Service, the system needs to be set up with users and authorization for those users. This is a mandatory step as the scenario does not work if the users do not have the required authorizations. In this step, a PFCG role has to be created to grant access authorizations to relevant business processes and assigned to the UMC Service User. This ensures that the user can perform the related tasks when using the services for SAP Multichannel Foundation for Utilities and Public Sector.

Procedure1. In transaction PFCG, create a new role ZUMC_SRV_USR using the templates /IWBEP/RT_USS_SRVUSR and

SAP_ISU_UMC_SRV.2. For authorization objects that do not have predefined values for authorization fields in the templates, you

must ensure that values relevant to the current business scenarios are provided.3. Check Customizing in transaction SPRO under the path SAP NetWeaver Application Server System

Administration Users and Authorizations Set Customizing Switch in Table PRGN_CUST .



If CHECK_S_USER_SAS is specified as YES, the authorization object S_USER_SAS must be manually added to the PFCG role for the UMC service user.

4. Add authorization object S_RFCACL for trusted RFC authorizations to the PFCG role ZUMC_REF_USR.Set activity to Execute and configure the rest of the RFC settings depending on what the service user is allowed to run.

3.3.2 Create PFCG Role for Reference User in SAP IS-U System

To execute the User Self Service, the system needs to be set up with users and authorization for those users. This is a mandatory step as the scenario does not work if the users do not have the required authorizations. In this step, a PFCG role has to be created to grant access authorizations to relevant business processes and assigned to the UMC Reference User. This ensures that the user can perform the related tasks when using the services for SAP Multichannel Foundation for Utilities and Public Sector.

Procedure

1. In transaction PFCG, create a new role ZUMC_REF_USR using the templates /IWBEP/RT_USS_INTUSR and SAP_ISU_UMC_ODATA.

2. For authorization object S_SERVICE and authorization field SRV_NAME (program, transaction or function module name) make sure that the following entries exist:Table 14Program ID Object Type Object Name


R3TR IWSG ERP_UTILITIES_UMC_PUBLIC_SRV



4. If you create your own services, you must add the authorization objects you have used to the role of the Reference User. Additionally, you must include entry of your service to the authorization object S_SERVICE as mentioned above.



3.3.3 Create Service User in SAP IS-U SystemTo execute the User Self Service, the system needs to be set up with users and the required authorization for those users. Additionally, the users have to be created and maintained through SAP NetWeaver ABAP AS User Management, using transaction SU01. A Service User is a standard SAP user of User Type Service created in the Gateway Hub and also in SAP Business Suite System with the IWBEP add-on..

ProcedureFor more information on how to create a Service User, see Create Service User in SAP CRM System [page 22].

3.3.4 Create Reference User in SAP IS-U SystemTo execute the User Self Service, the system needs to be set up with users and the required authorization for those users. Additionally, the users have to be created and maintained through SAP NetWeaver ABAP AS User Management, using transaction SU01. A Service User is a standard SAP user of User Type Reference created in the Gateway Hub and also in SAP Business Suite System with the IWBEP add-on. This user is used by the user management service to create users in the system.

ProcedureFor more information on how to create a Reference User, see Create Reference User in SAP CRM System [page 23].

3.3.5 Activate BC-Sets in SAP IS-U SystemYou have to activate the BC Sets ISU_UMC_CORRESP_DISPATCH_CONTROL using transaction SCPR20. Based on the delivered example, you can maintain your own Customizing for communication preference categories and generate a new variant using a different variant prefix.

3.4 Set Up B2C User ManagementConfiguration tasks specific to User Self Service are included in Customizing for SAP NetWeaver Gateway. To access these Customizing activities, do the following:1. Use transaction SPRO and open the SAP Reference IMG.2. Navigate to SAP NetWeaver Gateway Service Enablement Backend OData Channel User Self Service

Setup .



3.4.1 Maintain URL for User Account Activation (Mandatory)You can maintain the activation URL of the application you are using to manage your user accounts as follows:1. Use transaction SPRO and open the SAP Reference IMG.2. Navigate to SAP NetWeaver Gateway Service Enablement Backend OData Channel User Self Service

Setup Maintain URL for User Account Activation .For the external service name of the User Request Management (/SAP/CRM_UTILITIES_UMC_URM), enter the URL to the sample UI Application, for example, .

NoteInstead of , all relevant information of your system with installed component UMCUI501 should be provided.

3.4.2 Maintain Number Range Interval for User Self Service (Mandatory)

You can maintain the number range for generating the users in the SAP system as follows:.1. Use transaction SPRO and open the SAP Reference IMG.2. Navigate to SAP NetWeaver Gateway Service Enablement Backend OData Channel User Self Service

Setup Maintain Number Range Interval for User Self Service .The number range must be 11 characters long. That is because an SAP username has 12 characters and SAP NetWeaver Gateway uses the scheme UXXXXXXXXXXX, where XXX is the number range.

3.4.3 Maintain RFC Destinations for User Replication (Mandatory)

It enables you to replicate the users from the SAP back end system to the SAP Gateway Hub system. You can carry out this activity as follows:1. Use transaction SPRO and open the SAP Reference IMG.2. Navigate to SAP NetWeaver Gateway Service Enablement Backend OData Channel User Self Service

Setup Maintain RFC Destinations for User Replication .

Procedure1. Use transaction SM59 and create trusted RFC connections to the SAP IS-U and SAP Gateway Hub systems.2. On the Logon & Security tab page, select the Current User check box for these RFCs.3. Select the Customizing activity Maintain RFC Destinations for User Replication and maintain the following

implementation types:



ISU_UMC: Pointing to the SAP IS-U RFC connection IWBEPUM: Pointing to the SAP Gateway Hub system

3.4.4 Maintain User Category (Mandatory)You can maintain the list of user categories for your application as follows.1. Use transaction SPRO and open the SAP Reference IMG.2. Navigate to SAP NetWeaver Gateway Service Enablement Backend OData Channel User Self Service

Setup Maintain User Category .For external service name CRM_UTILITIES_UMC_URM, specify user category text and Reference User Name as UMC_REFERENCE_USER, which is a user alias created in the step Create Reference User in SAP CRM System [page 23].

NoteIf you enhanced User Request Management Service, you must specify the external service name that you created in the Customizing instead of the SAP-delivered CRM_UTILITIES_UMC_URM.

3.4.5 Verify User Request (Optional)You can specify the implementation for the Business Add-In (BAdI) /IWBEP/BD_MGW_URM_VERIFICATION. This BAdI defines the functionality for verifying the information provided during the user request creation.You can maintain this Customizing activity as follows:1. Use transaction SPRO and open the SAP Reference IMG.2. Navigate to SAP NetWeaver Gateway Service Enablement Backend OData Channel User Self Service

Setup Verify User Request .

3.4.6 Define Notification Process for User Request Management (Optional)

You can specify the implementation for the BAdI /IWBEP/BD_MGW_URM_NOTIFICATION, here. It defines the functionality for sending notifications from the User Request Management application.You can maintain this Customizing activity as follows:1. Use transaction SPRO and open the SAP Reference IMG.2. Navigate to SAP NetWeaver Gateway Service Enablement Backend OData Channel User Self Service

Setup Define Notification Process for User Request Management .The User Request Management application has the provision to deliver notifications using e-mail as the standard communication method. You can enhance the solution by adding your own notification mechanism. SAP Multichannel Foundation for Utilities and Public Sector application has a default implementation of this BAdI in



Enhancement Implementation CRM_IU_UMC_URM - CRM_IU_UMC_URM_VERIFICATION (check that this implementation is active).

3.4.7 Implement User Management (Optional)You can specify the implementation for the BAdI /IWBEP/BD_MGW_UM_USR_MANAGER to manage the users, here.You can maintain this Customizing activity as follows:1. Use transaction SPRO and open the SAP Reference IMG.2. Navigate to SAP NetWeaver Gateway Service Enablement Backend OData Channel User Self Service

Setup Implement User Management .SAP Multichannel Foundation for Utilities and Public Sector has a default implementation of this BAdI in Enhancement Implementation CRM_IU_UMC_UM - CRM_IU_UMC_UM_USER_MANAGER.

3.4.8 Define Handler for User Management Notification (Optional)

You can specify the implementation for the BAdI /IWBEP/BD_MGW_UM_NOTIFICATION to notify about the user creation, here.You can maintain this Customizing activity as follows:1. Use transaction SPRO and open the SAP Reference IMG.2. Navigate to SAP NetWeaver Gateway Service Enablement Backend OData Channel User Self Service

Setup Define Handler for User Management Notification .

3.4.9 User Request Cleanup (Optional)You can delete the user requests that are in process, open, completed or cancelled by using this activity as follows:1. Use transaction SPRO and open the SAP Reference IMG.2. Navigate to SAP NetWeaver Gateway Service Enablement Backend OData Channel User Self Service

Setup User Request Cleanup .



3.5 Quick Testing of OData Services CRM_UTILITIES_UMC and ERP_UTILITIES_UMC

ProcedureIt is sometimes necessary to perform a quick test on OData services to see how the entities work. By performing the following steps, you can test OData services with your user via the SAP Gateway client or Google Chromes Advanced Rest client:1. You must ensure that you have a user with the same username in transaction SU01 in the SAP Gateway Hub,

SAP CRM and SAP ERP systems.2. Use transaction SU01 on the SAP ERP and SAP CRM systems, open your user, and choose Goto References

in the menu.3. Create a new reference for your user, and set Object Type to BUS1006.4. Set Key to the business partner ID which has test data with which you would like to test the OData services.5. Go to the SAP Gateway client and execute a GET request on ERP_UTILITIES_UMC or CRM_UTILITIES_UMC

services for OData entity Account.6. You should receive the data for the business partner that you assigned to yourself upon performing GET

account.7. If you did not receive the data, perform an analysis on the user authorization log in transaction SU53 to see if

you are missing any authorizations for your user.

NoteYou must ensure that the test user does not exist in the production environment.



4 Configuration of SAP IS-U System as Standalone Scenario

In order to configure your SAP IS-U system as a standalone system scenario, certain roles, users and activations need to be maintained in the system. The following sections provide you with instructions on how to set up SAP IS-U as the standalone system.

4.1 Configuring the SAP Gateway Hub System

4.1.1 SAP NetWeaver System SettingsTo allow proper authentication for online users, it is necessary to set correct Application Server (AS) profile parameters related to HTTP Security Session Management on AS ABAP. This can be done in transaction SICF_SESSIONS.For more information, see the SAP Application Help at help.sap.com under SAP NetWeaver SAP NerWeaver Platform Security Information Security Guide User Administration and Authentication User Authentication and Single Sign-On .To check HTTP Session Management settings, run transaction SICF_SESSIONS. Sample values for HTTP session parameters are: login/create_sso2_ticket = 2 login/accept_sso2_ticket = 1 login/ticketcache_off = 0 login/ticket_only_by_https = 1 icf/user_recheck = 1

NoteDepending on your session security configuration, these parameters may differ.

4.1.2 SAP Gateway ActivationProcedureIn order to check whether SAP Gateway is activated, do the following:1. Use transaction SPRO in the system.2. Navigate to SAP NetWeaver Gateway OData Channel Configuration Activate or Deactivate SAP

NetWeaver Gateway .


SAP Multichannel Foundation for Utilities and Public SectorConfiguration of SAP IS-U System as Standalone Scenario

4.1.3 Maintain System Alias for the SAP IS-U SystemProcedureIn order to create system aliases for the SAP IS-U system proceed as follows:1. In transaction SM59, create trusted RFC connections to the appropriate systems.2. On the Logon and Security tab pages for these RFCs, select the Current User checkbox.3. Use transaction SPRO and open the SAP Reference IMG.4. Navigate to SAP NetWeaver Gateway OData Channel Configuration Connection SettingsManage

SAP System Aliases .5. Create system alias for the SAP IS-U system. Create system alias for the SAP IS-U system.

4.1.4 Register ServicesOData Channel implementations retrieve the data from an SAP Business Suite system, which is a back end system. You can use the OData Services that have already been defined by SAP; alternately, you can redefine the OData Services according to your requirements. Once an OData Service has been defined in the back end system, the Service must be registered or activated in the SAP Gateway system.

ProcedureIn order to register services in SAP Gateway Hub system, proceed as follows:1. In transaction /IWFND/MAINT_SERVICE, choose the Add Service option.2. Select the system alias of the SAP IS-U system and select Get Services.3. Add the following services:

ERP_UTILITIES_UMC ERP_UTILITIES_UMC_URM USERMANAGEMENT ERP_UTILITIES_UMC_PUBLIC_SRV

4. Select a package in the customer namespace for the objects to be created during the registration of the services.

NoteIn the context of SAP Multichannel Foundation for Utilities and Public Sector, the originally delivered SAP Gateway service USERREQUESTMANAGEMENT has been enhanced by adding Utilities-specific business logic validation (Contract Account ID and business partners E-mail address are used for user request validation). ERP_UTILITIES_UMC_URM replaces the original USERREQUESTMANAGEMENT service.

5. For each registered service, select the ICF Node pushbutton and then select Configure (SICF)6. For additional security, navigate to the Logon Data tab page, and adjust the security parameters as

necessary, for example, the SSL parameter.



4.1.5 Create PFCG Roles for Service User for SAP Gateway Hub System

To execute the User Self Service, the system needs to be setup with users and authorizations for those users. This is a mandatory step as the scenario does not work if the users do not have the required authorizations. In this step, a PFCG role must be created to grant access authorizations to relevant business processes and then assigned to the Service User. This ensures that the user can perform the related tasks when using the services for SAP Multichannel Foundation for Utilities and Public Sector.

Procedure1. In transaction PFCG, create a new role ZUMC_SRV_USR using the templates /IWFND/RT_GW_USR, /IWBEP/

RT_USS_SRVUSR.

NoteAdd additional required authorization objects /IWFND/SRV, S_SECPOL and S_TCODE.


R3TR IWSG ERP_UTILITIES_UMC_URM




4.1.6 Create PFCG Roles for Reference User for SAP Gateway Hub System

To execute the User Self Service, the system needs to be set up with users and authorizations for those users. This is a mandatory step as the scenario does not work if the users do not have the required authorizations. In this



step, a PFCG role must be created to grant access authorizations to relevant business processes and then assigned to the Reference User. This ensures that the user can perform the related tasks when using the services for SAP Multichannel Foundation for Utilities and Public Sector.

Procedure

1. In transaction PFCG, create a new role ZUMC_REF_USR using the /IWBEP/RT_USS_INTUSR template.2. For authorization object S_SERVICE and authorization field SRV_NAME (program, transaction or function

module name), you must ensure that the following entries exist:Table 16Program ID Object Type Object Name


R3TR IWSG USERMANAGEMENT

NoteThe name of the authorization role is provided as an example only. You can choose any other name in the customer namespace.For the object names to show up in the F4 Help, you must register and activate the OData Services mentioned in the preceding table in transaction /IWFND/MAINT_SERVICE and then execute the service in the SAP NetWeaver Gateway client. For more information, see the section Register Services [page 31].


4.1.7 Create Service User in SAP Gateway Hub SystemProcedure

To execute the User Self Service, the system needs to be set up with users and the required authorizations for those users. Additionally, the users have to be created and maintained through SAP NetWeaver ABAP AS User Management, using transaction SU01. A Service User is a standard SAP user of User Type Service created in the SAP Gateway Hub and also in the SAP Business Suite System with the IWBEP add-on. A Service User should be able to access the OData Service /IWBEP/USERREQUESTMANAGEMENT.1. In transaction SU01, create user UMC_SRV_USR.





4.1.8 Create Reference User in SAP Gateway Hub SystemProcedure

To execute the User Self Service, the system needs to be set up with users and the required authorization for those users. Additionally, the users have to be created and maintained through SAP NetWeaver ABAP AS User Management, using transaction SU01. A Reference User is a standard SAP user of User Type Reference created in the SAP Gateway Hub and also in SAP Business Suite System with the IWBEP add-on. This user is used by the user management service as a template to create other users in the system.1. In transaction SU01, create user UMC_REF_USR.



4.1.9 Set Service User in SICF Node for ERP_UTILITIES_UMC_URM

Procedure

In order to set the service user in the ICF Node for ERP_UTILITIES_UMC_URM, proceed as follows:1. In transaction SICF, find the node /default_host/sap/opu/odata/sap/erp_utilities_umc_urm.2. Under Logon Data, specify logon settings for the SAP Gateway Hub system for the service user:

Client: SAP Gateway Hub system client User: UMC_SRV_USR Password: UMC_SRV_USR users password

3. Disable Cross-Site Request Forgery (CSRF) for ERP_UTILITIES_UMC_URM ICF node since the service is executed in the context of the service user. In order to disable CSRF validation in the Service Data tab page of the ICF node, select GUI Configuration and add parameter ~CHECK_CSRF_TOKEN with value 0.

4.2 Configuring the SAP IS-U SystemThe SAP IS-U system must be configured in the same way as the SAP IS-U system mentioned in the section describing the configuration of SAP CRM as a leading system scenario.For more information, see the description for the same step under Configuring the SAP IS-U System [page 23].



4.2.1 Create PFCG Role for Service User in the SAP IS-U System

To execute the User Self Service, the system needs to be set up with users and authorization for those users. This is a mandatory step as the scenario does not work if the users do not have the required authorizations. In this step, a PFCG role has to be created to grant access authorizations to relevant business processes and assigned to the Service User. This ensures that the user can perform the related tasks when using the services for SAP Multichannel Foundation for Utilities and Public Sector.

Procedure1. In transaction PFCG, create a new role ZUMC_SRV_USR using the templates /IWBEP/RT_USS_SRVUSR and

SAP_ISU_UMC_SRV_USR.2. For authorization object S_SERVICE and authorization field SRV_NAME (program, transaction or function

module name), you must ensure that the following entries exist: Program ID: R3TR Object Type: IWVS Object Name: ERP_UTILITIES_UMC_URM 0001


4. Check Customizing in transaction SPRO under the path SAP NetWeaver Application Server System Administration Users and Authorizations Set Customizing Switch in Table PRGN_CUST .

If CHECK_S_USER_SAS is specified as YES, the authorization object S_USER_SAS must be manually added to the PFCG role for the Service User.

4.2.2 Create PFCG Role for Reference User in the SAP IS-U System

To execute the User Self Service, the system needs to be se tup with users and authorization for those users. This is a mandatory step as the scenario does not work if the users do not have the required authorizations. In this step, a PFCG role has to be created to grant access authorizations to relevant business processes and assigned to the Service User. This ensures that the user can perform the related tasks when using the services for SAP Multichannel Foundation for Utilities and Public Sector.

Procedure1. In transaction PFCG, create a new role ZUMC_REF_USR using the templates /IWBEP/RT_USS_INTUSR and

SAP_ISU_UMC_ODATA.2. For authorization object S_SERVICE and authorization field SRV_NAME (program, transaction or function

module name) make sure that the following entries exist:



Table 17Program ID Object Type Object Name

R3TR IWVS /IWBEP/USERMANAGEMENT 0001

R3TR IWVS ERP_UTILITIES_UMC 0001

NoteThe name of the authorization role is provided as an example only. You can choose any other name in the customer namespace.

For authorization objects that do not have predefined values for authorization fields in the templates, you must ensure that values relevant to the current business scenarios are provided.

4.2.3 Create Service User in the SAP IS-U SystemTo execute the User Self Service, the system needs to be set up with users and the required authorization for those users. Additionally, the users have to be created and maintained through SAP NetWeaver ABAP AS User Management, using transaction SU01. A Service User is a standard SAP user of User Type Service created in the Gateway Hub and also in the SAP Business Suite System with the IWBEP add-on. A Service User should be able to access the OData service /IWBEP/USERREQUESTMANAGEMENT_0001.

More Information

For more information on how to create a Service User, see the description for the same step under the SAP CRM as leading system scenario at Create Service User [page 22].

4.2.4 Create Reference User in the SAP IS-U SystemTo execute the User Self Service, the system needs to be set up with users and the required authorization for those users. Additionally, the users have to be created and maintained through SAP NetWeaver ABAP AS User Management, using transaction SU01. A Service User is a standard SAP user of User Type Referencecreated in the Gateway Hub and also in the SAP Business Suite System with the IWBEP add-on. This user is used by the user management service to create users in the system.

More Information

For more information on how to create a Reference User, see the description for the same step under the SAP CRM as leading system scenario at Create Reference User [page 23].



4.2.5 Activate BC-Sets in SAP IS-U System

You have to activate the BC Sets ISU_UMC_CORRESP_DISPATCH_CONTROL using transaction SCPR20. Based on the delivered example, you can maintain your own Customizing for communication preference categories and generate a new variant using a different variant prefix.

4.3 Set Up B2C User Management

Configuration tasks specific to User Self Service are included in Customizing for SAP Gateway. To access these Customizing activities, do the following:1. Use transaction SPRO and open the SAP Reference IMG.2. Navigate to SAP NetWeaver Gateway Service Enablement Backend OData Channel User Self Service

Setup .

4.3.1 Maintain URL for User Account Activation (Mandatory)

You can maintain the activation URL of the application you are using to manage your user accounts as follows:1. Use transaction SPRO and open the SAP Reference IMG.2. Navigate to SAP NetWeaver Gateway Service Enablement Backend OData Channel User Self Service

Setup Maintain URL for User Account Activation .For the external service name of the User Request Management (ERP_UTILITIES_UMC_URM), enter the URL in the sample UI Application, if it exists, for example, .

4.3.2 Maintain Number Range Interval for User Self Service (Mandatory)

You can maintain the number range to generate users in the SAP system as follows:1. Use transaction SPRO and open the SAP Reference IMG.2. Navigate to SAP NetWeaver Gateway Service Enablement Backend OData Channel User Self Service

Setup .The number range must be 11 characters long. That is because an SAP username has 12 characters and SAP Gateway uses the scheme UXXXXXXXXXXX, where XXX is the number range.



4.3.3 Maintain RFC Destinations for User Replication (Mandatory)

It enables you to replicate the users from the SAP back end system to the SAP Gateway Hub system.You can maintain this Customizing activity as follows:1. Use transaction SPRO and open the SAP Reference IMG.2. Navigate to SAP NetWeaver Gateway Service Enablement Backend OData Channel User Self Service

Setup Maintain RFC Destinations for User Replication .

Procedure

1. Use transaction SM59 and create a trusted RFC connection to the SAP Gateway Hub systems.2. On the Logon & Security tab page, select the Current Use check box for these RFCs.

Implementation type is IWBEPUM: Pointing to the SAP Gateway Hub System

4.3.4 Maintain User Category (Mandatory)You can maintain the list of user categories for your application as follows:1. Use transaction SPRO and open the SAP Reference IMG.2. Navigate to SAP NetWeaver Gateway Service Enablement Backend OData Channel User Self Service

Setup Maintain User Category .For external service name ERP_UTILITIES_UMC_URM, specify user category text and Reference User Name as UMC_REFERENCE_USER, which is a user alias created in the step Create Reference User in SAP-IS-U System..

NoteIf you have enhanced User Request Management Service, you must specify the external service name that you created in Customizing instead of the SAP-delivered ERP_UTILITIES_UMC_URM.

4.3.5 Verify User Request (Optional)You can specify the implementation for the Business Add-In (BAdI) /IWBEP/BD_MGW_URM_VERIFICATION. This BAdI defines the function for verifying the information provided during the user request creation.You can implement this BAdI as follows:1. Use transaction SPRO and open the SAP Reference IMG.2. Navigate to SAP NetWeaver Gateway Service Enablement Backend OData Channel User Self Service

Setup Verify User Request .3. Proceed with creating the BAdI implementation.



4.3.6 Define Notification Process for User Request Management (Optional)

You can specify the implementation for the BAdI /IWBEP/BD_MGW_URM_NOTIFICATION, here. It defines the function for sending notifications from the User Request Management application.You can maintain this Customizing activity as follows:1. Use transaction SPRO and open the SAP Reference IMG.2. Navigate to SAP NetWeaver Gateway Service Enablement Backend OData Channel User Self Service

Setup Define Notification Process for User Request Management .The User Request Management application has the provision to deliver notifications using E-mail as the standard communication method. You can enhance the solution by adding your own notification mechanism. SAP Multichannel Foundation for Utilities and Public Sector has a default implementation of this BAdI in Enhancement Implementation ISU_UMC_URM - ISU_UMC_URM_VERIFICATION (check to ensure that this implementation is active).

4.3.7 Implement User Management (Optional)You can specify the implementation for the BAdI /IWBEP/BD_MGW_UM_USR_MANAGER to manage the users as follows:1. Use transaction SPRO and open the SAP Reference IMG.2. Navigate to SAP NetWeaver Gateway Service Enablement Backend OData Channel User Self Service

Setup Implement User Management .SAP Multichannel Foundation for Utilities and Public Sector has a default implementation of this BAdI in the Enhancement Implementation ISU_UMC_UM - ISU_UMC_UM_USER_MANAGER.

4.3.8 Define Handler for User Management Notification (Optional)

You can specify the implementation for the BAdI /IWBEP/BD_MGW_UM_NOTIFICATION to create a notification about the user creation, here.You can maintain this Customizing activity as follows:1. Use transaction SPRO and open the SAP Reference IMG.2. Navigate to SAP NetWeaver Gateway Service Enablement Backend OData Channel User Self Service

Setup Define Handler for User Management Notification .

4.3.9 User Request Cleanup (Optional)You can delete the user requests that are in process, open, completed or cancelled using this activity.



You can maintain this Customizing activity as follows:1. Use transaction SPRO and open the SAP Reference IMG.2. Navigate to SAP NetWeaver Gateway Service Enablement Backend OData Channel User Self Service

Setup User Request Cleanup .

4.4 Quick Testing of OData Services ERP_UTILITIES_UMC

4.4.1 Quick Testing of OData Services ERP_UTILITIES_UMCProcedureIt is sometimes necessary to perform a quick test on OData services to see how the entities work. By performing the following steps, you can test OData services with your user via the SAP Gateway client or Google Chromes Advanced Rest client:1. You must ensure that you have a user with the same username in transaction SU01 in the SAP Gateway Hub,

and SAP ERP systems.2. Use transaction SU01 on the SAP ERP and SAP CRM systems, open your user, and choose Goto

References in the menu.3. Create a new reference for your user, and set Object Type to BUS1006.4. Set Key to the business partner ID which has test data with which you would like to test the OData services.5. In the SAP Gateway client, execute a GET request on the ERP_UTILITIES_UMC service for OData entity

Account.6. You should receive the data for the business partner that you assigned to yourself upon performing GET

account.7. If you did not receive the data, perform an analysis on the user authorization log in transaction SU53 to see if

you are missing any authorizations for your user.

NoteYou must ensure that the test user does not exist in the production environment.



5 Configuration of SAP Self-Service for Utilities Mobile App

The following section describes the steps to configure your mobile apps for iOS and Android in SAP Mobile Platform (SMP).

PrerequisitesIn order to configure the SAP Self-Service for Utilities apps, the following prerequisites must be fulfilled: The SMP installation must have been completed. For more information, see help.sap.com/smp303svr . Admin and push notification users must be set up.

5.1 Working Example of How to Set Up SAP Self-Service for Utilities Mobile App

The following process describes how the SAP Self-Service for Utilities mobile app can be set up once the prerequisite steps have been completed.

NoteWe are using only the onboarding process and push notification feature and there is no persistent data, user management, data model and offline mode.

Process1. Create application com.sap.umc.mobile.

Endpoint: :/sap/opu/odata/sap/ERP_UTILITIES_UMC/ Rewrite Mode: No Rewriting Type: Hybrid SSO Mechanisms: SSO2 and Basic

2. Create a connection to the back end system. CRM_UTILITIES_UMC: :/sap/opu/odata/sap/CRM_UTILITIES_UMC CRM_UTILITIES_UMC_PUBLIC_SRV: :/sap/opu/odata/sap/

CRM_UTILITIES_UMC_PUBLIC_SRV CRM_UTILITIES_UMC_URM: :/sap/opu/odata/sap/CRM_UTILITIES_UMC_URM ERP_UTILITIES_UMC: https://:/sap/opu/odata/sap/ERP_UTILITIES_UMC/

SAP Multichannel Foundation for Utilities and Public SectorConfiguration of SAP Self-Service for Utilities Mobile App


ERP_UTILITIES_UMC_PUBLIC_SRV: :/sap/opu/odata/sap/ERP_UTILITIES_UMC_PUBLIC_SRV

USERMANAGEMENT: :/sap/opu/odata/IWBEP/USERMANAGEMENT VBI_APPL_DEF_SRV (optional): :/sap/opu/odata/sap/VBI_APPL_DEF_SRV VBI_GEOCODER_SRV (optional): :/sap/opu/odata/sap/VBI_GEOCODER_SRV

NoteFor the public service, authentication of any type is not required to be set. corresponds to the SAP Gateway Server address.This configuration assumes that SAP CRM is being used as the leading system.

3. Create Security Profile UMC in settings: Control Flag: required URL: /:/sap/opu/odata/sap/ERP_UTILITIES_UMC/ Try Basic Auth if Token Auth Fails: checked SSO Cookie Name: MYSAPSSO2

On the Application tab page under Authentication, select UMC profile.4. On the Push tab page, enable push for Apple and Android.

Go the Mac Developer Library on Apple's website and search for the document Apple Push Notification Service for push notifications. Follow the instructions to create a certificate.

Go to the Android Developers website and search for Google Cloud Messaging for Android. Follow the instructions to create the sender ID and API key.

5. Back end SAP ERP system report (ISU_UMC_BROADCAST_SAMPLE) to send push notifications to all registered devices: Enter the user name and password provided by the SMP administrator, for example, push URL:http://:/restnotification/application/com.sap.umc.mobile/.6. After running the report, you should get status 201, which means the push was successfully sent. In case of

error regarding proxy and SSL, contact your IT department to import the certificate or set up a proxy).7. Push only works if PUSH ports are not blocked by your firewall.

NoteFirewalls usually block these ports (for example: APN:5223,2195,2196 GCM: 5228-5230).

5.2 Additional Setup InformationProcedureConfigure the user type as Internet User (the alias name) for the Basic Authentication logon procedure in our service:1. In transaction SICF, double-click the service.2. Click the Change icon.



3. Under Logon Data/Authentication, select Internet User.4. Save your changes.

NoteAt this time, it is not possible to reset password or sign up for a new account using the app from the login page. This is because the connection has not yet been set. This feature is only available online.



6 Application Operations

6.1 SAP Gateway Service Model Development in SAP CRMSAP Multichannel Foundation for Utilities and Public Sector is delivered with a default project for OData Services. The default project is called CRM_UTILITIES_UMC in SAP CRM and ERP_UTILITIES_UMC on the SAP ERP side.Behind each OData Service in the back end system, the SAP Gateway engine generates a Model Provider and a Data Provider: Model Provider defines a structure of the model. It can be enhanced either manually (old way) or by using the

SAP Gateway Service Builder (transaction SEGW). Data Provider defines the logic of handling HTTP requests for all entities in the service model. It can be

enhanced by using the development approach introduced in SAP Multichannel Foundation for Utilities and Public Sector.

To modify the existing project or to create your own, you use the service extensibility features in SAP Gateway Service Builder (transaction SEGW). The Business Add-In (BAdI) CRM_IU_UMC_ODATA is called in the data provider extension class for each OData Entity requested by the system. This BAdI implementation provides the infrastructure to extend the existing SAP Multichannel Foundation for Utilities and Public Sector implementation with the additional functions that you created.SAP Multichannel Foundation for Utilities and Public Sector has a certain approach towards OData Entity implementation in the Data Pprovider class: Data Provi

Documents

MCF_ADMIN_GUIDE_1_5