Search Results flow_status




Overview
Explore in AI Chat

Overview

IBE_ORDER_SUM_V is an APPS-owned database view within the Oracle E-Business Suite iStore (IBE) module. It exposes a denormalized, order-centric summary that joins order header data from the Order Management schema with customer and party information from the Trading Community Architecture (TCA) and status descriptions from Order Management lookups. The view is designed to present a single row per order header, combining commercial attributes of the order with the identity of the sold-to customer and, crucially, the sold-to contact.

Because iStore operates as a self-service ordering front end that must display order summaries and history to web users, this view bridges the transactional order tables and the TCA model that stors customer and contact reference data. Reporting tools, iStore pages, and integration interfaces reference it to avoid repeatedly re-implementing the same multi-table joins. In the EBS 12.1.1 and 12.2.2 releases the view retains a VALID status and is documented as resolving against synonym-backed base objects in the APPS schema.

Underlying Base Objects

The documented base objects for IBE_ORDER_SUM_V are OE_ORDER_HEADERS_ALL (SYNONYM), HZ_CUST_ACCOUNTS (SYNONYM), HZ_CUST_ACCT_SITES_ALL (SYNONYM), HZ_CUST_SITE_USES_ALL (SYNONYM), HZ_PARTIES (SYNONYM), and OE_LOOKUPS (VIEW). The join logic is defined as follows:

  • OE_ORDER_HEADERS_ALL is the driving table, supplying the order header, its identifiers, dates, flags, and both the SOLD_TO_ORG_ID and SOLD_TO_CONTACT_ID.
  • SOLD_TO_ORG_ID is equated to HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID, linking the order to the customer account.
  • HZ_CUST_ACCOUNTS.PARTY_ID is equated to HZ_PARTIES.PARTY_ID, resolving the customer name.
  • OE_LOOKUPS is joined on LOOKUP_CODE = FLOW_STATUS_CODE with LOOKUP_TYPE = 'FLOW_STATUS', providing the human-readable order status meaning.
  • HZ_CUST_SITE_USES_ALL and HZ_CUST_ACCT_SITES_ALL are outer-joined (via INVOICE_TO_ORG_ID = SITE_USE_ID and CUST_ACCT_SITE_ID respectively) so that bill-to account and site identifiers are returned without eliminating order rows that lack a matching site use.

Key Columns

The view projects a mixture of identifiers, dates, flags, and descriptive attributes:

Common Use Cases and Queries

Typical applications include iStore order history displays, order summary reports, and integrations that need customer and contact context alongside order status. The following query retrieves orders for a specific sold-to contact:

  • SELECT ORDER_NUMBER, ORDERED_DATE, CUSTOMER_NAME, SOLD_TO_CONTACT_ID, MEANING FROM APPS.IBE_ORDER_SUM_V WHERE SOLD_TO_CONTACT_ID = :contact_id AND ORG_ID = :org_id ORDER BY ORDERED_DATE DESC;
  • SELECT MEANING AS ORDER_STATUS, COUNT(*) FROM APPS.IBE_ORDER_SUM_V WHERE BOOKED_FLAG = 'Y' GROUP BY MEANING;
  • SELECT ORDER_NUMBER, CUST_PO_NUMBER, CUSTOMER_NAME FROM APPS.IBE_ORDER_SUM_V WHERE CUST_ACCOUNT_ID = :cust_account_id AND OPEN_FLAG = 'Y';

Note that the view does not join the contact table directly; SOLD_TO_CONTACT_ID is carried through from the order header, so it is available for filtering but not for returning contact name or e-mail attributes without an additional join.