Search Results oe_invoice_numbers




Overview

The OE_INVOICE_NUMBERS table is a core data object within the Oracle E-Business Suite (EBS) Order Management (ONT) module. Its primary function is to manage the generation and storage of invoice numbers that are specifically tied to delivery entities. This table acts as a critical junction point between the shipping fulfillment process and the invoicing cycle, ensuring a traceable link from a physical or logical delivery to its corresponding financial document. By storing this relationship, it supports business processes where invoice numbering is driven by delivery information, which is common in complex shipping and direct-to-customer scenarios.

Key Information Stored

While the full column list is not detailed in the provided metadata, the core relationship is defined by the foreign key to the WSH_NEW_DELIVERIES table. The most critical columns are therefore:

  • DELIVERY_ID: A foreign key column that references the WSH_NEW_DELIVERIES.DELIVERY_ID. This column establishes the fundamental link between a specific delivery record and the invoice number data.
  • INVOICE_NUMBER (inferred): Although not explicitly listed, the table's purpose implies a column or columns storing the generated invoice number or number sequence. This could be a single number or components that form a unique invoice identifier.
  • Additional columns likely include creation date, last update date, and the user who performed the action, following standard Oracle EBS audit convention.

Common Use Cases and Queries

This table is essential for troubleshooting and reporting on the invoice generation process from deliveries. A common operational query involves identifying the invoice number for a specific delivery or tracing back which delivery a particular invoice was created from. For example, to find invoice information for a known delivery ID, a DBA or support analyst might execute:

SELECT oin.invoice_number, oin.creation_date
FROM ont.oe_invoice_numbers oin
WHERE oin.delivery_id = <delivery_id_value>;

Conversely, to audit deliveries that have not yet had an invoice number generated, a LEFT JOIN query against WSH_NEW_DELIVERIES would be used. This table is also pivotal in custom reports that need to join shipping data directly to invoice numbers without navigating through the entire Order-to-Cash transactional flow.

Related Objects

The primary and most significant relationship for the OE_INVOICE_NUMBERS table is with the Shipping Execution module's WSH_NEW_DELIVERIES table, as defined by its foreign key. This dependency means that for a record to exist in OE_INVOICE_NUMBERS, a corresponding delivery must first exist in WSH_NEW_DELIVERIES. While not listed in the excerpt, this table is likely referenced by or feeds data into key Order Management and Receivables interfaces or base tables responsible for creating final transaction lines in AR_INVOICES_ALL or RA_INTERFACE_LINES_ALL. Direct queries or integrations involving delivery-based invoicing must consistently join through this table to maintain data integrity.