Oracle ERP Cloud – Design

Document

Oracle ERP to HSBC Bank Integration for payments

Document Location

SharePoint link

Last Updated: 2024-11-28

 Document Controls

Identification / Ownership

Role Title Name Project Role

Data
Business Owner Stakeholder / Steven Douglas Project Manager
Client SME
Functional
Functional Owner Abhishek Ruhela Functional Consultant
Analyst
Technical
Technical Owner N/A
Analyst
3-rd Party
Third-Party Owner
Contact
Technical QA/
Technical Lead Sumit Chauhan Project Lead
Reviewer
Functional QA/ Functional Finance Functional
Abhishek Ruhela
Reviewer Lead Consultant
Client Functional
Client SME Steven Douglas Project Manager
SME

Version History
0.1 – 1.0: Initial document creation and defining business requirements. Once business requirements are fully defined,
change to version 1.0
1.1 – 2.0: Functional design. Once functional design is defined and reviewed by functional lead, change to version 2.0
2.1 – 3.0: Technical design. Once technical design is completed and reviewed, change version to 3.0
3.1 – 4.0: Technical build. Once build components are documented, including tech unit testing results, change version to 4.0
4.1 – 5.0: Unit testing and signoff. Once unit testing is completed and results are entered into this document, change to
version 5.0 (FINAL)

Version Date Updated By Description of Change

1.0 Defined business requirements
2.0 24-01-2024 Abhishek Ruhela Functional design defined and reviewed
3.0 N/A Technical design is completed and reviewed

4.0 29-01-2024 Abhishek Ruhela Build components are documented including tech unit testing results

5.0(Final) Unit testing completed and results entered into the document

GDD -Oracle ERP/SCM Cloud Page 2 of 14

 Status Tracking and Approvals

Section Completed By Completed Date Confirmed By Confirmed Date

Business Requirements

Functional Design

Technical Design

Technical Build

Technical Unit Testing

Functional Unit Testing

Client Testing SME

GDD -Oracle ERP/SCM Cloud Page 3 of 14

Table of Contents

1 Business Requirements.....................................................................................................................5
1.1 Identification........................................................................................................................................... 5
1.2 Requirements.......................................................................................................................................... 5
2 Functional Design.............................................................................................................................6
2.2 Functional Design Details........................................................................................................................ 6
2.3 Execution Characteristics........................................................................................................................ 7
2.4 Functional Unit Testing (FUT)............................................................................................................8
3 Technical Design.............................................................................................................................11
3.1 Technical Solution Overview................................................................................................................. 11
3.2 Technical Specifications........................................................................................................................ 11
3.3 Legacy/ Third-Party Technical Specifications........................................................................................11
3.4 Middleware Technical Specifications....................................................................................................11
4 Build / Development Details...........................................................................................................12
4.1 Oracle ERP/SCM Cloud Solution............................................................................................................12
4.1.1 Program / Data Flow................................................................................................................................12
4.1.2 Development Objects................................................................................................................................7
4.1.3 Technical Security Details..........................................................................................................................7
4.1.4 Additional Object Details.........................................................................................................................15
4.2 Legacy/ Third-Party Solution Objects....................................................................................................15
4.3 Middleware Solution Objects................................................................................................................15
4.4 Technical Unit Testing (DUT).............................................................................................................9
5 Migration Details..............................................................................................................................9
5.2 Oracle ERP/SCM Cloud Solution............................................................................................................17
5.2.1 When was it migrated to prod?...............................................................................................................17
5.2.2 Who migrated it?.....................................................................................................................................17

GDD -Oracle ERP/SCM Cloud Page 4 of 14

1 Business Requirements
Includes but is not limited to: Reports, Interfaces, Conversion, Extensions, Workflow, Fast Formula.

1.1 Identification

Object/Feature Oracle ERP to HSBC Bank Integration Module

Name for payments
Business areas and Legacy or 3rd HSBC Bank
stakeholders Party System(s)

1.2 Requirements

Define Scope The purpose of this integration is to enable secure payment processing with HSBC using a provided public
key uploaded to the UCM server.
Specify Public key provided by HSBC Bank (This key is used for validating the digital signature of inbound
Requirements acknowledgment of file or bank statement and to encrypt the bank statement file shared) to process the
payment ahead.

Assumptions Renamed public key must be configured and automatically imported in system for smooth payment process.

Downstream Once the configuration is done the PGP Public key will be automatically imported in system.
Impact

Known Issues N/A

Known Risks Public key not displaying under List of Values due to wrong configuration

Out of Scope N/A

GDD -Oracle ERP/SCM Cloud Page 5 of 14

2 Functional Design
2.2 Functional Design Details
Embed any design documents within the table below, or hyperlink to the document.

Legacy or Third- HSBC

Party System
Process Flow PGP Key to be updated in Oracle Fusion for Encryption/Decryption of Data from HSBC Bank.
This streamlined process ensures a secure and efficient integration of the public key for HSBC bank transactions
and further payment process

Data Flow N/A

Direction
Data Mapping N/A
Transmission N/A
requirement
Specify Pre-  Upload the renamed public key file in Oracle Fusion File Import and export
requisites  Configure the PGP Public key to automate the importing process into the system
Security N/A
Requirements
Functional N/A
Assumptions

2.3 Execution Characteristics

Run Characteristics Please specify Yes to indicate the requirement of how the client wishes to run the interface:
 Real-time: No
 On-Demand: Yes
 Scheduled Periodically: No

Changes Only plus Full File (reset of baseline file): Yes/No

Schedule Daily ( ) Weekly ( ) Monthly ( ) Quarterly ( ) Annually ( Yes ) Real-time ( )
Other (specify) – such as requirement to run at specific time(s)

Expected peak N/A

period data volume
Dependencies Predecessor: Upload the renamed public key file in Oracle Fusion File Import and export, Configure
the PGP Public key to automate the importing process into the system
Successor: N/A
Run Parameters Pubic key provided by bank
Exception Handling N/A
Delivery Option Oracle Fusion
Notifications N/A

GDD -Oracle ERP/SCM Cloud Page 6 of 14

2.4 Functional Unit Testing (FUT)

Approach

Provide a brief description of the overall approach.

The public key is a crucial component provided by HSBC for seamless integration into their banking system. This key serves a dual
purpose: validating the digital signature of inbound acknowledgments for files or bank statements and encrypting the shared bank
statement files for payment transactions.

Steps to Upload Public Key File

1. Rename the Public Key:
 Add '_Public.Key' as a suffix to the bank-provided key, ensuring no special characters except underscore are present.
Example: "hsbc_prd_pgp_202302_public.key" [1].
 The total characters of the public key should be less than 28, or the system will reject the file.

2. Upload the Renamed Public Key:

 Navigate to upload the file through Navigator > More > File Import and Export.
 Click the add (+) button and select the 'public key file' for upload.

3. Select Account for Upload:

 During the file upload, choose the Account as "Fin/Payments/Import" to specify the purpose of the uploaded public key.

4. Configure Transmission Settings:

 Navigate to the transmission configuration page via Setup & Maintenance > Payments > Manage Transmission
Configurations.
 Choose the uploaded public key file from the List of Values (LOV) matching the name in UCM.
5. Search and Save Bank Configuration:

 Search for the relevant bank, e.g., "LU_HSBC_Payment."

 In the PGP Public Key Encryption section, select your public key from the LOV.
 Click 'Save and Close' to complete the configuration, automatically importing the key into the system.

This streamlined process ensures a secure and efficient integration of the public key for HSBC bank transactions and further
payment process

GDD -Oracle ERP/SCM Cloud Page 7 of 14

Test Cases
Document initial test cases. These are not test scripts, which will be developed separately as part of functional
unit testing.

Depe Person Pre-Requisite Input

Process Transaction
Scenario nden Steps Number/Para to Executing Parameters/ Expected Results
Area Details
cy meters the Test Key Fields
Test Case 1-Upload Navigation(Oracle fusion) Renamed public key
the renamed public Click on Navigator > More > File Import and file should be
key file. export>Click on plus to select public key file> successfully uploaded.
Choose file(select the files from the desired
location)> select the Account as
N/A
“Fin/Payments/Import”> Save and Close

Test Case 2- Select The key name must

the key name in the Navigation(Oracle fusion) appear in the LOV
LOV same as Setup & Maintenance > Payments > Manage same as uploaded in
uploaded in UCM on Transmission Configurations UCM.
transmission N/A
configuration page.

Navigation(Oracle fusion) Navigate PGP Public

Test Case 3- Mapping Setup & Maintenance > Payments > Manage Key Encryption Key and
the Configured Transmission Configurations>Search>Input select your public key
public key with the the bank name(eg: LU_HSBC_Payment) from the LOV and then
bank. N/A click on ‘Save and
Close’ configuration
must be completed.

Steps to upload Public Key File

Open/Closed Issues

# Open/Close Issue Owner Resolution Comments

1 N/A .

GDD -Oracle ERP/SCM Cloud Page 8 of 14

3 Technical Design
3.1 Technical Solution Overview
N/A

3.2 Technical Specifications

Embed any technical specification documents within the table below, or hyperlink to the document.

Tools Selection N/A

Source & Target N/A
Tables/Components
File Layout N/A
Data Mapping / N/A
Translation

Data Transmission N/A

Approach

Middleware N/A
Requirements

Logging & Error N/A

Handling
Data Validation & N/A
Audit
Security N/A
Requirements
Assumptions N/A

3.3 Legacy/ Third-Party Technical Specifications

HSBC
HSBC Provides a public key - The public key is a link provided by the bank which is required to be added in the
bank integration process.

3.4 Middleware Technical Specifications

N/A

GDD -Oracle ERP/SCM Cloud Page 9 of 14

3.1 Oracle ERP/SCM Cloud Solution
3.1.1 Program / Data Flow
N/A

3.1.2 Development Objects

N/A

3.1.3 Development Objects

Source and Target System Description:

Interface Name Source Target

N/A

Connections Description:
Connection Name Adapter

N/A

4.1.2.2 Sample File(s) / Sample Payload(s)

Link to Sample(s): N/A

File Name Reference

Sample Request N/A
Payloads
Sample Response N/A
Payloads

GDD -Oracle ERP/SCM Cloud Page 10 of 14

 Visio Diagram

SQL Query N/A

Table Structure N/A

4.1.2.3 OIC Middleware Integrations

Integration Name Integration Identifier Description Package

N/A N/A

4.1.2.4 OIC Connections

Connection Name Connection Type Description

N/A

4.1.2.5 Lookups

GDD -Oracle ERP/SCM Cloud Page 11 of 14

 Lookup Name Description

N/A

4.1.2.5.1 Columns In Lookups

Column Name Hardcoded Value

N/A

4.1.2.6 ATP Objects Details

Table Name Object Type Object Description Table Structure
N/A

4.1.2.7 Reports
N/A
Data Model
Path Description
/Report Name Query

N/A

3.1.4 Technical Security Details

N/A

3.1.5 Additional Object Details

N/A

3.2 Legacy/ Third-Party Solution Objects

HSBC – to get the public key file and upload in Oracle Fusion

3.3 Middleware Solution Objects

N/A

GDD -Oracle ERP/SCM Cloud Page 12 of 14

3.4 Technical Unit Testing (DUT)

Test Cases – N/A

Depe Person Pre-Requisite Input

Process Transaction
Scenario nden Steps Number/Para to Executing Parameters/ Expected Results
Area Details
cy meters the Test Key Fields

Test Results
N/A

GDD -Oracle ERP/SCM Cloud Page 13 of 14

4 Migration Details
4.2 Oracle ERP/SCM Cloud Solution
4.2.1 When was it migrated to prod?

4.2.2 Who migrated it?

GDD -Oracle ERP/SCM Cloud Page 14 of 14