1.2 Release Enhancements

Hybrid Address Support for Parties as per ISO 20022 Guidelines

System is enhanced to support hybrid (semi-structured) postal address option for all the parties in settlement instruction maintenance and in settlement subsystem of contracts. Town Name and Country are mandatory in the maintenance.

The payment message generation request to OBPM carries the structured address field values maintained for the parties.

ISO 20022 MX Message Support for Foreign Exchange Trade

System supports below listed foreign exchange trade messages in ISO20022 MX format( equivalent to MT300 - Foreign Exchange Confirmation):
  • Foreign Exchange Trade Instruction (fxtr.014.001) - Sent by a participant to a central system to notify the creation of the foreign exchange trade agreed by both trading parties.
  • Foreign Exchange Trade Instruction Amendment (fxtr.015.001) -Sent by a participant to a central system to notify the amendment of the foreign exchange trade previously confirmed by the sender.
  • Foreign Exchange Trade Instruction Cancellation (fxtr.016.001) - Sent by a participant to a central system to notify the cancellation of the foreign exchange trade previously confirmed by the sender.

SWIFT 2025 changes

System is enhanced to support SWIFT 2025 Regulatory changes:
  • A new parameter for SWIFT 2025 is introduced to control enabling/disabling the usage of SWIFT 2025 changes.
  • The field name for mandatory tag 30V under Mandatory Sequence B-Transaction Details, will now be renamed to Settlement date from earlier named Value Date . This will impact MT 300 and MT 304.
  • In MT305( Foreign Currency Option Confirmation) mandatory field 31a will support a new Option W in addition to existing Option G which will specify the date, time, and location at which the option expires.

OBRH Integration Guide

OBTR is enhanced to support the integration with External Products like OBPM, ELCM and FCUBS through OBRH Existing External Service Maintenance screens for OBPM, ELCM and FCUBS are enhanced by adding Header Profile and Communication type fields.

Oracle Banking Microservice Architecture (OBMA) and Oracle Development Tool (ODT) Core Merger

The OBMA Core and ODT Core have been unified into a single common core system to be shared by both OBMA and ODT products.
  • Functions that existed in both cores have been removed from the ODT common core if they were already available in the OBMA common core.
  • The OBMA common core screens will now be used to maintain all common core data.
  • The ODT common core will reference OBMA common core data through Oracle database views.
  • Replication of the following entities from Oracle FLEXCUBE Universal Banking to the ODT common core has been discontinued:
    • External Customer
    • External Customer Account
    • External Chart of Accounts
    • External Consumer Loan Account
    • External Transaction Code

Parent topic: Release Notes - Introduction