Results for “picking_header_id”

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

Overview

JAI_OM_OE_GEN_TAXINV_T is a table owned by the JA schema within the Oracle E-Business Suite Asia/Pacific Localizations product. Its documented purpose is to hold the delivery identifier for which an excise invoice number is to be generated. In practice it functions as a staging and control table used by the Indian localizations (and related Asia/Pacific excise/tax regimes) to associate a delivery, its underlying sales order, picking and ship-to information, and the relevant ledger before the statutory excise or tax invoice is produced.

The table is populated from Order Management, Shipping, and Receivables-related flows and is consumed by the localization's tax invoice generation programs. Because it does not describe a single business entity but instead records the association between several existing entities—deliveries, order headers, picking headers, ship-to sites, and ledgers—the heuristic Data Vault classification derived from its foreign-key structure is that of a link. Practically, this is a many-to-many-style connective record tying transactional shipment events to the tax documents that must legally accompany them.

Key Information Stored

The table carries sixteen documented columns in the 12.2.2 schema. The most operationally significant are:

• DELIVERY_ID – Foreign key to WSH_NEW_DELIVERIES; the principal delivery for which the excise invoice is required. This is the core business identifier named in the object description.
• DELIVERY_DETAIL_ID – Foreign key to WSH_DELIVERY_DETAILS, identifying the specific line or item within the delivery.
• ORDER_HEADER_ID – Foreign key to OE_ORDER_HEADERS_ALL, linking the record back to the originating sales order header (the object the user searched for).
• SOURCE_HEADER_ID – A second reference to OE_ORDER_HEADERS_ALL, typically preserving the source order from which the delivery was derived.
• PICKING_HEADER_ID – Foreign key to SO_PICKING_HEADERS_ALL, tying the record to the pick-release step.
• SHIP_TO_SITE_USE_ID – Foreign key to HZ_CUST_SITE_USES_ALL, identifying the ship-to site use for tax determination.
• SET_OF_BOOKS_ID – Foreign key to GL_LEDGERS, identifying the ledger for accounting and reporting context.
• STATUS_CODE – Processing status of the invoice generation record (for example, pending, generated, or failed).
• DATE_RELEASED and DATE_CONFIRMED – Business dates marking when the delivery was released and confirmed.
• OBJECT_VERSION_NUMBER – Optimistic locking column used by the Oracle Applications Framework.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – Standard audit columns maintained by EBS conventions.

No surrogate primary key is separately documented in the metadata other than the delivery-level identifiers; the combination of delivery and detail identifiers serves as the practical business key.

Common Use Cases and Queries

Typical uses include identifying deliveries awaiting excise invoice generation, reconciling generated invoices against shipments, and reporting order-to-invoice tax status. A representative query joining the staging table to the sales order header is:

• SELECT t.delivery_id, t.order_header_id, h.order_number, t.status_code, t.date_released FROM jai_om_oe_gen_taxinv_t t, oe_order_headers_all h WHERE t.order_header_id = h.header_id AND t.status_code = 'PENDING';
• SELECT t.delivery_id, t.delivery_detail_id, t.set_of_books_id, t.ship_to_site_use_id FROM jai_om_oe_gen_taxinv_t t WHERE t.date_confirmed IS NOT NULL;
• Reporting the count of pending versus generated excise invoices per ledger, per ship-to site, or per legal entity for statutory filings.
• Integrating with concurrent programs that populate the excise invoice number once generation completes.

Related Objects

The documented foreign keys establish the following significant relationships:

• WSH_NEW_DELIVERIES on DELIVERY_ID – the delivery header.
• WSH_DELIVERY_DETAILS on DELIVERY_DETAIL_ID – delivery line detail.
• OE_ORDER_HEADERS_ALL on ORDER_HEADER_ID and SOURCE_HEADER_ID – the originating and source sales orders.
• SO_PICKING_HEADERS_ALL on PICKING_HEADER_ID – the pick-release header.
• HZ_CUST_SITE_USES_ALL on SHIP_TO_SITE_USE_ID – customer ship-to site usage.
• GL_LEDGERS on SET_OF_BOOKS_ID – the ledger defining accounting context.

These relationships confirm that the table is a localization-specific link between the Order Management, Shipping, Receivables/customer, and General Ledger sub-ledgers.