Search Results jai_po_req_line_taxes

Overview

The JAI_PO_REQ_LINE_TAXES table is a core data object within the Oracle E-Business Suite (EBS) Asia/Pacific Localizations module (product JA). Its primary function is to persistently store detailed tax information associated with individual requisition lines. In the context of Oracle Purchasing (PO) in releases 12.1.1 and 12.2.2, this table enables the complex tax calculations and compliance reporting required for specific countries in the Asia/Pacific region. It acts as a child table to the standard PO_REQUISITION_LINES_ALL table, extending the base requisition functionality to capture localization-specific tax attributes that are not present in the global application. The table's existence is critical for ensuring accurate tax determination, liability tracking, and audit trails for procurement requests before they are converted into purchase orders.

Key Information Stored

While the specific column list is not detailed in the provided metadata, the documented primary and foreign key relationships definitively indicate the critical data elements stored. The composite primary key, consisting of REQUISITION_LINE_ID and TAX_ID, establishes that the table stores one or more tax records for each requisition line. The foreign keys reveal the table holds identifiers linking to the tax master (TAX_ID to JAI_CMN_TAXES_ALL), tax categories (TAX_CATEGORY_ID to JAI_CMN_TAX_CTGS_ALL), the requisition header (REQUISITION_HEADER_ID), and the vendor (VENDOR_ID to HZ_PARTIES). Typically, such a table would also store calculated tax amounts, tax rates, tax recovery flags, and jurisdictional information, forming a complete snapshot of the tax applied to a requisition line at the time of its creation.

Common Use Cases and Queries

The primary use case is supporting the tax calculation engine during requisition entry and providing data for tax reports. A common operational query involves retrieving all tax lines for a specific requisition to display on a review form or to feed a downstream interface. For reporting and reconciliation, analysts frequently query this table to aggregate tax amounts by vendor, tax type, or period. A sample SQL pattern to join with master data is:

• SELECT prla.segment1 req_num, prla.line_num, jprlt.*, jcta.tax_code FROM jai_po_req_line_taxes jprlt JOIN po_requisition_lines_all prla ON jprlt.requisition_line_id = prla.requisition_line_id JOIN jai_cmn_taxes_all jcta ON jprlt.tax_id = jcta.tax_id WHERE prla.requisition_header_id = :req_header_id;

Another critical use case is during the requisition-to-purchase order conversion process, where the tax data from this table is often transferred to the corresponding purchase order line tax tables (e.g., JAI_PO_LINE_TAXES) to maintain consistency and auditability.

Related Objects

The table is centrally connected to several key EBS objects via foreign key constraints, as documented. Its relationships are fundamental to data integrity.

• PO_REQUISITION_LINES_ALL: The primary parent table. Joined via JAI_PO_REQ_LINE_TAXES.REQUISITION_LINE_ID.
• PO_REQUISITION_HEADERS_ALL: Provides header-level context. Joined via JAI_PO_REQ_LINE_TAXES.REQUISITION_HEADER_ID.
• JAI_CMN_TAXES_ALL: The master tax definition table. Joined via JAI_PO_REQ_LINE_TAXES.TAX_ID.
• JAI_CMN_TAX_CTGS_ALL: The tax category master. Joined via JAI_PO_REQ_LINE_TAXES.TAX_CATEGORY_ID.
• HZ_PARTIES: The Trading Community Architecture (TCA) registry for parties, providing vendor details. Joined via JAI_PO_REQ_LINE_TAXES.VENDOR_ID.

This table is also a likely source for various localization-specific tax reports and may be referenced by APIs or concurrent programs within the JA module for tax processing and validation.