Search Results ibe_order_detail_v




Overview
Explore in AI Chat

Overview

IBE_ORDER_DETAIL_V is a reporting view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It resides in the IBE (iStore) product family and exposes line-level detail for sales orders captured or displayed through the iStore storefront. The view consolidates order line attributes, item master descriptive data, pricing and totals, shipment scheduling, and configuration/return indicators into a single flattened result set, allowing iStore pages and downstream reports to render order details without issuing multiple joins against the Oracle Order Management base tables.

The object is documented with status VALID and is treated as a read-only presentation layer. It is not designed for direct DML; all persisted attributes remain in the underlying Order Management and inventory tables. Within Oracle EBS reporting and integration, the view serves as the canonical iStore source for order line inquiries, order confirmation displays, and extract programs that require priced, item-described order lines.

Underlying Base Objects

The documented base objects for the view include OE_ORDER_LINES_ALL (synonym) and OE_ORDER_HEADERS_ALL (synonym) as the primary transactional sources, MTL_SYSTEM_ITEMS_VL (view) and MTL_UNITS_OF_MEASURE_TL (synonym) for item and unit-of-measure descriptive data, CZ_CONFIG_DETAILS_V (view) for configuration detail names, OE_LOOKUPS (view) and OE_TRANSACTION_TYPES_TL (synonym) for lookup and line-type meaning resolution, and several PL/SQL program units: OE_TOTALS_GRP (used to derive order totals), OE_PROFILE (profile option evaluation), CZ_UTILS and FND_PROFILE (utility and profile access).

The join structure links order lines to their parent header, to the item master via inventory item identifiers, and to lookup and configuration sources for code-to-meaning translation. The totals columns are computed through OE_TOTALS_GRP.GET_ORDER_TOTAL rather than being stored, which means query cost is sensitive to the number of lines and the frequency of totals calls in the SELECT list.

Key Columns

Common Use Cases and Queries

Typical usages include iStore order history pages, order confirmation summaries, pricing audits, and return-eligibility checks that rely on LINE_RETURNABLE_FLAG. Because the totals columns invoke OE_TOTALS_GRP, queries are best filtered to a single header or a bounded set of lines.

Example — retrieve order line details with pricing for a specific order:

  • SELECT line_id, line_number, item_number, ordered_quantity, unit_selling_price, extended_price, line_status FROM ibe_order_detail_v WHERE header_id = :p_header_id ORDER BY line_number;

Example — identify returnable lines that have shipped:

  • SELECT line_id, item_number, shipped_quantity, line_retunable_flag FROM ibe_order_detail_v WHERE header_id = :p_header_id AND line_retunable_flag = 'Y' AND shipped_quantity > 0;

Users searching for CONTAINER_ITEM_FLAG should expect the flag to derive from the item master container attribute exposed within the view text; because the documented excerpt truncates the expression, verify the compiled view definition in the target instance (for example via ALL_VIEWS.TEXT) before relying on its exact semantics in custom SQL.