3.2.1.1 Changes across Domains

As part of OBELCM migration to OBMA architecture, following are common changes/enhancements done across domains.

  1. Redesigned Maintenance Screens : Maintenances screens across entities are re-designed for smoother experience with following features,
    • Sequencing of data segments in the order of natural data capture flow.
    • Redesigned OBMA screen layouts with logical grouping of sections and fields within sections for faster, clearer data entry.
  2. Inquiry Options: New look inquiry screens enabled with intuitive drill down capabilities covering,
    • Liability and Liability History Inquiry
    • Facility and Facility History Inquiry
    • Collateral Query and Collateral History
    • Pool Summary
    • Utilization Inquiry for Liability, Facility, Collateral and Collateral pool
    • Utilization log inquiry for Liability, Facility, Collateral and Collateral pool
    • For added convenience, these inquiry screens can be launched independently or accessed seamlessly through drill-down paths.
  3. Credit Rating and Score:
    • A common maintenance is now available for both Credit Score and Credit Rating.
    • Credit Scores are now associated with agencies, consistent with the model used for Credit Ratings.
  4. Notification:
    • Notification definition is enhanced to provide one-stop solution for following,
      • Generic Notification
      • Entity specific notification
      • Alert definition
    • Entity specific notification like collateral, facility, liability, exposure and collateral pool are moved from entity level to notification definition.
    • Parameters related to List of operands have been enhanced to support the above types and now offers many more for selection.
    • Alerts have been consolidated into Notification Maintenance, providing a single location to configure both notifications and factory‑shipped alerts.
  5. Common Attribute Bulk Maintenance – This screen now serves as a generic attribute maintenance option for Customer–Liability Linkage Maintenance. Exposure setup is now available in Exposure Maintenance for a more streamlined experience.
  6. External System Maintenance: External System Maintenance is streamlined to focus on Corporate DDA, with a convenient option to choose the accounting entry mode (Single or Double).
  7. Static Type maintenance: Static Type Maintenance in Oracle Banking Enterprise Limits and Collateral Management (OBELCM), is used to define and manage static or reference data codes that are utilized throughout the ELCM application. It now has maintenance options for below data types,
    • CONSTOFOWNER
    • CONSTRUCTION STAGE
    • CROPS
    • INS POLICY ENDORSED
    • LIVESTOCK
    • METALSFORM
    • METALTYPE
    • PROPERTYTYPE
    • SENIORITY
    • UNDERLINE DOC
    • ZONE CLASSIFICATION
    • OBLIGATIONTYPE
  8. Global Exposure Parameter: The Global Exposure Parameter maintenance is now managed via the PROPERTIES table and is consumed by plato-config-service. It supports both GETB_PARAM and CSTB_PARAM parameters, enabling centralized configuration and streamlined management of global exposure parameter settings.
  9. Mandatory Batch Program Maintenance: The EOD (End-of-Day) workflow automates the processing of critical batch operations, reconciliations, and system updates that must be completed at the close of each business day. This workflow ensures that all transactional and operational data are processed, validated, and consolidated accurately before the start of the next business day. OBELCM ships JSON configurations for all batch jobs, which can be integrated and configured as part of the Branch EOD in the Common Core.
  10. File Processing: Inbound File Processing done through Interface Definition and bulk upload in ODT will now have pre-defined file formats (flat file or JSON) for each service. The inbound files (adhering to the corresponding formats) needs to be placed in a folder (configuration setting provided for the path) for processing. A scheduler job will pick up these files on scheduled intervals based on a pre-configured frequency and process the files. Errors if any will be written to a file in the 'Error' folder in the same path. For Outbound extracts, a service endpoint is exposed which needs to be invoked manually to generate the extracts.

Parent topic: Functional Changes