Results for “oe_invoice_numbers”
34 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
OE_INVOICE_NUMBERS is a transactional table owned by the ONT (Order Management) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is the generation of invoice numbers based on the delivery name, which positions it as a delivery-level numbering control structure rather than a general-purpose master or reference table. The table operates at the intersection of Order Management and Shipping execution: it stores invoice numbering artifacts that are keyed to a specific delivery recorded in WSH_NEW_DELIVERIES, and it cross-references the delivery-level invoice number entity WSH_INVOICE_NUMBERS. In practice, the object supports the assignment and audit of invoice numbers produced when deliveries are fulfilled and subsequently invoiced, and its procedural columns indicate that rows are populated by concurrent programs or server-side logic rather than by direct user entry.
From a modeling perspective, the mined Data Vault classification is satellite-leaning. This is a heuristic suggestion: the table carries descriptive and control attributes attached to a delivery parent, and its foreign keys point outward to delivery and invoice number entities rather than forming an independent hub of business keys. Analysts building a Data Vault or dimensional representation should therefore treat OE_INVOICE_NUMBERS as a satellite subordinate to the WSH_NEW_DELIVERIES hub/link structure, joined through DELIVERY_ID.
Key Information Stored
The physical schema documented for 12.2.2 comprises twelve columns. The most significant are:
- INVOICE_NUMBER_ID — the primary identifier for the row and the documented foreign key reference point into WSH_INVOICE_NUMBERS. This is the surrogate primary key candidate rather than a user-visible business key.
- DELIVERY_ID — the foreign key to WSH_NEW_DELIVERIES, establishing the delivery context that drives invoice number generation. This is the principal business-key candidate, since invoice numbering is documented as delivery-name based.
- INDEX_NUMBER — used to sequence or index invoice numbers within a delivery; supports the "invoice numbers" plural semantics of the table.
- REQUEST_ID — the concurrent request that created or updated the row, enabling traceability of the batch process responsible for number generation.
- PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — identify the concurrent program and the last time it touched the row.
- CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS WHO columns providing user and timestamp audit information.
No unique index columns beyond the primary key are documented in the available metadata, so DELIVERY_ID combined with INDEX_NUMBER is the practical business-key candidate for reconciliation and de-duplication checks.
Common Use Cases and Queries
The dominant use case is tracing which invoice numbers were generated for a given delivery, and which concurrent request produced them. A typical query joins the table to its delivery parent:
- Delivery-to-invoice reconciliation: SELECT oin.invoice_number_id, oin.delivery_id, oin.index_number FROM ont.oe_invoice_numbers oin WHERE oin.delivery_id = :delivery_id;
- Audit of generation batches: filter on REQUEST_ID or PROGRAM_ID to isolate rows produced by a specific concurrent program run and its PROGRAM_UPDATE_DATE window.
- Exception reporting: identify deliveries that have no OE_INVOICE_NUMBERS row (missing invoice number) by outer-joining from WSH_NEW_DELIVERIES.
- Duplicate detection: group by DELIVERY_ID and INDEX_NUMBER to detect collisions in generated numbering.
- Data Vault or OBIEE extraction: use CREATION_DATE and LAST_UPDATE_DATE as delta-detection columns for incremental ETL against the delivery hub.
Related Objects
The following objects are the most significant relationships for this table:
- WSH_NEW_DELIVERIES — referenced through OE_INVOICE_NUMBERS.DELIVERY_ID; the authoritative delivery header and the parent driving invoice number generation.
- WSH_INVOICE_NUMBERS — referenced through OE_INVOICE_NUMBERS.INVOICE_NUMBER_ID; the related invoice numbering entity at the shipping level.
- WSH_DELIVERY_ASSIGNMENTS — links deliveries to order lines, useful for tracing a generated invoice number back to the originating sales order line.
- OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL — the order context reached through delivery assignments for invoice-to-order reporting.
- RA_CUSTOMER_TRX_ALL / AR invoice tables — the downstream receivables records where the resulting invoice is ultimately posted, joined via delivery and order references.
- FND_CONCURRENT_REQUESTS — joined on REQUEST_ID to resolve the program and user that executed invoice number generation.
-
This table is used for generating invoice numbers based on the delivery name.
-
This table is used for generating invoice numbers based on the delivery name.
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - ONT Tables and Views 12.2.2
OM WorkFlow Activity Skip Log.
-
eTRM - ONT Tables and Views 12.1.1
OM WorkFlow Activity Skip Log.
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - ONT Tables and Views 12.2.2
OM WorkFlow Activity Skip Log.
-
eTRM - ONT Tables and Views 12.1.1
OM WorkFlow Activity Skip Log.