Results for “program_id”

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

Overview

The OE_HEADERS_INTEROP_115_V view is a documented dictionary object in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, owned by the APPS schema and classified under the ONT (Order Management) product family. Its official status is VALID. Per the ETRM metadata, the object is explicitly annotated as "No longer used."

The view functions as a projection over the Order Management order header entity, exposing a narrow slice of header-level attributes for external consumption. Historically, the "INTEROP" naming convention in the OE schema identified views intended for outbound or inbound interface processing — typically consumed by Order Management Open Interfaces, XML messaging, or adjacent applications such as Advanced Pricing, Shipping, or legacy integrations. The numeric suffix ("115") indicates a versioned interface contract, allowing Oracle to evolve column-level exposure without invalidating prior consumer dependencies.

Although the underlying view text remains intact and compiles as VALID in supported releases, Oracle no longer maintains or recommends this view for new development. Its presence in a 12.2.2 instance is a legacy artifact rather than an active integration point.

Underlying Base Objects

The documented base object is OE_ORDER_HEADERS, referenced through a SYNONYM. This is the authoritative transaction table storing order header records for the Order Management module, keyed by HEADER_ID and linked to operating units via ORG_ID.

The view is defined as a simple column-projection SELECT — a SELECT ... FROM OE_ORDER_HEADERS with no joins, filters, or transformations. This is significant because it carries no referential enrichment: it does not join to OE_ORDER_TYPES, HZ_CUST_ACCOUNTS, or any pricing or shipping tables. All attributes are inherited directly from the single base table.

If the base synonym resolves to a stale or invalidated object in a given environment, the view's VALID status can be misleading — validity reflects compilation only, not runtime data availability.

Key Columns

The exposed columns comprise the standard EBS audit and header identity set:

• HEADER_ID — Primary key of the order header; the join anchor to OE_ORDER_LINES and related entities.
• ORG_ID — Operating unit identifier; drives Multi-Org security (MOAC) filtering.
• ORDER_TYPE_ID — Foreign key to the order transaction type, governing workflow and fulfillment rules.
• ORDER_NUMBER — User-facing order identifier visible to customers and agents.
• CREATION_DATE / CREATED_BY — Row creation audit pair.
• LAST_UPDATE_DATE / LAST_UPDATED_BY / LAST_UPDATE_LOGIN — Modification audit trail.
• PROGRAM_APPLICATION_ID / PROGRAM_ID / PROGRAM_UPDATE_DATE — Concurrent program context that last touched the row.

Common Use Cases and Queries

The view is retained chiefly to satisfy legacy interface consumers. A typical inspection query:

• SELECT HEADER_ID, ORG_ID, ORDER_NUMBER, CREATION_DATE FROM APPS.OE_HEADERS_INTEROP_115_V WHERE ORG_ID = :p_org_id;
• SELECT COUNT(*) FROM APPS.OE_HEADERS_INTEROP_115_V WHERE TRUNC(CREATION_DATE) = TRUNC(SYSDATE);
• SELECT * FROM APPS.OE_HEADERS_INTEROP_115_V WHERE HEADER_ID = 123456;

For new development, Oracle recommends querying OE_ORDER_HEADERS directly, or utilising the supported Order Management public views such as OE_ORDER_HEADERS_V, which include security predicates and fuller attribute coverage. Teams should audit for any residual dependencies before retirement.