Search Results ard_t1

Overview

JAI_AR_RCTA_TRIGGER_PKG is an Oracle EBS Applications (APPS) package that implements trigger-handler logic for the Oracle Financials for India (JAI) localization, specifically targeting Receivables (AR) transactions. Its naming convention follows the standard trigger model: procedures prefixed ARI, ARU, ARD, and ASI correspond to Insert, Update, Delete, and a related post-processing action against the RA_CUSTOMER_TRX_ALL record type. A package-level record, t_rec RA_CUSTOMER_TRX_ALL%rowtype, defines the row structure passed into every handler. The package exists primarily to apply Indian statutory requirements — most notably Tax Collected at Source (TCS) and Tax Deducted at Source (TDS) treatment — and to resolve problematic transactional conditions arising from AutoInvoice and Bill Only order flows.

Key Procedures and Functions

Twelve procedures are documented. Each trigger handler receives old and new row images (pr_old, pr_new), an action indicator (pv_action), and returns status through pv_return_code and pv_return_message, following the EBS event-based trigger signature.

• ARI_T1 — Insert-time handler for RA_CUSTOMER_TRX_ALL rows, executing localization validation or enrichment when a new AR transaction header is created.
• ARU_T1 through ARU_T6 — Update-time handlers covering discrete update scenarios against the AR transaction header.
• ARU_T7 — Introduced under Bug 5631784 (file version 120.1) specifically to deliver TCS functionality for updated AR transactions.
• ARU_T8 — A further update-time handler in the same series.
• ARD_T1 — Added under Bug 7450481 (version 120.0.12000000.3), which addressed the AutoInvoice Import program terminating in error for Bill Only orders.
• ASI_T1 — A related handler in the trigger series, invoked for the corresponding seeded event.

Procedure bodies are not reproduced in the documentation; consumers should treat parameter signatures as fixed at the documented rowtype-based pattern.

Tables Accessed

The package reads and writes AR transaction structures and their JAI localization extensions:

• RA_CUSTOMER_TRX_ALL — Source of the rowtype and the primary trigger subject.
• JAI_AR_TRXS, JAI_AR_TRX_LINES — India-localization transaction header and line detail used for tax computation and storage.
• JAI_AR_TRX_INS_HDRS_T, JAI_AR_TRX_INS_LINES_T, JAI_AR_TRX_COPY_HDR_T, JAI_AR_TRX_APPS_RELS_T — Intermediate copy/insert staging tables for transaction headers, lines, and application relationships.
• JAI_AP_TDS_THHOLD_SLABS, JAI_AP_TDS_THHOLD_TAXES — Withholding threshold slab and tax configuration driving TDS/TCS determination.
• HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL — Customer account site and site-use data, typically for place-of-supply and tax registration resolution.
• GL_CODE_COMBINATIONS — Accounting flexfield validation for generated distributions.
• FND_APPLICATION, FND_CONCURRENT_PROGRAMS, FND_CONCURRENT_REQUESTS — Application and concurrent request metadata, used to identify or inspect the invoking concurrent process.

Usage Notes

JAI_AR_RCTA_TRIGGER_PKG is not intended to be called directly by end users. It is invoked as a registered event handler on RA_CUSTOMER_TRX_ALL within the Oracle Financials for India localization, triggered by AR transaction inserts and updates occurring through AutoInvoice, standard Receivables forms, and order-to-invoice flows. The package is referenced by three other packages, indicating reuse in dependent localization logic. The documented change history ties ARU_T7 to TCS enablement and ARD_T1 to the corrective fix for AutoInvoice failures on Bill Only orders, making version currency important when diagnosing such errors. Custom code should call the procedures only with a fully populated RA_CUSTOMER_TRX_ALL rowtype and should always inspect pv_return_code and pv_return_message, since localization validations communicate outcomes exclusively through those out parameters rather than raising exceptions.