Results for “index_number”

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

Overview

WSH_INVOICE_NUMBERS is a shipping-related table owned by the OE (Order Entry) schema in Oracle E-Business Suite. Its documented purpose is to store shipping invoice numbers, and it functions as the record of invoice numbering activity associated with outbound deliveries processed through the Oracle Shipping execution flow. The table sits at the intersection of shipping confirmation and order-to-cash invoice generation: once deliveries are confirmed in Oracle Shipping, invoice numbers are allocated and captured here, providing a linkage between the physical shipment (the delivery) and the financial document reference.

The table carries a single-column surrogate primary key defined by the constraint WSH_INVOICE_NUMBERS_PK on the column INVOICE_NUMBER_ID — the exact identifier referenced by the search term "invoice_number_id". A second unique index, WSH_INVOICE_NUMBERS_U1, also covers INVOICE_NUMBER_ID, reinforcing its uniqueness role. A business-key candidate is documented through WSH_INVOICE_NUMBERS_U2, a composite unique index on (DELIVERY_ID, INDEX_NUMBER), which guarantees a deterministic sequence of invoice numbers per delivery.

Using a heuristic Data Vault classification mined from the foreign key structure, this table is satellite-leaning. It appears to represent descriptive, transaction-generated attributes attached to a parent delivery rather than a true many-to-many hub or link construct. This classification is offered as a modeling suggestion rather than an authoritative dependency.

Key Information Stored

The documented physical schema contains 12 columns. The most significant are the following.

• INVOICE_NUMBER_ID — surrogate primary key of the table, enforced by WSH_INVOICE_NUMBERS_PK and WSH_INVOICE_NUMBERS_U1. This is the value users typically search for and the column most commonly joined from dependent objects.
• DELIVERY_ID — foreign key to WSH_DELIVERIES. It ties each invoice number row to the shipment it belongs to and, together with INDEX_NUMBER, forms the composite unique business key.
• INDEX_NUMBER — sequence or occurrence indicator that disambiguates multiple invoice numbers recorded against a single delivery.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE — the standard concurrent program audit block, identifying the shipping or interface process that inserted the row.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — the standard "WHO" audit columns present on most EBS transactional tables, recording creation and last modification context.

Common Use Cases and Queries

The primary operational use case is tracing which invoice numbers were assigned to a given delivery, either for reconciliation between Oracle Shipping and Receivables or for supporting documentation such as packing slips and shipping manifests.

• Retrieve all invoice numbers for a delivery: SELECT INVOICE_NUMBER_ID, DELIVERY_ID, INDEX_NUMBER FROM OE.WSH_INVOICE_NUMBERS WHERE DELIVERY_ID = :p_delivery_id;
• Resolve a specific invoice reference: SELECT * FROM OE.WSH_INVOICE_NUMBERS WHERE INVOICE_NUMBER_ID = :p_invoice_number_id;
• Join to delivery headers to report shipment and invoice context: SELECT d.DELIVERY_ID, d.NAME, n.INVOICE_NUMBER_ID, n.INDEX_NUMBER FROM OE.WSH_INVOICE_NUMBERS n, OE.WSH_DELIVERIES d WHERE n.DELIVERY_ID = d.DELIVERY_ID;

Reporting teams also use the concurrent program audit columns to audit which concurrent request generated invoice numbers within a given period, and to confirm that no delivery was left uninvoiced.

Related Objects

• WSH_DELIVERIES — parent delivery table referenced by WSH_INVOICE_NUMBERS.DELIVERY_ID; the primary parent of this satellite.
• OE_INVOICE_NUMBERS — holds its own INVOICE_NUMBER_ID column that references WSH_INVOICE_NUMBERS, making it a child/dependent object on the same identifier.
• WSH_DELIVERY_DETAILS — supplies line-level shipment context for the associated delivery.
• WSH_NEW_DELIVERIES — the interface table through which delivery data, and by extension invoice numbering activity, is staged.
• OM/WSH shipping APIs and the pick-confirm and ship-confirm concurrent processes populate this table during delivery confirmation.