Results for “rcv_matching”
12 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
APPS.JAI_APTAX_PKG_CLIENT_EXTN is a client extension package body shipped with the Oracle E-Business Suite Financials product family, specifically the Asia/Pacific localizations that supply tax determination logic for Payables and related sub-ledger flows. In EBS 12.1.1 and 12.2.2, this package provides the hooks through which India localizations (JAI — "Japan/Asia/India" prefixed modules) integrate tax calculation into the Accounts Payable matching process. Its principal business purpose is to determine the tax amount applicable to a matched invoice line, whether the underlying match originated from a purchase order receipt (PO matching) or from a receiving transaction (RCV matching).
The package header comment identifies it as jai_aptax_pkg_client_extn.plb, with a version label of 120.1.12020000.1 dated 2012/07/18, consistent with the 12.1.3/12.2.2 code lines. Because it is a PLB (wrapped/compiled) body, its implementation is intended as an extension point that customers or localization developers can override, while the core taxonomy of tax precedence logic remains anchored to the JAI common tax tables.
Key Procedures and Functions
The package body exposes a single documented procedure:
- JAI_CALC_APMATCH_TAX — the core tax determination routine for AP matching. Per the documented logic, it accepts a match type, invoice identifier, invoice line number, tax identifier, line location identifier, receiving transaction identifier, and an in-out tax amount parameter. The procedure evaluates the adhoc tax flag from
JAI_CMN_TAXES_ALL: if the adhoc flag isY, the incoming tax amount is returned unchanged. If the adhoc flag isN, the procedure branches on the match type. ForPO_MATCHING, tax precedences are retrieved fromJAI_PO_TAXESfiltered by tax identifier and line location identifier. ForRCV_MATCHING, precedences are retrieved fromJAI_RCV_LINE_TAXESjoined withRCV_SHIPMENT_LINES,RCV_TRANSACTIONS, andJAI_CMN_TAXES_ALL. The tax target amount is then assembled from the precedence sequence — precedence 0 is the line amount and precedence 1 is the tax amount fromJAI_AP_MATCH_INV_TAXES— summed, and finally the applicable tax rate is applied to produce the returned tax amount.
In the provided excerpt the executable section contains only NULL;, indicating that this shipped body functions as a stub or extension template rather than an active implementation. Customer-specific logic is expected to replace the NULL placeholder.
Tables Accessed
The documented and referenced tables underlying the procedure include:
- JAI_CMN_TAXES_ALL — holds the tax definition and, critically, the adhoc tax flag that determines whether recalculation is bypassed.
- JAI_PO_TAXES — tax precedence information for purchase order matching, keyed by tax identifier and line location identifier.
- JAI_RCV_LINE_TAXES — tax precedence information for receiving matching, keyed by tax identifier and receiving transaction identifier, joined to RCV_SHIPMENT_LINES and RCV_TRANSACTIONS.
- JAI_AP_MATCH_INV_TAXES — source of matched invoice tax amounts used when a precedence references a prior matched line.
These tables are accessed through APPS synonyms, consistent with the ETRM metadata note that table references are resolved via APPS.
Usage Notes
This package is invoked during AP invoice matching validation, typically when the Payables matching engine or the India localization's tax validation hooks evaluate whether tax should be recalculated for a matched line. It is referenced by two other packages in the metadata, indicating it forms part of a call chain rather than being called directly from a form or concurrent program. Implementers customizing India AP tax behavior should treat JAI_CALC_APMATCH_TAX as the designated client extension point: the shipped body is a stub, and the documented precedence rules (steps 3.1 through 3.4) define the contract any custom implementation must honour. Because the source is a wrapped PLB, downstream modifications should be performed by rebuilding the body from source rather than attempting to edit compiled code.
-
View: JAI_PO_RCV_TAXES_V 12.2.2
View for PO RCV taxes
APPS.JAI_PO_RCV_TAXES_V·↳ JAI_CMN_DOCUMENT_TAXES·↳ JAI_CMN_LINES·↳ JAI_CMN_TAXES_ALL·Explore JA module →