TAQA SF ECP Implementation- Release 2

Technical Specification – Travel Management App

Project Identification
Project ID
Project Name TAQA SF ECP Implementation- Release 2
Customer Organisation TAQA
Siddhesh Ananta Tilekar
Customer Success Manager, Email [email protected]
Vishnu Balakrishnan
Customer Project Manager, Email [email protected]
Raghavendra Kolanu
Document Author, Email [email protected]
 Process Name Technical Specification

Approvals and Authorizations

Ver. No. Ver. Date Prepared By Reviewe Review Approved Affected Section & Summary of Change
d By Date By

1.0 10-11- Raghavendr

2024 a Kolanu

Document Version: <Date> INTERNAL Page 2 of 12

 Process Name Technical Specification

Table of Content
1. Overview....................................................................................................................................................3
2. System Architecture...................................................................................................................................4
3. Application Design......................................................................................................................................4
4. Technical Requirements.............................................................................................................................5
5. Development Specifications.......................................................................................................................6
6. Security.......................................................................................................................................................6
....................................................................................................................................................................... 6
7. Performance...............................................................................................................................................7
8. Testing........................................................................................................................................................7
9. Deployment................................................................................................................................................8
10. Maintenance and Support........................................................................................................................8
11. Documentation.........................................................................................................................................9
12. Appendices...............................................................................................................................................9
13. Application Output...................................................................................................................................9

Document Version: <Date> INTERNAL Page 3 of 12

 Process Name Technical Specification

1. Overview
 Purpose: Develop a custom SAPUI5 application for Managing Travel Requests within the
organization.
 Scope: Provides Functionalities for Creating, Reading, Updating, and Managing Travel request data.
 Objectives: Streamline request handling and enhance usability with a modern SAPUI5 interface.

2. System Architecture
 High-Level Architecture Diagram:

 Components:
o SAP BTP Services: SAP HANA Cloud, SAP Business Application Studio
o SAPUI5: Version 1.123.1
o Backend Systems: SAP OData services configured in manifest.json,SAP SuccessFactors.

Document Version: <Date> INTERNAL Page 4 of 12

 Process Name Technical Specification

3. Application Design
 UI Design:
o Views: XML Views ( View1.view.xml)
o Controllers: Core logic files (BaseController.js, View1.controller.js)
 Navigation Structure:
o Home
o Travel Request Details
o Create Request
o Reissue

4. Technical Requirements
 SAPUI5 Version: 1.123.1
 SAP BTP Services: SAP Business Application Studio

Document Version: <Date> INTERNAL Page 5 of 12

 Process Name Technical Specification

 Roles: TAQA_TRAVEL_FOCALPEOPLE.
 Backend Systems:
o OData Services: TSDCLNT100 /API_PROJECT_V2,
TSDCLNT100 /API_COSTCENTER_SRV, TSDCLNT100 /API_INTERNALORDER_SRV,
SF/odata/v2, TAQA_BTP/v2/taqa-srv/.

5. Development Specifications
 Frontend Development:
o Views: Detailed XML files defining UI.
o Controllers: Contains logic for data handling and event processing.
o Models: JSON files for static data, ODataModel for backend integration.
 Routing and Navigation: RouteView1 for View1, defined in manifest.json.
 Event Handling: Standard SAPUI5 event patterns.
 Data Binding: Two-way binding for dynamic UI updates.
 Integration: SF-BTP integration via CPI auto schedule job, program written in CAPM service Taqa.DB.

Functions implemented in the Controller

S.No Function Name Description

1 onInit Initialisation of models, objects and variables
2 getEmpDetailsEmail Validating the logged in user is admin or not
3 onSearch Fetching the details based on the user inputs

Document Version: <Date> INTERNAL Page 6 of 12

 Process Name Technical Specification

4 onCreatePress Create the Travel request

5 onRivewButtonPress Review the Travel request
6 onAgentInitiateProcess Initiate the request to Travel Team
7 onPdfButtonPress Download the Travel Request Form
8 handleUploadPress Upload the PDF form into DMS system
9 onAddFamilyButtonPress Add the Family details to Travel form
10 onAddButtonPress Add the Ticket details to Travel form
11 onCompleteButtonPress Complete the Travel request form
12 onUpdateButtonPress Update the Travel request form
13 onCancel Cancel the Travel request form

6. Security
 Authentication: OAuth 2.0 with SAP ID Service
 Authorization: Role-based access control (RBAC)
 Data Encryption: HTTPS for data transmission, AES-256 for data at rest

7. Performance
 Performance Optimization: Code minification, lazy loading for views
 Caching Strategies: Local storage for static assets

Document Version: <Date> INTERNAL Page 7 of 12

 Process Name Technical Specification

8. Testing
 Unit Testing: QUnit for controller logic validation
 Integration Testing: Testing data flow between frontend and backend services
 User Acceptance Testing (UAT): Conducted with end-users

9. Deployment
 Environments:
o Development: taqa_dev_fiori
o Testing: taqa_qas_fiori
o Production: taqa_prd_fiori

Document Version: <Date> INTERNAL Page 8 of 12

 Process Name Technical Specification

10. Maintenance and Support

 Logging and Monitoring: Cloud Foundry tools
 Issue Tracking: [Specify Tool if used]

11. Documentation
 User Documentation: In docs folder
 Technical Documentation: Code and configuration details in docs

12. Appendices
 Glossary: SAPUI5, BTP, OData
 References: SAP Developer Guide

Document Version: <Date> INTERNAL Page 9 of 12

 Process Name Technical Specification

13. Application Output

Document Version: <Date> INTERNAL Page 10 of 12

 Process Name Technical Specification

Document Version: <Date> INTERNAL Page 11 of 12

 Process Name Technical Specification

Document Version: <Date> INTERNAL Page 12 of 12