Results for “first_ack_date”

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

Overview

The APPS.OE_CRM_ORDER_HEADERS_V view is a compatibility view provided by Oracle Order Management (ONT) for Customer Relationship Management (CRM) usage only. It resides in the APPS schema with a status of VALID and is shipped as part of Oracle E-Business Suite Release 12.1.1 and 12.2.2. The view presents order header information sourced from the oe_order_headers_all table, exposing a broad column set that spans order identity, sourcing, pricing, party and contact references, tax, freight, audit, descriptive flexfield (DFF) attributes, and status flags.

Because the view is explicitly designated for CRM consumption, it functions as a stable, pre-joined interface for CRM-facing reporting and integration rather than as a general-purpose Order Management access point. Applications and extensions that require order header data in a CRM context can query this view directly, avoiding direct dependency on the underlying order header table and its column layout. The view also plays a role in identifying order provenance, including the SOURCE_DOCUMENT_ID column referenced in the object name context.

Underlying Base Objects

Per the documented ETRM metadata, the view's referenced base object is OE_ORDER_HEADERS, accessed through a synonym in the APPS schema. The view text confirms that it is based on the oe_order_headers_all table. The distinction between OE_ORDER_HEADERS (synonym) and oe_order_headers_all reflects the standard EBS convention where the "_ALL" table physically stores multi-organization rows, and the synonym provides a consistent reference point.

The view is a straightforward selection projection — it does not perform joins to order lines, parties, or lookup tables. Consequently, consumers must join to additional objects (such as OE_ORDER_LINES_ALL, HZ_CUST_ACCOUNTS, or HZ_PARTIES) when line-level or customer detail is required. The inclusion of ORG_ID confirms that the view respects multi-organization data, and queries should be filtered accordingly to honor operating unit (MO) security.

Key Columns

• HEADER_ID — Primary identifier for the order header; the principal join key.
• ORG_ID — Operating unit identifier; required for multi-org data filtering.
• ORDER_NUMBER / ORDER_TYPE_ID / VERSION_NUMBER — Core order identity and type classification.
• ORDER_SOURCE_ID / SOURCE_DOCUMENT_TYPE_ID / ORIG_SYS_DOCUMENT_REF / SOURCE_DOCUMENT_ID — Sourcing and provenance columns identifying the originating system and source document.
• ORDERED_DATE / REQUEST_DATE / PRICING_DATE — Key transactional dates.
• BOOKED_FLAG / OPEN_FLAG / CANCELLED_FLAG — Order lifecycle and status indicators.
• SOLD_TO_ORG_ID / SHIP_TO_ORG_ID / INVOICE_TO_ORG_ID / DELIVER_TO_ORG_ID — Party role identifiers (with corresponding CONTACT_ID columns).
• SALESREP_ID — Associated sales representative.
• ATTRIBUTE1–15 / GLOBAL_ATTRIBUTE1–20 — Descriptive and global DFF segments.
• Audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE) — Standard WHO columns for change tracking.

Common Use Cases and Queries

Typical scenarios include CRM order reporting, source document tracing, and cross-application integration where a CRM module needs order header attributes. To trace orders by source document, the following query demonstrates use of the searched column:

• SELECT header_id, order_number, ordered_date, source_document_id FROM oe_crm_order_headers_v WHERE source_document_id = :p_source_doc_id AND org_id = :p_org_id;
• SELECT header_id, order_number, booked_flag FROM oe_crm_order_headers_v WHERE booked_flag = 'Y' AND ordered_date >= :p_start_date;
• SELECT header_id, order_number, cust_po_number, sold_to_org_id FROM oe_crm_order_headers_v WHERE cust_po_number = :p_po_number;

Because the view lacks joins, filters and lookups must be applied by the consumer. Restricting queries by ORG_ID and leveraging indexed columns such as HEADER_ID and ORDER_NUMBER maintains acceptable performance.