Search Results aru_t2




Overview
Explore in AI Chat

Overview

JAI_OM_WDD_TRIGGER_PKG is an Oracle E-Business Suite package owned by the APPS schema and classified under the ETRM taxonomy as an "OTHER" API. Its name and structure identify it as a trigger-handler package for the Oracle Order Management and Shipping execution flow — specifically the Warehouse Delivery Details (WDD) entity, corresponding to the WSH_DELIVERY_DETAILS table. The package operates within the Oracle India Localization (JAI) product family, which extends standard EBS functionality with India-specific statutory requirements such as excise, VAT, TDS, and RG23 registers.

The package declares a package-level record variable, t_rec, anchored to WSH_DELIVERY_DETAILS%ROWTYPE, which is passed to every procedure as the old and new row images. This record-based signature indicates that the procedures are intended to be invoked from database triggers on WSH_DELIVERY_DETAILS, receiving the transitioning row values and returning a return code and return message to the caller. In this way the package acts as the localized business logic layer behind shipping-trigger events, particularly the ARU (after-update) and ARD (after-delete) events on delivery details.

Key Procedures and Functions

The documented package specification exposes six procedures, all of which share a uniform signature consisting of an old record, a new record, an action indicator, and output parameters for return code and return message (the specification excerpt shows only the ARD_T1 through ARU_T3 declarations, but the ETRM metadata confirms ARU_T4 and RG23D_REV_ACCOUNTING are also documented members).

  • ARD_T1 — Handler for an after-delete event on delivery details. The "T1" suffix denotes trigger number one. It processes the deletion of a delivery line with respect to India localization rules.
  • ARU_T1 — Handler for the first after-update event on WSH_DELIVERY_DETAILS. Likely reacts to attribute changes that affect downstream India tax or excise treatment.
  • ARU_T2 — Second after-update handler, covering a distinct attribute-change condition from ARU_T1.
  • ARU_T3 — Third after-update handler. This is the specific procedure associated with the search term "aru_t3", indicating user interest in the after-update trigger logic for delivery details.
  • ARU_T4 — Fourth after-update handler, addressing yet another change condition on the delivery detail record.
  • RG23D_REV_ACCOUNTING — Performs reversal accounting for RG23D register entries, reflecting India excise law requirements for warehouse-to-dealer movements and their reversal when a shipment is modified or cancelled.

No parameter lists should be inferred beyond those shown in the specification; the documented calls accept old and new row images and return diagnostic status.

Tables Accessed

The package reads and writes a broad set of India localization and standard shipping tables through APPS synonyms. The principal operational table is WSH_DELIVERY_DETAILS, which supplies the trigger row data. India localization tables include JAI_CMN_RG_23D_TRXS, JAI_CMN_RG_BALANCES, JAI_CMN_RG_OTHERS, and JAI_CMN_JOURNAL_ENTRIES together with its sequence-backed counterpart JAI_CMN_JOURNAL_ENTRIES_S, supporting RG23D register maintenance and reversal entries. Tax and threshold logic draws on JAI_CMN_TAXES_ALL, JAI_AP_TDS_THHOLD_SLABS, and JAI_AP_TDS_THHOLD_TAXES. Receipt and matching data come from JAI_CMN_MATCH_RECEIPTS and JAI_CMN_MATCH_TAXES. Supporting setup and control tables include JAI_CMN_FIN_YEARS, JAI_CMN_INVENTORY_ORGS, JAI_CMN_DEBUG_CONTEXTS, and GL_CURRENCIES for currency validation.

Usage Notes

JAI_OM_WDD_TRIGGER_PKG is not a user-invoked package. It is called by database triggers on WSH_DELIVERY_DETAILS during shipping transactions in Oracle Order Management and Oracle Shipping Execution, and the ETRM metadata confirms it is referenced by two other packages. Deployments supporting India localization will see it fire whenever delivery detail records are inserted, updated, or deleted, ensuring that RG23D balances, journal entries, and India tax data remain synchronized. Because it relies on the JAI_CMN_* setup tables, the India localization configuration must be complete before shipping transactions are processed. Diagnosing issues in this package typically involves enabling the debug context via JAI_CMN_DEBUG_CONTEXTS and reviewing the return code and return message values passed back to the trigger.