Results for “jai_po_rla_trigger_pkg”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

JAI_PO_RLA_TRIGGER_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, part of the Oracle Financials for India (JAI) localization layer that extends standard procurement functionality to meet Indian statutory requirements. The package name references "RLA," denoting the Receiving Line Adjustment or associated tax-adjustment trigger mechanism tied to purchasing and receiving flows in the Procure-to-Pay cycle. Its core business purpose is to synchronize and recalculate India-specific tax attributes on purchase requisitions, purchase orders, and receiving transactions whenever qualifying lifecycle events occur.

In EBS 12.1.1 and 12.2.2 the object is reported as VALID, and its dependency metadata confirms a direct reference to PO_REQUISITION_LINES_ALL, establishing it within the requisition-to-order conversion path where tax defaults and Excise/CST/VAT determinations must remain consistent.

Key Procedures and Functions

The documented interface exposes four program units, designated ARI_T1, ARU_T1, ARU_T2, and ARU_T3. The naming convention follows the Oracle trigger idiom: the ARI prefix denotes an After-Insert row-level trigger body, and the ARU prefix denotes an After-Update row-level trigger body. The numeric suffixes T1, T2, and T3 distinguish multiple trigger entry points on the underlying base table(s), each associated with a distinct database trigger definition.

• ARI_T1 — After-Insert handler invoked when a new purchasing document line (requisition line or order line) is created, responsible for seeding India tax attributes on the newly inserted record.
• ARU_T1 — After-Update handler for the primary update path, recalculating tax attributes when material line columns change.
• ARU_T2 — Second after-update entry point covering an alternate column set or lifecycle transition.
• ARU_T3 — Third after-update entry point, typically reserved for a further distinct header/line/location update scenario.

All four are procedure bodies; no parameter lists are documented, as they are designed to be called from trigger context using the :NEW and :OLD correlation values.

Tables Accessed

The package reads and writes a broad slice of the procurement and India tax data model. Core transactional tables include PO_REQUISITION_LINES_ALL, PO_REQUISITION_HEADERS_ALL, PO_HEADERS_ALL, PO_LINES_ALL, and PO_LINE_LOCATIONS_ALL, which supply the document context used to derive applicable taxes. India localization extensions JAI_PO_REQ_LINES, JAI_PO_REQ_LINE_TAXES, JAI_PO_LINE_LOCATIONS, and JAI_PO_TAXES store the localized tax detail records written during trigger processing.

Reference and setup data come from JAI_CMN_TAXES_ALL (tax definitions and rates), JAI_CMN_VENDOR_SITES (supplier site tax registration details), and MTL_UNITS_OF_MEASURE (unit-of-measure conversion used in tax computation). UTL_FILE and V$PARAMETER are referenced for diagnostic file output and environment/parameter inspection, indicating an internal logging and configuration-check capability.

Usage Notes

JAI_PO_RLA_TRIGGER_PKG is not intended for direct invocation by end users or custom code. It is executed automatically through database triggers defined on the purchasing tables it references, and its public program units ARI_T1, ARU_T1, ARU_T2, and ARU_T3 fire in response to insert and update DML on those underlying documents. Because the metadata notes it is referenced by zero other packages, the dependency surface is confined to trigger wiring, which means impact assessment during upgrades or patches must focus on the trigger definitions rather than PL/SQL call chains.

During the 12.1.1 to 12.2.2 upgrade, verify that triggers referencing this package are compiled VALID and that India localization patches are applied consistently. Any diagnostics written via UTL_FILE require the correct directory parameter to be configured, as read through V$PARAMETER. Customizations should avoid modifying this package directly; extension logic should be layered through supported forms personalization or custom trigger alternatives to preserve Oracle support.