Results for “dpw_assigned_flag”

50+ results




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

Overview

OE_UPGRADE_WSH_IFACE is an Order Management (ONT) staging and interface table used during the upgrade of sales order data that originates from or integrates with Oracle Shipping Execution (WSH). Its documented description is "Sales Order upgrade table - Shipping integration," which indicates that the table exists to hold and transform shipping-oriented order line attributes before they are validated and migrated into the target 12.1.1 or 12.2.2 shipping and order management data model. The object resides in the ONT schema and is classified as VALID in the ETRM repository.

Because shipping integration spans picking, packing, departure scheduling, and delivery confirmation, the table acts as a consolidation point for the shipping attributes that must be reconciled against the receiving Shipping Execution tables during an upgrade. The metadata indicates a heuristic Data Vault classification of "standalone," meaning the mined foreign key structure did not reveal a classic hub-and-satellite dependency pattern. As a modeling suggestion, this suggests the table is best treated as a transient interface construct rather than a durable business entity, and its contents should be validated and archived rather than retained as a long-term source of record.

Key Information Stored

The documented 12.2.2 physical schema contains 55 columns. The most operationally significant columns include:

The table also carries standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN), a CONTEXT column, and fifteen generic ATTRIBUTE columns for descriptive flexfield data. The surrogate primary key is LINE_DETAIL_ID; no unique business-key index is documented, so business-key candidates such as the combination of LINE_ID plus PICKING_LINE_ID should be treated as logical rather than enforced keys.

Common Use Cases and Queries

Typical use cases center on upgrade reconciliation and exception reporting. A common pattern joins the interface table to picking and order line tables to identify lines that shipped but did not migrate cleanly:

  • Reconciliation of shipped quantities against picking lines via SO_PICKING_LINES_ALL.
  • Validation of departure assignments via WSH_DEPARTURES for shipped lines lacking a departure.
  • Exception reporting for lines where SHIPPED_QUANTITY exceeds QUANTITY or where INVOICED_QUANTITY is inconsistent.
  • Audit of customer item mapping through MTL_CUSTOMER_ITEMS.

Representative SQL includes a join from OE_UPGRADE_WSH_IFACE to SO_PICKING_LINES_ALL on PICKING_LINE_ID, and to WSH_DEPARTURES on DEPARTURE_ID, to surface orphaned or mismatched records. Because the table is a staging object, queries should generally be run during or immediately after the upgrade window, and output should be archived before the interface rows are purged.

Related Objects

The documented foreign keys point to three reference tables, which form the core dependency set:

  • SO_PICKING_LINES_ALL — joined on OE_UPGRADE_WSH_IFACE.PICKING_LINE_ID.
  • MTL_CUSTOMER_ITEMS — joined on OE_UPGRADE_WSH_IFACE.CUSTOMER_ITEM_ID.
  • WSH_DEPARTURES — joined on OE_UPGRADE_WSH_IFACE.DEPARTURE_ID.

Beyond the documented foreign keys, related order management and shipping entities include OE_ORDER_LINES_ALL (via LINE_ID), MTL_SYSTEM_ITEMS_B (via INVENTORY_ITEM_ID), and the WSH delivery and delivery-detail tables that consume departure data. These objects should be reviewed together when diagnosing upgrade failures, since inconsistencies in any of them can propagate into the interface table.