Fiori 10 Installation
Short Description
SAP Fioro 10...
Description
SAP Fiori Document Version: 1.0 - 2013-09-24
SAP Fiori Installation and Configuration
Table of Contents 1
Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
1.1
Prerequisites Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2
SAP Notes for SAP NetWeaver AS ABAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.3
SAP Notes for SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.4
SAP Notes for SAP NetWeaver Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.5
SAP Notes for SAP UI5 for NetWeaver Add-On. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.6
Prerequisites for My Shopping Cart and Track Shopping Carts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2
Install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.1
Setup Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.2
Install Add-On Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 2.2.1
2.3
2.4
2.5
2.6
Integration and SAP UI5 Components for SAP Fiori Applications. . . . . . . . . . . . . . . . . . . . . . 10
Configure SAP Business Suite Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.3.1
Define Users and Authorizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.3.2
Configure the Back-End Event Publisher. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.3.3
Specify Connection Settings to SAP NetWeaver Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Configure SAP NetWeaver Gateway Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.4.1
Configure App-Specific Gateway Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.4.2
Activate Gateway and UI5 Services in SICF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Components and Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 2.5.1
Gateway Services for Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.5.2
SICF Services for UI Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
Access Apps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 2.6.1
Access SAP Fiori Apps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3
Employee Apps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.1
Configure Employee Apps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
3.2
My Paystubs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.3
My Travel Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.4
My Shopping Cart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 3.4.1
SRM Services Used by My Shopping Cart and Track Shopping Carts. . . . . . . . . . . . . . . . . . . 23
3.5
Track Shopping Carts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3.6
My Benefits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
3.7
My Timesheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.8
My Leave Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4
Manager Apps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.1
Configure Manager Apps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.2
Approve Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.3
Approve Shopping Carts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
SAP Fiori Installation and Configuration Table of Contents
4.4
Approve Purchase Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4.5
Approve Purchase Contracts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
4.6
Approve Requisitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.7
Approve Travel Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.8
Approve Travel Expenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.9
Approve Timesheets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4.10
My Spend. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 4.10.1
Set Up Personalization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
4.11
Approve Leave Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5
Sales Rep Apps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.1
Configure Sales Rep Apps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.2
Create Sales Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
5.3
5.2.1
Employee Master Record Creation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
5.2.2
Configuration Parameters for Sales Orders Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . .40
Track Sales Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41 5.3.1
Status Aggregation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
5.4
Change Sales Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
5.5
Customer Invoices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
5.6
Track Shipments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
5.7
Check Price and Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
6
Purchasing Agent Apps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
6.1
Configure Purchasing Agent Apps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
6.2
Order From Requisitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
6.3
Track Purchase Order. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
7
How To. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
7.1
Implement a Business Add-On. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
7.2
Define an Approval Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
7.3
Configure Launch Settings for Custom Workflows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
7.4
Create a System Alias. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
7.5
Configure Task Decisions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
SAP Fiori Installation and Configuration Table 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. Prerequisites
More Information
❑ SAP NetWeaver Application Server Advanced Business Application Programming (AS ABAP) 7.0 SPS21 and above
●
http://help.sap.com/nw_platform
●
SAP Notes for SAP NetWeaver AS ABAP [page 5]
❑ For SAP Fiori applications based on SAP ERP:
●
http://help.sap.com/erp
●
SAP Notes for SAP ERP [page 6]
SAP Enterprise Resource Planning (ERP) 6.0 SPS15 or above ●
6.0 SPS 15 and above 6.0
●
EnhP2 SPS 06 and above 6.0
●
EnhP3 SPS 05 and above 6.0
●
EnhP4 SPS 05 and above 6.0
●
EnhP5 SPS 03 and above 6.0
●
EnhP6 SPS 01 and above
7.00 SP 21 and above & SAP Note 1774246 ❑ For the Approve Shopping Cart application based on SAP SRM: ●
SRM 7.0 SPS02
For the My Shopping Cart and Track Shopping Carts applications based on SAP SRM: ●
SRM 7.0 SP11
●
SAP SRM User Interface Add-On 1.0 SP01
❑ SAP NetWeaver Gateway 2.0 SPS06
Prerequisites for My Shopping Cart and Track Shopping Carts [page 7]
●
SAP Notes for SAP ERP [page 6]
IW_BEP 2.0* (SP06)
●
http://help.sap.com/nwgateway20
●
GW_CORE 200 (SP06)
●
●
IW_PGW 100 (SP03)
SAP NetWeaver Gateway Installation Guide>Installation Prerequisites
●
IW_FND 250 (SP06) with SAP Note 1812143
●
SAP NetWeaver Gateway Installation Guide
●
SAP Netweaver Gateway Installation Guide>Installing SAP NetWeaver Gateway Components
●
●
4
For the My Shopping Cart and Track Shopping Carts applications, special prerequisites apply:
JSON - IWFND 2.50 (NW 7.02) SP04 with SAP Note 1648418 (and the included note SAP Note 1650141)
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
SAP Fiori Installation and Configuration Prerequisites
Prerequisites ●
JSON -IWFND 2.40** (NW 7.00) ON 7.20 Kernel with SAP Note 1648418 (and the included note SAP Note 1650141)
❑ SAP UI5 for NetWeaver Add-On ●
UISAPUI5 100 SP04 UI5 library 1.12 (if NW 7.0 or later)
●
UI_INFRA 100 SP04
●
UI2_700 100 SP04
●
UI2_701 100 SP04 (If NW 7.0 EHP1 or later)
●
UI2_702 100 SP04 (If NW 7.0 EHP1 or later)
●
UI2_731 100 SP04 (If NW 7.3 EHP1 or later, if NW 7.1 EHP3 or later)
●
UI2_FND 100 SP04
●
UI2_SRVC 100 SP04
❑ Define a Remote Function Call (RFC) Destination from ECC or SRM to Gateway ❑ RFC Destination from SAP NetWeaver Gateway to ECC or SRM ❑ Register alias for the ECC or SRM RFC Destination to the SAP NetWeaver Gateway
1.2
More Information
Note ●
* IW_BEP 2.0 SP06 (with SAP Note 1799722 and SAP Note 1805831) is needed in the source ERP Central Component (ECC) system below NetWeaver 7.4.
●
** JSON - IWFND 2.40 (NW 7.00) ON 7.00 Kernel is not supported - Atom only
SAP Notes for SAP UI5 for NetWeaver Add-On [page 7]
●
Creating RFC Connections
●
Setting up a trusted connection between Gateway and ECC or SRM: Connection Settings SAP NetWeaver Gateway to SAP Systems
●
Create a System Alias [page 53]
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
SAP Note 1774246
Mobile Inbox: Inbox API
SAP Note 1799549
SAP WAPI_CREATE_OUTBOX: Optional parameter
SAP Note 1805986
Additional parameter for SAP WAPI_ATTACHMENT_ADD
SAP Note 1754533
Enhancement of WAPI trace
SAP Fiori Installation and Configuration Prerequisites
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
5
SAP Note Number
Description
SAP Note 1809628
Additional methods for IF_SWF_UTL_WAPI_FRAMEWORK
1.3
SAP Notes for SAP ERP
The following table lists the SAP Notes that must be applied to SAP Enterprise Resource Planning (ERP): SAP Note Number
Description
SAP Note 1799549
SAP WAPI_CREATE_OUTBOX: Optional parameter
SAP Note 1805986
SAP WAPI_CREATE_OUTBOX: Optional parameter
SAP Note 1754533
Enhancement of WAPI trace
SAP Note 1809628
Additional methods for IF_SWF_UTL_WAPI_FRAMEWORK
For Approval apps: (SAP_BASIS component): SAP Note 1774246
Mobile Inbox: Inbox API
Note If IW_BEP software component version is Release 2 Support Package 06 or more or if IW_BEP software component version is Release 2 Support Package 05 or less AND SAP Note 1766501: Check Data Container Type Returned by DPC has been installed, then you must apply SAP Note 1799807: Suppress Message / IWBEP/CM_MGW_RT 157.
1.4
SAP Notes for SAP NetWeaver Gateway
The following table lists the SAP Notes that must be applied to SAP NetWeaver Gateway: SAP Note Number
Description
Required For
SAP Note 1799722
IW_BEP Adjustments to Task Gateway for SP06
SAP Note 1805831
Workflow Support Decision options Nature (Positive/ Negative)
For SAP ERP systems using SAP NetWeaver 7.31 and below. For more information, see Installing SAP NetWeaver Gateway Components.
SAP Note 1866093
Patches for the Gateway SPS06 required for FIORI
6
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
●
Approve Requests
●
Approve Shopping Carts
SAP Fiori Installation and Configuration Prerequisites
SAP Note Number
1.5
Description
Required For ●
Approve Requisitions
●
Approve Purchase Orders
SAP Notes for SAP UI5 for NetWeaver Add-On
The following table lists the SAP Notes that must be applied to SAP UI5 for NetWeaver Add-On SAP Note Number
Description
SAP Note 1759682
UI Add-on for SAP NetWeaver Central Note
SAP Note 1666368
Installing UI Add-on 1.0 for SAP NetWeaver
SAP Note 1666369
Support Packages for UI Add-on 1.0 for SAP NetWeaver
SAP Note 1852767
Patches for the NW UI Add-on SP04 required for SAP Fiori
1.6 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 AddOn.
SAP Fiori Installation and Configuration Prerequisites
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
7
Related Information Master Guide for SAP SRM User Interface Add-On 1.0 Configuration Cookbook for the SAP SRM User Interface Add-On (SRM Community) SAP SRM User Interface Add-On on SAP Help Portal SRM Services Used by My Shopping Cart and Track Shopping Carts [page 23] 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.
8
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
SAP Fiori Installation and Configuration Prerequisites
2
Install
2.1
Setup Checklist
This 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 1
More Information
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 10]
❑
Install Add-On Components on SAP NetWeaver Gateway
●
See Install Add-On Components [page 10]
Configure SAP Business Suite Components
To configure SAP Business Suite Components:
2
3
●
Define Users and Authorizations [page 12]
●
Configure the Back-End Event Publisher [page 13]
●
Specify Connection Settings to SAP NetWeaver Gateway [page 14]
Configure SAP NetWeaver Gateway Settings ❑
Define Users and Authorizations
❑
Specify Language Settings
Note The languages configured on the back end must correspond to the languages configured for the SAP Fiori apps.
4
5
Configure SAP Netweaver Gateway Components ❑
Activate Gateway and UI5 Services in SICF
See Activate Gateway and UI5 Services in SICF [page 15]
❑
Configure App-Specific Gateway Services
See Activate Gateway and UI5 Services in SICF [page 15]
Configure Specific Apps
See the configuration instructions specific to your application:
SAP Fiori Installation and Configuration Install
●
Configure Employee Apps [page 21]
●
Configure Manager Apps [page 28]
●
Configure Sales Rep Apps [page 38]
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
9
Task
More Information ●
Configure Purchasing Agent Apps [page 46]
Note You must also activate Standard Mode (Odata) Services for the following Manager approval applications: Approve Requests Approve Leave Requests Approve Shopping Requests Approve Purchase Orders Approve Purchase Requisitions Approve Purchase Contracts For more information, see Activate and Maintain Services. 6
Access the applications
2.2
Access SAP Fiori Apps [page 17]
Install Add-On Components
To 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 10] 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.
2.2.1 Integration and SAP UI5 Components for SAP Fiori Applications 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. The SAP Fiori apps can be downloaded from the SAP Service Marketplace at https://websmp205.sap-ag.de/. Select
10
Products
Software download .
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
SAP Fiori Installation and Configuration Install
Table 1: Scenario-Specific UI5 and OData Components Application
Product Version on SAP Service Marketplace
UI Component
OData Component in SAP Business Suite
My Timesheet
FIORI TIMERECORDING
UISRA002 100
SRA002 600
My Shopping Cart
FIORI SHOPCARTCRE
UISRA014 100
Uses SRM component SRMNXP01 100
Track Shopping Carts
FIORI SHOPCARTTRK
UISRA011 100
Uses SRM component SRMNXP01 100
My Travel Requests
FIORI TRAVELREQCRE
UISRA004 100
SRA004 600
My Leave Requests
FIORI LEAVEREQCRE
UIHCM002 100
GBHCM002 (SP07) + SAP Notes
My Paystubs
FIORI PAYSLIPLOOK
UISRA006 100
SRA006 600
My Benefits
FIORI MYBENENRO
UISRA007 100
SRA007 600
My Spend
FIORI MYDEPTSPEND
UISRA012 100
SRA012 600
Approve Requests
FIORI GENERICINBX
UIGIB001 100
Included in IW_PGW 100 (SP03)
Approve Leave Requests
FIORI LEAVEREQAPPR
UIHCM003 100
GBHCM003 600 (SP06) + SAP Notes
Approve Shopping Carts
FIORI SHOPCARTAPPR
UISRM001 100
GBSRM001 700 (SP07) + SAP Notes
Approve Travel Expenses
FIORI TRAVELEXPAPPR
UISRA008 100
SRA008 600
Approve Travel Requests
FIORI TRAVELREQAPPR
UISRA009 100
SRA009 600
Approve Purchase Orders
FIORI PURCHASEORDAPPR
UIAPP002 100
GBAPP002 600
Approve Timesheets
FIORI TIMESHTAPPR
UISRA010 100
SRA010 600
Approve Purchase Contracts
FIORI PURCHASECONTAPPR
UISRA001 100
SRA001 600
Approve Requisitions
FIORI PURCHASEREQAPPR
UIAPP001 100
GBAPP002 600
Check Price and Availability
FIORI PRICECHECK
UISRA016 100
SRA016 600
Create Sales Orders
FIORI ORDERCRE
UISRA017 100
SRA017 600
Track Sales Orders
FIORI ORDERSTSTRK
UISRA018 100
SRA018 600
Track Shipments
FIORI SHIPTRK
UISRA019 100
SRA019 600
Employee
Manager
Sales Representatives
SAP Fiori Installation and Configuration Install
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
11
Application
Product Version on SAP Service Marketplace
UI Component
OData Component in SAP Business Suite
Change Sales Orders
FIORI ORDERCHG
UISRA018 100
SRA018 600
Customer Invoices
FIORI INVOICEBILL
UISRA021 100
SRA021 600
Order from Requisitions
FIORI ORDERPOREQ
UISRA013 100
SRA013 600 + SAP Notes
Track Purchase Order
FIORI TRACKPO
UISRA020 100
SRA020 600 + SAP Notes
Purchasing Agent
Note For 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 21] 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 28] 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 38] 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 46] 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. The following SAP Fiori apps include business roles: ●
Approve Requests
●
Approve Leave Request
●
Approve Shopping Cart
●
Approve Requisition
●
Approve Purchase Order
●
My Leave Requests
●
Approve Purchase Contracts
12
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
SAP Fiori Installation and Configuration Install
These roles, in addition to the personalization settings, ensure that managers are authorized to display the correct data for their organizational entities and perform the approval activities. 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
Role
SAP Approve Requests
No role provided, but authorization must be assigned for usage of the service
Approve Leave Request
SAP_GBHCM_LEAVE_APPROVAL_MGR
Approve Shopping Cart
SAP_GBSRM_CART_APPROVAL_MANAG
Approve Purchase Requisition
SAP_GBAPP_PR_APPROVAL_MANAGER
Approve Purchase Order
SAP_GBAPP_PO_APPROVAL_MANAGER
My Leave Requests
SAP_GBHCM_LEAVE_REQUEST_EMPL and also the Gateway role SAP_HCM002_HCM_LVRQ_CR
Approve Purchase Contracts
SAP_SRA01_PC_APPROVAL_MANAGER
○ 4.
Alternatively, create a customer role based on SU22 entries of the SAP R3TR/IWSV service (S_SERVICE).
Assign the new role(s) to the application users. For more information about users and authorizations, see User Management.
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.
Note This step is not relevant for the My Shopping Cart and Track Shopping Carts applications. Related Information Configure Backend Event Publisher
SAP Fiori Installation and Configuration Install
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
13
2.3.3 Specify Connection Settings to SAP NetWeaver Gateway Specify 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 Configuration Connection Settings in the Backend System SAP 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 application, and check that it is activated. 1.
maint_service
transaction, add the service for the
In your Gateway system, go to transaction /IWFND/maint_service.
Note You 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.
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 15] This table lists the SAP NetWeaver Gateway services required for SAP Fiori applications. Activate and Maintain Services
14
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
SAP Fiori Installation and Configuration Install
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
4.
Check that all Gateway services for all SAP Fiori applications are active:
sap
opu
odata
sap .
○
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 15] This table lists the SAP NetWeaver Gateway services required for SAP Fiori applications. SICF Services for UI Applications [page 16] 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 Applications
This table lists the SAP NetWeaver Gateway services required for SAP Fiori applications. Application Name
External Service Name
Employee My Travel Requests
sra004_srv
My Leave Requests
leaverequest, version 2
My Paystubs
sra006_srv
My Benefits
sra007_benefits_srv
My Timesheet
sra002_timesheet_srv
My 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/)
Manager
SAP Fiori Installation and Configuration Install
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
15
Application Name
External Service Name
Approve Leave Requests
leaveapproval
Approve Shopping Carts
cartapproval, version 2
Approve Purchase Orders
gbapp_poapproval
Approve Requisitions
gbapp_prapproval
Approve Requests
taskprocessing
Approve Travel Requests
sra009_srv
Approve Timesheets
sra010_timesheet_approval_srv
Approve Purchase Contracts
sra001_contract_approval_srv
Approve Travel Expenses
sra008_srv
Approve Purchase Contracts
sra001_pcapproval
My Spend
sra012_spend_srv
Sales Representatives Check Price and Availability
sra016_price_avail_srv
Customer Invoices
sra021_srv
Change Sales Orders
sra018_so_tracking_srv
Create Sales Orders
sra017_salesorder_create_srv
Track Sales Orders
sra018_so_tracking_srv
Track Shipments
sra019_shipment_tracking_srv
Purchasing Agent Order From Requisitions
sra013_po_from_pr_srv
Track 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 Name
Launch Page for Tile CHIPs
/ui2/launchpage
Employee My Travel Requests
ui5_fi_trreq_cr
My Paystubs
ui5_hcm_ps_mon
My Benefits
ui5_hcm_ben_ovw
My Leave Requests
ui5_hcm_lr_cr
My Timesheet
ui5_hcm_ts_man
16
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
SAP Fiori Installation and Configuration Install
Application Name
Service Name
My Shopping Cart
ui5_srm_sc_cr
Track Shopping Cart
ui5_srm_sc_mon
Manager Approve Leave Requests
ui5_hcm_lr_apv
Approve Shopping Carts
ui5_srm_sc_apv
Approve Purchase Orders
ui5_mm_po_apv
Approve Requisitions
ui5_mm_pr_apv
Approve Travel Requests
ui5_fi_trreq_apv
Approve Timesheets
ui5_hcm_tsa
Approve Purchase Contracts
ui5_mm_pc_apv
Approve Travel Expenses
ui5_fi_trex_apv
Approve Requests
ui5_ca_all_apv
My Spend
ui5_co_spe_mon
Sales Representative Check Price and Availability
ui5_scm_pa_chk
Customer Invoices
ui5_sd_inv_mon
Change Sales Orders
ui5_sd_so_man
Track Shipments
ui5_sd_ship_mon
Create Sales Order
ui5_sd_so_cr
Track Sales Order
ui5_sd_so_mon
Purchasing Agent Order From Requisitions
ui5_mm_popr_cr
Track Purchase Order
ui5_mm_po_tr
2.6 2.6.1
Access Apps Access SAP Fiori Apps
Users can access SAP Fiori applications directly or via the home page (the launch page). Related Information SAP Fiori App URLs [page 18] To open a SAP Fiori application directly, use the relative URL listed in this table. Add Apps to the User's Home Page [page 19] You define which SAP Fiori applications appear on a user's home page (launch page) by assigning users to predefined roles.
SAP Fiori Installation and Configuration Install
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
17
2.6.1.1
SAP Fiori App URLs
To open a SAP Fiori application directly, use the relative URL listed in this table.
Note If 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 Applications Application
URL
Employee My Benefits
/sap/bc/ui5_ui5/sap/ui5_hcm_ben_ovw/index.html
My Leave Requests
/sap/bc/ui5_ui5/sap/ui5_hcm_lr_cr/index.html
My Pay Stubs
/sap/bc/ui5_ui5/sap/ui5_hcm_ps_mon/index.html
My Shopping Cart
/sap/bc/ui5_ui5/sap/ui5_srm_sc_mon/index.html?create=true
My TimeSheet
/sap/bc/ui5_ui5/sap/ui5_hcm_ts_man/index.html
My Travel Requests
/sap/bc/ui5_ui5/sap/ui5_fi_trreq_cr/index.html
Track Shopping Carts
/sap/bc/ui5_ui5/sap/ui5_srm_sc_mon/index.html
Manager Approve Leave Requests
/sap/bc/ui5_ui5/sap/ui5_hcm_lr_apv/index.html
Approve Purchase Contracts
/sap/bc/ui5_ui5/sap/ui5_mm_pc_apv/index.html
Approve Purchase Orders
/sap/bc/ui5_ui5/sap/ui5_mm_po_apv/index.html
Approve Requests
The target URL depends on your custom workflow scenario. For more information, see Configure Launch Settings for Custom Workflows [page 51].
Approve Requisitions
/sap/bc/ui5_ui5/sap/ui5_mm_pr_apv/index.html
Approve Shopping Carts
/sap/bc/ui5_ui5/sap/ui5_srm_sc_apv/index.html
Approve Timesheets
/sap/bc/ui5_ui5/sap/ui5_hcm_ts_apv/index.html
Approve Travel Expenses
/sap/bc/ui5_ui5/sap/ui5_fi_trex_apv/index.html
Approve Travel Requests
/sap/bc/ui5_ui5/sap/ui5_fi_trreq_ap/index.html
My Spend
/sap/bc/ui5_ui5/sap/ui5_co_spe_mon/index.html
Sales Representatives Change Sales Orders
/sap/bc/ui5_ui5/sap/ui5_sd_so_mon/index.html?change=true
Check Price and Availability
/sap/bc/ui5_ui5/sap/ui5_sd_prav_mon/index.html
18
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
SAP Fiori Installation and Configuration Install
Application
URL
Create Sales Orders
/sap/bc/ui5_ui5/sap/ui5_sd_so_cr/index.html
Customer Invoices
/sap/bc/ui5_ui5/sap/ui5_sd_inv_mon/index.html
Track Sales Orders
/sap/bc/ui5_ui5/sap/ui5_sd_so_mon/index.html
Track Shipments
/sap/bc/ui5_ui5/sap/ui5_sd_ship_mon/index.html
Purchasing Agent Order From Requisitions
/sap/bc/ui5_ui5/sap/ui5_mm_pr_cr/index.html
Track 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.
Note All 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 Page Application
Role for Launch Page
Employee My Benefits
SAP_SRA007_HCM_BEN_OVW
My Leave Requests
SAP_HCM002_HCM_LVRQ_CR
My Pay Stubs
SAP_SRA006_HCM_PS_MON
My Shopping Cart
SAP_SRA014_SRM_SC_CR
My TimeSheet
SAP_SRA002_HCM_TS_MAN
My Travel Requests
SAP_SRA004_FI_TRREQ_CR
Track Shopping Carts
SAP_SRA011_SRM_SC_MON
Manager Approve Leave Requests
SAP_HCM003_HCM_LVRQ_APR
Approve Purchase Contracts
SAP_SRA001_MM_PC_APV
Approve Purchase Orders
SAP_APP002_MM_PO_APR
SAP Fiori Installation and Configuration Install
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
19
Application
Role for Launch Page
Approve Requests
The role depends on your custom settings. For more information, see Configure Launch Settings for Custom Workflows [page 51].
Approve Requisitions
SAP_APP001_MM_PR_APR
Approve Shopping Carts
SAP_SRM001_SRM_SHOP_APR
Approve Timesheets
SAP_SRA010_HCM_TS_APV
Approve Travel Expenses
SAP_SRA008_FI_TREX_APV
Approve Travel Requests
SAP_SRA009_FI_TRREQ_AP
My Spend
SAP_SRA012_CO_SPE_MON
Sales Representatives Change Sales Orders
SAP_SRA003_SD_SO_CHG
Check Price and Availability
SAP_SRA016_SD_PRAV_MON
Create Sales Orders
SAP_SRA017_SD_SO_CR
Customer Invoices
SAP_SRA021_SD_INV_MON
Track Sales Orders
SAP_SRA018_SD_SO_MON
Track Shipments
SAP_SRA019_SD_SHIP_MON
Purchasing Agent Order From Requisitions
SAP_SRA013_MM_PR_CR
Track 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 NetWeaver SAP NetWeaver Platform
20
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
SAP Fiori Installation and Configuration Install
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 Apps App
Description
Configuration information
My 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 27]
My Paystubs
Check and manage, at any time through mobile devices See My Paystubs [page or desktop, a digital version of all your pay stubs issued 21] by the company for each payroll period.
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 23]
Track Shopping Carts
Track the status of your shopping cart.
Track Shopping Carts [page 25]
My Timesheet
Manage your time entry data quickly, efficiently, anywhere, at any time on desktop or mobile device.
See My Timesheet [page 26]
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 25]
3.2
My Paystubs
To enable the SAP Fiori My Paystubs application, you must perform a number of configuration tasks.
SAP Fiori Installation and Configuration Employee Apps
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
21
Tasks 1
❑
Apply the fix in SAP Note 890828
More Information SAP Note 890828, HRBG & HRUS: ABAP dump in class CL_HR_PAY_RESULT_GB/US, is available from the SAP Service Marketplace.
Note You 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_R GDIR. 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 SelfService (ESS) Applications.
Refer to the following document in the SAP Library for detailed information:
Business Package for
Employee Self-Service (SAP ERP) 1.0 the pages as follows: Applications
and expand
Employee Self-Service (ESS)
Benefits and Payment
Salary
Statement
Note SAP Fiori does not support Concurrent Employment.
Note If 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.
22
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
SAP Fiori Installation and Configuration Employee Apps
3.3
My Travel Requests
To 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 Cart
To 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 Prerequisites for My Shopping Cart and Track Shopping Carts [page 7] 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 Carts 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. To select these services in the service catalog, filter for the namespace /SRMNXP/ .
External Service Name
Service Description
ACC_ASS_SEARCH_HELP
Account assignment search help
ACC_ASSIGN_CATEGORY
Service for account assignment category description
ACC_ASSIGN_FLD_METADATA
Service for account assignment file metadata
ACC_ASSIGN_SRH
Account assignment search help service
APPROVAL_SERVICE
Approval service
APVR_SRCHLP
Search help for approver and reviewer
CATALOG_LAUNCH_DETAILS
Catalog launch details
COUNTRY_SH_SERVICE
Service for country search
CROSS_CATALOG_SEARCH
Cross catalog search
CTLG_CATEGORIES
Service to list catalog categories
SAP Fiori Installation and Configuration Employee Apps
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
23
External Service Name
Service Description
CUR_EXCH_RATE_SERVICE
Service for currency exchange rates
DOMAIN_VALUES
Domain values
GETDEFUSRSET
Service for getting default user settings
GRECIPIENT_SH_SERVICE
SH for goods recipient
ITEMHISTORY_SERVICE
Item history service
LANGUAGE
Service for language
LOGICAL_SYSTEM
Service for logical system
NOTES_SERVICE
Service for notes
ORDERTRACK_SERVICE
Order track service
PC_SH_SERVICE
Service for product category search help
PERSONAL_MARKERS
Personal marker service
PLANT_SH_SERVICE
Search help for plant
PRICE_SCALES
Item price scales
PRO_DET_IMAGES_SERVICE
Product details image service
PRO_DET_SERVICE
Service for product details
PRODUCT_MASTER
Service for product master
PRODUCT_TYPE
Service for product type
REC_ORDERS
Data provider for recent orders
REGION_SH_SERVICE
Service for region search
REVIEW
Review service for rating and review
SEARCH_TERMS_SERV
Search terms service
SHIP_ADDR_SH_SERVICE
Service for shipping address
SHOPPING_CART
Service for shopping cart
SRCH_FILTER
Search filter model
SRMSHOPPING_CART
SRM shopping cart PDO service
STLOCATION_SH_SERVICE
Search help for storage location
SUPPLIER_SH_SERVICE
Service for supplier search help
USER_CATALOG_LIST
User catalog provider
USERS_LIST
User list under one user name
UTIL
Service for utilities
24
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
SAP Fiori Installation and Configuration 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 Prerequisites for My Shopping Cart and Track Shopping Carts [page 7] 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 1
❑
Activate HR-BEN business function
More Information 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 10]
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_OVW
6
❑
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.
8
❑
Verify IMG Configuration
In the back-end system, call transaction SIMGH and open the My Benefits node.
SAP Fiori Installation and Configuration Employee Apps
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
25
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.
Note Ensure that you check the Prerequisites Checklist [page 4] and the Setup Checklist [page 9] before configuring My Timesheet. Tasks
More Information
1
❑
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 10]), 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 In addition to installing the components in the the Gateway. installation and configuration instructions (see Setup Checklist [page 9]) Ensure Gateway service SRA002_TIMESHEET_SRV is activated. For more information see, Configure App-Specific Gateway Services [page 14].
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 User Profile
System
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 AddOns (BAdIs) for the application.
Deploy the following BAdIs: ●
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.
26
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
SAP Fiori Installation and Configuration Employee Apps
Tasks
More Information ●
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 Requests
To enable the SAP Fiori My Leave Requests application, you must perform a number of configuration tasks: Tasks 1
❑
Ensure that the prerequisite SAP Notes have been applied.
More Information 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.0 SAP Note 1621488: ESS LEA: Customizing attributes are not correctly fetched SAP Note 1803429: HCM Leave Request App version 2
●
For component GBHCM002 (SP08): SAP Note 1852791: Checkman correction in class /GBHCM/CL_ELR_BEA_AUNIT SAP Note 1851674: Short dump when getting TimeAccount SAP Note 1846479: Leave requests cannot be created or approved/rejected SAP Note 1842934: Leave type is not displayed
SAP Fiori Installation and Configuration Employee Apps
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
27
4
Manager Apps
4.1
Configure Manager Apps
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. Table 5: Manager Apps App
Description
Configuration Information
My Spend
My Spend provides accurate budget and spend information anywhere and anytime.
My Spend [page 35]
Approve Requests
Approve, reject, or forward various approval requests Approve Requests [page from a desktop or mobile device. Define the approval 29] 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 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 Travel Expenses
Review and approve employees' travel expenses on Approve Travel Expenses the go or in the office. View details on each receipt, [page 34] and receive alerts if expenses exceed the budget limits defined in the company travel policy.
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 29]
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 30]
Approve Requisitions
View pending purchase requisitions and approve them. If necessary, forward approvals to a different employee for further processing.
Approve Requisitions [page 32]
Approve Travel Requests
Approve or refuse travel requests on desktop as well as on mobile devices.
Approve Travel Requests [page 33]
Approve Timesheets
View all pending approvals for employees’ timesheets and approve timesheets.
Approve Timesheets [page 35]
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 31]
28
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
Approve Leave Requests [page 36]
SAP Fiori Installation and Configuration Manager Apps
4.2
Approve Requests
To enable SAP Fiori Approve Requests, you must perform a number of configuration tasks. Task 1
More Information
❑
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.
❑
Ensure the prerequisite SAP Notes have been applied after the installation of the integration add-ons.
See the Prerequisites Checklist [page 4] for the SAP Notes that apply to all of the following: Approve Requests Approve Leave Requests Approve Shopping Carts Approve Purchase Orders Approve Purchase Requisitions Approvel Purchase Contracts
2
❑
Ensure that you have configured the connection between SAP NetWeaver Gateway and your back-end system.
Specify Connection Settings to SAP NetWeaver Gateway [page 14]
3
❑
Ensure that you have activated the Gateway services for the task.
Activate Gateway and UI5 Services in SICF [page 15]
4
❑
Check that you have connected the Gateway service for the task to your backend system.
See Activate and Maintain Services.
5
❑
Define a scenario for your custom approval 1. workflow. 2. 3.
Define a scenario ID. Assign user roles for which you want to enable the workflow. Assign the task ID of the approval workflow you have already defined in SAP Business Workflow.
For more information, see Define an Approval Scenario [page 48]. 6
❑
Assign task decisions to your approval workflow.
See Configure Task Decisions [page 53].
7
❑
Configure the launch settings for your custom approval workflow.
For more information, see Configure Launch Settings for Custom Workflows [page 51].
4.3
Approve Shopping Carts
To enable SAP Fiori Approve Shopping Carts, you must perform a number of configuration tasks.
SAP Fiori Installation and Configuration Manager Apps
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
29
Task 1
More Information
❑
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.
❑
Ensure the prerequisite SAP Notes have been applied after the installation of the integration add-ons.
See the Prerequisites Checklist [page 4] for the SAP Notes that apply to all of the following: Approve Requests Approve Leave Requests Approve Shopping Carts Approve Purchase Orders Approve Purchase Requisitions 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 SRM SAP Note 1842502: CAA: Information for limit item is not retrieved
2
❑
Ensure that you have configured the connection between SAP NetWeaver Gateway and your back-end system.
Specify Connection Settings to SAP NetWeaver Gateway [page 14]
3
❑
Ensure that you have activated the Gateway services for the task.
Activate Gateway and UI5 Services in SICF [page 15]
4
❑
Check that you have connected the Gateway service for the task to your backend system.
See Activate and Maintain Services.
5
❑
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 shopping cart approval workflow you have already defined in SAP Business Workflow.
For more information, see Define an Approval Scenario [page 48].
4.4
Approve Purchase Orders
To enable SAP Fiori Approve Purchase Orders, you must perform a number of configuration tasks.
30
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
SAP Fiori Installation and Configuration Manager Apps
Task 1
❑
Ensure that all application-specific prerequisites are in place.
More Information You must configure the approval workflow that defined the task type(s) to be used for Approve Purchase Orders.
Note If you are using the release strategy in SAP Materials Management Purchasing (MM-PUR), you need to set up a connection between the release strategy and SAP Business Workflow. 2
❑
Ensure the prerequisite SAP Notes have been applied after the installation of the integration add-ons.
See the Prerequisites Checklist [page 4] for the SAP Notes that apply to all of the following: Approve Requests Approve Leave Requests Approve Shopping Carts Approve Purchase Orders Approve Purchase Requisitions Apply the following SAP Note for Approve Purchase Orders (Component GBAPP002): SAP Note 1309042
3
❑
Ensure that you have configured the connection between SAP NetWeaver Gateway and your back-end system.
Specify Connection Settings to SAP NetWeaver Gateway [page 14]
4
❑
Ensure that you have activated the Gateway services for the task.
Activate Gateway and UI5 Services in SICF [page 15]
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 purchase approval workflow you have already defined in SAP Business Workflow.
For more information, see Define an Approval Scenario [page 48].
4.5
Approve Purchase Contracts
To enable SAP Fiori Approve Purchase Contracts, you must perform a number of configuration tasks.
SAP Fiori Installation and Configuration Manager Apps
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
31
Task 1
❑
Ensure that all application-specific prerequisites are in place.
More Information You must configure the approval workflow that defined the task type(s) to be used for Approve Purchase Contracts.
Note If you are using the release strategy in SAP Materials Management Purchasing (MM-PUR), you need to set up a connection between the release strategy and SAP Business Workflow. 2
❑
Ensure the prerequisite SAP Notes have been applied after the installation of the integration add-ons.
See the Prerequisites Checklist [page 4] for the SAP Notes that apply to all of the following: Approve Requests Approve Leave Requests Approve Shopping Carts Approve Purchase Orders Approve Purchase Requisitions Approve Purchase Contracts
3
❑
Ensure that you have configured the connection between SAP NetWeaver Gateway and your back-end system.
Specify Connection Settings to SAP NetWeaver Gateway [page 14]
4
❑
Ensure that you have activated the Gateway services for the task.
Activate Gateway and UI5 Services in SICF [page 15]
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 purchase approval workflow you have already defined in SAP Business Workflow.
For more information, see Define an Approval Scenario [page 48].
4.6
Approve Requisitions
To enable SAP Fiori Approve Requisitions, you must perform a number of configuration tasks.
32
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
SAP Fiori Installation and Configuration Manager Apps
Task 1
❑
Ensure that all application-specific prerequisites are in place.
More Information You must configure the approval workflow that defined the task type(s) to be used for Approve Requisitions.
Note If you are using the release strategy in SAP Materials Management Purchasing (MM-PUR), you need to set up a connection between the release strategy and SAP Business Workflow. 2
❑
Ensure the prerequisite SAP Notes have been applied after the installation of the integration add-ons.
See the Prerequisites Checklist [page 4] for the SAP Notes that apply to all of the following: Approve Requests Approve Leave Requests Approve Shopping Carts Approve Purchase Orders Approve Requisitions
3
❑
Ensure that you have configured the connection between SAP NetWeaver Gateway and your back-end system.
Specify Connection Settings to SAP NetWeaver Gateway [page 14]
4
❑
Ensure that you have activated the Gateway services for the task.
Activate Gateway and UI5 Services in SICF [page 15]
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 purchase requisition approval workflow you have already defined in SAP Business Workflow.
For more information, see Define an Approval Scenario [page 48].
4.7
Approve Travel Requests
To enable the SAP Fiori Approve Travel Requests application, you must must ensure all prerequisites are in place and perform the following configuration tasks:
SAP Fiori Installation and Configuration Manager Apps
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
33
Task 1
❑
Ensure configuration table SRA009_T_CONFIG is maintained.
More Information 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
Configuration table SRA009_T_TASKTYP must be
SRA009_T_TASKTYP is maintained.
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 1
❑
Ensure configuration table SRA008_T_CONFIG is maintained.
More Information 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
Configuration table SRA008_T_TASKTYP must be
SRA008_T_TASKTYP is maintained.
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.
Note The Approve Travel Expenses app works only on a system whose workflows do not use the Check Trip Facts task.
34
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
SAP Fiori Installation and Configuration Manager Apps
4.9
Approve Timesheets
To enable the SAP Fiori Approve Timesheets application, you must must perform a number of configuration tasks. Task
More Information
1
❑
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 10].
3
❑
Enable the SRA010_TIMESHEET_APPROVAL
See Activate Gateway and UI5 Services in SICF [page 15]
SICF Services for the Gateway 4
❑
Enable the UI5_HCM_TSA SICF
See Activate Gateway and UI5 Services in SICF [page 15]
Services for UI5 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 Spend To enable the SAP Fiori My Spend application, you must perform a number of configuration tasks. Task 1
❑
Configure users.
SAP Fiori Installation and Configuration Manager Apps
More Information See Set Up Personalization [page 36].
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
35
4.10.1 Set Up Personalization SAP 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 Functional Packages DataCollective
2.
Manager Self-Service (mySAP ERP)
transaction SPRO Personalization
Business Packages/
Personalization
Processing .
The following personalization dialog boxes are relevant, and values must be maintained for the following monitors: ○
Cost Center: DIA_CCMONITOR
○
Internal Order: DIA_IOMONITOR
Note You 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.
Note Note 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 Requests To enable SAP Fiori Approve Leave Requests, you must perform a number of configuration tasks. Task 1
36
❑
Ensure that the application-specific prerequisites are in place.
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
More Information ●
You must configure the approval workflow that defined the task type(s) to be used for Approve Leave Requests.
●
Each application user must be mapped to a valid personnel number with the necessary authorizations.
SAP Fiori Installation and Configuration Manager Apps
Task ❑
Ensure the prerequisite SAP Notes have been applied after the installation of the integration add-ons.
More Information See the Prerequisites Checklist [page 4] for the SAP Notes that apply to all of the following: Approve Requests Approve Leave Requests Approve Shopping Carts Approve Purchase Orders Approve Purchase Requisitions The following SAP Notes must be applied for Approve Leave Requests: ●
For the component GBHCM003: SAP Note 1621475: SAP Note 1525104 SAP Note 1555377 SAP Note 1487720 SAP Note 1538601
●
For the component GBHCM003 SP07: SAP Note 1854502 SAP Note 1793784 SAP Note 1846661 SAP Note 1849088 SAP Note 1883884
2
❑
Ensure that you have configured the connection between SAP NetWeaver Gateway and your back-end system.
3
❑
Ensure that you have activated the Gateway Activate Gateway and UI5 Services in SICF [page 15] services for the task.
4
❑
Check that you have connected the Gateway service for the task to your backend system.
See Activate and Maintain Services.
5
❑
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.
Specify Connection Settings to SAP NetWeaver Gateway [page 14]
For more information, see Define an Approval Scenario [page 48].
SAP Fiori Installation and Configuration Manager Apps
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
37
5
Sales Rep Apps
5.1
Configure Sales Rep Apps
Sales 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 Apps App
Description
Configuration Information
Check 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 44]
Create Sales Orders
Create sales orders on desktop and mobile devices. Create Sales Orders [page Sales representatives can reorder using a customer's 38] previously placed orders and select individual products to add to a new order.
Track Sales Orders
Manage the sales orders for customers by checking the Track Sales Orders [page status of order items and delivery schedules on both 41] desktop and mobile devices.
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 43]
Track Shipments
Provide precise shipment information to customers from a desktop or mobile device.
Track Shipments [page 44]
Customer Invoices
View customers unpaid, past due and disputed invoices or memos on a desktop of mobile device.
Customer Invoices [page 43]
5.2
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 40]
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
38
❑
Define Configuration Parameters
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
In the Define Configuration Parameters menu option, the following configuration parameters in Create
SAP Fiori Installation and Configuration Sales Rep Apps
Task
More Information Sales Orders application are maintained: See Configuration Parameters for Sales Orders Applications [page 40]. 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. Implementation 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 AddOn [page 48].
SAP Fiori Installation and Configuration Sales Rep Apps
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
39
5.2.1
Employee Master Record Creation
To 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 (SYUNAME) (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 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.2.2 Configuration Parameters for Sales Orders Applications The accompanying table lists the configuration parameters for the Sales Orders apps. Parameter
Description
Document 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.
Sold To Party (SOLD_TO / PARTNER_ROLE)
The value of the sold-to party parameter defines which partner role in the customer master is used for the sold-to party. The suggested value is AG.
40
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
SAP Fiori Installation and Configuration Sales Rep Apps
Parameter
Description
Forwarding Agent (FORWARDING_AGENT / PARTNER_ROLE)
The value of the forwarding agent parameter defines which partner role in the custonemr master is used for the forwarding agent. The suggested value is SP..
Notes To Receiver (NOTES_TO_RECEIVER / SO_TEXT_ID)
The value of the notes to receiver parameter contains the text ID for the location of the text object. The suggested value is 001.
Shipping Instructions (SHIPPING_INSTRUCTIONS / SO_TEXT_ID)
The value of the shipping instructions parameter contains the text ID for the location of the text object. The suggested value is 0012.
5.3
Track Sales Orders
To enable the SAP Fiori Track Sales Orders application, you must perform a number of configuration tasks. Task
More Information
1
❑
Ensure that an employee master record is created.
2
❑
Configure user information for the To configure user information for Track Sales Orders, application. call transaction SIMGH and open the Track Sales
See Employee Master Record Creation [page 40]
Orders node. 3
❑
Define Configuration Parameters
In the Define Configuration Parameters menu option, you can assign values for the following configuration parameters in Track Sales Orders: ●
Document Type (DOCTYPE)
●
Order Period (ORDPERIOD)
●
Search Period (SEAPERIOD)
For more information on the parameters, see Configuration Parameters for Sales Orders Applications [page 40]. 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 (BADI_SO_USR_TO_CUSTOMER) - This BAdI is used in the Track Sales Orders add-on. BADI_SO_USR_TO_CUSTOMER is located in enhancement spot ES_SDRA_SO. Use it to implement a method for associating employee to customers. A BAdI implementation, SRA018_SO_USR_TO_CUSTOMER, is activated in the standard system. In this implementation the
SAP Fiori Installation and Configuration Sales Rep Apps
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
41
Task
More Information customers are associated with the employee by reading the employee responsible in the partner function of the customer master. ●
Get Contacts Info (BADI_SO_CONTACTS) - This BAdI is used in the Track Sales Orders add-on. BADI_SO_CONTACTS is located in the enhancement spot ES_SRA_SO. Use it to implement a method for contact information selections (for example, title, name, phone number, and email address) displayed in the contacts tab of the Track Sales Orders application. The application can display two contacts for each customer. These can be contacts such as a dispute coordinator maintained in the partner functions of the customer master.
For more information, see Implement a Business AddOn [page 48].
5.3.1
Status Aggregation
There are two status fields: one for scheduled deliveries and one for the order item.
5.3.1.1
Status of Scheduled Delivery of an Order Item
A delivery schedule can have a status of Open, Shipped, or In Process. There is no direct link between a scheduled delivery and a delivery document and its goods issue: they are only linked to the order item. Delivery documents and goods issue quantities are dynamically allocated to scheduled delivery, based on dates. ●
A delivery schedule has the status Open if there is no delivery document assigned/allocated to it.
●
A delivery schedule has the status Shipped if the net goods issue quantity (goods issues minus goods issues cancellations) is equal to its confirmed quantities.
●
In all other situations the delivery schedule has the status In Process.
5.3.1.2
Status of an Order Item
The status of an order item is determined by looking at the status of its delivery schedules ●
42
If all delivery schedules of an order item are in status Open, the status of the order item is Open.
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
SAP Fiori Installation and Configuration Sales Rep Apps
●
If all delivery schedules of an order item are in status Shipped, the status of the order item is Shipped.
●
For any other combination of status fields of the delivery schedules, the status of the order item is In Process.
5.4
Change Sales Orders
To enable the SAP Fiori Create Sales Orders application , you must perform a number of configuration tasks. Task 1
❑
Implement and execute all the configuration tasks for the Track Sales Orders application.
2
❑
Turn on the EDITENABLED flag.
3
❑
Configure user information for the application.
More Information See Track Sales Orders [page 41].
To configure user information for Change Sales Orders, call transaction SIMGH and open the Change Sales Orders node. By default, the change order functionality is disabled. To enable the change functionality, enter X as the value for the EDITENABLED parameter. By default the value for this parameter is blank.
5.5
Customer Invoices
To enable SAP Fiori Customer Invoices you must perform a number of tasks. Table 7: Configure Customer Invoices Checklist Task 1
❑
Deploy the Business Add-In (BAdI): bdsra021_usr_to_customer
More Information This BAdI can be customized by changing the default VE Sales Employee code to the one implemented in your system configuration. Follow the SAP guidelines for the implementation of BAdIs. For more information, see Steps to activate BAdI Implementations.
Note In the Customer Invoices app, the related transaction for the list of available invoices is FBL5. The status of documents retrieved from FI customer account can be as follows:
SAP Fiori Installation and Configuration Sales Rep Apps
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
43
Task
More Information ●
Unpaid, past due included paid but with a clearing date in the future only
●
Disputed
For those documents the combination of Posting key x SD document type is: Posting key = 1 x SD doc type = O Posting key = 1 & SD doc type = P Posting key = 11 & SD doc type = M
5.6
Track Shipments
To enable the SAP Fiori Track Shipments app, you must ensure that any prerequisites are in place and perform a number of configuration tasks. Task 1
❑
Define the URL for each carrier (vendor).
More Information The URL is used to provide a hyperlink from the tracking number. In the back-end system, call transaction SIMGH and open the Define URL for Carriers node.
2
❑
Ensure the following Business Add-Ins (BAdIs) are deployed: Freight BAdI Image retriever BAdI User ID to Customer BAdI
Freight BAdI is used to fetch the freight charge for a particular shipment. A default implementation is delivered for the BAdI definition. Image retriever BAdI can be used to retrieve the image for a partner. Neither an active implementation nor a default implementation is delivered for the BAdI definition. Use ID to Customer BAdI is used to fetch a list of customers assigned to a particular user ID. A default implementation is delivered for the BAdI definition. A node for each of the three BAdIs is provided in the IMG.
5.7
Check Price and Availability
To enable the SAP Fiori Check Price and Availability application, you must must perform a number of configuration tasks.
44
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
SAP Fiori Installation and Configuration Sales Rep Apps
Task 1
❑
2
Configure user information for the application.
More Information In the back-end system, call transaction SIMGH, and open the Check Price and Availability node.
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 10]
4
❑
Check that you have enabled the SRA016_PRICE_AVAIL_SRV SICF
See Activate Gateway and UI5 Services in SICF [page 15]
Services for the Gateway 5
❑
Check that you have enabled the
See Activate Gateway and UI5 Services in SICF [page 15]
UI5_SD_PRAV_MON SICF Services for UI5 6
7
❑
❑
Deploy the Business Add-in: ●
BD_SRA016_USR_TO_CUSTOMER
●
BD_SRA016_PROD_IMG_RETRIEV ER
●
BD_SRA016_PLANT
Maintain the information for the Sales Order Document type and Price Condition Type in the configuration table SRA016_T_CONFIG
SAP Fiori Installation and Configuration Sales Rep Apps
For instructions on how to activate BAdI implementations, see Steps To Activate BAdI Implementations and Deploy Business Add-In XSS_REM_INTERFACE.
Not applicable
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
45
6
Purchasing Agent Apps
6.1
Configure Purchasing Agent Apps
The purchasing agent uses the apps to perform tasks such as ordering from requisitions and tracking purchase orders. Table 8: Purchasing Agent Apps App
Description
Configuration Information
Order from Requisitions
Convert approved purchase requisitions into purchase orders. The app automatically assigns matching suppliers to each purchase requisition, and then bundles the requisitions to create a purchase order for each supplier. Purchase orders can be simulated in the app before they are created in the back-end system.
Order From Requisitions [page 46]
Track Purchase Order
View important purchase order information. For each purchase order, the app shows the overall order fulfillment status, the quantities and values, and a graphical view of the process flow.
Track Purchase Order [page 46]
6.2
Order From Requisitions
To install the SAP Fiori Order from Requisitions application, you must apply a number of SAP Notes. Task 1
❑
6.3
Apply the required SAP Notes.
More Information To install the application, apply the following SAP Notes and apply the manual steps described in the notes: ●
SAP Note 1857391
●
SAP Note 1855300
Track Purchase Order
To install the SAP Fiori Track Purchase Order application, you must apply a number of SAP Notes. Task 1
46
❑
Apply the required SAP Notes.
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
More Information To install the application, apply the following SAP Notes and apply the manual steps described in the notes:
SAP Fiori Installation and Configuration Purchasing Agent Apps
Task
SAP Fiori Installation and Configuration Purchasing Agent Apps
More Information ●
SAP Note 1857512
●
SAP Note 1855299
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
47
7
How To
7.1
Implement a Business Add-On
You can create your own implementation of a Business Add-On (BAdI). After calling up the IMG activity, a dialog box appears, which displays the standard BAdI implementation. To create your own implementation, follow these steps: 1.
Choose Create.
2.
In the dialog box, enter a name for the BAdI implementation in the Implementation field.
3.
Select Create. The screen for creating BAdI implementations appears.
4.
From the tab index, select Interface. The Name of implemented class field is already filled on the tab page because a class name is automatically assigned to the implementation when you name it.
5.
Save your entries.
6.
Assign the implementation to a development class.
7.
Place the cursor on the method and double-click to enter method processing.
8.
Enter the code for the implementation between the statements method ~ and end method.
9.
Save and implement your code.
10. Return to the Edit Implementation screen.
Note You can create an implementation and activate it at a later time. In this case, end the processing stage at this point . 11. Save the entries on the Edit Implementation screen . 12. Select Activate. The code you stored in the method will be run when the application program is executed.
7.2
Define an Approval Scenario
To define an approval scenario, you add a scenario, assign a consumer type, assign roles, and define tasks. You must define approval scenarios for the following SAP Fiori applications: ●
Approve Requests
●
Approve Leave Requests
●
Approve Shopping Carts
●
Approve Purchase Orders
●
Approve Purchase Requisitions
48
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
SAP Fiori Installation and Configuration How To
●
Approval Purchase Contracts
1.
Add an approval scenario: a) In your SAP NetWeaver Gateway system, run transaction SPRO and choose NetWeaver
Gateway Service Enablement
Content
SAP Reference IMG
Task Gateway Service
SAP
Scenario Definition .
b) Choose New Entries. c) For each approval application you want to use, fill in the following fields and then save your entries:
Field
Approve Requests (Custom Workflow)
Approve Leave Requests
Scenario Identifier
LEAVEREQU ESTAPPROV AL
Approve Shopping Carts
Approve Purchase Requisitions
Approve Purchase Orders
Approve Purchase Contracts
CARTAPPRO VAL
PR_APPROV AL
PO_APPROV AL
PC_APPROV AL
Technical /IWPGW/ Service Name TASKPROCE SSING
/GBHCM/ LEAVEAPPR OVAL
/GBSRM/ CARTAPPRO VAL
GBAPP_PRA PPROVAL
GBAPP_POA PPROVAL
SRA001_PCA PPROVAL
EntitySet External Name
Task
LeaveReques WorkflowTas t k
WorkflowTas k
WorkflowTas k
WorkflowTas k
Property External Name
TaskDefinitio nID
TaskDefinitio nID
TaskType
TaskType
TaskType
TaskType
Class for Scenario Count
If the scenario is not a part of the Business Workflow engine, and you want to see the number of tasks pending for this scenario, enter the name of the class that implements the /IWWRK/ IF_TGW_SCE NARIO interface in the SAP system.
/GBHCM/ CL_APPROV AL_ITEM_CO UNT
Not available
CL_GBAPP_A PV_PR_WOR KITEM_COU NT
CL_GBAPP_A CL_SRA001_ PV_PO_WOR PC_WORKITE KITEM_COU M_COUNT NT
SAP Fiori Installation and Configuration How To
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
49
2.
Field
Approve Requests (Custom Workflow)
Approve Leave Requests
Approve Shopping Carts
Approve Purchase Requisitions
Approve Purchase Orders
Quick Act.
Select the Quick Act checkbox to enable quick approval of workflow items (iPad only).
Approve Purchase Contracts
Assign a consumer type: a) In the Scenario Definition table, select the row containing your approval scenario. b) In the Dialog Structure, choose Assign Consumer Type to Scenario. c) Choose New Entries. d) In the Task Gateway Consumer Type field, select TABLET. e) Save your entries.
3.
Assign role: In this step you can assign an approval scenario to a number of roles. That is, the scenario will only be available to users who are assigned one of the relevant PFCG roles a) In the Task Gateway Consumer Type table, select the row for TABLET. b) In the Dialog Structure section, choose Assign Role to Consumer Type and Scenario. c) Choose New Entries. d) In the Role column, select the desired role. e) Save your entries.
4.
Define tasks: a) In the Dialog Structure, choose Scenario Definition and select the row containing your approval scenario. b) In the Dialog Structure section, choose Task Definition for Scenario. c) Choose New Entries. d) In the Task Type field, enter the relevant task ID or IDs for the selected scenario(s). SAP Fiori Application
Scenario
Task Type ID
Approve Leave Requests
LEAVEREQUESTAPPROVAL
Optional:
Note This is a free-text information field. If you are using a custom HR approval workflow (optional), you can use this field to note the task ID.
50
Approve Shopping Carts
CARTAPPROVAL
TS40007953
Approve Purchase Requisitions
PR_APPROVAL
TS00007986
Approve Purchase Orders
PO_APPROVAL
TS20000166
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
SAP Fiori Installation and Configuration How To
SAP Fiori Application
Scenario
Task Type ID
Approve Requests (custom workflow)
Task type ID for the approval workflow in SAP Business Workflow
Approve Purchase Contracts
PC_APPROVAL
TS20000172
e) In the SAP System Alias field, enter the source system alias for the task type. The Task Gateway service should be connected to the selected system aliases.
Note Central hub deployment only: Use the SAP System Alias that is defined as “For Local App”. You can define SAP system aliases with activity Manage SAP System Aliases . f)
7.3
Save your entries.
Configure Launch Settings for Custom Workflows
You configure launch settings for custom workflows to add a tile for the SAP Fiori Approve Requests to the launch page. The launch page is part of the User Interface Add-On for SAP NetWeaver. The configuration options are described in detail in the administration guide for this add-on. The steps below cover only the critical settings for SAP Fiori Approve Requests.
Task
Key Settings
Section in Administration Guide for User Interface AddOn
1
Open the catalog administration page
Use the following URL: http:// :/sap/bc/ ui5_ui5/ui2/launchpage/admin/ admin.html
2
Create a catalog entry for Approve Requests.
Make a note of your catalog ID. You will need Setting Up the Launch it later to set up role-based access to the Page > Catalog application . Administration > Creating Catalogs
3
Add a tile to the launch page.
In the Select Tile dialog, select App Launcher Setting Up the Launch (dynamic). Page > Catalog Administration > The tile then shows the number of items Creating Catalogs > awaiting approval. Creating Tiles
SAP Fiori Installation and Configuration How To
Setting Up the Launch Page > Catalog Administration
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
51
Task
4
Configure the tile
Key Settings
Section in Administration Guide for User Interface AddOn
Dynamic Data area: ●
Service URL: /sap/opu/odata/ iwpgw/taskprocessing;mo/ ScenarioCollection/? $filter=key eq ' '
Setting Up the Launch Page > Catalog Administration > Configuring App Launcher Tiles
Use the scenario ID you defined for your approval workflow in customizing under SAP NetWeaver Enablement Service
Gateway Service
Content
Task Gateway
Scenario Definition .
Navigation area:
5
Configure a user role to enable user-specific access to the approval application.
●
Use Launchpad Deactivate this checkbox.
●
Target URL /sap/bc/ui5_ui5/sap/ui5_ca_all_apv/ index.html? backToHome=true&scenarioId=
1.
In your back-end system, call transaction PFCG (Role Maintenance).
2.
Select the relevant role.
Setting Up the Launch Page > Authorizations for Tiles on the Launch Page
Note We recommend you use the role defined for the workflow scenario under
SAP NetWeaver
Service Enablement Gateway Service Definition
Gateway
Content
Task
Scenario
Assign Role to Customer
Type and Scenario . 3.
52
One the Menu tab, insert a node of type Catalog Provider with the following values: ○
Catalog Provider: Free text, for example 001
○
Catalog Type: Catalog Page
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
SAP Fiori Installation and Configuration How To
Task
Key Settings
○
Section in Administration Guide for User Interface AddOn
Catalog Page: (This is the ID of the catalog entry you created in step 1.)
Users assigned to this role will now see the tile for your Approve Requests application when they call the launch page. For more information, see the documentation for the User Interface Add-On for SAP NetWeaver on SAP Help Portal at http://help.sap.com/nw-uiaddon > Application Help > User Interface Add-On 1.0 SPS04 for SAP NetWeaver, which you can also access via the link in Related Links. Related Information User Interface Add-On for SAP NetWeaver
7.4
Create a System Alias
You need to create an additional system alias for the back-end connection. 1.
Ensure there is a system alias for the back-end system with the software version DEFAULT.
2.
In addition to the DEFAULT software version, add a system alias with the following parameters: a) Local App checkbox: Selected b) Software version: Select the relevant data provider such as /IWPGW/BWF , or IWPGW/BPM (for a BPM server) For more information, see Creating the System Alias for Applications.
Related Information Creating the SAP System Alias for Applications
7.5
Configure Task Decisions
You can assign the decision options from your workflow task to the “approve” and “reject” options in the Approve Requests application 1.
In your back-end system, run transaction SPRO.
2.
Choose
SAP NetWeaver
Gateway Service Enablement
Content
Workflow Settings
Maintain Task
Names and Decision Options . 3.
In the Step Name table, enter the following:
SAP Fiori Installation and Configuration How To
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
53
a) Workflow ID: The ID of your workflow template, for example WS30000015. b) Step ID: The task step in your workflow template. c) Icon MIME Repository Path: Leave blank. d) Step Description: Enter the task name.
Note This name appears as the heading of the detail screen in the Approve Requests application. 4.
Select the entry in the Step Name table and open the Decision Keys in the navigation panel.
5.
Assign the decision keys for approval and rejection as follows: a) In the Decision Key field, enter the decision key that you want to use for approval.
Note The Decision Key corresponds to the Outcome Name for the task in the Workflow Builder. b) In the Nature field, select POSITIVE. c) In the Decision Key field, enter the decision key that you want to use for rejection. d) In the Nature field, select NEGATIVE. You can ignore the other fields in this table.
Note If the step type for the workflow task is User Decision, you can skip step 5. In this case, the first decision option is always assigned to POSITIVE (approve), and the second option to NEGATIVE (reject).
54
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
SAP Fiori Installation and Configuration How To
www.sap.com/contactsap
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Please see http://www.sap.com/corporate-en/legal/copyright/ index.epx for additional trademark information and notices.
View more...
Comments
