You are on page 1of 29

MOB207

Successfully Mobilize Fiori Apps


Mukul Nagle
Deloitte Consulting LLP
AGENDA

Case study background


Considerations for Fiori Mobilization
Benefits and lessons learned

2
CASE STUDY BACKGROUND

3
Case Study Background

SAP greenfield implementation at a telecom


chip manufacturer
Global presence 5,000 users in 25 countries
HR, Finance, Sales, Supply Chain, BI
Fiori and mobility at the core of all modules
Mobile device management (MDM) rollout

4
Business challenges

Need to modernize ERP platform to scale business


Risk of low user adoption after ERP go-live
Low productivity in transactional processing
Unavailability of real-time data for decision making
Lack of mobile self-service for users across 25 countries
Limited visibility into sales and warehouse operations
Security risk in corporate data on mobile devices

5
Why invest in enterprise UX?
Productivity
How easy is it for users to learn the application? How efficiently can they accomplish
basic tasks every time?

Improved data quality and error reduction


How many errors do users make, how severe are these errors, and how easily can they
recover from them?

User Satisfaction
How pleasant and motivating is it to use the application?

Enhanced decision making


Does the application provide specific data needed for making effective decisions?

6
UX Approach

Traditional Approach Day-in-the-Life Approach

Multiple Complex
Roles Pain Points. Motivation

Transaction Transaction Tasks Objectives


Transaction Transaction
App App
Transaction Transaction
Tools
App App
Transaction
App App
Unified Experience and
App Integrated Apps

7
Mobility Scope
16 standard and custom Fiori apps for HR, Sales, Supply
Chain, Procurement
Mobile SAP Inbox / UWL
Enterprise Warehouse Dashboard
SAP Mobile Platform (SMP) 3.0
SaaS apps: Cloud for Travel (C4T), BOBJ Mobile, Success
Factors Bizx
Mobile Device Management using Airwatch

8
Fiori and Mobility application scope

Employee Self Service Finance Sales & Operations Travel and Expense SaaS
Timesheet Approvals Invoice Approvals Sales Order approvals Travel Request Form Success Factors

Leave requests Project Accounting EWM Dashboard Travel Request GetThere


Approvals Approvals
Termination request Purchase Requisition Cloud for Travel
approvals Internal Order Approvals
Approvals
Recognition Approvals Engineering Service
Shopping Cart Requests
Create Position Approvals
Approvals
Mobility features

Usability Mobility Mobile Devices


Mobile Universal Mobile Device Management Samsung Galaxy S3/S4
Worklist (UWL) (1,500 devices)
Mobile Security
Branding iPhone 4S, 5, 5S, 6 (800
Performance Testing devices)
Change Mgmt.
App Containerization iPad 2, 3 (4,500 devices)
Training
App Provisioning
Push Notifications Apple
& Android

10
Fiori standard technical features
Fiori is a HTML5 and JavaScript based application that runs in desktop
and mobile browsers.

Consistency integrated with the same functionality as SAP GUI


Responsive web design adapts to desktop or laptop form factor
Extensible ability to easily customize Fiori apps through numerous
UI controls and readymade libraries
Role-based enables end users to personalize the Fiori launch pad
Branding user interface and look-n-feel can be customized to
match corporate branding standards

11
Fiori Deployment Options

Desktop / mobile browser SAP Fiori Client Kapsel container

Contains in-built browser


Downloadable native app Only option for Fiori to
Browser based apps
Contains commonly used access native mobile features
Runs on all devices
Cordova plug-ins Offers App Administration
No installation required
Native device integration Push Notifications
Consistent UX across devices
Notification App Updates Offline application data
SMP services required

12
Why Kapsel was chosen?

Improve app caching performance


Secure connectivity to SAP backend
Enhance mobile data security
Enable Apple / Google push notifications
Control app deployment to user devices
Manage app lifecycle through MDM software
13
Considerations for Fiori Mobilization

14
Considerations for Mobilizing Fiori

Fiori app registration


Mobile user authentication
Functional Testing
Fiori performance optimization
SAP Push notifications
Device native features
Mobile app rollout

15
Fiori App Registration
Cloud
APNS, GCM A. MDM installation on device
B. Device registration in SMP
C Internal
Firewall SAP Mobile C. Device registration in Apple /
Platform (SMP) Google cloud for messaging
B

SAP Systems
A

SAP ECC
MDM SAP FIORI
add-on
Tunnel

SAP SRM
SAP FIORI
add-on

User Devices with


MDM
SAP NetWeaver
Gateway
Internet DMZ Corporate Network
16
Mobile user authentication
Cloud
APNS, GCM 1. User enters ID / password
2. SMP authenticates user and
Internal
Firewall SAP Mobile issues SAP logon ticket
Platform (SMP) 3. Use is Single Signed On (SSO)
2 to SAP Gateway using the
SAP Systems SAP login ticket
1 4. SAP Gateway web services
SAP Logon 4 SAP ECC call backend RFCs
MDM Ticket SAP FIORI
SAP Logon add-on
Tunnel Ticket

SAP SRM
SAP FIORI
add-on
3

User Devices with


MDM
SAP NetWeaver
Gateway
Internet DMZ Corporate Network
17
Functional Test Scenarios

App Role based Transaction Parallel


User Login
Functionality access processing Testing

Multi-browser Multi-device Network Geographical


Device Testing
Testing Testing Testing Testing

App Push Geographical


MDM Testing Device registration
Lifecycle Notifications Testing

18
Fiori performance optimization
Mobile Solution Stack Test Metrics

Server response time


Server Hardware resources
DB performance

Response time
Network Network bandwidth
Network quality / latency

Application load time


Device CPU, memory Footprint
Web service processing time

App payload
Client App HTML asset reuse
Caching performance
19
Push Notifications setup
Cloud
5 APNS, GCM 4

Internal
Firewall SAP Mobile
Platform (SMP)

SAP Systems
SAP Logon
Tickets
3
SAP ECC
MDM 1 SAP FIORI
SAP Logon add-on
Tunnel Tickets

SAP SRM
SAP FIORI
add-on
2

User Devices with


MDM
SAP NetWeaver
Gateway
Internet DMZ Corporate Network
20
Integration with native device features
Cordova Plug-ins Kapsel Add-ons
Camera Offline OData
Capture Push
Geolocation App Update
Contacts Logger
Accelerometer E2E Tracing
Device Information Settings
Network Connection Auth Proxy
Battery Status
Compass Barcode Scanning
Media Playback Calendar
Access File Encrypted Storage
File Transfer Voice Recording
Dialog Notification In-App Message
Vibration Notification App Preferences
Globalization Attachment Viewer
SplashScreen Cache Manager
In-App Browser Printer
SAP Mobile Platform DebugConsole Online Apps
Status Bar Toolbar
21
Mobility rollout
MDM rolled out in
waves prior to SAP go-
live
Fiori apps launched in
waves after SAP go-
live
Dedicated user and
executive
communications
deployed for each
wave deployment
End-to-end support
team established for
mobile tickets
Results and lessons learned

23
Channels For SAP Approvals

Fiori Fiori Portal


App Fiori
Approvals Approvals Worklist
Worklist
App (web) (UWL)

Devices Mobile devices Laptop, Tablets Laptop, Tablets Laptop

3 waves post Go-


Deployment live
At Go-live At Go-live At Go-live
Project outcome
Mobile self-service for Travel, Expense, Learning and Performance
Anytime, anywhere access to SAP approvals for 5000+ employees
Sensitive data over secured devices and network
Real-time mobile push notifications for SAP workflow items
Increased asset efficiency in $3 billion sales and warehouse operations
1,000 work items average are processed across process areas per day
500+ Timesheet/Leave requests
300+ Sales/Purchase requests
100+ Engineering Service/Travel requests

26
Benefits delivered

Ease of use for most-used SAP functionality


Simplified user interface and fewer clicks for complex SAP transactions
Anytime, any device access to SAP backend
Role-based, personalized and flexible deployment options
High degree of SAP investment reuse
Consistency of data and configuration between SAP backend and apps
Higher user adoption during a SAP big-bang go live
Lessons Learned
Encourage active business participation in design sessions
Mobility app functionality is not a replication of the ECC backend
transactions
Design the UX to limit the number of clicks and screens
Reduce volume of SAP fields to only those required for approvals
Design apps for minimal or none end-user training
Manage the variation of devices supported to contain testing effort
Deploy in phases for better quality user support
Organize support team to debug mobile as well as backend modules
and
Simple app and proactive communications are a winning formula

28
FOLLOW US

Thank you for your time


Follow us on at @ASUG365

29

You might also like