Results for “date_ordered”

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

Overview

The view APPS.OEBV_ORDER_HEADERS is a Business Intelligence System (BIS) view defined in the Oracle E-Business Suite Order Management (ONT) module. Its documented purpose is to expose order header information for consumption by Oracle IT and downstream reporting or integration layers. It is a denormalized, presentation-oriented read-only view rather than a transactional entity, and it exists to simplify access to the core OE_ORDER_HEADERS table by pre-joining lookup descriptions and enforcing a default security predicate.

The view is registered in the ETRM as status VALID with owner APPS, and is present across 12.1.1 and 12.2.2. Because it selects from the base header table with a row-limiting WHERE clause, it is best understood as a filtered projection of order headers rather than a complete mirror of the underlying table. This behavior has practical consequences for reporting completeness that users should understand before building queries against it.

Underlying Base Objects

The view is defined over a single base object, OE_ORDER_HEADERS (referenced through a synonym), aliased internally as HEADER. There are no documented joins to customer, site, or contact tables; foreign-key identifiers such as SOLD_TO_ORG_ID, SHIP_TO_CONTACT_ID, and INVOICE_TO_CONTACT_ID are surfaced as raw ID values and must be resolved by the caller if descriptive attributes are required.

The most significant structural characteristic is the restriction predicate WHERE '_SEC:HEADER.SHIP_FROM_ORG_ID' IS NOT NULL, which applies the multi-org security model to the SHIP_FROM_ORG_ID attribute. This means only rows whose ship-from organization is accessible under the active security context are returned. Several columns are also expressed as lookup-translation expressions using the _LA: convention (for example, _LA:HEADER.SALES_CHANNEL_CODE:OE_LOOKUPS:SALES_CHANNEL:MEANING), which resolves coded values into their displayed meanings at runtime.

Key Columns

The view exposes a broad set of header attributes. Columns that are directly available include:

• Identifiers: HEADER_ID, ORDER_NUMBER, ORDER_TYPE_ID, ORG_ID.
• Customer and party references: SOLD_TO_ORG_ID, SHIP_TO_ORG_ID, INVOICE_TO_ORG_ID, SHIP_FROM_ORG_ID, END_CUSTOMER_ID.
• Contact identifiers: SOLD_TO_CONTACT_ID, SHIP_TO_CONTACT_ID, INVOICE_TO_CONTACT_ID, END_CUSTOMER_CONTACT_ID. The view column list exposes a CUSTOMER_CONTACT_ID entry corresponding to this contact family; this is the field relevant to the search term customer_contact_id.
• Commercial attributes: ORDERED_DATE, CUST_PO_NUMBER, TRANSACTIONAL_CURR_CODE, PAYMENT_TYPE_CODE, PRICE_LIST_ID, AGREEMENT_ID, PAYMENT_TERM_ID, SALESREP_ID.
• Status and flags: FLOW_STATUS_CODE, BOOKED_FLAG, CANCELLED_FLAG, TAX_EXEMPT_FLAG, TAX_EXEMPT_REASON_CODE, TAX_EXEMPT_NUMBER.
• Audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY.
• Lookup-translated columns: _LA:SALES_CHANNEL, _LA:TAX_EXEMPTED, _LA:SHIPMENT_PRIORITY, _LA:FREIGHT_TERMS, _LA:BOOKED_FLAG, _LA:CANCELLED_FLAG, and the IB owner/location attributes.

Common Use Cases and Queries

The view is typically used for header-level reporting, integration extracts, and reconciliation of order status. A common pattern is to filter by date and flow status while returning translated lookup values for presentation:

• Reporting booked versus cancelled orders by currency and sales channel.
• Extracting order headers for interface or data-warehouse loads keyed on HEADER_ID.
• Filtering by contact to locate orders associated with a specific CUSTOMER_CONTACT_ID, then joining back to OE_ORDER_LINES_ALL for line detail.

A representative query joining the view back to the base header table for attributes not projected by the view is shown below:

SELECT v.ORDER_NUMBER, v.CUSTOMER_CONTACT_ID, v.FLOW_STATUS_CODE,
       h.ORDER_CATEGORY_CODE
  FROM APPS.OEBV_ORDER_HEADERS v, APPS.OE_ORDER_HEADERS h
 WHERE v.HEADER_ID = h.HEADER_ID
   AND v.CUSTOMER_CONTACT_ID IS NOT NULL;

Because the view carries the ship-from organization security predicate, queries executed under a restricted organization context may return fewer rows than expected. Analysts should verify their multi-org profile settings and, where comprehensive coverage is required, consider querying OE_ORDER_HEADERS directly instead of relying on the view.