Search Results jai_om_oe_gen_taxinv_t




Overview
Explore in AI Chat

Overview

The table JAI_OM_OE_GEN_TAXINV_T is a core data object within the Asia/Pacific Localizations (JA) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. Its primary function is to manage the generation of excise tax invoices, a critical legal requirement for jurisdictions like India. The table acts as a staging or control table that identifies specific delivery lines for which an excise invoice number must be generated. By holding these identifiers, it facilitates the integration between the Order Management (OM) and Shipping Execution modules and the localized tax invoice generation logic, ensuring compliance with regional statutory reporting.

Key Information Stored

While the full column list is not provided in the metadata, the documented foreign key relationships explicitly reveal the table's critical data points. The table stores key identifiers that link a tax invoice generation request to the core transactional entities of EBS. The essential columns inferred from these relationships include DELIVERY_ID, DELIVERY_DETAIL_ID, and PICKING_HEADER_ID from the shipping modules; ORDER_HEADER_ID and SOURCE_HEADER_ID from Order Management; SHIP_TO_SITE_USE_ID for the customer location; and SET_OF_BOOKS_ID for the legal entity or ledger context. This structure indicates the table captures the necessary context—specific delivery line, order, customer, and ledger—to trigger and record the generation of a unique excise invoice number for the transaction.

Common Use Cases and Queries

The primary use case is the batch or online process that queries this table for pending deliveries requiring excise invoices. A typical process would join this control table to the main transactional tables to fetch all relevant header and line details for invoice formatting and numbering. Common reporting queries would focus on the status of invoice generation, such as identifying deliveries associated with a specific order that have not yet been processed. A sample diagnostic SQL to see active records would be:

SELECT gt.delivery_id, gt.order_header_id, d.name delivery_name, h.order_number
FROM jai_om_oe_gen_taxinv_t gt,
     wsh_new_deliveries d,
     oe_order_headers_all h
WHERE gt.delivery_id = d.delivery_id
  AND gt.order_header_id = h.header_id;

Data in this table is typically inserted by localization-specific logic during the delivery or shipping confirmation process and is purged or marked as processed once the excise invoice number is successfully generated and assigned.

Related Objects

The table maintains integral relationships with several core EBS tables, as documented by its foreign keys. These relationships are essential for fetching the complete transaction data needed for invoice generation.

  • WSH_NEW_DELIVERIES & WSH_DELIVERY_DETAILS: Joined via DELIVERY_ID and DELIVERY_DETAIL_ID to retrieve shipping execution information.
  • OE_ORDER_HEADERS_ALL: Joined via both ORDER_HEADER_ID and SOURCE_HEADER_ID to access the sales order header details.
  • SO_PICKING_HEADERS_ALL: Joined via PICKING_HEADER_ID to link to the Order Management picking batch.
  • HZ_CUST_SITE_USES_ALL: Joined via SHIP_TO_SITE_USE_ID to obtain the customer ship-to address details for the invoice.
  • GL_LEDGERS: Joined via SET_OF_BOOKS_ID to determine the correct ledger for financial and legal reporting compliance.