Search Results pick_release_status

Overview

APPS.SO_LINES_CURRENT_DEMAND_V is a supplementary Oracle EBS view owned by the APPS schema and registered under FND Design Data as OE.SO_LINES_CURRENT_DEMAND_V. It exposes a flattened, form-oriented projection of order line demand data drawn from the Order Management (OE) entity set. In Oracle EBS 12.1.1 and 12.2.2 the view carries a status of VALID and is classified as a supplementary view intended to simplify Oracle Forms coding. Oracle's published guidance explicitly warns that this view is not a supported query or data-manipulation interface; its definition may change substantially between minor or major releases and should not be treated as a stable public API.

Functionally, the view presents current demand at the sales order line and shipment level. It is closely associated with the "demand stream" concept in Order Management, which distinguishes independent demand from dependent demand (for example, components of an ATO configuration or a model's option lines). Because the column set includes DEMAND_STREAM_ID, ORDERED_QUANTITY, CANCELLED_QUANTITY, SHIPPED_QUANTITY, INVOICED_QUANTITY, PICK_RELEASED_QUANTITY, and OPEN_BACKORDERED_QUANTITY, the view is oriented toward reporting the current fulfillment state of each line rather than toward transactional maintenance. Its primary consumers are Oracle Forms blocks and, in a secondary sense, custom reports or interfaces that require a consolidated line-level demand snapshot without joining the underlying Order Management tables directly.

Underlying Base Objects

Per the documented metadata, APPS.SO_LINES_CURRENT_DEMAND_V references the following base objects: OE_QUERY (PACKAGE), SO_HEADERS (VIEW), SO_LINES (VIEW), and SO_ORDER_TYPES (SYNONYM). The presence of OE_QUERY in the dependency list is significant: it indicates that the view's logic is at least partially supplied by the Order Management query package, which is the standard mechanism used by Oracle to build the runtime query text that populates sales order forms and their associated blocks. The view therefore sits on top of the same abstraction layer used by the Order Management application itself, rather than on raw base tables.

SO_HEADERS and SO_LINES are the canonical header and line views in Order Management and supply the order number, header identifier, line identifier, line number, shipment number, item, and quantity attributes. SO_ORDER_TYPES, resolved through an APPS synonym, contributes the order type name and order type identifier. Because the view is defined against these higher-level objects rather than directly against OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL, its column semantics inherit the security, multi-org, and logical-model behavior of the Order Management views at the time of the release in which it was compiled.

Key Columns

The view exposes twenty-nine columns. The identifying columns are ORDER_NUMBER, ORDER_TYPE_ID, ORDER_TYPE_NAME, HEADER_ID, LINE_ID, LINE_NUMBER, SHIPMENT_NUMBER, and OPTION_NUMBER. Customer context is provided by CUSTOMER_ID, while ORIGINAL_SYSTEM_REFERENCE and ORIGINAL_SYSTEM_LINE_REFERENCE support external or legacy system cross-referencing.

DEMAND_STREAM_ID is the column most directly relevant to the search that surfaced this view. It identifies the demand stream to which the line's demand belongs, allowing independent and dependent demand to be distinguished within a single result set. DATE_REQUESTED_CURRENT provides the current requested ship or schedule date. PARENT_LINE_ID and ATO_LINE_ID reflect the configuration hierarchy for model and kit structures, linking option or component lines back to their parent.

Item identification is handled by INVENTORY_ITEM_ID and ITEM_TYPE_CODE. Status and control flags include OPEN_FLAG, ATO_FLAG, PICK_RELEASE_STATUS, SHIP_CONFIRM_STATUS, MFG_RELEASE_STATUS, and SERVICE_INTERFACE_STATUS. The quantity columns — ORDERED_QUANTITY, CANCELLED_QUANTITY, SHIPPED_QUANTITY, INVOICED_QUANTITY, PICK_RELEASED_QUANTITY, and OPEN_BACKORDERED_QUANTITY — permit line-level fulfillment analysis without additional aggregation.

Common Use Cases and Queries

Typical usage is diagnostic or reporting-oriented: locating open demand by demand stream, reconciling shipped and invoiced quantities against ordered quantities, or identifying lines awaiting pick release, manufacturing release, or service interface processing.

The documented query template is:

• SELECT ORDER_NUMBER, ORDER_TYPE_ID, CUSTOMER_ID, ORIGINAL_SYSTEM_REFERENCE, ORDER_TYPE_NAME, LINE_ID, LINE_NUMBER, SHIPMENT_NUMBER, OPTION_NUMBER, ORIGINAL_SYSTEM_LINE_REFERENCE, HEADER_ID, DEMAND_STREAM_ID, DATE_REQUESTED_CURRENT, PARENT_LINE_ID, ATO_LINE_ID, INVENTORY_ITEM_ID, ITEM_TYPE_CODE, OPEN_FLAG, ATO_FLAG, PICK_RELEASE_STATUS, SHIP_CONFIRM_STATUS, MFG_RELEASE_STATUS, SERVICE_INTERFACE_STATUS, ORDERED_QUANTITY, CANCELLED_QUANTITY, SHIPPED_QUANTITY, INVOICED_QUANTITY, PICK_RELEASED_QUANTITY, OPEN_BACKORDERED_QUANTITY FROM APPS.SO_LINES_CURRENT_DEMAND_V;
• Filter by DEMAND_STREAM_ID to isolate a specific demand stream for investigation.
• Filter by OPEN_FLAG = 'Y' to restrict results to open lines.
• Compare ORDERED_QUANTITY against SHIPPED_QUANTITY or OPEN_BACKORDERED_QUANTITY to assess fulfillment gaps.

Given Oracle's explicit warning that this supplementary view may change dramatically between releases, any integration or custom report built on it should be treated as version-specific and revalidated when upgrading between 12.1.1 and 12.2.2.