Search Results jai_po_req_lines




Overview
Explore in AI Chat

Overview

The JAI_PO_REQ_LINES table is a core data object within the Asia/Pacific Localizations (JA) module of Oracle E-Business Suite (EBS) releases 12.1.1 and 12.2.2. It functions as a localization extension table, designed to store country-specific tax and regulatory information that augments the standard requisition line data. Its primary role is to capture and persist tax-related details mandated for legal compliance in supported Asia/Pacific jurisdictions, which are not natively accommodated by the base Oracle Purchasing tables. The table is integral to ensuring that procurement processes adhere to localized tax calculation, reporting, and invoicing requirements.

Key Information Stored

The table's structure centers on linking to standard requisition entities and storing associated tax attributes. The primary key, REQUISITION_LINE_ID, establishes a one-to-one relationship with a line in the standard PO_REQUISITION_LINES_ALL table. A critical foreign key, TAX_CATEGORY_ID, links to the JAI_CMN_TAX_CTGS_ALL table, which holds the master definitions for applicable tax categories in the localization. While the specific detail columns are not enumerated in the provided metadata, based on its described purpose, the table typically stores calculated tax amounts (e.g., tax lines for GST, VAT, or other regional taxes), tax rates, tax jurisdiction codes, and indicators for tax applicability or recovery. The REQUISITION_HEADER_ID foreign key provides a direct link to the requisition header for consolidated tax reporting.

Common Use Cases and Queries

This table is primarily accessed for generating localized tax reports, auditing tax calculations on requisitions, and supporting the tax determination process during requisition entry and approval. A common reporting use case involves joining the table to standard purchasing tables to reconcile requisition values with localized tax amounts. For instance, a query to analyze tax details for a specific requisition would typically join through the REQUISITION_LINE_ID:

  • SELECT prla.segment1 req_number, prla.line_num, jprl.* FROM jai_po_req_lines jprl, po_requisition_lines_all prla WHERE jprl.requisition_line_id = prla.requisition_line_id AND prla.requisition_header_id = :p_req_header_id;

Another critical scenario is validating tax setup by joining to the tax category master table to ensure all requisition lines have a valid and active tax category assigned, which is essential for accurate tax computation during the creation of purchase orders from requisitions.

Related Objects

The JAI_PO_REQ_LINES table maintains defined foreign key relationships with several core EBS tables, as documented in the metadata:

  • PO_REQUISITION_LINES_ALL: The principal relationship. JAI_PO_REQ_LINES.REQUISITION_LINE_ID references PO_REQUISITION_LINES_ALL.REQUISITION_LINE_ID. This joins the localization data to the standard requisition line.
  • PO_REQUISITION_HEADERS_ALL: JAI_PO_REQ_LINES.REQUISITION_HEADER_ID references PO_REQUISITION_HEADERS_ALL.REQUISITION_HEADER_ID. This allows header-level aggregation of tax data.
  • JAI_CMN_TAX_CTGS_ALL: JAI_PO_REQ_LINES.TAX_CATEGORY_ID references JAI_CMN_TAX_CTGS_ALL.TAX_CATEGORY_ID. This links the line to the master tax category controlling the tax rules and rates.

These relationships ensure data integrity and are fundamental for any integration, data migration, or reporting involving Asia/Pacific localized tax data for requisitions.