Search Results jai_po_request_t




Overview
Explore in AI Chat

Overview

The JAI_PO_REQUEST_T table is a core data object within the Asia/Pacific Localizations (JA) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It functions as a transactional staging and processing table specifically designed to support the automated defaulting of tax information for purchase orders. Its primary role is to serve as the underlying data structure for the JAINPOCR concurrent program, which processes purchase order requests to calculate and apply the correct tax defaults based on localized rules for supported countries in the Asia/Pacific region. The table's design, with multiple foreign key relationships to core purchasing and tax entities, indicates its critical function in bridging standard EBS procurement transactions with localized tax compliance logic.

Key Information Stored

While specific column definitions are not provided in the metadata, the documented foreign key relationships explicitly reveal the key identifiers stored in this table. Each record likely represents a purchase order line-level request for tax processing. The essential foreign key columns stored include PO_HEADER_ID, PO_LINE_ID, and LINE_LOCATION_ID, which anchor the request to the standard purchase order in PO_HEADERS_ALL, PO_LINES_ALL, and PO_LINE_LOCATIONS_ALL. For tax determination, the table stores TAX_ID and TAX_CATEGORY_ID, linking to the localization tax tables JAI_CMN_TAXES_ALL and JAI_CMN_TAX_CTGS_ALL. The VENDOR_ID links to the trading partner in HZ_PARTIES, and the LINE_FOCUS_ID provides a specific reference to the localized tax attributes in JAI_PO_LINE_LOCATIONS.

Common Use Cases and Queries

The predominant use case is the execution and support of the JAINPOCR concurrent program. This program queries records from JAI_PO_REQUEST_T, likely populated by a triggering event or a batch selection process, to perform tax calculations. Common queries involve joining this table to its referenced entities to extract a complete dataset for tax processing. For troubleshooting or reporting, one might analyze pending requests or audit processed transactions. A sample diagnostic SQL pattern would be:

  • SELECT jpr.*, pl.line_num, ph.segment1 po_number FROM jai_po_request_t jpr, po_lines_all pl, po_headers_all ph WHERE jpr.po_line_id = pl.po_line_id AND jpr.po_header_id = ph.po_header_id AND jpr.process_flag = 'PENDING';

This would identify requests awaiting tax defaulting processing by the concurrent program.

Related Objects

JAI_PO_REQUEST_T is a central hub with defined foreign key dependencies to several standard and localized tables. The documented relationships are as follows:

  • PO_HEADERS_ALL: Via JAI_PO_REQUEST_T.PO_HEADER_ID. Links to the purchase order header.
  • PO_LINES_ALL: Via JAI_PO_REQUEST_T.PO_LINE_ID. Links to the purchase order line.
  • PO_LINE_LOCATIONS_ALL: Via JAI_PO_REQUEST_T.LINE_LOCATION_ID. Links to the shipment/schedule line.
  • HZ_PARTIES: Via JAI_PO_REQUEST_T.VENDOR_ID. Links to the supplier master.
  • JAI_CMN_TAXES_ALL: Via JAI_PO_REQUEST_T.TAX_ID. Links to the localized tax definitions.
  • JAI_CMN_TAX_CTGS_ALL: Via JAI_PO_REQUEST_T.TAX_CATEGORY_ID. Links to the tax category master.
  • JAI_PO_LINE_LOCATIONS: Via JAI_PO_REQUEST_T.LINE_FOCUS_ID. Links to the localized tax attributes for the PO line location.

The primary dependent object is the JAINPOCR concurrent program, which is the main consumer of the data stored in this table.