Results for “vat_exemption_refno”

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

Overview

JAI_OM_WSH_LINES_ALL is an Oracle E-Business Suite table owned by the JA (Asia/Pacific Localizations) schema. It exists to capture localization-specific information at the picking-line level, supporting statutory requirements for India and other Asia/Pacific jurisdictions that demand excise, VAT, and GST detail on outbound delivery and shipment lines. In Oracle EBS 12.1.1 and 12.2.2, the table operates as a supplementary localizations layer that sits alongside standard Oracle Order Management (OM) and Warehouse Management (WSH) delivery tables rather than replacing them.

The rows in this table are keyed to delivery detail records, meaning one row corresponds broadly to one shipped or picked delivery line, enriched with fiscal and tax attributes used for local reporting, excise invoice generation, and GST compliance. The documented physical schema contains 70 columns, indicating a wide, attribute-rich structure typical of localization extensions.

Based on the foreign-key structure mined from the ETRM metadata, the heuristic Data Vault classification of this object is satellite-leaning. In Data Vault modeling terms, this suggests the table behaves principally as a descriptive satellite attached to delivery, picking, and order hubs, carrying context, tax, and reference data rather than acting as an independent business hub. The presence of a single-column primary key on DELIVERY_DETAIL_ID reinforces this interpretation.

Key Information Stored

The primary key JAI_OM_WSH_LINES_ALL_PK is defined on the single surrogate column DELIVERY_DETAIL_ID, which links each localization row to its parent delivery detail. A unique-key constraint, JAI_OM_WSH_LINES_ALL_UK1, is documented on the combination of DELIVERY_ID and DELIVERY_DETAIL_ID, establishing that pair as the principal business-key candidate.

The most significant columns fall into several groups:

• Delivery and picking linkage: DELIVERY_ID, DELIVERY_DETAIL_ID, PICKING_LINE_ID, PICKING_HEADER_ID, SPLIT_FROM_DELIVERY_DETAIL_ID
• Order linkage: ORDER_HEADER_ID, ORDER_LINE_ID, ORDER_TYPE_ID, CUSTOMER_ID, SHIP_TO_ORG_ID
• Fiscal and excise detail: EXCISE_INVOICE_NO, EXCISE_INVOICE_DATE, EXCISE_AMOUNT, BASIC_EXCISE_DUTY_AMOUNT, ADD_EXCISE_DUTY_AMOUNT, OTH_EXCISE_DUTY_AMOUNT, ASSESSABLE_VALUE, REGISTER
• VAT detail: VAT_INVOICE_NO, VAT_INVOICE_DATE, VAT_ASSESSABLE_VALUE, VAT_EXEMPTION_FLAG, VAT_EXEMPTION_TYPE, VAT_EXEMPTION_REFNO
• GST detail: GST_INVOICE_NO, GST_INVOICE_DATE, GST_ASSESSABLE_VALUE
• Item and organization: ORGANIZATION_ID, INVENTORY_ITEM_ID, SUBINVENTORY, LOCATION_ID, UNIT_CODE, QUANTITY, SELLING_PRICE, TAX_CATEGORY_ID, TAX_AMOUNT
• Exemption and form references: EXC_EXEMPT_CERT_FLAG, CT3_FORM_FLAG, AR3_FORM_NO, AR3_FORM_DATE, PREPRINTED_EXCISE_INV_NO
• Standard WHO/audit and extensibility: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, OBJECT_VERSION_NUMBER, ATTRIBUTE_CATEGORY, ATTRIBUTE1 through ATTRIBUTE15

The fifteen ATTRIBUTE columns and OBJECT_VERSION_NUMBER follow the standard EBS extensibility and optimistic-locking conventions.

Common Use Cases and Queries

Typical usage centers on statutory tax reporting, excise and GST invoice reconciliation, and shipment-level audit. A common pattern joins this table back to delivery and order tables for a full line picture:

• Excise/GST invoice reconciliation: retrieve EXCISE_INVOICE_NO, GST_INVOICE_NO, and ASSESSABLE_VALUE by DELIVERY_DETAIL_ID for a date range.
• Tax category analysis: aggregate TAX_AMOUNT and ASSESSABLE_VALUE grouped by TAX_CATEGORY_ID and ORGANIZATION_ID.
• Exemption tracking: filter on VAT_EXEMPTION_FLAG, EXC_EXEMPT_CERT_FLAG, and AR3_FORM_NO to list lines requiring exemption certificates.
• Order-to-shipment tracing: join ORDER_LINE_ID to OE_ORDER_LINES_ALL to trace localization tax detail from order line to delivery detail.
• Split shipment handling: follow SPLIT_FROM_DELIVERY_DETAIL_ID to reconcile lines created when a delivery detail was split.

A representative query might select DELIVERY_DETAIL_ID, GST_INVOICE_NO, and GST_ASSESSABLE_VALUE where GST_INVOICE_DATE falls within a reporting period, optionally grouped by ORGANIZATION_ID.

Related Objects

The table participates in a dense web of foreign-key relationships. The most significant related objects, with their actual join columns, are:

• WSH_DELIVERY_DETAILS — referenced via SPLIT_FROM_DELIVERY_DETAIL_ID.
• WSH_NEW_DELIVERIES — referenced via DELIVERY_ID.
• SO_PICKING_LINES_ALL — referenced via PICKING_LINE_ID.
• SO_PICKING_HEADERS_ALL — referenced via PICKING_HEADER_ID.
• OE_ORDER_HEADERS_ALL — referenced via ORDER_HEADER_ID.
• OE_ORDER_LINES_ALL — referenced via ORDER_LINE_ID.
• OE_TRANSACTION_TYPES_ALL — referenced via ORDER_TYPE_ID.
• HZ_PARTIES — referenced via CUSTOMER_ID.
• HR_ALL_ORGANIZATION_UNITS — referenced via ORG_ID and SHIP_TO_ORG_ID.
• JAI_OM_WSH_LINE_TAXES — a dependent child table referencing this table via DELIVERY_DETAIL_ID.

Additional localization dependencies include JAI_CMN_INVENTORY_ORGS, JAI_INV_ITM_SETUPS, and JAI_CMN_TAX_CTGS_ALL, which supply organization, item-setup, and tax-category context respectively. Together these relationships confirm the table's role as a satellite extension of the standard Oracle shipping and order-management data model.