Search Results aru_t1




Overview

The APPS.JAI_PO_RA_TRIGGER_PKG package body is a stub-level PL/SQL component that exists to support trigger-based logic on the Oracle Purchasing releases entity within Oracle E-Business Suite 12.1.1 and 12.2.2. It resides in the APPS schema and is classified under the ETRM (E-Business Suite Technical Reference Manual) taxonomy as an "OTHER" API, meaning it is not a formally published public interface but rather an internal supporting object. Its declared purpose, per the embedded header comment block, is to serve as the callable target for the database trigger named JAI_PO_RA_ARIUD_T1, which is associated with the PO_RELEASES_ALL table. The package encapsulates logic that historically belonged to an older trigger identified as JAI_PO_RA_ARU_T1. In practical terms, the package provides a structured container in which release-related trigger behavior is invoked, isolating row-level trigger code from the database trigger definition itself and allowing the trigger body to delegate to packaged PL/SQL. The "JAI" prefix indicates this is part of the Oracle Joint Application Implementation / localization extension family, frequently associated with India-specific (Asia-Pacific) statutory and business requirements layered over standard Purchasing functionality.

Key Procedures and Functions

The package body exposes a single documented procedure, ARU_T1. The name follows the conventional trigger-naming pattern in Oracle Forms and PL/SQL ("ARU" indicating After Row Update, and "T1" identifying the first trigger of that type). ARU_T1 accepts old and new record representations, an action indicator, and two OUT parameters that return status and message information — a signature typical of trigger-delegation procedures rather than a business API. Critically, the current implementation body of ARU_T1 contains only a NULL statement, meaning the procedure is intentionally empty in this shipping version. This reflects a common EBS pattern in which trigger-delegation procedures are defined as placeholders, reserved for customer or localization-specific extensions, or retained for backward compatibility with triggers that previously contained logic. No additional procedures or functions are documented for this package.

Tables Accessed

ETRM metadata records that this package references PO_RELEASES_ALL through APPS synonyms. PO_RELEASES_ALL is the core Oracle Purchasing table storing release information tied to blanket purchase agreements and planned orders. Because ARU_T1 is an after-row-update trigger handler for releases, any future or customer-added logic within it would logically operate against record-level release data passed in via the pr_old and pr_new parameters. In the current stub form, no DML is performed, but the table association confirms the package's domain: validation, derivation, or auditing of release rows at the point of update. The reference to PO_RELEASES_ALL is consistent with the trigger naming ("PO_RA" indicating Purchasing releases).

Usage Notes

JAI_PO_RA_TRIGGER_PKG is not intended to be called directly from forms, concurrent programs, or external custom code. It is invoked indirectly by the database trigger JAI_PO_RA_ARIUD_T1, which passes the old and new record images along with the action and returns status and message values. The trigger itself fires on insert, update, and delete operations against PO_RELEASES_ALL, delegating update activity to the ARU_T1 procedure. The package is also noted in ETRM as being referenced by one other package, indicating a minor dependency relationship within the APPS schema. Because the procedure body is a stub, implementations that require release-level validation or localization logic typically extend this package body directly, preserving the trigger wiring while inserting the desired business rules. During upgrades between 12.1.1 and 12.2.2, the object should be treated as a standard delivered artifact; any modifications must be re-applied after patching unless registered as a custom extension.