2. Agenda
Pitfalls in Business process
Introduction to SAP Fiori Solutions
SAP Fiori Apps
Architecture
Overview
Service Scope
Wrap Up and Q&A
3. Pain Points in Approval Process
Delay in approval(need to intimate approver via mail/call)
No Approval Notification
Approve/Reject option not available
In case of Rejection, need custom table entry deletion explicitly
Difficult to keep the records
4. Key benefits of SAP Fiori
Improving customer’s user experience
Increase
productivity
Employees are able
to get the job done
anytime, anywhere
Managers can
streamline processes,
impact business
results
Apps are coherent
and easy to use
Additional features
(example: mass
approvals) to
accelerate handling
Lower risk Reduce TCO
Implementation aligned to
business value and
feasibility
Supportability by SAP
SAP validated and tested
Future-proof investment
Continuous innovation
Improve time to
value
Faster implementation
Predictable
implementation
timeline
Better quality
assurance/reliability
Standards-based,
flexible software
framework
Instant roll out
capabilities to different
devices
Reduce customization
and integration
complexity via SAP
Fiori toolkit and rapid-
deployment offerings
Lower maintenance
costs
Reuse of skill sets
Intuitive usage
significantly reduces
learning effort and cost
5. Why FIORI?
• SAP Fiori is cross platform collection of mobile applications(600+ apps) for different
business functions of SAP
• SAP Fiori is ready made applications which are ready to be deployed as per your current
SAP system configurations
• SAP Fiori rapid deployment solution helps customer deploying Fiori apps faster and easier
way
10. SAP Fiori - Frontend Technology
Fiori apps build with SAP UI5 technology (HTML5)
UI artifacts are deployed with ABAP technology
Support of smartphones, tablets, and desktop (by responsive design
patterns)
Different form factors and operating systems are supported with single
code line
Fiori Apps are launched and running in the Fiori Launchpad as UI
components
Business data is retrieved through OData services during runtime
11. SAP Fiori – Architecture
Transactional Apps (AT1) - Business Suite Version / Enhancement Package
• Focused on transactional scenarios
released to run with the latest
enhancement package
e.g. SAP ERP 6.0 EhP 7, SAP CRM 7.0
EhP 3, SAP SRM 7.0 EhP 3 …
• Apps are deployed by ABAP UI add-ons
• Apps are connected via OData services
• OData services are shipped
via ABAP Support Packages
on the highest available Business Suite
release
e.g. SAP ERP 6.0 EhP 7, SAP CRM 7.0
EhP 3, SAP SRM 7.0 EhP 3 …
• HANA and any database* are supported
12. SAP Fiori Apps on Any DB Today
Across lines of business and industries
13. SAP Fiori Launchpad
Web-based entry point for SAP business applications across platforms and
devices
• The FIORI Launchpad
provides end-users an entry
point to Fiori applications
in a role-based, consistent
and user-friendly manner
using tiles.
• Tiles show
dynamic/live/real-time
application information
(like status, KPIs) on the
home page.
• Predefined content and
high degree of
personalization .
• Tiles can be selected from
catalogs and arranged in
groups.
• Search is integrated.
17. Service Scope - Infrastructure SAP Fiori foundation deployment
• Deploy infrastructure Notes for
SAP Gateway and SAP UI5
• Deploy SAP UI5 for NetWeaver
Add-On
• Connect SAP Gateway to SAP
Backend
• Configure Backend Event
Publisher
• High Availability Landscape
Deployment
• SAP Gateway and SAP UI5 are the core component of SAP Fiori infrastructure with
the capability to support multiple users and applications in a productive
environment.
• Gateway is integrated with SAP Business Suite systems and provides a set of oData
services. SAP UI5 enables the consumption of those oData services in any
compatible browser for a true multi-channel UI experience
18. Service Scope - SAP Gateway Deployment Options
1) Central Hub Deployment of
SAP Gateway
2) Embedded Deployment of
SAP Gateway
Recommendation is to use the Central
Hub Deployment, if several SAP backend
systems need to be connected.
Use the Embedded Deployment if
you only need to connect to one
backend system.