Search Results jai_po_taxes




Overview
Explore in AI Chat

Overview

JAI_PO_TAXES is a localization table owned by the JA (Asia/Pacific Localizations) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the information of localization tax lines at a Purchase Order line location level. In practice, this means the table captures the tax detail associated with each scheduled shipment or distribution line of a PO — that is, at the granularity of the PO line location — rather than only at the header or aggregate line level. It supports the Asia/Pacific tax and localization requirements that are not handled by the standard tax engine alone, providing a repository for computed tax lines, tax rates, tax amounts, and the precedence logic used to derive them.

From a modeling perspective, the metadata's documented foreign key structure — a composite primary key of LINE_FOCUS_ID and TAX_ID referencing multiple parent tables — suggests a link-style classification in Data Vault terms. The heuristic Data Vault classification is a modeling suggestion only; implementers should validate it against actual cardinality and business rules before adopting it in a warehouse design.

Key Information Stored

The table is defined with 32 documented columns. The most operationally significant columns include:

The surrogate primary key (JAI_PO_TAXES_PK on LINE_FOCUS_ID, TAX_ID) should be distinguished from the business-key candidate captured by unique index JAI_PO_TAXES_UK1 on PO_LINE_ID, LINE_LOCATION_ID, and TAX_ID, which reflects the natural uniqueness of a tax per PO line location.

Common Use Cases and Queries

Typical reporting and reconciliation scenarios include extracting localized tax amounts per PO line location, validating that computed tax equals TAX_AMOUNT, and tracing tax precedence to explain how a compounded tax was derived. A common pattern joins the table to its parents to present readable tax detail:

  • Join JAI_PO_TAXES to PO_HEADERS_ALL on PO_HEADER_ID and PO_LINES_ALL on PO_LINE_ID to report tax by PO.
  • Join to PO_LINE_LOCATIONS_ALL on LINE_LOCATION_ID to attribute tax to a specific shipment or distribution.
  • Join to JAI_CMN_TAXES_ALL on TAX_ID and JAI_CMN_TAX_CTGS_ALL on TAX_CATEGORY_ID to resolve tax names and categories.
  • Join to HZ_PARTIES on VENDOR_ID when analyzing tax by supplier.

A representative query would select PO_HEADER_ID, PO_LINE_ID, LINE_LOCATION_ID, TAX_ID, TAX_RATE, and TAX_AMOUNT from JAI_PO_TAXES, with predicates on PO_HEADER_ID and CURRENCY, filtered by LAST_UPDATE_DATE for incremental extraction. Summing TAX_AMOUNT grouped by TAX_CATEGORY_ID supports localization tax reporting, while ordering by PRECEDENCE_1 through PRECEDENCE_10 reconstructs the tax application sequence.

Related Objects

The table participates in a well-defined web of relationships through its documented foreign keys:

  • JAI_PO_LINE_LOCATIONS — Referenced via LINE_FOCUS_ID; the closest localization parent.
  • PO_LINE_LOCATIONS_ALL — Referenced via LINE_LOCATION_ID.
  • PO_LINES_ALL — Referenced via PO_LINE_ID.
  • PO_HEADERS_ALL — Referenced via PO_HEADER_ID.
  • JAI_CMN_TAXES_ALL — Referenced via TAX_ID, providing tax definitions.
  • JAI_CMN_TAX_CTGS_ALL — Referenced via TAX_CATEGORY_ID.
  • HZ_PARTIES — Referenced via VENDOR_ID for supplier identity.

These parents form the primary join surface for any query or extract built on JAI_PO_TAXES, and their keys should be used to drive consistent reporting across the Asia/Pacific localization tax stack.