Search Results jai_om_oe_so_lines

Overview

JAI_OM_OE_SO_LINES is a table owned by the JA schema and delivered as part of the Oracle E-Business Suite Asia/Pacific (APAC) Localizations module (product code JA). Its documented purpose is to store localization information for sales orders processed through Oracle Order Management. In the 12.1.1 and 12.2.2 releases, the table is registered as VALID and contains 52 documented columns, functioning as the localization extension to the standard OE_ORDER_LINES_ALL entity. Where Oracle's base Order Management tables capture the global sales order line structure, JAI_OM_OE_SO_LINES carries the India-centric statutory attributes required for tax determination, excise and VAT compliance, and GST reporting that the core schema does not natively hold.

The ETRM metadata's heuristic Data Vault classification for this object is link. Taken as a modeling suggestion, this reflects the table's role as an associative structure that binds a sales order line context (header and line identifiers) to a tax category and to downstream shipment/split line references, rather than acting as a pure reference hub or a descriptive satellite of a single business key. The presence of informative attributes such as assessable values and exemption details means the object also functions partially as a satellite, so the link classification should be treated as directional rather than absolute.

Key Information Stored

The surrogate primary key is LINE_ID, enforced by the unique index JAI_OM_OE_SO_LINES_PK. A second unique index, JAI_OM_OE_SO_LINES_U1, is defined on (HEADER_ID, LINE_ID) and serves as a documented business-key candidate. The most operationally significant columns are:

• LINE_ID — surrogate primary key of the localization record.
• HEADER_ID — foreign key to OE_ORDER_HEADERS_ALL, anchoring the record to the sales order.
• SHIPMENT_SCHEDULE_LINE_ID — foreign key to OE_ORDER_LINES_ALL, identifying the shipment schedule line.
• SPLIT_FROM_LINE_ID — foreign key to OE_ORDER_LINES_ALL, capturing the originating line when the order line was split.
• LINE_NUMBER / SHIPMENT_LINE_NUMBER — business line numbering for the order and shipment schedule respectively.
• INVENTORY_ITEM_ID — the inventory item associated with the localized line.
• QUANTITY, UNIT_CODE, SELLING_PRICE, LINE_AMOUNT — quantity ordered, unit of measure, unit selling price, and extended line amount.
• TAX_CATEGORY_ID — foreign key to JAI_CMN_TAX_CTGS_ALL, driving tax determination.
• ASSESSABLE_VALUE, TAX_AMOUNT, LINE_TOT_AMOUNT, GST_ASSESSABLE_VALUE — the assessable base, tax charged, line total, and GST-specific assessable value.
• VAT_ASSESSABLE_VALUE, VAT_REVERSAL_PRICE, VAT_EXEMPTION_FLAG, VAT_EXEMPTION_TYPE, VAT_EXEMPTION_DATE, VAT_EXEMPTION_REFNO — VAT base and exemption evidence.
• EXCISE_EXEMPT_TYPE, EXCISE_EXEMPT_REFNO, EXCISE_EXEMPT_DATE, SERVICE_TYPE_CODE — excise exemption and service classification details.
• SHIPMENT_SCHEDULE_FLAG, ATO_FLAG, LC_FLAG, SHIP_TO_ORG_ID — status and context flags, including shipping organization.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 — the standard EBS descriptive flexfield columns for customer-specific localization extensions.

Common Use Cases and Queries

Reporters use this table to produce statutory tax and excise registers, GST reconciliation extracts, and VAT exemption audits. A typical join links the localization row to its order header and line context, for example: SELECT j.LINE_ID, j.HEADER_ID, j.LINE_NUMBER, j.ASSESSABLE_VALUE, j.TAX_AMOUNT, j.LINE_TOT_AMOUNT FROM JA.JAI_OM_OE_SO_LINES j WHERE j.HEADER_ID = :p_header_id. To resolve the tax category description, join TAX_CATEGORY_ID to JAI_CMN_TAX_CTGS_ALL. To reconcile localized lines against standard order lines, join SHIPMENT_SCHEDULE_LINE_ID to OE_ORDER_LINES_ALL.LINE_ID. Aggregate queries grouped by TAX_CATEGORY_ID or by SHIP_TO_ORG_ID support periodic tax liability reporting, while filters on VAT_EXEMPTION_FLAG or EXCISE_EXEMPT_TYPE support compliance exception reviews. Because the table is localization-specific, interrogating ATTRIBUTE_CATEGORY before reading ATTRIBUTE1–ATTRIBUTE15 avoids misinterpreting customized flexfield content.

Related Objects

• OE_ORDER_HEADERS_ALL — referenced via HEADER_ID; provides order-level context (customer, order type, dates).
• OE_ORDER_LINES_ALL — referenced twice, via SHIPMENT_SCHEDULE_LINE_ID and SPLIT_FROM_LINE_ID; supplies the standard line and split-line details.
• JAI_CMN_TAX_CTGS_ALL — referenced via TAX_CATEGORY_ID; defines the tax category applied to the line.
• JAI_OM_OE_SO_LINES_PK / JAI_OM_OE_SO_LINES_U1 — the unique indexes enforcing the surrogate key and the (HEADER_ID, LINE_ID) business-key candidate.
• Order Management localization APIs and concurrent programs in the JA module that populate and consume this table during order entry, tax calculation, and statutory extraction.