Search Results booked_date

Overview

OKX_ORDER_HEADERS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKX – Contracts Integration product family. It exposes order header information sourced from Oracle Order Management, presenting a consolidated, flattened projection of the OE_ORDER_HEADERS_ALL base table. The view is valid and available in both Oracle EBS 12.1.1 and 12.2.2 environments, where it is primarily consumed by Contracts Integration processes and by reporting or interface programs that require order header attributes without joining directly to the Order Management transactional tables.

The view carries a synthetic primary key structure: column ID1 returns the header identifier (OH.HEADER_ID) and ID2 returns a literal '#'. Additional descriptive columns such as NAME (ORDER_NUMBER), STATUS (a literal 'A'), DESCRIPTION (NULL), START_DATE_ACTIVE (SYSDATE), and END_DATE_ACTIVE (NULL) are provided to satisfy generic lookup or flexfield-style consumers that expect a standardized descriptive column set. Because it is a view rather than a table, it introduces no independent storage and reflects the current state of the underlying order data at query time.

Underlying Base Objects

The documented referenced base objects for OKX_ORDER_HEADERS_V are:

• OE_ORDER_HEADERS_ALL (accessed via the OE_ORDER_HEADERS_ALL synonym) — the primary transactional table supplying all order header columns.
• ASO_ORDER_INT (PACKAGE) — invoked within the view definition to derive the TOTAL_AMOUNT column through the function ASO_ORDER_INT.GET_ORDER_TOTAL.

The view text performs a single-table selection from OE_ORDER_HEADERS_ALL (aliased OH) with no joins to order lines, customers, or other entities. TOTAL_AMOUNT is computed per row by calling ASO_ORDER_INT.GET_ORDER_TOTAL(OH.HEADER_ID, NULL, 'ALL'), which aggregates the order total across all line types. This package dependency means the view inherits the execution semantics, privileges, and any performance characteristics of the ASO_ORDER_INT package API. Since the view and its dependencies reside in APPS, access is governed by standard APPS schema grants and any custom responsibility-level security applied over the underlying Order Management data.

Key Columns

The view exposes the core operational attributes of an order header. Notable columns include:

• HEADER_ID (ID1) — unique order header identifier; the effective primary key.
• ORDER_NUMBER — the user-visible order number, also mapped to the NAME column.
• ORG_ID — operating unit identifier, essential for multi-org filtering.
• ORDER_TYPE_ID, ORDER_SOURCE_ID, ORDER_CATEGORY_CODE — classify the order transaction.
• SOLD_TO_ORG_ID, SOLD_TO_CONTACT_ID — the selling-party organization and its associated contact; SOLD_TO_CONTACT_ID is the column most relevant to the user's search and identifies the contact at the sold-to customer site.
• SHIP_TO_ORG_ID, INVOICE_TO_ORG_ID, INVOICE_TO_CONTACT_ID, DELIVER_TO_CONTACT_ID — party and contact references across the order lifecycle.
• AGREEMENT_ID, CUST_PO_NUMBER, PRICE_LIST_ID, PAYMENT_TERM_ID — commercial terms and references.
• BOOKED_FLAG, OPEN_FLAG, CANCELLED_FLAG, FLOW_STATUS_CODE — status indicators for order progression.
• ORDERED_DATE, REQUEST_DATE, BOOKED_DATE, PRICING_DATE, CREATION_DATE, EXPIRATION_DATE — key dates for cycle-time and aging analysis.
• TRANSACTIONAL_CURR_CODE, CONVERSION_RATE, CONVERSION_TYPE_CODE, CONVERSION_RATE_DATE — currency and conversion attributes.
• TOTAL_AMOUNT — derived order value returned by ASO_ORDER_INT.GET_ORDER_TOTAL.

Common Use Cases and Queries

Typical scenarios include Contracts Integration reconciliation, order-status reporting, and extracting sold-to contact information for downstream interfaces. The following examples illustrate practical usage.

Retrieve order headers for a specific operating unit:

• SELECT order_number, ordered_date, sold_to_org_id, sold_to_contact_id, total_amount FROM apps.okx_order_headers_v WHERE org_id = :p_org_id;

Locate orders by sold-to contact (directly addressing the searched column):

• SELECT order_number, cust_po_number, booked_flag, flow_status_code FROM apps.okx_order_headers_v WHERE sold_to_contact_id = :p_contact_id;

Summarize booked order value by currency and status:

• SELECT transactional_curr_code, flow_status_code, COUNT(*) order_count, SUM(total_amount) total_value FROM apps.okx_order_headers_v WHERE booked_flag = 'Y' AND org_id = :p_org_id GROUP BY transactional_curr_code, flow_status_code;

Because TOTAL_AMOUNT is computed via the ASO_ORDER_INT package, queries returning this column incur per-row function execution; restricting the result set through filters on ORG_ID, dates, or flags before aggregation is advisable for performance on high-volume environments.