Fiori10 Install En

SAP FioriDocument Version: 1.0 - 2013-12-17

SAP Fiori Installation and Configuration

Table of Contents1 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41.1 Prerequisites Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.2 Required SAP NetWeaver Gateway Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61.3 SAP Notes for SAP NetWeaver Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.4 Required User Interface Add-On Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.5 SAP Notes for User Interface Add-On. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.6 SAP Notes for SAP NetWeaver AS ABAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.7 SAP Notes for SAP ERP and SAP SRM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

2 Install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.1 Setup Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.2 Install Add-On Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

2.2.1 Integration and SAP UI5 Components for SAP Fiori Applications. . . . . . . . . . . . . . . . . . . . . . 122.3 Configure SAP Business Suite Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.3.1 Define Users and Authorizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.3.2 Configure the Back-End Event Publisher. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.3.3 Specify Connection Settings to SAP NetWeaver Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2.4 Configure SAP NetWeaver Gateway Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.4.1 Configure App-Specific Gateway Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.4.2 Activate Gateway and UI5 Services in SICF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2.5 Components and Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182.5.1 Gateway Services for Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182.5.2 SICF Services for UI Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

2.6 Access Apps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.6.1 Access SAP Fiori Apps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

3 Employee Apps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.1 Configure Employee Apps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.2 My Paystubs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.3 My Travel Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.4 My Shopping Cart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

3.4.1 SRM Services Used by My Shopping Cart and Track Shopping Carts. . . . . . . . . . . . . . . . . . . 263.4.2 Additional Prerequisites for My Shopping Cart and Track Shopping Carts. . . . . . . . . . . . . . . .28

3.5 Track Shopping Carts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.6 My Benefits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .293.7 My Timesheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.8 My Leave Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

4 Manager Apps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334.1 Configure Manager Apps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

2 2013 SAP AG or an SAP affiliate company. All rights reserved.SAP Fiori Installation and Configuration

Table of Contents

4.2 Approve Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344.2.1 SAP Notes for Approve Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354.2.2 Task Processing Service User Exits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354.2.3 Extensibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

4.3 Approve Shopping Carts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364.4 Approve Purchase Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374.5 Approve Purchase Contracts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384.6 Approve Requisitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .404.7 Approve Travel Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414.8 Approve Travel Expenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424.9 Approve Timesheets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434.10 My Spend. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

4.10.1 Set Up Personalization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .444.11 Approve Leave Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

5 Sales Rep Apps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475.1 Configure Sales Rep Apps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475.2 Employee Master Record Creation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475.3 Create Sales Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48

5.3.1 Configuration Parameters for Sales Orders Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . 495.4 Track Sales Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

5.4.1 Status Aggregation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515.5 Change Sales Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525.6 Customer Invoices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .525.7 Track Shipments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535.8 Check Price and Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

6 Purchasing Agent Apps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566.1 Configure Purchasing Agent Apps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .566.2 Order From Requisitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566.3 Track Purchase Order. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

7 How To. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587.1 Implement a Business Add-On. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587.2 Define an Approval Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .587.3 Configure Launch Settings for Custom Workflows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .617.4 Create a System Alias. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637.5 Configure Task Decisions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

SAP Fiori Installation and ConfigurationTable of Contents 2013 SAP AG or an SAP affiliate company. All rights reserved. 3

1 Prerequisites

1.1 Prerequisites Checklist

Before you can install and configure SAP Fiori apps, you must ensure that the prerequisite software is installed and Remote Function Call (RFC) connections are set up.

Deployment of SAP NetWeaver Gateway

For running SAP Fiori apps, we recommend that you use a Central Hub Deployment of SAP NetWeaver Gateway. This means you install SAP NetWeaver Gateway independent of consumer technologies in a standalone system, either behind or in front of the firewall. Setting up your system landscape with the Central Hub Deployment option means that you separate business content from front-end content. You therefore have to install components on a back-end server and a front-end server.We do not recommend the Embedded Deployment option. This document is entirely based on the Central Hub Deployment option.For more information about SAP NetWeaver Gateway deployment options, see SAP Library for SAP NetWeaver Gateway 2.0 SP06 on SAP Help Portal at http://help.sap.com/nwgateway20. Select Application HelpSupport Package 06 SAP NetWeaver Gateway Master Guide Deployment Options/Embedded Versus Hub Deployment .

Prerequisites for the Front-End Server (SAP NetWeaver Gateway hub)

Prerequisites More Information SAP NetWeaver Gateway 2.0, SPS 07 The required SAP NetWeaver Gateway installation

depends on your SAP NetWeaver product version. Required SAP NetWeaver Gateway Components [page

6]

User Interface Add-On for SAP NetWeaver The required components depend on your SAP NetWeaver installation. Required User Interface Add-On Components [page

7] SAP Notes for User Interface Add-On [page 8]


Prerequisites

Prerequisites for the Back-End Application Server

Prerequisites More Information SAP NetWeaver 7.0 SPS 21 or higher http://help.sap.com/nw_platform

SAP Notes for SAP NetWeaver AS ABAP [page 8] For SAP Fiori applications based on SAP ERP:

SAP Enterprise Resource Planning (ERP) 6.0 SPS15 or higher: SAP ERP 6.0 SPS 15 or higher SAP ERP 6.0 EhP2 SPS 06 or higher SAP ERP 6.0 EhP3 SPS 05 or higher SAP ERP 6.0 EhP4 SPS 05 or higher SAP ERP 6.0 EhP5 SPS 03 or higher SAP ERP 6.0 EhP6 SPS 01 or higher

ERP installations prior to SAP NetWeaver 7.4: Back-End Event Provider - Software

Component IW_BEP 200 SP 07

http://help.sap.com/erp SAP Notes for SAP ERP and SAP SRM [page 9]

For the Approve Shopping Cart application based on SAP SRM: SRM 7.0 SPS 02

http://help.sap.com/srm SAP Notes for SAP ERP and SAP SRM [page 9]

For the My Shopping Cart and Track Shopping Carts applications based on SAP SRM: SRM 7.0 SP 11 SAP SRM User Interface Add-On 1.0 SP 01

http://help.sap.com/srm SAP Notes for SAP ERP and SAP SRM [page 9] Additional Prerequisites for My Shopping Cart and

Track Shopping Carts [page 28]

Connection Prerequisites

Prerequisites More Information Connect SAP NetWeaver Gateway to your

back-end system (Trusted RFC)Connection Settings: SAP NetWeaver Gateway to SAP Systems

Connect your back-end system to SAP NetWeaver Gateway (Trusted RFC)

Connection Settings on the Back-End System

Approval apps only: Additional system alias for task processing

Create a System Alias [page 63]

SAP Fiori Installation and ConfigurationPrerequisites 2013 SAP AG or an SAP affiliate company. All rights reserved. 5

Browser Prerequisites

For the browser prerequisites and supported operating systems, see the entry for the respective app in the Product Availability Matrix (PAM) on SAP Service Marketplace. In the PAM view, choose Technical Release Information Web Browser Platforms .

1.2 Required SAP NetWeaver Gateway Components Use the table below to determine the relevant SAP NetWeaver Gateway 2.0 components for your SAP NetWeaver installation, as well as any relevant SAP Notes.SAP NetWeaver Product Version

SAP NetWeaver Gateway Component

Required Software ComponentsComponent Support Package

SAP NetWeaver 7.0SAP EhP1 for SAP NetWeaver 7.0

Gateway Server Core NW 700/701

GW_CORE 190SAP IW FND 240

SP 03SP 03

Gateway PGW IW_PGW 1001)

IW_BEP 2002)SP 04SP 07

SAP EhP2 for SAP NetWeaver 7.0

Gateway Server Core NW 702

GW_CORE 200SAP IW FND 250SAP WEB UIF 7.01

SP 07SP 07SP 11



SAP EhP3 for SAP NetWeaver 7.0

Gateway Server Core NW 703/731

GW_CORE 200SAP IW FND 250SAP WEB UIF 7.31

SP 07SP 07SP 09



SAP NetWeaver 7.4 Part of SAP NetWeaver 7.43)

GW_FND 740 SP 04

Gateway PGW NW 740 IW_PGW 1001) SP 03

1) Only relevant for the following SAP Fiori approval apps: Approve Requests, Approve Shopping Carts, Approve Leave Requests, Approve Purchase Orders, Approve Requisitions, Approve Purchase Contracts2) Only relevant for SAP Fiori apps based on SAP ERP and SAP Fiori Approve Requests


Prerequisites

3) As from SAP NetWeaver 7.4, the components GW_CORE, IW_FND, and IW_BEPP are replaced a new software component for the SAP NetWeaver Gateway foundation, SAP_GWFND. This component is delivered as part of SAP NetWeaver 7.4.

Related Information

SAP NetWeaver Gateway 2.0 on SAP Help PortalSAP NetWeaver Gateway Installation PrerequisitesInstalling SAP NetWeaver Gateway Components

1.3 SAP Notes for SAP NetWeaver GatewayThe following table lists the SAP Notes that must be applied to SAP NetWeaver Gateway:SAP Note Number Description

1931156 General Information: SAP Netweaver Gateway 2.0

1.4 Required User Interface Add-On Components Use the table below to determine the components of the User Interface Add-On 1.0 for SAP NetWeaver that are required for your SAP NetWeaver installation.Your SAP NetWeaver Intstallation Required User Interface Add-On Components

Software Component Support PackageFor installations below SAP NetWeaver 7.4:

All installations below SAP NetWeaver 7.4 UI_INFRA 100 SP 06UI2_700 100 SP 06UI2_FND 100 SP 06UI2_SRVC 100 SP 06UISAPUI5 100 SP 06, latest UI5 library

SAP EhP1 for SAP NetWeaver 7.0 or higher UI2_701 100 SP 06UI2_702 100 SP 06

SAP EhP3 for SAP NetWeaver 7.1 or higherSAP EhP1 for SAP NetWeaver 7.3 or higher

UI2_731 100 SP 06


Your SAP NetWeaver Intstallation Required User Interface Add-On ComponentsSoftware Component Support Package

SAP NetWeaver 7.4 SAP_UI 740

NoteSAP_UI is the successor of the UI2* and UISAPUI5 software components.

SP 05

1.5 SAP Notes for User Interface Add-On

The following table lists important SAP Notes for the User Interface Add-On for SAP NetWeaver.SAP Note Number Description

1759682 UI Add-on for SAP NetWeaver Central Note

1666368 Installing UI Add-on 1.0 for SAP NetWeaver (below SAP NetWeaver 7.4)

1666369 Support Packages for UI Add-on 1.0 for SAP NetWeaver (below SAP NetWeaver 7.4)

1.6 SAP Notes for SAP NetWeaver AS ABAP

The following table lists the SAP Notes that must be applied to SAP NetWeaver Application Server Advanced Business Application Programming (AS ABAP):SAP Note Number Description

1774246 Mobile Inbox: Inbox API

1799549 SAP WAPI_CREATE_OUTBOX: Optional parameter

1805986 Additional parameter for SAP WAPI_ATTACHMENT_ADD

1754533 Enhancement of WAPI trace

1809628 Additional methods for IF_SWF_UTL_WAPI_FRAMEWORK


Prerequisites

1.7 SAP Notes for SAP ERP and SAP SRMThe following table lists the SAP Notes that must be applied in the back-end application.SAP Note Number Description



1754533 Enhancement of WAPI trace

1809628 Additional methods for IF_SWF_UTL_WAPI_FRAMEWORK

For Approval apps: (SAP_BASIS component): 1774246

Mobile Inbox: Inbox API


2 Install

2.1 Setup ChecklistThis checklist lists, in order, the tasks that must be performed to install and configure the SAP Fiori applications. It also provides links to related information and instructions.

Task More Information1 Install

Deploy the SAP Fiori packages on the SAP Business Suite back-end system

See Integration and SAP UI5 Components for SAP Fiori Applications [page 12]

See Install Add-On Components [page 11]

Install Add-On Components on SAP NetWeaver Gateway

2 Configure SAP Business Suite Components To configure SAP Business Suite Components: Define Users and Authorizations [page

14] Configure the Back-End Event Publisher

[page 15] Specify Connection Settings to SAP

NetWeaver Gateway [page 16]

3 Configure SAP NetWeaver Gateway Settings Define Users and Authorizations Specify Language Settings

NoteThe languages configured on the back end must correspond to the languages configured for the SAP Fiori apps.

4 Configure SAP Netweaver Gateway Components Activate Gateway and UI5 Services in SICF See Activate Gateway and UI5 Services in

SICF [page 17] Configure App-Specific Gateway Services See Activate Gateway and UI5 Services in

SICF [page 17]5 Configure Specific Apps See the configuration instructions specific to

your application: Configure Employee Apps [page 24] Configure Manager Apps [page 33] Configure Sales Rep Apps [page 47]


Install

Task More Information Configure Purchasing Agent Apps [page

56]

NoteYou must also activate Standard Mode (Odata) Services for the following Manager approval applications:

Approve RequestsApprove Leave RequestsApprove Shopping RequestsApprove Purchase OrdersApprove Purchase RequisitionsApprove Purchase Contracts

For more information, see Activate and Maintain Services.

6 Access the applications Access SAP Fiori Apps [page 20]

Release Information Note

For information about the latest support package stack updates, see SAP Note 1917162 . This SAP Note also references the Release Information Notes for the individual SAP Fiori apps.

2.2 Install Add-On ComponentsTo install the appropriate integration and SAP UI5 components on your SAP NetWeaver Gateway 2.0 server, perform the following steps:1. Execute the transaction SAINT to access the add-on installation tool.

For more information on using SAINT, read the SAP Add-On Installation Tool documentation.2. Start the installation in the add-on installation tool.

Related Information

Integration and SAP UI5 Components for SAP Fiori Applications [page 12]The following table lists the UI and integration components for each SAP Fiori application. The UISRA* components need to be installed on the Gateway server and the SRA* components on the backend server.

SAP Fiori Installation and ConfigurationInstall 2013 SAP AG or an SAP affiliate company. All rights reserved. 11

2.2.1 Integration and SAP UI5 Components for SAP Fiori ApplicationsThe following table lists the UI and integration components for each SAP Fiori application. The UISRA* components need to be installed on the Gateway server and the SRA* components on the backend server.You can download the SAP Fiori apps from SAP Service Marketplace:

1. Open the software download center at http://service.sap.com/swdc .2. Choose Installations and Upgrades or Support Packages and Patches Search for Installations and

Upgrades (or Search for Support Packages and Patches). 3. Enter the search term Fiori.4. Navigate to the relevant app using the product version listed in the table below, for example, FIORI

TIMERECORDING.Ensure that the SAP NetWeaver Gateway UI component and the OData integration component installed in your landscape both have the latest support package level. For an overview of the available support package stacks, see the SAP Note 1917162 .

NoteSAP Fiori support packages are incremental and do not consolidate all previous deliveries. You need to install SAP Fiori support packages in sequence.

Table 1: Scenario-Specific UI5 and OData ComponentsApplication Product Version on SAP

Service MarketplaceUI Component OData Component in

SAP Business SuiteEmployeeMy Timesheet FIORI TIMERECORDING UISRA002 100 SRA002 600My Shopping Cart FIORI SHOPCARTCRE UISRA014 100 Uses SRM component

SRMNXP01 100Track Shopping Carts FIORI SHOPCARTTRK UISRA011 100 Uses SRM component

SRMNXP01 100My Travel Requests FIORI TRAVELREQCRE UISRA004 100 SRA004 600My Leave Requests FIORI LEAVEREQCRE UIHCM002 100 GBHCM002 (SP 10) +

SAP NotesMy Paystubs FIORI PAYSLIPLOOK UISRA006 100 SRA006 600My Benefits FIORI MYBENENRO UISRA007 100 SRA007 600ManagerMy Spend FIORI MYDEPTSPEND UISRA012 100 SRA012 600Approve Requests FIORI GENERICINBX UIGIB001 100 Included in IW_PGW 100

(SP 04)


Install

Application Product Version on SAP Service Marketplace

UI Component OData Component in SAP Business Suite

Approve Leave Requests FIORI LEAVEREQAPPR UIHCM003 100 GBHCM003 600 (SP 08) + SAP Notes

Approve Shopping Carts FIORI SHOPCARTAPPR UISRM001 100 GBSRM001 700 (SP 10) + SAP Notes

Approve Travel Expenses FIORI TRAVELEXPAPPR UISRA008 100 SRA008 600Approve Travel Requests FIORI TRAVELREQAPPR UISRA009 100 SRA009 600Approve Purchase Orders FIORI

PURCHASEORDAPPRUIAPP002 100 GBAPP002 600

Approve Timesheets FIORI TIMESHTAPPR UISRA010 100 SRA010 600Approve Purchase Contracts

FIORI PURCHASECONTAPPR

UISRA001 100 SRA001 600

Approve Requisitions FIORI PURCHASEREQAPPR

UIAPP001 100 GBAPP002 600

Sales RepresentativesCheck Price and Availability

FIORI PRICECHECK UISRA016 100 SRA016 600

Create Sales Orders FIORI ORDERCRE UISRA017 100 SRA017 600Track Sales Orders FIORI ORDERSTSTRK UISRA018 100 SRA018 600Track Shipments FIORI SHIPTRK UISRA019 100 SRA019 600Change Sales Orders FIORI ORDERCHG UISRA018 100 and

UISRA003 100SRA018 600 and SRA003 600

Customer Invoices FIORI INVOICEBILL UISRA021 100 SRA021 600Purchasing AgentOrder from Requisitions FIORI ORDERPOREQ UISRA013 100 SRA013 600 + SAP NotesTrack Purchase Order FIORI TRACKPO UISRA020 100 SRA020 600 + SAP Notes

NoteFor some SAP Fiori applications, you must also implement SAP Notes to complete the installation. For more information, see the sections for the individual applications.

Related Information

Configure Employee Apps [page 24]Employee Apps are used to submit requests for leave and travel, view paystubs and benefits, manage time entry data, and create shopping carts.


Configure Manager Apps [page 33]Manager apps are used to approve requests for leave and travel, purchase orders, requisitions, shopping carts, timesheets, and purchase contracts. The apps can also be used to view budget and spend information.Configure Sales Rep Apps [page 47]Sales representatives use the apps to check price and availability; create, track, and change sales orders; track shipments, and view information about customer invoices.Configure Purchasing Agent Apps [page 56]The purchasing agent uses the apps to perform tasks such as ordering from requisitions and tracking purchase orders.

2.3 Configure SAP Business Suite Components

2.3.1 Define Users and Authorizations

Set up users and assign authorizations to your users in the back-end system.Back-end users with specific granted authorizations are required. In most cases, users in the back-end system already exist and have application-specific authorizations. SAP delivers back-end PFCG roles for every transactional app. These roles comprise references to the OData services that are required to use the applications. Based on the OData service reference, authorization proposals of the OData service can be used to create authorization profiles.1. Create a technical service (service agnostic) role.

a) When you enter the authorization maintenance for the role, use the role template /IWBEP/RT_MGW_USR. It contains the authorization for the OData Channel RFC function group /IWBEP/FGR_MGW_CLIENT_IF.

b) Add the authorization object S_RFCACL (authorization for a trusted RFC destination between SAP NetWeaver Gateway and SAP back-end systems).

c) Maintain the correct authorization values.d) Generate the profile.

2. Assign this technical role to the application users.3. Copy the application-specific SAP roles in the table below into the customer namespace and maintain the

authorization values correctly.

Application RoleEmployeeMy Timesheet SAP_HCM_TS_CRE_APPMy Shopping Cart SAP_SRM_SC_CREATE_APPTrack Shopping Carts SAP_SRM_SC_TRACK_APPMy Travel Requests SAP_FIN_TR_CRE_APPMy Leave Requests SAP_GBHCM_LEAVE_REQUEST_EMPLMy Paystubs SAP_HCM_PS_MON_APP


Install

Application RoleMy Benefits SAP_HCM_BEN_MON_APPManagerMy Spend SAP_FIN_SPE_MON_APPApprove Requests No special role requiredApprove Leave Requests SAP_GBHCM_LEAVE_APPROVAL_MGRApprove Shopping Carts SAP_SRM_SC_APV_APPApprove Travel Expenses SAP_FIN_TE_APV_APPApprove Travel Requests SAP_FIN_TR_APV_APPApprove Purchase Orders SAP_MM_PO_APV_APPApprove Timesheets SAP_HCM_TS_APV_APPApprove Purchase Contracts SAP_MM_PC_APV_APPApprove Requisitions SAP_MM_PR_APV_APPSales RepresentativeCheck Price and Availability SAP_SD_PRAV_MON_APPCreate Sales Orders SAP_SD_SO_CRE_APPTrack Sales Orders SAP_SD_SO_MON_APPTrack Shipments SAP_LE_SHIP_MON_APPChange Sales Orders SAP_SD_SO_MAN_APPCustomer Invoices SAP_SD_INV_MON_APPPurchasing AgentOrder from Requisitions SAP_MM_PURORD_OR_APPTrack Purchase Order SAP_MM_PURORD_TPO_APP

Alternatively, create a customer role based on SU22 entries of the SAP R3TR/IWSV service (S_SERVICE).4. Assign the new role(s) to the application users.

2.3.2 Configure the Back-End Event Publisher

Specify the settings for the OData Channel in the BEP component (IW_BEP).Depending on your underlying SAP NetWeaver release, the configuration settings for OData Channel and the structure in the Implementation Guide (IMG) may differ. For more information, see Backend Event Publisher (BEP) Configuration.

NoteThis step is not relevant for the My Shopping Cart and Track Shopping Carts applications.


Related Information

Configure Backend Event Publisher

2.3.3 Specify Connection Settings to SAP NetWeaver GatewaySpecify the settings that can be used by the OData Channel and the BEP component to establish the connection from your ERP system to SAP NetWeaver Gateway.Depending on your underlying SAP NetWeaver release the configuration settings for OData Channel and the structure in the Implementation Guide (IMG) may differ. See OData Channel Configuration in the SAP Library for more details, available via the web link in Related Links.For more information on connection settings, see the Connection Settings on the Backend System topic in the SAP Library for SAP NetWeaver Gateway on the SAP Help Portal, available via the links in Related Links.

Related Information

OData Channel ConfigurationConnection Settings in the Backend SystemSAP NetWeaver Gateway

2.4 Configure SAP NetWeaver Gateway Components

2.4.1 Configure App-Specific Gateway Services

To configure gateway services, go to the IWFND maint_service transaction, add the service for the application, and check that it is activated.1. In your Gateway system, go to transaction /IWFND/maint_service.

NoteYou must repeat the following steps (2 to 6) for each SAP Fiori application you installed.

2. Select Add Service.3. Enter the system ALIAS for the target ERP system that you defined when configuring the connection between

Gateway and the ERP system.4. Select Get Services, then select the service for the application that you want to configure.


Install

5. Click the Technical service name.6. In the Add Service window, select local object and validate.7. Return to the main_service main screen.8. Check that all SAP Fiori services are activated.

Related Information

Gateway Services for Applications [page 18]This table lists the SAP NetWeaver Gateway services required for SAP Fiori applications.Activate and Maintain Services

2.4.2 Activate Gateway and UI5 Services in SICF

To activate the required Gateway services, go the required transaction, and check the services are active:1. In your Gateway system, go to transaction SICF.2. Select Execute.3. Navigate to the relevant namespace:

For the Approve Requests app: sap opu odata iwpgw For the My Leave Requests and Approve Leave Requests apps: sap opu odata gbhcm For other SAP Fiori apps: sap opu odata sap

4. Check that all Gateway services for the SAP Fiori applications you want to use are active: Right-click each service. Activate Service should be inactive (grayed out). If Activate Service is active, right-click each service and select Activate Service.

5. Navigate to sap bc ui5_ui5 sap .6. Check that all ICF nodes for the installed applications are active:

Right-click each service. Activate Service should be inactive (grayed out). If Activate Service is active, right-click each service and select Activate Service.

Related Information

Gateway Services for Applications [page 18]This table lists the SAP NetWeaver Gateway services required for SAP Fiori applications.SICF Services for UI Applications [page 19]This table lists the relevant SICF services for the UI applications of SAP Fiori applications.


2.5 Components and Services

2.5.1 Gateway Services for ApplicationsThis table lists the SAP NetWeaver Gateway services required for SAP Fiori applications.

Application Name External Service NameEmployeeMy Travel Requests sra004_srvMy Leave Requests leaverequest, version 2My Paystubs sra006_srvMy Benefits sra007_benefits_srvMy Timesheet sra002_timesheet_srvMy Shopping Cart Uses services from the SAP SRM User Interface Add-On

(namespace /SRMNXP/)Track Shopping Carts Uses services from the SAP SRM User Interface Add-On

(namespace /SRMNXP/)ManagerApprove Leave Requests leaveapprovalApprove Shopping Carts cartapproval, version 2Approve Purchase Orders gbapp_poapprovalApprove Requisitions gbapp_prapprovalApprove Requests taskprocessingApprove Travel Requests sra009_srvApprove Timesheets sra010_timesheet_approval_srvApprove Travel Expenses sra008_srvApprove Purchase Contracts sra001_pcapproval, version 1My Spend sra012_spend_srvSales RepresentativesCheck Price and Availability sra016_price_avail_srvCustomer Invoices sra021_srvChange Sales Orders sra018_so_tracking_srvCreate Sales Orders sra017_salesorder_create_srvTrack Sales Orders sra018_so_tracking_srvTrack Shipments sra019_shipment_tracking_srvPurchasing AgentOrder From Requisitions sra013_po_from_pr_srv


Install

Application Name External Service NameTrack Purchase Order sra020_po_tracking_srv

2.5.2 SICF Services for UI Applications

This table lists the relevant SICF services for the UI applications of SAP Fiori applications.

Application Name Service NameLaunch Page for Tile CHIPs /ui2/launchpageEmployeeMy Travel Requests ui5_fi_trreq_crMy Paystubs ui5_hcm_ps_monMy Benefits ui5_hcm_ben_ovwMy Leave Requests ui5_hcm_lr_crMy Timesheet ui5_hcm_ts_manMy Shopping Cart ui5_srm_sc_crTrack Shopping Cart ui5_srm_sc_monManagerApprove Leave Requests ui5_hcm_lr_apvApprove Shopping Carts ui5_srm_sc_apvApprove Purchase Orders ui5_mm_po_apvApprove Requisitions ui5_mm_pr_apvApprove Travel Requests ui5_fi_trreq_apvApprove Timesheets ui5_hcm_tsaApprove Purchase Contracts ui5_mm_pc_apvApprove Travel Expenses ui5_fi_trex_apvApprove Requests ui5_ca_all_apvMy Spend ui5_co_spe_monSales RepresentativeCheck Price and Availability ui5_sd_prav_monCustomer Invoices ui5_sd_inv_monChange Sales Orders ui5_sd_so_manTrack Shipments ui5_sd_ship_monCreate Sales Order ui5_sd_so_crTrack Sales Order ui5_sd_so_mon


Application Name Service NamePurchasing AgentOrder From Requisitions ui5_mm_popr_crTrack Purchase Order ui5_mm_po_tr

2.6 Access Apps

2.6.1 Access SAP Fiori AppsUsers can access SAP Fiori applications directly or via the home page (the launch page).

Related Information

SAP Fiori App URLs [page 20]To open a SAP Fiori application directly, use the relative URL listed in this table.Add Apps to the User's Home Page [page 21]You define which SAP Fiori applications appear on a user's home page (launch page) by assigning users to predefined roles.

2.6.1.1 SAP Fiori App URLsTo open a SAP Fiori application directly, use the relative URL listed in this table.

NoteIf you want to embed the SAP Fiori application into an existing portal page, add the URL parameter backToHome=true . This enables the user to return to the portal page from the application. Example:

/sap/bc/ui5_ui5/sap/ui5_hcm_lr_cr/index.html?backToHome=true

Table 2: Relative URLs for SAP Fiori ApplicationsApplication URLEmployeeMy Benefits /sap/bc/ui5_ui5/sap/ui5_hcm_ben_ovw/index.htmlMy Leave Requests /sap/bc/ui5_ui5/sap/ui5_hcm_lr_cr/index.htmlMy Pay Stubs /sap/bc/ui5_ui5/sap/ui5_hcm_ps_mon/index.html


Install

Application URLMy Shopping Cart /sap/bc/ui5_ui5/sap/ui5_srm_sc_mon/index.html?create=trueMy TimeSheet /sap/bc/ui5_ui5/sap/ui5_hcm_ts_man/index.htmlMy Travel Requests /sap/bc/ui5_ui5/sap/ui5_fi_trreq_cr/index.htmlTrack Shopping Carts /sap/bc/ui5_ui5/sap/ui5_srm_sc_mon/index.htmlManagerApprove Leave Requests /sap/bc/ui5_ui5/sap/ui5_hcm_lr_apv/index.htmlApprove Purchase Contracts /sap/bc/ui5_ui5/sap/ui5_mm_pc_apv/index.htmlApprove Purchase Orders /sap/bc/ui5_ui5/sap/ui5_mm_po_apv/index.htmlApprove Requests The target URL depends on your custom workflow scenario. For more

information, see Configure Launch Settings for Custom Workflows [page 61].

Approve Requisitions /sap/bc/ui5_ui5/sap/ui5_mm_pr_apv/index.htmlApprove Shopping Carts /sap/bc/ui5_ui5/sap/ui5_srm_sc_apv/index.htmlApprove Timesheets /sap/bc/ui5_ui5/sap/ui5_hcm_ts_apv/index.htmlApprove Travel Expenses /sap/bc/ui5_ui5/sap/ui5_fi_trex_apv/index.htmlApprove Travel Requests /sap/bc/ui5_ui5/sap/ui5_fi_trreq_ap/index.htmlMy Spend /sap/bc/ui5_ui5/sap/ui5_co_spe_mon/index.htmlSales RepresentativesChange Sales Orders /sap/bc/ui5_ui5/sap/ui5_sd_so_mon/index.html?change=trueCheck Price and Availability /sap/bc/ui5_ui5/sap/ui5_sd_prav_mon/index.htmlCreate Sales Orders /sap/bc/ui5_ui5/sap/ui5_sd_so_cr/index.htmlCustomer Invoices /sap/bc/ui5_ui5/sap/ui5_sd_inv_mon/index.htmlTrack Sales Orders /sap/bc/ui5_ui5/sap/ui5_sd_so_mon/index.htmlTrack Shipments /sap/bc/ui5_ui5/sap/ui5_sd_ship_mon/index.htmlPurchasing AgentOrder From Requisitions /sap/bc/ui5_ui5/sap/ui5_mm_pr_cr/index.htmlTrack Purchase Orders /sap/bc/ui5_ui5/sap/ui5_mm_po_trR/index.html

2.6.1.2 Add Apps to the User's Home Page

You define which SAP Fiori applications appear on a user's home page (launch page) by assigning users to predefined roles.


NoteAll SAP Fiori applications are preconfigured in the launch page catalog, except for the Approve Requests application. If you are using Approve Requests to process custom approval workflows or workflows delivered by SAP, you need to add the application to the launch page catalog yourself.

1. In your SAP NetWeaver Gateway system, call transaction PFCG (Role Maintenance).2. Assign users to the predefined launch page role for your SAP Fiori application.

Table 3: SAP Fiori Roles for the Launch PageApplication Role for Launch PageEmployeeMy Benefits SAP_SRA007_HCM_BEN_OVWMy Leave Requests SAP_HCM002_HCM_LVRQ_CRMy Pay Stubs SAP_SRA006_HCM_PS_MONMy Shopping Cart SAP_SRA014_SRM_SC_CRMy TimeSheet SAP_SRA002_HCM_TS_MANMy Travel Requests SAP_SRA004_FI_TRREQ_CRTrack Shopping Carts SAP_SRA011_SRM_SC_MONManagerApprove Leave Requests SAP_HCM003_HCM_LVRQ_APRApprove Purchase Contracts SAP_SRA001_MM_PC_APVApprove Purchase Orders SAP_APP002_MM_PO_APRApprove Requests The role depends on your custom settings. For more information, see

Configure Launch Settings for Custom Workflows [page 61].Approve Requisitions SAP_APP001_MM_PR_APRApprove Shopping Carts SAP_SRM001_SRM_SHOP_APRApprove Timesheets SAP_SRA010_HCM_TS_APVApprove Travel Expenses SAP_SRA008_FI_TREX_APVApprove Travel Requests SAP_SRA009_FI_TRREQ_APMy Spend SAP_SRA012_CO_SPE_MONSales RepresentativesChange Sales Orders SAP_SRA003_SD_SO_CHGCheck Price and Availability SAP_SRA016_SD_PRAV_MONCreate Sales Orders SAP_SRA017_SD_SO_CRCustomer Invoices SAP_SRA021_SD_INV_MONTrack Sales Orders SAP_SRA018_SD_SO_MON


Install

Application Role for Launch PageTrack Shipments SAP_SRA019_SD_SHIP_MONPurchasing AgentOrder From Requisitions SAP_SRA013_MM_PR_CRTrack Purchase Orders SAP_SRA020_MM_PO_TR

Users see the tiles for the assigned SAP Fiori applications on the home page.To call the home page, enter the following URL: https:// : /sap/bc/ui5_ui5/ui2/launchpage/home.html.The launch page is part of the User Interface Add-On for SAP NetWeaver. For more information about setting up the launch page, see the documentation on SAP Help Portal at http://help.sap.com/nw-uiaddon > Application Help > User Interface Add-On 1.0 SPS04 for SAP NetWeaver.For more information about setting up user roles, see the documentation for SAP NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Search for Configuration of User and Role Administration.

Related Information

User Interface Add-On 1.0 SPS04 for SAP NetWeaverSAP NetWeaver Platform


3 Employee Apps

3.1 Configure Employee Apps

Employee Apps are used to submit requests for leave and travel, view paystubs and benefits, manage time entry data, and create shopping carts.

Table 4: Employee AppsApp Description Configuration

informationMy Leave Requests Create and submit leave requests on a desktop or

mobile device. Track the status of your requests, and see your current leave balance.

My Leave Requests [page 31]

My Paystubs Check and manage, at any time through mobile devices or desktop, a digital version of all your pay stubs issued by the company for each payroll period.

See My Paystubs [page 24]

My Shopping Cart A one-stop desktop and mobile solution to employees' enterprise shopping needs; use the app to create the cart, and select approvers. The app leverages the powerful SAP(R) Supplier Relationship Management (SRM) catalog search capability to enable easy shopping and workflow approval.

See My Shopping Cart [page 26]

Track Shopping Carts Track the status of your shopping cart. Track Shopping Carts [page 29]

My Timesheet Manage your time entry data quickly, efficiently, anywhere, at any time on desktop or mobile device.

See My Timesheet [page 30]

My Travel Requests Manage - create, submit, edit, and check status - your travel requests on desktop as well as on mobile device.

Apply the corrections contained in SAP Note 1887701 .

My Benefits View an overview of your enrolled benefit plans throughout the year, and all the details of all benefits offered by the company.

See My Benefits [page 29]

3.2 My Paystubs

To enable the SAP Fiori My Paystubs application, you must perform a number of configuration tasks.


Employee Apps

Tasks More Information1 Apply the fix in SAP Note 890828 SAP Note 890828 , HRBG & HRUS: ABAP dump in

class CL_HR_PAY_RESULT_GB/US, is available from the SAP Service Marketplace.

NoteYou need to deploy this fix only if it has not yet been deployed.

2 Deploy the business add-in (BAdI), XSS_REM_INTERFACE using the classic BAdI implementation.

The XSS_REM_INTERFACE BAdI is required to filter pay stub statements after a payroll run. This BAdI, which is present in the ECC system, belongs to the software component EA-HRRXX. Ensure that the following method of the BAdI is implemented: IF_EX_XSS_REM_INTERFACE~PROVIDE_FILTERED_RGDIR. Deploy the BAdI as a classic BAdI.For instructions on how to activate BAdI implementations, see Steps To Activate BAdI Implementations.

3 Configure parameters to allow employees to view the salary statement as a PDF-based form. Your employees can print the salary statement from the web application or save it.Pay stubs are displayed in SAP Firoi in the same manner as they are displayed in Employee Self-Service (ESS) Applications.

NoteSAP Fiori does not support Concurrent Employment.

NoteIf you launch the application from an icon on the home screen of an iPhone or an iPad, it opens full-screen in a browser instance that does not contain a back button.

Refer to the following document in the SAP Library for detailed information: Business Package for Employee Self-Service (SAP ERP) 1.0 and expand the pages as follows: Employee Self-Service (ESS) Applications Benefits and Payment Salary Statement

SAP Fiori Installation and ConfigurationEmployee Apps 2013 SAP AG or an SAP affiliate company. All rights reserved. 25

3.3 My Travel RequestsTo enable the SAP Fiori My Travel Requests application, you must perform a required configuration task.The following SAP Note must be applied:

SAP Note 890828 HRGB & HRUS: ABAP dump in class CL_HR_PAY_RESULT_GB/US

3.4 My Shopping CartTo enable the SAP Fiori My Shopping Cart app, you must ensure that all prerequisites are in place and perform a number of configuration tasks.

Related Information

Additional Prerequisites for My Shopping Cart and Track Shopping Carts [page 28]Additional prerequisites apply for the SAP Fiori My Shopping Cart and Track Shopping Carts applications. These applications do not use OData services for ABAP integration. Instead, they re-use SAP NetWeaver Gateway services from the SAP SRM User Interface Add-On.

3.4.1 SRM Services Used by My Shopping Cart and Track Shopping CartsThe following table lists the SAP SRM services used by the SAP Fiori My Shopping Cart and Track Shopping Carts applications. These services are provided by the SAP SRM User Interface Add-On.To select these services in the service catalog, filter for the namespace /SRMNXP/ .

External Service Name Service DescriptionACC_ASS_SEARCH_HELP Account assignment search help ACC_ASSIGN_CATEGORY Service for account assignment category descriptionACC_ASSIGN_FLD_METADATA Service for account assignment file metadataACC_ASSIGN_SRH Account assignment search help serviceAPPROVAL_SERVICE Approval serviceAPVR_SRCHLP Search help for approver and reviewerCATALOG_LAUNCH_DETAILS Catalog launch details


Employee Apps

External Service Name Service DescriptionCOUNTRY_SH_SERVICE Service for country searchCROSS_CATALOG_SEARCH Cross catalog searchCTLG_CATEGORIES Service to list catalog categoriesCUR_EXCH_RATE_SERVICE Service for currency exchange ratesDOMAIN_VALUES Domain valuesGETDEFUSRSET Service for getting default user settings GRECIPIENT_SH_SERVICE SH for goods recipientITEMHISTORY_SERVICE Item history serviceLANGUAGE Service for languageLOGICAL_SYSTEM Service for logical systemNOTES_SERVICE Service for notesORDERTRACK_SERVICE Order track servicePC_SH_SERVICE Service for product category search helpPERSONAL_MARKERS Personal marker servicePLANT_SH_SERVICE Search help for plantPRICE_SCALES Item price scalesPRO_DET_IMAGES_SERVICE Product details image servicePRO_DET_SERVICE Service for product detailsPRODUCT_MASTER Service for product masterPRODUCT_TYPE Service for product typeREC_ORDERS Data provider for recent ordersREGION_SH_SERVICE Service for region searchREVIEW Review service for rating and reviewSEARCH_TERMS_SERV Search terms serviceSHIP_ADDR_SH_SERVICE Service for shipping addressSHOPPING_CART Service for shopping cartSRCH_FILTER Search filter modelSRMSHOPPING_CART SRM shopping cart PDO serviceSTLOCATION_SH_SERVICE Search help for storage locationSUPPLIER_SH_SERVICE Service for supplier search helpUSER_CATALOG_LIST User catalog providerUSERS_LIST User list under one user name


External Service Name Service DescriptionUTIL Service for utilities

3.4.2 Additional Prerequisites for My Shopping Cart and Track Shopping Carts

Additional prerequisites apply for the SAP Fiori My Shopping Cart and Track Shopping Carts applications. These applications do not use OData services for ABAP integration. Instead, they re-use SAP NetWeaver Gateway services from the SAP SRM User Interface Add-On.The table below outlines the critical installation and configuration steps that you need to complete in your SRM system before installing these two SAP Fiori applications.

Prerequisites Install the central SAP NetWeaver Gateway components GW_CORE and IW_FND in your SAP SRM system. Install the SAP SRM User Interface Add-On 1.0 SP 01 in your SAP SRM system. Connect SAP NetWeaver Search and Classification (TREX) to your SAP SRM system and enable OCI5 for the

catalogs. If you use the Lean Inbox in SAP SRM:

Activate the soft switch SRM_700_LOCAL_MENU in your SAP SRM system. Customize the SAP SRM User Interface Add-On.

For the complete list of prerequisites, see the appendix of the Master Guide for the SAP SRM User Interface Add-On.

Related Information

Master Guide for SAP SRM User Interface Add-On 1.0Configuration Cookbook for the SAP SRM User Interface Add-On (SRM Community)SAP SRM User Interface Add-On on SAP Help PortalSRM Services Used by My Shopping Cart and Track Shopping Carts [page 26]The following table lists the SAP SRM services used by the SAP Fiori My Shopping Cart and Track Shopping Carts applications. These services are provided by the SAP SRM User Interface Add-On.


Employee Apps

3.5 Track Shopping Carts

To enable the SAP Fiori Track Shopping Carts app, you must ensure that all prerequisites are in place and perform a number of configuration tasks.

Related Information

Additional Prerequisites for My Shopping Cart and Track Shopping Carts [page 28]Additional prerequisites apply for the SAP Fiori My Shopping Cart and Track Shopping Carts applications. These applications do not use OData services for ABAP integration. Instead, they re-use SAP NetWeaver Gateway services from the SAP SRM User Interface Add-On.

3.6 My Benefits

To enable the SAP Fiori My Benefits application, you must must perform a number of configuration tasks.Task More Information

1 Activate HR-BEN business function Software component dependencies are already maintained in PPMS, so the SAINT tool takes care of the dependency validation.Because the SAP Fiori My Benefits application relies on the configuration data available for Standard HR Benefits module, it is a mandatory prerequisite for the application to have HR Benefits (HR-BEN) available and configured.

2 Map communication types Map 0105 communication type for the employee PERNR to the system user ID.

3 Install Gateway Server Components For more information see: Integration and SAP UI5 Components for SAP Fiori Applications [page 12]

4 Enable the SICF Services for the Gateway

Service name: SRA007_BENEFITS_SRV

5 Enable the SICF Services for UI5 Service name: UI5_HCM_BEN_OVW6 Ensure that the User Role is shipped

with the application.Role: SAP Standard MSS

7 Deploy the Business Add-in SRA007_BADI_BENEFITS

For instructions on how to activate BAdI implementations, see Steps To Activate BAdI Implementations and Deploy Business Add-In XSS_REM_INTERFACE.


Task More Information8 Verify IMG Configuration In the back-end system, call transaction SIMGH and open the

My Benefits node.

3.7 My Timesheet

To enable the SAP Fiori My Timesheet application, you must ensure that all prerequisites are set up and perform a number of configuration tasks.

NoteEnsure that you check the Prerequisites Checklist [page 4] and the Setup Checklist [page 10] before configuring My Timesheet.

Tasks More Information1 Ensure application-specific

prerequisite software is installed.Install and configure ERP Central Component (ECC) 6.0. For more information, see the SAP Help Portal.

2 Confirm the Gateway Server components are installed.

In addition to installing the components in the installation and configuration instructions (see Integration and SAP UI5 Components for SAP Fiori Applications [page 12]), install and configure the ECC EA-HR600 component. If the add-on EA-HRGXX level is 604, reference SAP Note 1158538 .

3 Start app-specific SICF services for the Gateway.

In addition to installing the components in the installation and configuration instructions (see Setup Checklist [page 10]) Ensure Gateway service SRA002_TIMESHEET_SRV is activated. For more information see, Configure App-Specific Gateway Services [page 16].

4 Set the Business Suite Roles for the app.

My Timesheet uses the Data Entry Profile (DEP) to determine the usage and behavior for the client. The System Administrator maintains the DEP for each user in the CVR parameter.

To set the DEP, from the SAP GUI, go to SystemUser Profile Own Data .If no DEP is set, the default DEP, ESS, is used. If no default DEP is found, the client receives an error message.

5 Deploy the required Business Add-Ons (BAdIs) for the application.

Deploy the following BAdIs:


Employee Apps

Tasks More Information BADI_SRA002_FIELDRANKINGS - Determines the

order in which cost objects are given importance for display in the cost assignment.

BADI_SRA002_PICKLIST_TXTFILTER - Extends the text search used by the Cost Assignment search. The default is to search for the text in field IDs and descriptions. This BAdI extends the search across other cost object attributes.

BADI_SRA002_QUICKENTRY_BEGDA - Determines the beginning date for calculating missing entries for Auto Entry and the My Timesheet app tile.

BADI_SRA002_QUICKENTRY_PROJ - Determines the proposed Cost Assignment objects in Auto Entry.

BADI_SRA002_WCSTATUSES - Determines the handling of CATS statuses highlighted in the monthly calendar. Allows for mapping other statuses to the three statuses used in My Timesheet.

For more information, see Steps to Activate BAdI Implementations.

3.8 My Leave RequestsTo enable the SAP Fiori My Leave Requests application, you must perform a number of configuration tasks:

Tasks More Information1 Ensure that the prerequisite SAP

Notes have been applied.In addition to the notes specified in the Prerequisites Checklist [page 4], the following notes must be applied: For component GBHCM002:

SAP Note 1625476 : Release Information: SAP Leave Request 2.0.0SAP Note 1621488 : ESS LEA: Customizing attributes are not correctly fetchedSAP Note 1803429 : HCM Leave Request App version 2

For component GBHCM002 (SP08):


Tasks More Information

SAP Note 1852791 : Checkman correction in class /GBHCM/CL_ELR_BEA_AUNITSAP Note 1851674 : Short dump when getting TimeAccountSAP Note 1846479 : Leave requests cannot be created or approved/rejectedSAP Note 1842934 : Leave type is not displayed


Employee Apps

4 Manager Apps

4.1 Configure Manager AppsManager apps are used to approve requests for leave and travel, purchase orders, requisitions, shopping carts, timesheets, and purchase contracts. The apps can also be used to view budget and spend information.

Table 5: Manager AppsApp Description Configuration

InformationMy Spend My Spend provides accurate budget and spend

information anywhere and anytime.My Spend [page 43]

Approve Requests Approve, reject, or forward various approval requests from a desktop or mobile device. Define the approval tasks that are supported by the app. You can add your own approval tasks using the workflow infrastructure, or use the approval workflows provided with the app.

Approve Requests [page 34]

Approve Leave Requests Approve or reject leave requests from direct reports using a desktop or mobile device. Key information for the approval decision is available, including a team calendar that shows overlapping leave requests.

Approve Leave Requests [page 44]

Approve Travel Expenses Review and approve employees' travel expenses on the go or in the office. View details on each receipt, and receive alerts if expenses exceed the budget limits defined in the company travel policy.

Approve Travel Expenses [page 42]

Approve Shopping Carts View pending shopping cart requests and approve entire carts or individual cart items. If necessary, forward approvals to a different employee for further processing.

Approve Shopping Carts [page 36]

Approve Purchase Orders View pending purchase orders and approve them. If necessary, forward approvals to a different employee for further processing.

Approve Purchase Orders [page 37]

Approve Requisitions View pending purchase requisitions and approve them. If necessary, forward approvals to a different employee for further processing. Note that only approval at item level is supported, that is, you can approve the items of requisitions individually. Approval at header level, that is, overall release of a purchase requisition, is not supported.

Approve Requisitions [page 40]

Approve Travel Requests Approve or refuse travel requests on desktop as well as on mobile devices.

Approve Travel Requests [page 41]

SAP Fiori Installation and ConfigurationManager Apps 2013 SAP AG or an SAP affiliate company. All rights reserved. 33

App Description Configuration Information

Approve Timesheets View all pending approvals for employees timesheets and approve timesheets.

Approve Timesheets [page 43]

Approve Purchase Contracts

View pending purchase contracts and approve them. If necessary, forward approvals to a different employee for further processing.

See Approve Purchase Contracts [page 38]

4.2 Approve RequestsTo enable SAP Fiori Approve Requests, you must perform a number of configuration tasks.

Task More Information1 Ensure that all application-specific

prerequisites are in place.You must configure the approval workflow that defined the task type(s) to be used for Approve Requests.

2 Ensure the prerequisite SAP Notes have been applied after the installation of the integration add-ons.

See SAP Notes for SAP ERP and SAP SRM [page 9] for the SAP Notes that apply to all of the following:

Approve RequestsApprove Leave RequestsApprove Shopping CartsApprove Purchase OrdersApprove Purchase RequisitionsApprovel Purchase Contracts

3 Check that you have aspecified the connection settings between SAP NetWeaver Gateway and your back-end system.

Specify Connection Settings to SAP NetWeaver Gateway [page 16]

4 Ensure that you have activated the Gateway service (Task Processing Service) and the UI5 service for the approve request.

Activate Gateway and UI5 Services in SICF [page 17]

5 Check that you have assigned and configured the connection or connections between the Task Gateway Service (/iwpgw/taskprocessing) and your back-end system or systems.

See System Aliases in Activate and Maintain Services. See also Assigning SAP System Alias to OData Service.

6 Define a scenario for your custom approval workflow.

See Define an Approval Scenario [page 58].

7 Assign task decisions to your approval workflow.

See Configure Task Decisions [page 64].


Manager Apps

Task More Information8 This step is optional depending on the

customer scenario.If the step type for the decision is not a User Decision, or if you want to make a new functionality applicable before a decision has been applied on a User Decision item, you must implement the /IWWRK/BADI_WFBEFORE_UPD_IB BAdI for handling the decision runtime.

See Workflow User Exists

9 Configure the launch settings for your custom approval workflow.

For more information, see Configure Launch Settings for Custom Workflows [page 61].

4.2.1 SAP Notes for Approve Requests

The following table lists the SAP Notes that must be applied for SAP Fiori Approve Requests:SAP Note Number Description

1866093 Patches for the Gateway SPS06 required for FIORI

1805831 Workflow Support Decision options Nature (Positive/Negative)

1921495 TGW: File name missing in $expand for attachments

1914864 Filtering by Status and Priority not working in $expand

4.2.2 Task Processing Service User Exits

User exits are the options given for the Task Gateway Service to add custom code into the standard workflow code.There are three possible entry points: When querying inbox or outbox items: changing the task subject At the moment of reading a specific item: changing the task subject and description, and adding extensible

elements Before an action has been taken on a user-decision item, that is, a decision that has been taken by the

approver.See Workflow User Exits


4.2.3 Extensibility

Business Add-Ins (BAdIs) let you extend Approve Requests and add custom code in the Task Gateway service.You can use the following Business Add-Ins: Before Update BAdI (/IWWRK/BADI_WF_BEFORE_UPD_IB) You can use BAdI /IWWRK/

BADI_WF_BEFORE_UPD_IB to handle decision runtime in the following cases: The step type for the workflow task is not User Decision. You want to execute an action before the work item is updated with the user decision.For more information, see SAP Help Portal SAP NetWeaver SAP NetWeaver Gateway SAP NetWeaver Gateway Content Guide SAP NetWeaver Gateway Supported OData Channel Scenarios Workflow Services

Workflow Task Service: Central Hub Deployment with IW_BEP Backend Installation Workflow User Exits . Task Gateway: Change subject in query (/IWPGW/BADI_TGW_TASK_QUERY) You can use this BAdI to change

the task title for all items in the list. Task Gateway: Modify task data (/IWPGW/BADI_TGW_TASK_DATA) You can use this BAdI to change the task

title or task description on the detail screen. Task Gateway: Provide User details (/IWPGW/BADI_TGW_USER_DETAIL) You can use this BAdI to change the

user details.

For more information, see SAP Help Portal SAP NetWeaver SAP NetWeaver Gateway SAP NetWeaver Gateway Content Guide SAP NetWeaver Gateway Supported OData Channel Scenarios Task Gateway Task Gateway User Exits .

4.3 Approve Shopping Carts

To enable SAP Fiori Approve Shopping Carts, you must perform a number of configuration tasks.Task More Information

1 Ensure that all application-specific prerequisites are in place.

You must configure the approval workflow that defined the task type(s) to be used for Approve Shopping Carts.


The following SAP Notes apply to Approve Shopping Carts:

GBSRM001 component: SAP Note 1625382 : Release Information: SAP Cart Approval 2.0.0

GBSRM001 SP08:SAP Note 1792098 : Collective Note: HTML5 WF Inbox - GW Services for SRMSAP Note 1842502 : CAA: Information for limit item is not retrieved


Manager Apps

Task More Information3 Ensure that you have configured the

connection between SAP NetWeaver Gateway and your back-end system.


4 Ensure that you have activated the Gateway services for the task.


5 Check that you have connected the Gateway service for the task to your backend system.

See Activate and Maintain Services.

6 Define a scenario for your approval workflow.

1. Define a scenario ID.2. Assign user roles for which you want to enable the

workflow.3. Assign the task ID of the leave request approval

workflow you have already defined in SAP Business Workflow.

For more information, see Define an Approval Scenario [page 58].

4.4 Approve Purchase OrdersTo enable SAP Fiori Approve Purchase Orders, you must perform a number of configuration tasks.


prerequisites are in place.You must configure the approval workflow that defined the task type(s) to be used for Approve Purchase Orders.

NoteYou must use the release strategy in SAP Materials Management - Purchasing , and you must set up a connection between the release strategy and SAP Business Workflow.



Approve RequestsApprove Leave RequestsApprove Shopping CartsApprove Purchase OrdersApprove Purchase RequisitionsApprove Purchase Contracts


Task More Information

Ensure that SAP Note 1309042 for EA-APPL has been implemented.

3 Ensure that you have configured the connection between SAP NetWeaver Gateway and your back-end system.




5 Check that you have connected the Gateway service for the task to your back-end system.







7 Optional: Implement BAdI Extend Model of Gateway Service for Approve Purchase Orders App, GBAPP_APV_PO_MDP

You can use this BAdI to enhance the entities, that is, the OData model, of the GBAPP_POAPPROVAL Gateway service. You can do this to add your own fields, for example.

NoteYou also have to enhance the user interface to display your own fields.

8 Optional: Implement BAdI Extend Runtime of Gateway Service for Approve Purchase Orders App, GBAPP_APV_PO_RDP

You can use this BAdI to change the runtime data that is returned by the Gateway service and displayed on the user interface of the Approve Purchase Orders app. (This is the main purpose of this BAdI.) This includes the use of pictures, changing the list of attachments and notes displayed, and changing the workflow.For more information, see the BAdI documentation and the example implementation.

4.5 Approve Purchase ContractsTo enable SAP Fiori Approve Purchase Contracts, you must perform a number of configuration tasks.


Manager Apps

Task More Information1 Ensure that all

application-specific prerequisites are in place.

You must configure the approval workflow that defined the task type(s) to be used for Approve Purchase Contracts.

NoteYou must use the release strategy in SAP Materials Management - Purchasing, you must set up a connection between the release strategy and SAP Business Workflow.











1. Define a scenario ID.2. Assign user roles for which you want to enable the workflow.3. Assign the task ID of the leave request approval workflow you have already

defined in SAP Business Workflow.For more information, see Define an Approval Scenario [page 58].

7 Optional: Implement BAdI Extend Model of

You can use this BAdI to enhance the entities, that is, the OData model, of the SRA001_PCAPPROVAL Gateway service. You can do this to add your own fields, for example.


Task More InformationGateway Service for Approve Purchase Contracts App, SRA001_APC_MDP


8 Optional: Implement BAdI Extend Runtime of Gateway Service for Approve Purchase Contracts App, SRA001_APC_RDP

You can use this BAdI to change the runtime data that is returned by the Gateway service and displayed on the user interface of the Approve Purchase Contract app. (This is the main purpose of this BAdI.) This includes the use of pictures, changing the list of attachments and notes displayed, and changing the workflow.For more information, see the BAdI documentation and the example implementation.

4.6 Approve RequisitionsTo enable SAP Fiori Approve Requisitions, you must perform a number of configuration tasks.


prerequisites are in place. Note that only approval at item level is supported. Approval at header level, that is, overall release of a purchase requisition, is not supported.

You must have configured the approval workflow that defines the task type(s) to be used for approving purchase requisition items.

NoteYou must use the release strategy in SAP Materials Management Purchasing (MM-PUR) and you must set up a connection between the release strategy and SAP Business Workflow. When customizing the release strategy, do not use Overall Release. This setting is intended for approval at header level, which is not supported for this app.



Approve RequestsApprove Leave RequestsApprove Shopping CartsApprove Purchase OrdersApprove Requisitions


Manager Apps

Task More InformationApprove Purchase Contracts












7 Optional: Implement BAdI Extend Model of Gateway Service for Approve Requisitions App , GBAPP_APV_PR_MDP

You can use this BAdI to enhance the entities, that is, the OData model, of the GBAPP_PRAPPROVAL Gateway service of the Approve Requisitions app. You can do this to add your own fields, for example.


8 Optional: Implement BAdI Extend Runtime of Gateway Service for Approve Requisitions App, GBAPP_APV_PR_RDP

You can use this BAdI to change the runtime data that is returned by the Gateway service and displayed on the user interface of the Approve Requisitions app. (This is the main purpose of this BAdI.) This includes the use of pictures, changing the list of attachments and notes displayed, and changing the workflow.For more information, see the BAdI documentation and the example implementation.

4.7 Approve Travel RequestsTo enable the SAP Fiori Approve Travel Requests application, you must must ensure all prerequisites are in place and perform the following configuration tasks:


Task More Information1 Ensure configuration table

SRA009_T_CONFIG is maintained.Configuration table SRA009_T_CONFIG must be maintained for a workflow decision key in case of a custom workflow for travel request approval.A node for this task is provided in the Implementation Guide (IMG).

2 Ensure configuration table SRA009_T_TASKTYP is maintained.

Configuration table SRA009_T_TASKTYP must be maintained for the task type used for approving the travel request.A node for this task is provided in the IMG.

4.8 Approve Travel Expenses

To enable the SAP Fiori Approve Travel Expenses application, you must must ensure all prerequisites are in place and perform a number of configuration tasks.

Task More Information1 Ensure configuration table

SRA008_T_CONFIG is maintained.Configuration table SRA008_T_CONFIG must be maintained for a workflow decision key in case of a custom workflow for travel expense approval.A node for this task is provided in the Implementation Guide (IMG).

2 Ensure configuration table SRA008_T_TASKTYP is maintained.

Configuration table SRA008_T_TASKTYP must be maintained for the task type used for approving the travel expense.A node for this task is provided in the IMG.

3 Ensure that the Travel Management module is installed and configured.

The app relies on configuration data available for the Travel Management module, so it is mandatory to have the module installed and configured.In the standard workflow, Approve Trip, there is a two-step approval process for travel expenses. The SAP Fiori Approve Travel Expenses application is used to perform only one approval process.You can enable one of three workflow tasks in the SAP Fiori application: Check Trip Facts Approve Trip Facts Custom workflow


Manager Apps

Task More Information

By default, the workflow task Approve Trip Facts is used to approve travel expenses.

4.9 Approve TimesheetsTo enable the SAP Fiori Approve Timesheets application, you must must perform a number of configuration tasks.

Task More Information1 Activate EA-HR business function Software component dependencies are already maintained

in PPMS, so the SAINT tool handles the dependency validation.

2 Install Gateway Server Components

Install Gateway Server Components - Gateway: SRA010 and UI: UISRA010 using the add-on installation tool (transaction SAINT). For more information, see Install Add-On Components [page 11].

3 Enable the SRA010_TIMESHEET_APPROVAL SICF Services for the Gateway

See Activate Gateway and UI5 Services in SICF [page 17]

4 Enable the UI5_HCM_TSA SICF Services for UI5

See Activate Gateway and UI5 Services in SICF [page 17]

5 Ensure that the SAP Standard MSS Role is included with the application.

6 Implement BAdI SRA010_BADI_TIMESHEET_APV (Optional)

The BAdI has 4 methods: GET_SUMMARY, TIME_PENDING_GET_ENTITYSET, REJ_REASON_GET_ENTITYSET, APPROVE_REJECT_ACTION.You implement this BAdI if you want any custom implementation logic for any of the standard process of obtaining the following: summary of timesheet entries, pending timesheet entries, approved/rejected timesheet entries, retrieving possible reasons for rejection.

4.10 My SpendTo enable the SAP Fiori My Spend application, you must perform a number of configuration tasks.


Task More Information1 Configure users. See Set Up Personalization [page 44].

4.10.1 Set Up PersonalizationSAP Fiori My Spend uses the personalization framework included with the EA-FIN business function.The Administrator defines Personalization for users. To configure for individual users, perform the following steps:1. From Integration with other mySAP.com components, go to transaction SPRO Business Packages/

Functional Packages Manager Self-Service (mySAP ERP) Personalization PersonalizationDataCollective Processing .

2. The following personalization dialog boxes are relevant, and values must be maintained for the following monitors: Cost Center: DIA_CCMONITOR Internal Order: DIA_IOMONITOR

NoteYou do not need to create groups if a user has only one cost center or one project. For multiple single and/or interval departments and projects, you still need to create corresponding groups and assign in MSS. There are additional authorization checks during the data read. SRS only retrieves the data for the authorized objects. For example, the department manager for the Cars business unit should only see his own cost centers. You can link his user ID to the relevant cost center groups.For more information, see the personalization framework standard documentation on the SAP Help Portal.

NoteNote that only one group from Personalization configuration is supported. If multiple groups are maintained for a particular user, the first group maintained for the user is used for data display on the iPad. This is valid for all three master data elements (Cost Center, Cost Element, and Internal Order).

4.11 Approve Leave RequestsTo enable SAP Fiori Approve Leave Requests, you must perform a number of configuration tasks.

Task More Information1 Ensure that the application-specific

prerequisites are in place. You must configure the approval workflow that

defined the task type(s) to be used for Approve Leave Requests.


Manager Apps

Task More Information Each application user must be mapped to a valid

personnel number with the necessary authorizations.

Ensure the prerequisite SAP Notes have been applied after the installation of the integration add-ons.



The following SAP Notes must be applied for Approve Leave Requests: For the component GBHCM003:

SAP Note 1621475SAP Note 1525104SAP Note 1555377SAP Note 1487720SAP Note 1538601

For the component GBHCM003 SP07:SAP Note 1854502SAP Note 1793784SAP Note 1846661SAP Note 1849088SAP Note 1883884








1. Define a scenario ID.2. Assign user roles for which you want to enable

the workflow.


Task More Information3. Assign the task ID of the leave request approval




Manager Apps

5 Sales Rep Apps

5.1 Configure Sales Rep AppsSales representatives use the apps to check price and availability; create, track, and change sales orders; track shipments, and view information about customer invoices.

Table 6: Sales Rep AppsApp Description Configuration

InformationCheck Price and Availability

Check the price and availability of any given material for customers, based on quantity and requested delivery date.

Check Price and Availability [page 54]

Create Sales Orders Create sales orders on desktop and mobile devices. Sales representatives can reorder using a customer's previously placed orders and select individual products to add to a new order.

Create Sales Orders [page 48]

Track Sales Orders Manage the sales orders for customers by checking the status of order items and delivery schedules on both desktop and mobile devices.

Track Sales Orders [page 50]

Change Sales Orders Change sales orders on desktop and mobile devices. You can also change the address of a shipment to expedite delivery of items to customers.

Change Sales Orders [page 52]

Track Shipments Provide precise shipment information to customers from a desktop or mobile device.

Track Shipments [page 53]

Customer Invoices View customers unpaid, past due and disputed invoices or memos on a desktop of mobile device.

Customer Invoices [page 52]

5.2 Employee Master Record CreationTo use the application, you must have implemented either Human Capital Management (HCM) or Sales and Distribution (SD) so that an employee master record has been created.An employee master record is created in either of the following cases: You have implemented HCM and maintained your employees in the HCM personnel records. The employee

personnel record in HCM has the infotype Communication, with a subtype of System User Name (SY-UNAME) (Infotype 0105, Subtype 0001)

If you have not implemented HCM, you must implement the SD configuration around Use Sales Employees with HR (Tcode: PULT). This IMG setting copies the appropriate HMC tables from the 000 Client and allows the setup of the Employee Record with the Infotype Communication and a Subtype of

SAP Fiori Installation and ConfigurationSales Rep Apps 2013 SAP AG or an SAP affiliate company. All rights reserved. 47

System User Name (SY-UNAME) (Infotype 0105, Subtype 0001). See SAP Note 854390 for more information.

Either of the above cases produces an employee master record, which associates the USERID of the employee with the personnel number assigned as a partner function sales employee in the customer master.

5.3 Create Sales Orders

To enable the SAP Fiori Create Sales Orders application , you must perform a number of configuration tasks.Task More Information

1 Ensure that an employee master record is created.

See Employee Master Record Creation [page 47]

2 Configure user information for the application.

To configure user information for Create Sales Orders, call transaction SIMGH, and open the Create Sales Orders node.

3 Define Configuration Parameters In the Define Configuration Parameters menu option, the following configuration parameters in Create Sales Orders application are maintained: See Configuration Parameters for Sales Orders Applications [page 49].To change the value of any of the parameters, execute the activity and edit the parameter value.

4 Deploy the required Business Add-Ins (BAdI)

Deploy the following BAdIs: Customer Association to Employee - This BAdI is

used in the Create Sales Orders add-on. You can find the BADI_SRA017_USER_TO_CUSTOMER in enhancement spot ES_SRA017_SALESORDER_CREATE. You can use it to implement a method for associating employees to customers. SRA017_SO_USR_TO_CUSTOMER is activated in the standard system. In this implementation the customers are associated with the employee by reading the employee responsible in the partner function of the customer master.

Retrieve Product Image- This BAdI is used in the Create Sales Orders add-on. You can find the BADI_SRA017_PROD_IMG_RETRIEVER in enhancement spot ES_SRA017_SALESORDER_CREATE. There is no default implementation of this BAdI.


Sales Rep Apps

Task More InformationImplementation needs to support following parameters: IV_MATERIAL Material ID. This parameter

is mandatory. IV_IMAGE_REQUIRED This flag is used to

indicate whether the image should be returned or only the metadata of the image. This is optional parameter.

EV_MIME_TYPE This should contain the type of image. This is optional information.

EV_IMAGE_XSTRING This field contains the image in XSTRING format .

EV_IMAGE_AVAILABLE This flag should return whether image is available or not.

For more information, see Implement a Business Add-On [page 58].

5.3.1 Configuration Parameters for Sales Orders Applications

The accompanying table lists the configuration parameters for the Sales Orders apps.

Parameter DescriptionDocument Type (DOCTYPE) By default Track Sales Orders is configured to use the standard order

document type (technical key TA resp. OR). Changing the document type to something other than a sales order may significantly impact the functionality of the application

Order Period (ORDPERIOD) The order period defines how many days into the past sales orders are retrieved. The suggested value is 30 days.

Search Period (SEAPERIOD) The search period defines how many days into the past search is looking for sales orders matching the search criteria. The suggested value is 90 days .

Product Search Limit (PRODUCT / SEARCH_LIMIT)

The product search limit defines how many products in the material master are returned that match the search criteria. The suggested value is 100 products.

Pricing Condition (LIST_PRICE / PRICING_CONDITION)

The value of the list price parameter determines the pricing conditions during the price and availability check and the order creation. The suggested value is PR00.

Ship To Party (SHIP_TO / PARTNER_ROLE) The value of the ship-to party parameter defines which partner role in the customer master is used for the ship-to party. The suggested value is WE.

SAP Fiori Installation and ConfigurationSales Rep Apps 2013 SAP AG or an SAP affiliate company. All rights reserved. 49

Parameter Des

Fiori10 Install En

Documents

Transcript of Fiori10 Install En