Search Results jai_po_request_t




Overview
Explore in AI Chat

Overview

JAI_PO_REQUEST_T is a transaction-staging table owned by the JA (Asia/Pacific Localizations) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to support the JAINPOCR concurrent program, which performs tax defaulting for purchasing documents. The table functions as a working repository where the concurrent process assembles candidate tax lines — tax, tax category, precedence values, rates, and computed amounts — before those results are applied to the purchasing transaction or surfaced for review. It is not a master or setup table; its contents are specific to a defaulting run and are keyed to individual purchase order headers, lines, and line locations.

Because the table carries foreign keys to multiple independent business entities (purchase orders, vendors, and tax definitions) without itself being a core entity, the heuristic Data Vault classification supplied in the metadata is link. In a Data Vault model, this suggests JAI_PO_REQUEST_T behaves as an associative or transactional structure that resolves relationships among hubs such as purchase orders, parties/vendors, and tax definitions, rather than acting as a standalone hub or a descriptive satellite.

Key Information Stored

The table contains 32 documented columns. The most significant are organized around three concerns: document context, tax determination, and audit/lifecycle tracking.

No surrogate primary key is enumerated in the supplied metadata, and no unique index is documented. The FK set clearly performs the identifying role for a row, with LINE_LOCATION_ID, PO_LINE_ID, or TAX_LINE_NO being the practical business-key candidates in combination with the concurrent request context.

Common Use Cases and Queries

The primary use case is diagnostic and reconciliation: confirming which taxes the JAINPOCR process proposed for a given purchase order and why. A typical pattern joins the staging rows back to the purchasing base tables:

  • Tax defaulting audit: SELECT r.po_header_id, r.po_line_id, r.tax_id, r.tax_rate, r.tax_amount FROM ja.jai_po_request_t r WHERE r.po_header_id = :p_po_header_id;
  • Precedence analysis: ordering by PRECEDENCE_1 through PRECEDENCE_10 to determine which criterion selected the winning tax for each line.
  • Vendor-level reporting: joining VENDOR_ID to HZ_PARTIES to summarize defaulted tax amounts by supplier.
  • Error investigation: identifying lines where TAX_ID or TAX_CATEGORY_ID is null after a JAINPOCR run, indicating the defaulting logic found no applicable tax.

Related Objects

Foreign key metadata identifies the following principal related objects and join columns:

  • PO_HEADERS_ALL via PO_HEADER_ID — the purchase order header context.
  • PO_LINES_ALL via PO_LINE_ID — the purchase order line being taxed.
  • PO_LINE_LOCATIONS_ALL via LINE_LOCATION_ID — the shipment or distribution detail.
  • JAI_PO_LINE_LOCATIONS via LINE_FOCUS_ID — the localization line reference used by the defaulting process.
  • JAI_CMN_TAXES_ALL via TAX_ID — the tax definition applied.
  • JAI_CMN_TAX_CTGS_ALL via TAX_CATEGORY_ID — the tax category classification.
  • HZ_PARTIES via VENDOR_ID — the supplier party record.

These relationships confirm that JAI_PO_REQUEST_T sits between the purchasing and Asia/Pacific tax localization schemas, acting as the bridge that the JAINPOCR concurrent program populates and consumes.