Search Results shipment_schedule_line_id

Overview

ICX_SO_LINES_VIEW_LINES_V is an Oracle E-Business Suite database view belonging to the ICX product family, which underpins Oracle iProcurement and related self-service procurement flows. It exposes order entry line information in a denormalized, presentation-ready form and is catalogued as the "Order Entry Line View." The view consolidates line-level attributes from order management so that iProcurement and dependent purchasing modules can display, validate, and process requisition-to-order and internal sales order line data without joining the underlying order management tables directly.

The object is documented in ETRM for EBS 12.1.1 and 12.2.2. Notably, the metadata records that the view is "Not implemented in this database," meaning it may not exist in every environment or release. Its presence is contingent on the installed applications and the specific product configuration of the instance. Where present, it functions primarily as a read-only reporting and integration surface rather than a transactional object. Its naming (ICX prefix, SO_LINES) signals its role as an iProcurement-facing view over sales order line data.

Underlying Base Objects

The documented metadata lists no explicitly referenced base objects, so the view's lineage must be inferred from its SQL text. The primary base table is the order management line table, aliased in the definition as SL, which supplies the core line records including quantities, dates, prices, and identifiers. This table is joined or correlated with the header table aliased SH, which provides the currency code used for all monetary formatting. The inventory item master, referenced through MSI, contributes the item description and serviceable product flag.

Several helper functions from the OEXVWLIN package are invoked to derive computed values such as schedule status, hold status, shipment number, line number, reserved quantity, and line total. Currency formatting is handled by FND_CURRENCY.SAFE_GET_FORMAT_MASK, and context is obtained from FND_PROFILE.VALUE_SPECIFIC for the SO_ORGANIZATION_ID profile option. Because the base object list is undocumented, the exact table names and join predicates should be confirmed against the deployed view source in the target instance.

Key Columns

• LINE_ID / HEADER_ID — Primary identifiers linking the line to its order header.
• ORDERED_QUANTITY / CANCELLED_QUANTITY / OPEN_QUANTITY — Ordered, cancelled, and net open quantities; OPEN_QUANTITY is computed as ordered minus cancelled.
• DATE_REQUESTED_CURRENT — The current requested date on the line, sourced directly from the base line record. This is the column most relevant to users searching on "date_requested_current."
• SCHEDULE_DATE / PROMISE_DATE / SHIP_SET_NUMBER — Scheduling and delivery attributes.
• SCHEDULE_STATUS / HOLD — Derived status indicators returned by OEXVWLIN package functions.
• UNIT_CODE / SHIPPED_QUANTITY / RESERVED_QUANTITY — Unit of measure and fulfillment quantities.
• SELLING_PRICE / LIST_PRICE / DISCOUNT / EXTENDED_PRICE / LINE_TOTAL — Monetary columns formatted using the header currency mask.
• ITEM / ITEM_DESC / TAX_CODE — Item concatenated segments, description, and tax classification.
• LINE_NUMBER / SHIPMENT_NUMBER / OPTION_NUMBER — Display numbering for lines, shipments, and options.

Common Use Cases and Queries

Typical usage centers on displaying order line detail within iProcurement and on ad hoc reporting of requested dates and quantities. A representative query filtering on the requested date column follows:

SELECT line_id, header_id, item, item_desc, ordered_quantity, open_quantity, date_requested_current, promise_date, schedule_status FROM icx_so_lines_view_lines_v WHERE date_requested_current BETWEEN :start_date AND :end_date ORDER BY date_requested_current;

Other scenarios include reconciling open quantity against shipped quantity, reviewing hold and schedule status for expediting, and validating pricing by comparing list price, selling price, and discount. Because the view relies on package functions and profile values, queries should run under an application user context with the correct SO_ORGANIZATION_ID, and performance should be verified against large order volumes.