2.2.4 Common Core Changes

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)