Search Results precedence_1




Overview
Explore in AI Chat

Overview

APPS.JAI_AP_TAXES_V is a consolidated reporting view within the Oracle E-Business Suite financials schema, specifically created to support the India localizations (JAI) tax requirements for Payables transactions. This view serves as a single, unified source of tax line information associated with Oracle Payables invoices, presenting an aggregation of tax detail originating from two distinct invoice processing streams: standalone tax entries and invoice-matched tax entries. By exposing a consistent columnar layout across both streams, the view allows downstream reporting, reconciliation, and integration processes to consume tax data from a single object rather than querying multiple views independently.

The view is notable for exposing the PRECEDENCE_1 through PRECEDENCE_10 columns, which represent a ten-level precedence hierarchy used in India tax calculation logic. This precedence structure plays a central role in determining the order in which Indian tax components (such as excise, VAT, CST, service tax, and cess) are applied and calculated on a given invoice line.

Underlying Base Objects

According to the ETRM metadata, JAI_AP_TAXES_V is defined as a UNION ALL of two underlying views:

  • JAI_AP_STANDALONE_TAXES_V — Represents tax lines associated with standalone Payables invoices, where tax is captured directly on the invoice.
  • JAI_AP_MATCH_INV_TAX_V — Represents tax lines associated with invoice-matched scenarios, such as those originating from purchase order or receipt matching flows.

Both underlying objects are themselves views, meaning JAI_AP_TAXES_V is a second-level abstraction over the actual base tables. Because the UNION ALL operator is used rather than UNION, no de-duplication occurs; every qualifying row from each source is returned. Column aliasing normalizes differences in source naming conventions, such as SOURCE_DOC_ID mapping to INVOICE_ID, and CURRENCY mapping to CURRENCY_CODE.

Key Columns

  • invoice_id — The internal identifier of the parent Payables invoice.
  • parent_line_number — The associated invoice line number, supplied as SOURCE_DOC_PARENT_LINE_NO from the standalone source and PARENT_INVOICE_LINE_NUMBER from the match source.
  • tax_line_no — The sequential tax line identifier.
  • tax_id — The reference to the tax definition in the tax setup.
  • tax_type — The classification of the tax component.
  • currency_code — The currency in which the tax amount is expressed.
  • tax_rate and qty_rate — The applicable percentage and quantity-based rates.
  • uom — The unit of measure associated with quantity-based tax.
  • tax_amt — The computed tax amount.
  • modvat_flag — Indicates whether the MODVAT (Modified Value Added Tax) credit mechanism applies.
  • precedence_1 … precedence_10 — The ordered precedence hierarchy defining the sequence in which tax components are applied.

Common Use Cases and Queries

Typical usage includes tax reconciliation reports, audit trails of applied precedence, and integration feeds to external tax engines or data warehouses. A representative query filtering on a tax precedence value follows:

  • Retrieving all tax lines where a given precedence level is populated, for example: SELECT invoice_id, parent_line_number, tax_line_no, tax_id, tax_type, tax_amt, precedence_1, precedence_2 FROM apps.jai_ap_taxes_v WHERE precedence_1 IS NOT NULL;
  • Aggregating total tax by invoice: SELECT invoice_id, SUM(tax_amt) FROM apps.jai_ap_taxes_v GROUP BY invoice_id;
  • Comparing standalone versus matched tax contributions by inspecting the source-specific normalization applied through the UNION ALL.

Because the view returns both standalone and matched tax records in a normalized form, it is a practical foundation for India localization tax reporting in both 12.1.1 and 12.2.2 environments.