Search Results orig_sys_shipment_ref




Overview
Explore in AI Chat

Overview

The OE_LOTSERIAL_ACKS_V view is a reporting and integration object within the Oracle E-Business Suite Order Management (ONT) module. It resides in the APPS schema and carries a VALID status in ETRM releases 12.1.1 and 12.2.2. The view is defined over the oe_lotserial_acks table and is described by Oracle as being "striped on organization," meaning its structure and content are organized around the multi-org (operating unit) partitioning model that governs Order Management data. In practice, the view presents lot and serial number acknowledgment records associated with order lines, shipments, and their source documents, exposing a denormalized, ready-to-query surface for lot/serial acknowledgment data used in order-to-shipment tracking and external system integration.

Underlying Base Objects

The view is defined over a single documented base object: OE_LOTSERIAL_ACKS, which is referenced through the synonym layer in the APPS schema. The view text is a straightforward projection of the base table's columns with no joins, filters, or aggregation applied, so it returns the same row set as the underlying table. Because the view is "striped on organization," the underlying table participates in the multi-org model, and callers depend on the active organization context (typically set through MO_GLOBAL or a similar mechanism) to scope results to the appropriate operating unit. This design keeps the view lightweight while preserving the organization-level security and partitioning conventions of Order Management.

Key Columns

The view exposes the following principal columns, each mapping directly to a base-table field:

  • ORDER_SOURCE_ID — identifies the source system that originated the acknowledgment record.
  • ORIG_SYS_DOCUMENT_REF, ORIG_SYS_LINE_REF, ORIG_SYS_SHIPMENT_REF, ORIG_SYS_LOT_SERIAL_REF — external system reference keys for the document, line, shipment, and lot/serial record, used for cross-system reconciliation.
  • ACKNOWLEDGMENT_FLAG and BUYER_SELLER_FLAG — status indicators describing the acknowledgment and the trading partner role.
  • CHANGE_SEQUENCE — ordering value for sequencing changes to the record.
  • LOT_NUMBER — the lot identifier for the affected inventory.
  • FROM_SERIAL_NUMBER and TO_SERIAL_NUMBER — define the serial number range covered by the acknowledgment; the user search for "from_serial_number" maps directly to the FROM_SERIAL_NUMBER column, which marks the lower bound of that interval.
  • QUANTITY and QUANTITY2 — the primary and secondary quantities associated with the acknowledgment.
  • CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle descriptive flexfield (DFF) segment columns, enabling extensible, customer-defined attributes.
  • OPERATION_CODE — indicates the operation performed against the lot/serial acknowledgment record.

Common Use Cases and Queries

Because the view mirrors its base table, it is most often used for reconciliation, external integration, and lot/serial tracking reports. A typical query filtering on the searched column might retrieve acknowledgment records for a known serial range:

  • Serial range reconciliation: SELECT ORDER_SOURCE_ID, LOT_NUMBER, FROM_SERIAL_NUMBER, TO_SERIAL_NUMBER, QUANTITY FROM OE_LOTSERIAL_ACKS_V WHERE FROM_SERIAL_NUMBER IS NOT NULL AND ORIG_SYS_DOCUMENT_REF = :p_doc_ref;
  • Lot/serial acknowledgment by shipment: joining ORIG_SYS_SHIPMENT_REF to shipment records to confirm that acknowledged lot/serial ranges match the shipped inventory.
  • Integration feed extraction: pulling CHANGE_SEQUENCE and the ORIG_SYS_* keys to build delta feeds for downstream or external order management systems.
  • Audit queries: inspecting the ATTRIBUTE and CONTEXT flexfield columns alongside OPERATION_CODE to audit changes recorded against specific lot/serial acknowledgments.

Callers should always establish the correct organization context before querying, given the view's organization-striped design.