0% found this document useful (0 votes)

39 views50 pages

CR_001_MashreqBank_ADM_Chargeability_Oracle Fusion Cloud_TDD_v1.0

The document outlines the Technical Specification for the Mashreq Bank Cloud Extension Project focusing on the ADM and Chargeability solution development. It details the purpose, scope, assumptions, and technical components necessary for the implementation of the solution, including integration with Oracle Fusion and various APIs. The document serves as a guide for developers to ensure successful business transformation through automated application integrations and comprehensive design specifications.

Uploaded by

Sekhar Srinivasiah

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as DOCX, PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

39 views50 pages

CR_001_MashreqBank_ADM_Chargeability_Oracle Fusion Cloud_TDD_v1.0

Uploaded by

Sekhar Srinivasiah

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as DOCX, PDF, TXT or read online on Scribd

You are on page 1/ 50

Mashreq Bank (MB)

Cloud Extension Project

Technical Specification – ADM & Chargeability Solution Development
September 2024 V 1.0

Oracle Consulting (OC)

Nithishkumar
`

Document Control
Document History
Version Date Author Summary of Changes

1 20th September Nithishkumar

Initial draft
2024

2 10th November Nithishkumar Updated the TDD based on phase1

2024 development

Reviewed By
Reviewer Date Role / Responsibility

Stanny Injeti Project Manager

Venkateswarlu Alaparthi Functional Lead

Sekhar Srinivasiah Extensions & Integrations Solution Architect

Oracle Consulting Services | Technical Specification for Mashreq Bank | September 2024 | Page 2 of 50
`

Table of Contents
Introduction............................................................................2
Purpose..............................................................................................................................................2
Scope.................................................................................................................................................2
Assumptions......................................................................................................................................3
References.........................................................................................................................................3

Notation Legend.....................................................................4
Introduction............................................................................5
Business Requirement.......................................................................................................................5
Oracle fusion (SAAS)..................................................................................................................5
Custom ADM Solution PAAS......................................................................................................5

Validations...............................................................................7
Solution Overview..................................................................8
Process Flow/Sequence Diagram.......................................................................................................8
Technical Architecture.......................................................................................................................9

Technical Component – ADM and Chargeability...................9

OIC Services & APIs............................................................................................................................9
OIC Package.....................................................................................................................................16
BIP Reports......................................................................................................................................16
ORDS Service...................................................................................................................................17
ORDS PL/SQL Packages....................................................................................................................29
User Interface Screen......................................................................................................................29
ADM APPROVAL HIERARCHY...........................................................................................................38
Custom Tables.................................................................................................................................38
Sequence.........................................................................................................................................40
Logging............................................................................................................................................40
Users & Security..............................................................................................................................40
SaaS setup/configurations...............................................................................................................40
Look up............................................................................................................................................41
Technology Platforms......................................................................................................................41

Risks, Assumptions & Dependencies....................................42

Open & Closed Issues...........................................................43

Oracle Consulting Services | Technical Specification for Mashreq Bank | September 2024 | Page 3 of 50
Introduction
Purpose
The objective of this document is to provide a Technical Specification to realise the solution outlined
in the corresponding Functional specification as part of their Oracle Cloud Extension initiative for the
Project ADM and Chargeability.

The Technical Specification supports the delivery of a successful business transformation by

 Mapping right technology capabilities with the functional solution to address key business
objectives
 Automating application Integrations
 Providing low level design for developers
 Capturing configurations, operational and other non-functional considerations for this
extension
 Comprehensive description of the various components including the extension process flow
 Technical specifications of the various services that comprise the solution

Scope
This document is the first iteration of the Technical Specification for the Project ADM and
Chargeability – Cloud Extension project. It is valid for the Oracle True Cloud Method Build stage. The
Project ADM and Chargeability - Cloud Extension Technical Specification will be updated as
appropriate for each True Cloud Method iteration and/or Phase of the project.

The content of this document provides a solution for the following items:

Ref Type Description

EXT Extension ADM

EXT Extension Chargeability

EXT Extension Worklist Notification

EXT Extension Approval Configuration Setup Screens

The Technical design aims to provide the following

Oracle Consulting Services | Technical Specification for Mashreq Bank |September 2024 | Page 2 of 50
1. Describe the applications technology landscape utilized in building this extension. It is also a
reference for the developers during the implementation phase.
2. Provide an overview of the custom process flows, validations and transformations and
integration touch points associated, as applicable
3. Describe the architectural components required to implement the agreed solution.
4. Technology capabilities with the functional solution to address key business objectives

Assumptions
This Technical specification assumes the following:

1. All custom configurations including the lookups, value sets, etc. are configured appropriately
in Fusion application.
2. Data entities for which the data sync must happen will be configured earlier or ready.
3. The same user would be used in both Fusion Cloud Applications and the PaaS Identity Store
for identity propagation and authentication.
4. Extension / Integration will work based on mentioned in FDD business scenario / use cases.
5. Any transformation required to be done, must be explicitly mentioned, and documented
within the functional design document.
6. Any new business scenario / use case identified post release of this functional specification,
will require change control.

References
The content of this document is based on the following reference documents.

Versio
Reference Description
n

CR_001_MashreqBank_ADM_Chargeability_Orac Functional Design Document 1.0

le Fusion Cloud_FDD_09_SEP_2024

Oracle Consulting Services | Technical Specification for Mashreq Bank |September 2024 | Page 3 of 50
3
Notation Legend
Artefact Description
Terminal or Terminator Shape The terminator symbol marks the starting or ending
point of the system. It usually contains the word "Start"
or "End."

Lines with Arrows The lines with arrows determine the flow through the
chart. Flowcharts are usually drawn from top to bottom
or left to right. Numbering shapes are optional.

Rectangle The rectangular artefact is used to artefact

"describe/define" a process or a single step.

Decision This symbol indicates a point where the outcome of a

decision dictates the next step. There can be multiple
outcomes, but often there are just two - yes and no.

Input / Output This symbol represents information entering or leaving

the system.

Subroutine or Predefined Process

This symbol indicates a sequence of actions that
perform a specific task embedded within a larger
process. This sequence of actions could be described in
more detail in a separate flowchart.
Stored Data This symbol indicates that information is coming into
the process from outside or leaving the process.

Oracle Consulting Services | Technical Specification for Mashreq Bank |September 2024 | Page 4 of 50
Introduction
Business Requirement
This section provides a technical overview of the solution that will meet the objectives for the ADM
(Authority Delegation Matrix) for purchase requisition approval hierarchy.

Oracle fusion (SAAS)

 User creates standard PR in Oracle fusion system.

 1st level of approval by fusion dummy username when user “SUBMIT” that PR.

 After submitting the PR, the status will be updated to "PENDING APPROVAL" in Fusion.

Custom ADM Solution PAAS

 On the standard PR page, the user cannot submit without enter and validating the
chargeability and ADM category. The user wants to click the ADM & Chargeability
hyperlink/button, which will navigate to a custom solution, copying the header and line data
to enter the chargeability details for each PR line and to ensure that the category is the same
for all PR lines.

 On the custom page, the user can enter chargeability for each line. For FA and PP item types,
chargeability is mandatory.

 In Chargeability Screen Save and Close option is also implemented, allowing users to enter
chargeability for remaining PR lines at a later time.

 We can provide an import option to add bulk records from an Excel file(csv). The following
steps should be followed for the import option:
1. The user should manually enter the account combination.
2. We should provide the import option at the PR line level.
3. After uploading the CSV file in the frontend, we can validate each line
entered in the Excel sheet and then send it to the pass table.
4. If any wrong combination is entered in the Excel sheet, we should display a warning
message.

This is how can implement the import functionality

 On the Chargeability screen, the user wants to select the account code combination
segment-wise. We validate and create the GL account code in fusion, and if an invalid
combination is selected, an error will be thrown.

Oracle Consulting Services | Technical Specification for Mashreq Bank |September 2024 | Page 5 of 50
 After entering chargeability for all lines, the user can save and close. However, if the
chargeability amount does not match the line amount, saving and closing will not be allowed
until the amounts match.

 After that, the user can proceed to submit the PR. Before submitting, they can preview the
approval hierarchy, which will follow the approval workflow

 Once user submitted the PR custom ADM approval workflow will trigger.

 After submitting the PR, the user needs to navigate to the Fusion PR page and click the
"Validate" hyperlink to check if the ADM category is correct and if chargeability details have
been entered. If not, the system will prevent the user from submitting the PR. At the PR
header level, the ADM category and Chargeability DFF will be checked upon clicking
"Validate." The system will validate the category and chargeability details in PaaS, and it will
update the DFF. Once the validation is successful, the user will be able to submit the PR in
Fusion.

 After submitting the PR, its status will change to "Pending Approval." In fusion , If the user
wants to know the approval status of the PR, they can go to the Manage Requisition page,
where the ADM and Chargeability hyperlink is available. By clicking on this hyperlink, the
user will be navigated to the same PR custom page, where they can view the approval action
history

 The approver will receive a notification via email, where they can approve, reject, reassign,
or request more information directly within the email. If they miss the email, they can take
action on the new custom worklist notification page “ADM PR APPROVAL”. Please find below
an image for reference.

Oracle Consulting Services | Technical Specification for Mashreq Bank |September 2024 | Page 6 of 50
 When the user clicks on the ADM PR Approvals page in Fusion, it opens the custom
notification page where the user can take action on the requested PR. Please see below
image for reference

 Upon final approval of the PR, whether the status is 'Approved' or 'Rejected' in VBCS, we are
updating the Fusion PR Status column as 'Approved' or 'Rejected' through the OIC API using
Oracle BPM Tasks.

Validations

 ADM Category Validation – When the user creates PR lines with different category codes,
the system will not allow them to submit the PR

 Chargeability Item Type Validation – If any PR line has an item type of FA or PP,
chargeability is mandatory for that line

 Chargeability Amount Validation – If the split chargeability amount does not equal to the PR
line amount, the system will throw an error.

 GL Account Code Combination Validation- If user creates a code combination with invalid
segment selection, we will throw an error message “Invalid combination”.

Oracle Consulting Services | Technical Specification for Mashreq Bank |September 2024 | Page 7 of 50
 Final Submit Validation – If the user tries to submit without entering chargeability for fixed
asset and prepaid item lines, the system will not allow submission and will display an error
message: "Chargeability is Mandatory."

Solution Overview
This section provides a technical overview of the solution that will meet the business objectives,
listed in the corresponding functional specification for the ADM and Chargeability.

Process Flow/Sequence Diagram

A high-level overview of the end-to-end process is as follows.

Oracle Consulting Services | Technical Specification for Mashreq Bank |September 2024 | Page 8 of 50
Approval workflow

Technical Architecture
A high-level overview of the technical architecture end to end process is shown below.

Oracle Consulting Services | Technical Specification for Mashreq Bank |September 2024 | Page 9 of 50
 The ADM and Chargeability solution will be built using the Visual Builder Cloud Service. To
support the various functionalities in the page Oracle Integration Cloud, ATP Database and
ORDS cloud PaaS services are used.

 The VBCS application will host the user interface screens, while the approval engine
workflow will define by VBCS email templates using JS, OIC, and some custom PL/SQL
packages.

 The data entered by the requesters or approvers will be stored in the ATP DB. The data
transfer between the cloud services will be performed using OIC and ORDS.

Technical Component – ADM and

Chargeability
OIC Services & APIs

This section provides more-detailed look at each integration used in this

Extension.

Oracle Consulting Services | Technical Specification for Mashreq Bank |September 2024 | Page 10 of 50
1. This Integration retrieves the PR header details from SaaS to PaaS.

Prompt Description
Integration Type fscmApi

Name getPurchaseRequisitionsHeader
Version latest
Method Get
Package NA
Integration File NA

2. This Integration retrieves the PR lines details from SaaS to PaaS.

Prompt Description
Integration Type fscmApi

Name getPurchaseRequisitionsLines
Version latest
Method Get
Package NA
Integration File NA

3. This Integration retrieves the distribution details of requested PR from SaaS to PaaS.

Prompt Description
Integration Type fscmApi

Name getPurchaseRequisitionsDistributions
Version latest
Method Get
Package NA
Integration File NA

4. This integration retrieves all segments and the ledger selected by the user, validates them,
and creates a GL code combination in Fusion. If any CVR rule exists, it will throw an error.

Oracle Consulting Services | Technical Specification for Mashreq Bank |September 2024 | Page 11 of 50
Prompt Description
Integration Type App based Integration

Name Account_Code_Combinations
Version 01.00.0000
Method Post
Identifier ACCOUNT_CODE_COMBINATIO
Package com.mashreq.adm
Integration File

5. This integration sends an email notification to approvers, including a copy of the PR header,
lines, chargeability, and approval history details.

Prompt Description
Integration Type App based Integration
ADM_APPROVAL_EAMIL_NOTIFICATIO
Name
N
Version 01.00.0000
Method Post
Identifier ADM_APPROVAL_EAMIL_NOTIFICA
Package com.mashreq.adm
Integration File

6. This Integration retrieves Supervisor and AOR details based on PR preparer or requester.

Prompt Description
Integration Type App based Integration
MB_ADM_SUPERVISOR_AOR_APPROV
Name
ERS
Version 01.00.0000
Method Get
Identifier MB_ADM_SUPERV_AOR_APPROV
Package com.mashreq.adm
Integration File

Oracle Consulting Services | Technical Specification for Mashreq Bank |September 2024 | Page 12 of 50
7. This Integration retrieves all FA locations from Fusion.