This document summarizes a case study of a SAPUI5 application developed to simplify the calculation and reporting of project gains and losses based on team performance. The key challenges were the need to integrate different systems and automate processes to reduce manual work. The solution involved developing connected applications using SAPUI5 as an open platform and integrating SAP ECC, a workflow engine, rules engine and other third party applications. This provided benefits like reduced data entry errors, automated approvals and visibility across processes.

1. Case Study
Processing Gain and Loss through a SAPUI5 Application

2. ©2015 Infosys Confidential
2
Challenges & Measures
Key Drivers Solution Benefits
• Simplify the calculation,
charging and reporting of
mid-project Gain / Loss
contingent on team
performance
• Un-integrated technology
with landscape leading to
lot of “back and forth”
between front & back
office staff
• Need for systems
integration, process
automation and consumer
grade intuitive user
experience cutting across
applications
• Ease of use and user
interface that “Wows”
• Mobile access
• Reduce / eliminate data
duplication and data entry
errors
• Simulation options for
smart decision making
• Visibility across entire
business process

3. ©2015 Infosys Confidential
3
Architecture
Connected
Applications
Open Source
Platform
Agnostic Apps
Process
simplification
Best
practices for
development
Leverage existing
architecture
• Use open source UI layer (UI5) to create platform
agnostic apps (mobile, handhelds, desktop) leveraging
OData services
• Create linkages between SAP, Workflow, rules engine,
3rd party applications to facilitate automation & process
simplification leading to reduction in manual effort
• Leverage existing architecture and code pieces to the
extent possible (technically as well as functionally)
• Follow best practice guidelines (for ex- while deploying
gateway servers or using OData services)

4. ©2015 Infosys Confidential
4
Project Overview
Nov 14 Dec 14 Jan 15 Feb 15
Roadmap Phase
• Vision and Strategy
• “To-be” business
capabilities
• Build business case
Build Phase
• Basis Installation (SAP
Gateway)
• Write / modify services
• Build integrations
• SAP customizations
• Convert master/ transaction
data if needed
Design Phase
• Write User stories
• Define Application architecture
• Design “To be” wireframes
(using “agile” methodology)
• Identify the nature of services-
• Use as-is
• Use with modification
• Build New
• Define Training and Support model
• Hardware Sizing
Release: Testing
and Deployment
Phase
• Unit & integration Test
• Performance Test
• User Acceptance
Testing
• Training
• Deployment

5. ©2015 Infosys Confidential
• Conduct interviews
• Wireframe UX
• Uncover explicit & Implicit
needs
• Lock Scope for app
• Demo application with
integrations
• Run scenarios
• Test user experience through
different devices
• Prototype user interfaces &
process flow
• Iterate process & UX
5
Design Phase
A focus on design thinking
Discover Design Deliver

6. ©2015 Infosys Confidential
6
Use Case
Persona- Billing Manager
Process
Step
Underlying
System
Desired
Benefit
Calculation of mid-
project Gain / Loss
contingent on
team’s
performance
ECC6.0
BI7.3
Simulation
options and
calculation
Validation of LOB
specific business
rules and
execution of
approval workflow
3rd party rules
engine
3rd party workflow
application
Integration of
rules & workflow
engine using
middleware
Financial postings ECC6.0 Integration of
request db and
ECC
4People
7Systems
36Screens
62Clicks
Average
turnaround
time –
3days
2People
3Screens
1app
7Clicks
Average
turnaround
time –
6hours

7. ©2015 Infosys Confidential
7
Architecture
SAPUI5 Application
Workflow Engine
Middleware
Reverse Proxy (SAP Web Dispatcher)
Rules Engine
SAP ECC
The flow diagram describes the process
flow between the integrated systems
The application was deployed on the
fiori Launchpad
The Launchpad hosted other applications
as well as this one

8. ©2015 Infosys Confidential
8
Landing Page

9. ©2015 Infosys Confidential
• Automate e2e business process to derive
maximum benefit of implementation
• Enterprise apps to cut across applications
(SAP, Oracle, 3rd party cloud etc.)
• Use existing services where applicable
(Web services, RFC’s, SOAP etc.)
• Analyze the possibility of UI5 development
with angularjs/ other JavaScript
frameworks
• Explore offline possibilities of FIORI apps
9
Key Takeaways
Strategic
• Data Accuracy
• Standardization &
consolidation
• Process & Technology
Improvement
• IT innovation
• Improved decision making
• Customer Satisfaction
Subjective Objective
• Complexity
Management
• Risk Management
• Retire Legacy apps
• Operational spending
• Standardized infrastructure
Tactical &
Operational

10. © 2014 Infosys Limited, Bangalore, India. All Rights Reserved. Infosys believes the information in this document is accurate as of its publication date; such information is subject to change
without notice. Infosys acknowledges the proprietary rights of other companies to the trademarks, product names and such other intellectual property rights mentioned in this document. Except
as expressly permitted, neither this documentation nor any part of it may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical,
printing, photocopying, recording or otherwise, without the prior permission of Infosys Limited and/ or any named intellectual property rights holders under this document.
Thank you
10