1.2 Release Enhancements

Following are the release enhancements of the OBCL 14.8.2.0.0 Innovation release.

  • 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.

  • 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.

  • 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)
  • Technical Changes
    This topic provides the information about the technical changes in this release.

Parent topic: Release Notes