Search Results icx_so_lines_view_returns_v




Overview
Explore in AI Chat

Overview

The view ICX_SO_LINES_VIEW_RETURNS_V belongs to the Oracle iProcurement (ICX) product family within Oracle E-Business Suite. The ETRM metadata for release 12.2.2 classifies this object with the description Obsolete and explicitly records its implementation status as Not implemented in this database. This classification is significant: it indicates that the view is a legacy construct retained for historical or upgrade reference purposes rather than an active, queryable database object in current 12.1.1 or 12.2.2 installations. The view was originally designed to expose sales order return line information — quantities, pricing attributes, return reasons, and credit-to-invoice references — for consumption by iProcurement workflows and related self-service purchasing pages. Because it is documented as obsolete, no runtime dependency exists in a standard configuration, and the object typically will not be found in the data dictionary on a fresh installation.

Underlying Base Objects

The documented metadata lists no referenced base objects, consistent with the view's obsolete status. However, the view text preserved in the ETRM excerpt reveals a join structure spanning several core Order Management (ONT) and related tables. The primary aliases SL and SH correspond to the sales order lines and sales order headers tables. The view's definition further references MSI (the master item table, for item descriptions), UOM (unit of measure codes), and AL (a lookup meaning source, used to translate return reason codes). A credit transaction reference is resolved through a table aliased RCT, which supplies TRX_NUMBER for the credit-to-invoice column. Two Oracle Order Management query APIs, OE_QUERY.ITEM_CONC_SEG and OE_QUERY.ACCEPTED_QTY, are invoked directly within the SELECT list, and FND_PROFILE.VALUE_SPECIFIC supplies the operating unit context. The view also joins through aliased return tables (referenced as RCTC and RTA in the canonical definition).

Key Columns

The view exposes a broad column set oriented around return processing. Identification columns include LINE_ID, HEADER_ID, LINE_NUMBER, and ORDER_NUMBER. Quantity logic is expressed through OPEN_QUANTITY, defined as ORDERED_QUANTITY minus CANCELLED_QUANTITY using NVL coalescing, alongside CANCELLED_QUANTITY and ACCEPTED_QUANTITY derived from the OE_QUERY API. Financial data is represented by SELLING_PRICE and CURRENCY_CODE. The RETURN_REASON column carries the decoded lookup meaning rather than the raw code, while CREDIT_TO_INVOICE surfaces the associated receivable transaction number. Item context is provided by INVENTORY_ITEM_ID, ITEM (the concatenated segment value), and ITEM_DESC, the latter defaulting to 'NO DESCRIPTION AVAILABLE' when null. Fifteen PRICING_ATTRIBUTE columns, fifteen generic ATTRIBUTE columns, and a CONTEXT column provide extensible descriptive flexfield flexibility.

Common Use Cases and Queries

In releases where the view remains present, it would be queried to report return line detail for a given order, supporting reconciliation between returns, credits, and inventory receipts. A typical access pattern filters on header or line identifiers, for example:

  • SELECT line_id, header_id, order_number, open_quantity, cancelled_quantity, return_reason, credit_to_invoice FROM icx_so_lines_view_returns_v WHERE order_number = :order_number;
  • SELECT line_number, item, item_desc, selling_price, accepted_quantity FROM icx_so_lines_view_returns_v WHERE header_id = :header_id AND open_quantity > 0;
  • SELECT return_reason, COUNT(*) FROM icx_so_lines_view_returns_v GROUP BY return_reason;

A user searching for "dummy_id" may encounter references to this view in outdated documentation or legacy customization scripts; the term does not correspond to any documented column in this object's definition. Because ICX_SO_LINES_VIEW_RETURNS_V is obsolete and not implemented, any query against it on a 12.1.1 or 12.2.2 instance will return an ORA-00942 error unless a site-specific copy has been manually recreated. Implementers should treat the definition as reference material only and source equivalent return data directly from the Order Management base tables or supported public views.