Results for “ibe_oe_order_summary_v”

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

Overview

The view IBE_OE_ORDER_SUMMARY_V belongs to the IBE (iStore) product family in Oracle E-Business Suite and provides a curated, security-filtered summary of order header information for use by the iStore application tier. Its principal role is to expose a compact set of order header attributes — order number, order date, customer identity, customer PO reference, and order category — while enforcing multi-org (operating unit) access through the EBS client-info mechanism. Rather than querying OE_ORDER_HEADERS_ALL directly, iStore pages and related reporting components consume this view so that the underlying join logic, org-id predicate, and customer-name resolution are centralized and consistent.

The view is documented as not implemented in the reference database from which the ETRM metadata was extracted, meaning the definition exists in the application object library but the physical view object is absent or disabled in that instance. This is typical of IBE objects that are created conditionally during iStore installation or patching. Where present, the view acts as a read-only reporting and integration surface and contributes no data of its own.

Underlying Base Objects

The ETRM metadata documents no referenced base tables, but the supplied view text clearly shows the definition is constructed over three sources:

• ASO_I_OE_ORDER_HEADERS_V — aliased OH, the order header source that itself wraps the Order Management header tables. The definition pins an index hint, /*+ INDEX (OH OE_ORDER_HEADERS_N2) */, steering the optimizer toward the order-number index.
• HZ_CUST_ACCOUNTS — aliased ACCT, the customer account registry in the Trading Community Architecture, joined on OH.SOLD_TO_ORG_ID = ACCT.CUST_ACCOUNT_ID.
• HZ_PARTIES — aliased CUST, joined on ACCT.PARTY_ID = CUST.PARTY_ID to supply the party (customer) name.

The operating-unit restriction is applied by extracting the first ten characters of USERENV('CLIENT_INFO'), converting to a number, and comparing it — via NVL with a sentinel of -99 — to OH.ORG_ID. When CLIENT_INFO is blank, both sides collapse to the sentinel, so the predicate passes; otherwise it restricts rows to the caller's current org. This mirrors the standard EBS multi-org security pattern and is the reason the view must be queried from an initialized session.

Key Columns

The view exposes the following documented columns:

• HEADER_ID — primary identifier of the order header; the join key to order lines, price adjustments, and workflow activity.
• CREATED_BY — user identifier that created the order, useful for audit and workload analysis.
• REFERENCE_NUMBER — the order's reference/cross-reference value, distinct from the visible order number; often used for external system reconciliation.
• ORDER_NUMBER — the user-facing order number (OH.ORDER_NUMBER).
• ORDERED_DATE — date the order was placed, the primary temporal dimension for trending.
• CUST_ACCOUNT_ID — the sold-to customer account ID, exposed via the SOLD_TO_ORG_ID alias.
• CUSTOMER_NAME — the party name resolved from HZ_PARTIES, presented as CUST.PARTY_NAME.
• CUST_PO_NUMBER — the customer purchase order number supplied on the order.
• ORDER_CATEGORY_CODE — classifies the order, for example as an order versus a return or a mixed category.

Common Use Cases and Queries

The view is principally used by iStore to display a customer's recent order history and by reporting queries that need a lightweight order header feed joined to customer identity. A representative query retrieves recent orders for a given customer account:

• SELECT order_number, ordered_date, customer_name, cust_po_number, order_category_code
• FROM ibe_oe_order_summary_v
• WHERE cust_account_id = :p_cust_account_id
• ORDER BY ordered_date DESC;

Because the org predicate derives from CLIENT_INFO, callers should initialize the session (for example through FND_GLOBAL.APPS_INITIALIZE or an equivalent iStore setup routine) before querying. For cross-customer reporting, aggregate by ORDER_CATEGORY_CODE or order date. Note that the view is header-level only: line, shipment, and price details require joins back to the Order Management tables through HEADER_ID. Given the "not implemented" status in the reference database, confirm object existence with ALL_VIEWS before relying on the view in a target instance.