Search Results jai_jom_lm_trigger_pkg




Overview
Explore in AI Chat

Overview

JAI_JOM_LM_TRIGGER_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that forms part of the Oracle Financials for India localization layer. Its principal business function is to serve as a trigger-oriented helper package supporting the land and matching logic applied to the India localization's order management and logistics workflows. In the context of EBS 12.1.1 and 12.2.2, the package is validated and active, and is classified under the generic "OTHER" API classification within the ETRM documentation set, indicating that it is not published as a formal public interface but rather used internally by the localization codebase.

The package operates in close conjunction with the JAI_JOM_LM_ARIUD_T1 database trigger. Where the trigger captures row-level After Insert, Update and Delete (ARIUD) events on an underlying transaction table, JAI_JOM_LM_TRIGGER_PKG provides the procedural body that interprets those events and applies the appropriate land-matching logic. This separation of trigger shell from package logic is a standard EBS design pattern that keeps trigger code thin and centralizes reusable business logic in a single package unit.

Key Procedures and Functions

The documented metadata lists a single program unit within the package: ARI_T1. Consistent with the package's trigger-supporting role, ARI_T1 is the handler invoked by the JAI_JOM_LM_ARIUD_T1 trigger to process the insert, update and delete events raised against the tracked transaction rows. Its responsibility is to translate a raw database event into the corresponding India localization land and matching business action, delegating to the appropriate internal logic for record creation, adjustment or removal.

Parameter lists are not exposed in the ETRM excerpt and should be confirmed against the live package specification in the environment before any dependency is built. The dependency chain is well documented: JAI_JOM_LM_TRIGGER_PKG references both APPS.JAI_OM_LC_MATCHINGS and STANDARD (the standard package used for EBS error and message handling). In turn, the package is referenced by APPS.JAI_JOM_LM_ARIUD_T1 and by itself, confirming recursive or internal self-invocation patterns common in trigger helper packages.

Tables Accessed

The documented table dependencies, resolved through APPS synonyms, are JAI_OM_LC_MATCHINGS and JAI_OM_LC_HDRS. JAI_OM_LC_MATCHINGS stores the line-level land and matching records that associate order or shipment details with localization matching outcomes. JAI_JOM_LM_TRIGGER_PKG reads and writes this table as the primary target of its processing, creating or updating matching rows in response to the trigger events.

JAI_OM_LC_HDRS holds the corresponding header-level land and matching information. The package accesses this table to validate the header context, retrieve exchange rate and document details, or maintain header status in line with the child matching records. Together, these two tables comprise the persistence layer the package manages.

Usage Notes

JAI_JOM_LM_TRIGGER_PKG is not intended for direct invocation from forms, concurrent programs or custom code. It is invoked indirectly whenever the JAI_JOM_LM_ARIUD_T1 trigger fires, which occurs automatically during DML on the associated transaction table. Because the trigger and package are part of the India localization, they activate only when that localization is licensed and enabled.

  • Confirm the live package specification before referencing ARI_T1 in custom code, as the ETRM excerpt does not document parameter lists.
  • Do not disable or modify the trigger or package in production; doing so will suppress India land and matching updates, causing reconciliation discrepancies.
  • When troubleshooting validation or matching errors, inspect the interaction between this package and JAI_OM_LC_MATCHINGS and JAI_OM_LC_HDRS first, as those tables hold the affected data.