Search Results oe_upgrade_log




Overview
Explore in AI Chat

Overview

The OE_UPGRADE_LOG table is owned by the ONT (Order Management) schema and resides in the Oracle E-Business Suite Order Management module. Its documented description is "Upgrade Control Information," identifying it as an EBS-internal control and audit table rather than a transactional or master-data entity. The table records information generated during the upgrade process that migrates and reconciles picking, delivery, and order line data across release boundaries. In EBS 12.1.1 and 12.2.2, the table is documented as VALID and contains 14 columns in the ETRM 12.2.2 physical schema.

From a heuristic Data Vault modeling perspective, the metadata classifies OE_UPGRADE_LOG as standalone. This suggests that, if the table were modeled in a Data Vault architecture, it would most appropriately be treated as a standalone satellite-like structure: it carries descriptive control and reconciliation attributes (quantities, comments, delivery, module, cycle) keyed to order and picking references, without being a pure hub or a link between two business keys. The presence of a foreign key to SO_PICKING_LINES_ALL and multiple order/line identifiers indicates the table functions as a technical reconciliation staging construct rather than a conformed business entity.

Key Information Stored

The documented columns capture the identifiers and control attributes needed to reconcile order line and picking line transformations performed during an upgrade cycle. The most significant columns include:

  • HEADER_ID — Identifier of the order header associated with the upgrade record; a primary join path into order header data.
  • OLD_LINE_ID and OLD_LINE_DETAIL_ID — Pre-upgrade references to the original order line and line detail records.
  • NEW_LINE_ID and NEW_LINE_NUMBER — Post-upgrade identifiers assigned to the transformed order line, enabling old-to-new mapping.
  • PICKING_LINE_ID — Foreign key to SO_PICKING_LINES_ALL, linking the upgrade record to the picking line involved in the transformation.
  • RETURN_QTY_AVAILABLE — Quantity available for return, preserved or recalculated during the upgrade.
  • MTL_SALES_ORDER_ID — Inventory sales order identifier connecting the record to the material transaction side.
  • COMMENTS — Free-text diagnostic or reconciliation notes recorded during the upgrade.
  • DELIVERY, MODULE, and CYCLE_ID — Contextual control attributes identifying the delivery, originating module, and upgrade cycle under which the record was written.
  • CREATION_DATE and LAST_UPDATE_DATE — Standard EBS audit columns showing when the record was inserted and last modified.

No explicit primary key or unique index columns are documented in the provided metadata beyond HEADER_ID, which acts as a likely surrogate or composite candidate key in the context of ONT upgrade control records. The combination of HEADER_ID, OLD_LINE_ID, and CYCLE_ID is a reasonable business-key candidate for uniquely identifying a given upgrade reconciliation row.

Common Use Cases and Queries

The primary use cases for OE_UPGRADE_LOG are post-upgrade verification, reconciliation of order lines before and after migration, and troubleshooting records that failed to transform correctly. Typical reporting includes identifying orders where the old and new line identifiers do not map one-to-one, and validating return quantity balances for picking lines that were modified.

A representative query joining to the referenced picking line table is:

  • SELECT u.HEADER_ID, u.OLD_LINE_ID, u.NEW_LINE_ID, u.RETURN_QTY_AVAILABLE, p.PICKING_LINE_ID FROM ONT.OE_UPGRADE_LOG u JOIN ONT.SO_PICKING_LINES_ALL p ON u.PICKING_LINE_ID = p.PICKING_LINE_ID WHERE u.CYCLE_ID = :cycle_id;
  • Reconciliation pattern: compare counts of HEADER_ID and distinct NEW_LINE_ID grouped by MODULE and CYCLE_ID to detect incomplete transformations.
  • Diagnostic pattern: query COMMENTS and CREATION_DATE for records flagged during a specific upgrade delivery.

Related Objects

The following objects are the most significant related entities based on the documented relationship data and ONT schema context:

  • SO_PICKING_LINES_ALL — Referenced by the documented foreign key OE_UPGRADE_LOG.PICKING_LINE_ID; the picking line involved in the upgrade transformation.
  • OE_ORDER_HEADERS_ALL — Joined via HEADER_ID to resolve order header context.
  • OE_ORDER_LINES_ALL — Joined via OLD_LINE_ID and NEW_LINE_ID to resolve line-level detail.
  • MTL_SALES_ORDERS — Joined via MTL_SALES_ORDER_ID for the inventory sales order reference.
  • OE_ORDER_LINES_ALL line detail extensions — Referenced through OLD_LINE_DETAIL_ID.
  • ONT upgrade driver scripts and concurrent programs — The processes that populate and consume OE_UPGRADE_LOG during migration cycles.