Search Results source_order_number

Overview

IBE_RETURN_DETAIL_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, registered under FND Design Data as IBE.IBE_RETURN_DETAIL_V. It presents Return Merchandise Authorization (RMA) line-level detail drawn from the Order Management transaction tables, exposing the header, line, item, quantity, and pricing attributes of return orders in a single denormalized structure. The view is categorized as Internal, and the ETRM documentation carries the standard Oracle warning that the object is intended for Oracle internal use only and is not supported for direct customer access except through standard Oracle Applications programs. In practice, the view is consumed by Oracle iStore and related order capture flows for rendering return detail and by reporting queries that need return-line granularity without joining the full set of OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL columns. The presence of ORDER_NUMBER, the user-visible return order number, makes the view particularly useful when a user searches on a visible order identifier rather than an internal surrogate key.

Underlying Base Objects

According to the documented view metadata for 12.2.2, IBE_RETURN_DETAIL_V is defined over the following base objects: MTL_SYSTEM_ITEMS_VL (view) for item master attributes, MTL_UNITS_OF_MEASURE_TL (synonym) for unit of measure translations, OE_LOOKUPS (view) for lookup code meanings, and the OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL synonyms for the transactional header and line records. The view also references the OE_PROFILE package (for profile option values such as operating unit and currency context) and the OE_TOTALS_GRP package (for price and total derivation). Because the view resolves against _ALL tables, it is subject to the operating unit security enforced by the OE profile and by Multi-Org views when accessed by a non-privileged user; the ORG_ID column reflects the operating unit that performed the transaction. Item and UOM descriptions are sourced through the _VL and _TL translation views, so the view returns language-appropriate descriptions based on the session's language environment.

Key Columns

• LINE_ID / HEADER_ID — System-generated identifiers for the return line and its parent return order header.
• ORDER_NUMBER — User-visible number of the return order; this is the column typically matched when a user searches for a return by order number.
• LINE_NUMBER — Sequence of the line within the order, used for ordering and cross-reference to the order line.
• TOP_MODEL_LINE_ID / LINK_TO_LINE_ID / ATO_LINE_ID — Configuration and ATO structure identifiers that tie component lines to their top model and immediate parent.
• ORG_ID — Operating unit that owns the transaction.
• ORDER_CATEGORY_CODE / LINE_CATEGORY_CODE — Classify the order (Order, Mixed, Return) and the individual line (regular order or return).
• TRANSACTIONAL_CURR_CODE — Currency of the order.
• INVENTORY_ITEM_ID / ITEM_NUMBER / ITEM_DESCRIPTION / PRODUCT_DESCRIPTION — Item identity and descriptive text.
• ORDER_QUANTITY_UOM / UOM_NAME — UOM code and its translated name.
• RETURNED_QUANTITY / ORDERED_QUANTITY / SHIPPED_QUANTITY / CANCELLED_QUANTITY — Quantity measures supporting return reconciliation.
• UNIT_LIST_PRICE / UNIT_SELLING_PRICE / EXTENDED_PRICE — List price, actual selling price, and extended amount for the line.

Common Use Cases and Queries

Typical uses include return authorization reporting, RMA line extraction for downstream systems, and reconciliation of returned versus shipped quantities. The following query retrieves return lines for a specific visible order number:

SELECT r.order_number,
       r.line_number,
       r.item_number,
       r.returned_quantity,
       r.uom_name,
       r.unit_selling_price,
       r.extended_price
  FROM apps.ibe_return_detail_v r
 WHERE r.order_number = :p_order_number
   AND r.line_category_code = 'RETURN'
 ORDER BY r.line_number;

For operating-unit-scoped reporting, constrain on ORG_ID and the transactional currency to align results with the user's access profile. Because the view is documented as Internal, direct queries should be treated as diagnostic or reporting exceptions, and production integrations should prefer supported Order Management APIs or the Oracle-provided concurrent programs.