1.2 Release Enhancements

Following are the release enhancements of the OBCL 14.9.0.0.0 release.

  • Trade Loans Processing

    OBCL now supports booking of Packing Credit Loan against Export LC or Purchase Order and Advance By Loan by capturing Import LC, and Proforma Invoice details. The integration with the Trade System has also been enhanced to pass these additional fields for processing, enabling a more complete and streamlined trade loan-booking workflow.

  • Contract Wise Liquidation Order

    The system provides the flexibility to decide the liquidation order for the components at the contract level. Preferences for component liquidation order would be defaulted from the product and user can modify the order at the contract during booking. Bilateral Auto Liquidation batch would consider the liquidation order from the contract level if the same is maintained. Syndication Contracts will continue to follow the liquidation order from the Product.

  • Floating Moratorium Interest Component

    The Moratorium component previously supported only a fixed interest rate type. The Moratorium component now supports a floating interest rate type, enabling periodic and automatic interest rate revisions during the moratorium period for loan accounts.

  • Disbursements - Payment Schedules with User defined Amounts

    The system now allows users to enter principal due amounts for manual disbursement contracts and retains those values after disbursement processing. Previously, principal schedule amounts were auto-derived by spreading the disbursed amount across the schedules. Banks can also configure whether payment schedules should be generated using user-entered amounts or system-derived amounts.

  • Async Participant Processing

    Participant Processing can now be run asynchronously in the background for Syndication transactions, including Contract Book, Payment, Amendment, and Rollover/Reprice Authorization. The branch-level control that previously applied process participants to either all deals or none has been enhanced and moved to the deal level, allowing users to selectively manage participant propagation for each deal.

  • SMS Merger Changes
    The following changes have been made to unify the SMS modules across OBMA and ODT:
    • The common data attributes shared between OBMA SMS and ODT SMS reside in the OBMA table.
    • These common data attributes are made available to ODT through a view.
    • ODT-specific additional SMS data attributes remain in ODT only.

    ODT SMS Screen Changes:

    User Interface changes are done to disable the fields which are populated from OBMA SMS.

    ODT Data model changes are done for the tables related to the below SMS screens:
    • User Creation (SSDUSRDF)
    • User Maintenance (SMDUSRDF)
    • Role Definition (SSDROLDF)
    • Role Maintenance (SMDROLDF)
  • Synchronous EOD between ODT and OBMA Framework

    The system now supports synchronous EOD between OBMA products and ODT products to ensure consistency and accurate status updates across frameworks.

    • New Parameter: OBMA_EOD_ENABLE – Determines whether EOD processing is triggered from ODT or OBMA. When enabled, EOD-related datastore updates for status and branch date from ODT are skipped to maintain synchronization.
    • The system now allow users, EOD to be triggered centrally from OBMA for both OBMA and ODT products:
      • Centralized EOD Trigger: Users initiate EOD from OBMA.
      • Automated ODT EOD Invocation: OBMA triggers the ODT EOD by calling the REST service of End Of Cycle Operations (AEDSTART / BrnEODStartService) for each EOD stage.
    • OBMA will wait/hold the EOD stage until ODT EOD stage is completed. Completion of ODT EOD stage, it will be identified by OBMA by querying the REST service of EOC Monitor(AEDBRMTR) (BrnEODMonitorService) screen.

    This enhancement ensures synchronized, streamlined, and automated EOD processing across the OBMA and ODT frameworks, reducing manual intervention and improving operational efficiency.

  • Common Core Merger Impact for OBCL

    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 Corporate Lending to the ODT common core has been discontinued:
      • External Customer
      • External Customer Account
      • External Chart of Accounts
      • External Consumer Loan Account
      • External Transaction Code

    Installer process has been extended to build Integrated WAR file instead of the previous EAR format for Web services. With this update, Common Core Web Services and ROFC Web Services are built independently, each generating its own dedicated WAR file.

  • Structured/Hybrid Address Regulatory Changes

    Enhanced to capture structured address in the Settlement Instruction Maintenance layer. This gets defaulted and editable at contract level, as existing. These structured address details of various parties are passed on to OBPM to trigger an outbound MX payment message.

    When Settlement Instructions are not maintained for a customer, then the structured address maintained in common core would be defaulted at the contract level.

    Hybrid address messages as recommended by SWIFT 25 rule book is also supported.

  • ELCM OBMA migration impact on OBCL-ELCM Integration

    OBCL now initiates requests to OBRH, which adds security tokens, transforms the requests as needed, and forwards them to ELCM for processing. After the systems respond, OBRH processes these responses and returns them to OBCL. This update streamlines and secures the integration workflow between OBCL and ELCM.

  • Technical Changes
    This topic provides the information about the technical changes in this release.

Parent topic: Release Notes