Results for “match_type”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

JAI_AP_INVOICE_LINES is a table owned by the JA (Asia/Pacific Localizations) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the tax details associated with standalone Payables invoices processed through the Asia/Pacific localization tax engine. Unlike standard Oracle Payables tax lines, which are normally captured through EBTax or the global tax architecture, this table holds localization-specific tax information that must be retained separately to satisfy regional statutory and reporting requirements, particularly for countries within the Asia/Pacific region.

From a dimensional modeling perspective, the documented foreign key structure suggests a heuristic Data Vault classification of link, connecting an invoice line in AP_INVOICE_LINES_ALL to a tax category in JAI_CMN_TAX_CTGS_ALL, and optionally to a location and organization unit. This classification is a modeling suggestion derived from the FK topology rather than an Oracle-defined attribute.

Key Information Stored

The table contains 20 documented columns. The most significant include:

• JAI_AP_INVOICE_LINES_ID — surrogate primary key defined by the unique index JAI_AP_INVOICE_LINES_PK and duplicated by JAI_AP_INVOICE_LINES_U1.
• INVOICE_ID and INVOICE_LINE_NUMBER — the business-key candidates, forming unique index JAI_AP_INVOICE_LINES_U2 and referencing AP_INVOICE_LINES_ALL.
• TAX_CATEGORY_ID — the tax category applied to the line, referencing JAI_CMN_TAX_CTGS_ALL.
• PARENT_INVOICE_LINE_NUMBER — supports tax lines attached to a parent distribution line.
• SUPPLIER_SITE_ID — the supplier site associated with the invoiced tax.
• LINE_AMOUNT and CURRENCY_CODE — the tax amount and its currency.
• LINE_TYPE_LOOKUP_CODE and SERVICE_TYPE_CODE — classifications for the tax line.
• MATCH_TYPE — indicates the matching basis (for example, invoice or purchase order).
• ORGANIZATION_ID and LOCATION_ID — the operating unit/organization and location, referencing HR_ALL_ORGANIZATION_UNITS and HR_LOCATIONS_ALL respectively.
• INTERFACE_FLAG and INTERFACE_EVENT — control downstream interface processing.
• Standard audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, LAST_UPDATED_BY.

Common Use Cases and Queries

Typical usage includes reconstructing the localization tax detail of a standalone Payables invoice, validating that tax amounts reconcile to the invoice header, and feeding localized tax reports. A simple join retrieves tax lines for a given invoice:

SELECT l.invoice_line_number, l.tax_category_id, l.line_amount, l.currency_code
FROM jai_ap_invoice_lines l
WHERE l.invoice_id = :invoice_id;

Reporting extracts frequently join to AP_INVOICE_LINES_ALL on INVOICE_ID and INVOICE_LINE_NUMBER to align localization tax with the base distribution, and to JAI_CMN_TAX_CTGS_ALL on TAX_CATEGORY_ID to resolve the tax category name. Reconciliation queries commonly aggregate LINE_AMOUNT by CURRENCY_CODE and TAX_CATEGORY_ID. Since JAI_AP_INVOICE_LINES_U2 enforces uniqueness on INVOICE_ID and INVOICE_LINE_NUMBER, queries filtered on that pair are fully indexed.

Related Objects

• AP_INVOICE_LINES_ALL — base invoice line table, joined on INVOICE_ID and INVOICE_LINE_NUMBER.
• JAI_CMN_TAX_CTGS_ALL — tax category definitions, joined on TAX_CATEGORY_ID.
• HR_LOCATIONS_ALL — location master, joined on LOCATION_ID.
• HR_ALL_ORGANIZATION_UNITS — organization units, joined on ORGANIZATION_ID.
• AP_INVOICES_ALL — invoice header, referenced transitively through INVOICE_ID.
• JAI_AP_INVOICE_LINES_PK / _U1 / _U2 — unique indexes enforcing primary and business-key uniqueness.

All relationships should be validated against the ETRM 12.2.2 repository prior to implementation.