Search Results jai_om_wsh_lines_all




Overview
Explore in AI Chat

Overview

The JAI_OM_WSH_LINES_ALL table is a core localization data repository within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Asia/Pacific (JA) region. Its primary function is to capture and persist country-specific transactional information at the granularity of a picking or delivery line. This table acts as a critical junction, linking standard Oracle Shipping (WSH) and Order Management (OM) entities with localized tax, regulatory, and organizational data mandated for compliant operations in supported countries. It is a mandatory table for the JA localization and is instantiated for each operating unit (ORG_ID) where the localization is active.

Key Information Stored

The table's structure is defined by its integration with foundational EBS modules. Its primary key (JAI_OM_WSH_LINES_ALL_PK) is the DELIVERY_DETAIL_ID, creating a one-to-one relationship with a line in WSH_DELIVERY_DETAILS. A unique key also enforces the combination of DELIVERY_ID and DELIVERY_DETAIL_ID. Key stored data elements, as indicated by its foreign key relationships, include identifiers for the originating sales order (ORDER_HEADER_ID, ORDER_LINE_ID, ORDER_TYPE_ID), the picking batch (PICKING_HEADER_ID, PICKING_LINE_ID), the customer (CUSTOMER_ID), and the ship-to location (SHIP_TO_ORG_ID). Crucially for localization, it links to the inventory organization (ORGANIZATION_ID), specific inventory item (INVENTORY_ITEM_ID), and the applicable tax category (TAX_CATEGORY_ID) from localization setup tables like JAI_CMN_INVENTORY_ORGS and JAI_CMN_TAX_CTGS_ALL.

Common Use Cases and Queries

This table is central to generating localized tax invoices, excise reports, and other statutory documents. Common operational and reporting queries involve joining this table to both standard and localization objects. A typical pattern retrieves all localized delivery lines for a specific sales order or delivery to calculate region-specific taxes. For auditing, one might query the linkage between a delivery detail and its associated localization setup.

  • Sample Query for Delivery Line Localization Context:
    SELECT jomwla.*, wdd.source_line_id
    FROM jai_om_wsh_lines_all jomwla,
         wsh_delivery_details wdd
    WHERE jomwla.delivery_detail_id = wdd.delivery_detail_id
    AND wdd.delivery_id = :p_delivery_id;
  • Integration Point: Data in this table is populated during the pick-confirm and ship-confirm processes via localization-specific hooks or APIs, ensuring the localized attributes are stamped on the transaction before it is completed.

Related Objects

JAI_OM_WSH_LINES_ALL has extensive dependencies, as shown by its foreign keys. It is a parent to the JAI_OM_WSH_LINE_TAXES table, which holds the calculated tax amounts for each line. Its major foreign key relationships integrate it with the following key EBS entities:

This network of relationships underscores its role as the central linchpin connecting transactional flows to the JA localization's compliance engine.