Search Results update_excise_invoice_no

Overview

JAI_AR_TRX_PKG is an Oracle E-Business Suite localization package owned by the APPS schema. It supports the India Localization (JAI) functionality associated with Oracle Receivables transaction processing, specifically the population and validation of excise and tax attributes attached to customer transactions. The package is classified as an "OTHER" API in the ETRM metadata, indicating it is not part of Oracle's published public API set but is nonetheless a documented object relied upon by other localization components.

The package header source (jai_ar_trx.pls, version 120.6, last modified 2006) shows a sustained change history driven by two major forces: the CASE compliance re-mapping of legacy DB entity names to new entity names, and the uptake of E-Business Tax (EBTax) by Oracle Receivables. The latter is reflected in the modification dated 23-June-2005 for bug 4468353, where cursors in the package became dependencies of jai_ar_match_tax.plb, jai_ar_rcta_t7.sql, jai_ar_trx.plb, and related objects. The package also normalizes the tax "Localization" literal to uppercase throughout all occurrences.

Key Procedures and Functions

• VALIDATE_INVOICE — The procedure targeted by the search term. It performs validation of an invoice (customer transaction) against the localization rules and tax attributes maintained by JAI, serving as the integrity gate before downstream excise or tax processing proceeds.
• UPDATE_EXCISE_INVOICE_NO — Maintains the excise invoice number association for transactions over a date range. Per bug 5369250 (version 120.5), the parameters p_start_date and p_end_date were changed from DATE to VARCHAR2 because the concurrent program passed values in canonical format, causing "ORA-01861: literal does not match format string." New local variables ld_start_date and ld_end_date hold the converted DATE values internally. No downstream dependencies resulted from this fix.
• UPDATE_REFERENCE — Updates reference information associated with the localized transaction records, maintaining consistency between the JAI transaction tables and their Receivables counterparts.

Tables Accessed

• RA_CUSTOMER_TRX_ALL and RA_CUSTOMER_TRX_LINES_ALL — the base Receivables invoice header and line tables read for validation and reference maintenance.
• RA_CUST_TRX_LINE_GL_DIST_ALL — distribution lines, used for tax and accounting consistency checks.
• ZX_PARTY_TAX_PROFILE and ZX_RATES_B — EBTax regime, rate, and party profile data consumed for localization tax determination.
• JAI_AR_TRXS and JAI_AR_TRX_LINES — the India Localization transaction and transaction-line extension tables, which the package queries and updates directly.
• JAI_OM_WSH_LINES_ALL and OE_ORDER_LINES_ALL — order management and shipping line data used to reconcile excise-relevant movement information with the invoice.
• DUAL — for scalar evaluation and date/session context resolution.

Usage Notes

JAI_AR_TRX_PKG is invoked from India Localization concurrent programs, from Oracle Receivables localization forms, and internally by other JAI packages — the metadata records that six packages reference it. The UPDATE_EXCISE_INVOICE_NO procedure is directly callable as a concurrent program; its historical date-format defect illustrates that callers must be aware of the VARCHAR2 signature rather than the original DATE signature. Because the package is classified as OTHER rather than a public API, customizations should call it defensively: do not assume parameter signatures are stable across patches, and confirm the current header definition in the target instance (12.1.1 or 12.2.2) before integration. The EBTax uptake annotations confirm that the package expects the ZX schema to be present and configured, so it should not be invoked in instances where E-Business Tax is not implemented.