Search Results jai_om_oe_so_lines_u1

Overview

The table JA.JAI_OM_OE_SO_LINES is a localization table owned by the JA (Subledger Accounting / India Localization) schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It stores jurisdiction-specific fiscal and statutory information for sales order lines originating in Oracle Order Management. In the base application, order line data resides in OE_ORDER_LINES_ALL; JAI_OM_OE_SO_LINES extends that data with tax, excise, VAT, and GST attributes required for statutory reporting in localizations supported by the JA schema.

The object is registered as VALID with the FND Design Data identifier JA.JAI_OM_OE_SO_LINES. It resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. Its heuristic Data Vault classification is link, meaning it is best modeled as an associative entity that joins the sales order header and line hubs while carrying descriptive transactional context. This classification is a modeling suggestion derived from the foreign-key structure, not a physical attribute of the table.

Key Information Stored

The surrogate primary key is LINE_ID, enforced by the unique index JAI_OM_OE_SO_LINES_PK in the APPS_TS_TX_IDX tablespace. A second unique index, JAI_OM_OE_SO_LINES_U1 (the object referenced in the search term jai_om_oe_so_lines_u1), enforces uniqueness on the composite (HEADER_ID, LINE_ID), making that pair the principal business-key candidate. A non-unique index, JAI_OM_OE_SO_LINES_N1, supports the reverse access path on (LINE_ID, HEADER_ID).

The most significant columns include:

• LINE_ID — surrogate primary key and line identifier.
• HEADER_ID — sales order header identifier, linking to OE_ORDER_HEADERS_ALL.
• LINE_NUMBER — display line number.
• SHIPMENT_SCHEDULE_LINE_ID — in ATO scenarios, holds the order_line_id of the model item for OPTION and CONFIG items.
• INVENTORY_ITEM_ID — inventory item identifier.
• QUANTITY — shipped or ordered line quantity.
• UNIT_CODE — unit of measure code.
• SELLING_PRICE and LINE_AMOUNT — price and line amount before tax.
• ASSESSABLE_VALUE, TAX_AMOUNT, LINE_TOT_AMOUNT — the tax computation triplet used for fiscal reporting.
• TAX_CATEGORY_ID — tax category foreign key to JAI_CMN_TAX_CTGS_ALL.
• VAT_ASSESSABLE_VALUE, VAT_EXEMPTION_FLAG, VAT_REVERSAL_PRICE — VAT reporting attributes.
• GST_ASSESSABLE_VALUE — GST assessable value.
• EXCISE_EXEMPT_TYPE, EXCISE_EXEMPT_REFNO, EXCISE_EXEMPT_DATE — excise exemption details.
• SPLIT_FROM_LINE_ID — records the originating order line when a line is split.
• OBJECT_VERSION_NUMBER and the standard Who columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) — audit and concurrency control.

Common Use Cases and Queries

Typical use cases include statutory tax and excise reporting, reconciliation of localized tax values against base order line amounts, and ATO/configuration line analysis. A representative query joining to the order header follows:

• SELECT l.line_id, l.header_id, l.line_number, l.quantity, l.tax_amount, l.vat_assessable_value FROM ja.jai_om_oe_so_lines l WHERE l.header_id = :p_header_id ORDER BY l.line_number;
• Reconciliation of tax values: join TAX_CATEGORY_ID to JAI_CMN_TAX_CTGS_ALL to resolve category descriptions.
• ATO scenario reporting: filter on SHIPMENT_SCHEDULE_LINE_ID IS NOT NULL to isolate OPTION and CONFIG items.
• Audit extraction: query by LAST_UPDATE_DATE range for period-end localization reconciliations.

Related Objects

• OE_ORDER_HEADERS_ALL — referenced by HEADER_ID; the base sales order header.
• OE_ORDER_LINES_ALL — referenced by SHIPMENT_SCHEDULE_LINE_ID and SPLIT_FROM_LINE_ID; the base order line.
• JAI_CMN_TAX_CTGS_ALL — referenced by TAX_CATEGORY_ID; resolves tax category definitions.
• JAI_OM_OE_SO_HEADERS — the companion header-level localization table.
• Oracle Order Management localization concurrent programs and reporting views that consume JAI_OM_OE_SO_LINES_U1 for header-and-line keyed lookups.