Search Results old_line_id




Overview
Explore in AI Chat

Overview

APPS.OE_UPGRADE_LOG_V is a database view in the Oracle E-Business Suite Order Management (OE) module. It presents a filtered subset of the OE_UPGRADE_LOG table, specifically returning only those records where the OLD_LINE_ID column is not null. Its principal purpose is to support the Order Management upgrade and post-upgrade reconciliation process, in which legacy order lines generated under earlier releases must be mapped forward to their new-line equivalents after an upgrade, migration, or patch-driven data conversion.

Because the view isolates rows carrying a historical line identifier, it functions as a diagnostic and audit surface. Rather than exposing the entire upgrade log — much of which concerns records that have no legacy line association — the view narrows the consumer's attention to the intersection of old and new order-line references. This makes it well suited to EBS reporting, upgrade validation, and integration feeds where only cross-referenced line mappings are relevant. As with most APPS-owned views, access is governed by the standard EBS responsibility and menu hierarchy, and the view inherits its privileges from the underlying synonym.

Underlying Base Objects

The view is defined over a single base object, the table OE_UPGRADE_LOG, exposed in the APPS schema through a synonym. The view performs no joins and no aggregation; it is a straightforward projection with a single filter predicate. The documented view text is:

Consequently, row cardinality, column data types, and referential behavior are entirely those of OE_UPGRADE_LOG. Any change to the base table's structure, or to the population logic that maintains it, propagates directly to the view. The synonym indirection means consumers should query the view by its APPS-qualified name rather than addressing the table directly.

Key Columns

  • HEADER_ID — Identifier of the order header to which the upgrade log record belongs; the primary grouping key across the view.
  • OLD_LINE_ID — The legacy or pre-upgrade line identifier. This is the column the view filters on; it is never null in returned rows and is the attribute most associated with the user's search term "old_line_id".
  • OLD_LINE_DETAIL_ID — The legacy line-detail identifier, providing the finer-grained reference within the old line.
  • PICKING_LINE_ID — Reference to the picking line, linking the upgrade record to fulfillment activity.
  • NEW_LINE_ID — The post-upgrade line identifier to which the legacy line was mapped; the core output of the reconciliation.
  • DELIVERY — Delivery attribute associated with the upgrade log record.

Common Use Cases and Queries

The view is typically used during and after an upgrade to confirm that legacy lines have been correctly re-identified. A common validation query joins the view back to order-line tables to verify that each NEW_LINE_ID resolves to a valid line for its HEADER_ID:

  • SELECT header_id, old_line_id, new_line_id FROM oe_upgrade_log_v WHERE header_id = :p_header_id;
  • SELECT header_id, old_line_id, old_line_detail_id, new_line_id FROM oe_upgrade_log_v ORDER BY header_id, old_line_id;
  • SELECT COUNT(*) FROM oe_upgrade_log_v WHERE new_line_id IS NULL;

The third query surfaces records where a legacy line exists but no new line has been assigned, a condition that frequently indicates an incomplete or failed conversion. Analysts also use the view to reconcile picking activity by correlating PICKING_LINE_ID with delivery records, and to drive targeted remediation reports listing all affected HEADER_ID values. Because the view is read-only and filter-bound, it is safe for ad hoc querying and for embedding in upgrade dashboards.