Search Results ari_t4




Overview

JAI_AR_RCTLA_TRIGGER_PKG is a localization package within the Oracle E-Business Suite Application Programmatic Interface (API) layer owned by the APPS schema. It is classified as an "OTHER" API and targets the Oracle Financials for India (JAI) module set, specifically the Receivables tax and localization trigger framework. Its primary business function is to serve as a trigger-based handler for events fired against Receivables customer transaction lines — primarily RA_CUSTOMER_TRX_LINES_ALL — so that Indian statutory tax logic (excise, Modvat recovery, TDS, service tax, and project-related tax treatment) is applied consistently when transaction lines are inserted, updated, or deleted.

The package header carries a change history documenting forward-porting from Release 11i to Release 12 (bug #6012570) and subsequent project billing enhancements and reimplementations (bugs #5879769, #5694855, #5684363, and #5684363 Modvat Recovery logic). It exposes 11 documented procedures/functions, several of which follow Oracle's standard trigger naming convention: ARD (delete), ARI (insert), ARIU (insert-or-update), and ARU (update), each with numeric suffixes indicating distinct trigger points (T1 through T4).

Key Procedures and Functions

  • ARD_T1 — Trigger handler for delete events on Receivables transaction lines; used to reverse or clean up associated Indian tax lines.
  • ARI_T1, ARI_T2, ARI_T3, ARI_T4 — Sequential insert trigger handlers that apply Indian tax rules for newly created transaction lines in staged order (T1 first, through T4).
  • ARIU_T1 — Combined insert-or-update handler invoked when a line may be either new or modified, ensuring tax derivation and defaulting logic is applied in both cases.
  • ARU_T1, ARU_T2 — Update trigger handlers that recompute Indian statutory tax outcomes when existing transaction line attributes change.
  • GET_SERVICE_TYPE — Function returning the service_type_code for a transaction line, added for bug #5879769. It supports service-tax determination.
  • IMPORT_PROJECTS_TAXES — Procedure that imports project-billing related tax data into the Indian localization tables, reimplemented in file version 120.6.
  • IS_THIS_PROJECTS_CONTEXT — Function that tests whether the current trigger context relates to Projects Billing; it gates project-specific logic in the other handlers.

Tables Accessed

The package reads and writes a wide span of Receivables, trading-community, and India localization tables, referenced through APPS synonyms:

Usage Notes

JAI_AR_RCTLA_TRIGGER_PKG is not a user-facing API. It is invoked from database triggers and the India Receivables tax engine whenever a row in RA_CUSTOMER_TRX_LINES_ALL is inserted, updated, or deleted, passing the old and new row images (pr_old, pr_new), the DML action (pv_action), and returning pv_return_code and pv_return_message for error handling.

It is referenced by 16 other packages, indicating it sits within a shared localization framework rather than a single entry point. Because the trigger points (T1 through T4) execute in sequence, a given transaction line may pass through multiple handlers — for example, ARI_T1 through ARI_T4 on insert, followed by ARIU_T1 or ARU_T1/ARU_T2 on modification. The constant lc_modvat_tax ('Modvat Recovery') illustrates embedded business constants tied to specific bugs. This package is applicable to both EBS 12.1.1 and 12.2.2 and should not be called directly from custom code; integrators should use the standard Receivables APIs instead.