Results for “tax_modified_flag”

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

Overview

JAI_PO_REQ_LINES is a localization table owned by the JA schema (Asia/Pacific Localizations) in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores country-specific requisition line information and associated tax amounts that are not captured by the base purchasing schema. Specifically, it functions as the tax and localization extension for requisition lines processed under Asia/Pacific tax regimes, holding the tax category, computed tax amount, and total amount for each affected line, along with suggested sourcing defaults.

The table holds 15 documented columns and is keyed by the unique index JAI_PO_REQ_LINES_PK on REQUISITION_LINE_ID. Its three foreign keys — to PO_REQUISITION_LINES_ALL, PO_REQUISITION_HEADERS_ALL, and JAI_CMN_TAX_CTGS_ALL — show that it sits beneath the standard purchasing requisition entities and references the JA common tax category catalog. Under a Data Vault modeling heuristic, this object is best classified as a link entity: it connects a requisition line to a tax category while carrying descriptive and measurable attributes, rather than acting as a standalone hub or a purely descriptive satellite.

Key Information Stored

The most important columns fall into three groups:

• Identity and relationships: REQUISITION_LINE_ID is the surrogate primary key and also the foreign key to PO_REQUISITION_LINES_ALL; REQUISITION_HEADER_ID references the parent requisition in PO_REQUISITION_HEADERS_ALL; TAX_CATEGORY_ID references the tax category definition in JAI_CMN_TAX_CTGS_ALL. These three columns form the principal business-key candidate set (with REQUISITION_LINE_ID enforced as unique).
• Tax and amount attributes: TAX_AMOUNT holds the calculated tax for the line, TOTAL_AMOUNT holds the line total including tax, and TAX_MODIFIED_FLAG records whether the default tax was overridden. CURRENCY_CODE identifies the currency in which these amounts are expressed.
• Sourcing and audit columns: SUGGESTED_VENDOR_NAME and SUGGESTED_VENDOR_LOCATION capture vendor recommendations for the localized requisition. CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER provide standard EBS audit and optimistic concurrency tracking.

Common Use Cases and Queries

The table is typically queried to report tax on requisitions for Asia/Pacific operating units, to reconcile localized tax amounts against the base purchasing schema, and to identify manually overridden tax lines.

• Join tax details to the base line:

  SELECT l.requisition_line_id, l.tax_amount, l.total_amount, l.currency_code
FROM jai_po_req_lines l
WHERE l.requisition_header_id = :header_id;

• Retrieve the tax category name for reporting:

  SELECT t.tax_category_id, t.tax_amount
FROM jai_po_req_lines t, jai_cmn_tax_ctgs_all c
WHERE t.tax_category_id = c.tax_category_id;

• Flag lines where tax was manually changed: WHERE tax_modified_flag = 'Y'.
• Aggregate localized tax by currency or period for tax reconciliation and accrual reporting, joining to PO_REQUISITION_HEADERS_ALL for organization and date context.

Related Objects

• PO_REQUISITION_LINES_ALL — the base requisition line, joined on REQUISITION_LINE_ID.
• PO_REQUISITION_HEADERS_ALL — the parent requisition, joined on REQUISITION_HEADER_ID.
• JAI_CMN_TAX_CTGS_ALL — the tax category definition, joined on TAX_CATEGORY_ID.
• Requisition entry and inquiry forms and the corresponding purchasing APIs, which populate and read these localization rows during requisition processing.
• Tax reporting and reconciliation views that consolidate JA localization tax data with base purchasing amounts.