Results for “modvat_flag”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

JAI_PO_REQ_LINE_TAXES is a transactional table in the JA (Asia/Pacific Localizations) product within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores tax information associated with individual requisition lines, capturing the tax lines, rates, amounts, and tax category assignments that apply to a purchasing requisition before it is converted into a purchase order. The object resides in the JA schema and is classified as VALID in the ETRM repository.

Oracle's tax engines for the Asia/Pacific region, particularly for India (JAI), maintain country-specific tax determination logic that cannot be handled entirely by the standard EBS Payables and Purchasing tax model. This table bridges that gap by persisting the calculated tax details at requisition line level, ensuring that tax amounts are carried forward consistently when requisitions are autocreated or copied into purchase orders.

Based on the foreign key structure, the heuristic Data Vault classification for this object is a link. The table connects independent entities — requisition lines, tax definitions, tax categories, and vendors — through a composite key, making it a natural association table rather than a hub or satellite.

Key Information Stored

The table contains 30 documented columns. The most significant are listed below, distinguishing key structural columns from ancillary data.

• REQUISITION_LINE_ID and TAX_ID — together these form the primary key, JAI_PO_REQ_LINE_TAXES_PK. REQUISITION_LINE_ID identifies the parent requisition line; TAX_ID identifies the specific tax being applied. This composite key is the table's only documented unique index and therefore its only business-key candidate.
• REQUISITION_HEADER_ID — denormalized reference to the requisition header, useful for header-level reporting without joining intermediate tables.
• TAX_LINE_NO — sequence number for ordering multiple tax lines on the same requisition line.
• TAX_RATE, TAX_AMOUNT, and TAX_TARGET_AMOUNT — the percentage rate applied, the tax amount computed for the line, and the taxable base amount respectively.
• CURRENCY and UOM — the currency in which the tax amount is expressed and the unit of measure tied to quantity-based rates.
• QTY_RATE — the per-unit tax rate when tax is determined on a quantity basis rather than a percentage.
• TAX_TYPE and MODVAT_FLAG — the classification of the tax and a flag indicating whether the line is eligible for MODVAT (modified value-added tax) credit treatment.
• TAX_CATEGORY_ID — the tax category that governs the determination rules for this line.
• VENDOR_ID — the supplier against whom the tax was determined, referencing HZ_PARTIES.
• PRECEDENCE_1 through PRECEDENCE_10 — a set of precedence columns used by the tax determination engine to resolve rule priorities during tax calculation.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER — standard WHO audit columns and the optimistic locking token used by the OAF framework.

Common Use Cases and Queries

The most frequent use of this table is to report and reconcile taxes calculated at requisition stage. Typical scenarios include auditing tax amounts before autocreate to purchase orders, verifying that MODVAT-eligible lines were correctly flagged, and producing tax registers for statutory compliance in Indian localization environments.

• Retrieving all tax lines for a requisition header, joining to PO_REQUISITION_HEADERS_ALL via REQUISITION_HEADER_ID.
• Summing TAX_AMOUNT by TAX_ID or TAX_CATEGORY_ID to reconcile against a tax summarization report.
• Comparing TAX_RATE and QTY_RATE to detect manually overridden or recalculated entries.
• Joining to JAI_CMN_TAXES_ALL for tax descriptions and to HZ_PARTIES for supplier details.

A representative query aggregates tax by requisition:

SELECT h.segment1, t.tax_id, SUM(t.tax_amount) FROM jai_po_req_line_taxes t JOIN po_requisition_headers_all h ON t.requisition_header_id = h.requisition_header_id WHERE t.creation_date >= :p_from GROUP BY h.segment1, t.tax_id;

Related Objects

• PO_REQUISITION_LINES_ALL — parent requisition line, joined on REQUISITION_LINE_ID.
• PO_REQUISITION_HEADERS_ALL — parent requisition header, joined on REQUISITION_HEADER_ID.
• JAI_CMN_TAXES_ALL — tax master defining each TAX_ID, supplying tax name and default rate information.
• JAI_CMN_TAX_CTGS_ALL — tax category master referenced through TAX_CATEGORY_ID, driving determination rules.
• HZ_PARTIES — trading partner registry referenced through VENDOR_ID for supplier identification.

These relationships confirm that the table functions as a transaction-level link between the purchasing requisition model and the JA tax configuration model, and it should be treated as such in any downstream reporting or integration design.