Search Results jai_om_wsh_line_taxes




Overview
Explore in AI Chat

Overview

The JAI_OM_WSH_LINE_TAXES table is a core data object within the Asia/Pacific Localizations (JA) product of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It functions as a transactional repository for tax line details that are directly associated with individual picking lines during the shipping and fulfillment process. Its primary role is to store and maintain the calculated tax information generated for specific delivery lines, enabling accurate tax accounting and reporting for shipped orders within the complex regulatory environments of the Asia/Pacific region. This table is integral to the localized tax engine, ensuring that tax calculations from the order management phase are correctly persisted and linked to the physical shipment execution.

Key Information Stored

While the specific column list is not detailed in the provided metadata, the documented primary and foreign key relationships define its critical structure. The table's composite primary key, JAI_OM_WSH_LINE_TAXES_PK, consists of DELIVERY_DETAIL_ID and TAX_ID. This indicates that for each unique delivery line (DELIVERY_DETAIL_ID), multiple tax records (TAX_ID) can be stored. The PICKING_LINE_ID column provides a direct link to the source picking transaction. Based on its purpose, the table would typically store attributes such as the tax rate, calculated tax amount, tax jurisdiction code, tax recovery type, and indicators for tax inclusivity. These columns collectively hold the complete tax liability breakdown for each shipped item.

Common Use Cases and Queries

A primary use case is the reconciliation of tax amounts between the order entry, shipping, and general ledger modules. Auditors or functional consultants may query this table to verify that taxes calculated on sales orders were correctly applied upon shipment. Common reporting needs include generating tax registers for statutory compliance or analyzing tax by product category for a given shipment batch. A typical SQL pattern involves joining to the related delivery and tax master tables to retrieve a comprehensive tax report for shipped lines.

SELECT wlt.*, wl.delivery_id, tl.tax_code
FROM ja.jai_om_wsh_line_taxes wlt,
     ja.jai_om_wsh_lines_all wl,
     ja.jai_cmn_taxes_all tl
WHERE wlt.delivery_detail_id = wl.delivery_detail_id
  AND wlt.tax_id = tl.tax_id
  AND wl.delivery_id = :p_delivery_id;

Related Objects

The table maintains defined foreign key relationships with several core EBS tables, anchoring it within the shipping and tax data model.

  • JAI_OM_WSH_LINES_ALL: Linked via JAI_OM_WSH_LINE_TAXES.DELIVERY_DETAIL_ID. This is the primary relationship, connecting tax lines to their corresponding delivery detail record.
  • JAI_CMN_TAXES_ALL: Linked via JAI_OM_WSH_LINE_TAXES.TAX_ID. This relationship provides access to the master tax definitions, rates, and rules used in the calculation.
  • SO_PICKING_LINES_ALL: Linked via JAI_OM_WSH_LINE_TAXES.PICKING_LINE_ID. This connects the tax record back to the original picking line generated from the sales order, ensuring traceability to the source transaction.