Search Results pricing_quantity

Overview

ASO_I_ORDER_LINES_V is a PL/SQL view owned by the APPS schema within the ASO – Order Capture product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to expose "Order lines" in a form consumable by Oracle Order Capture, Oracle iStore, and related order-to-cash reporting and integration layers. The view is documented as VALID and is defined in ETRM under the Order Capture module.

Functionally, the view is a denormalized projection of order line data joined to item master and price list context, so that downstream consumers can read a single row per order line enriched with item description and price list details without repeating the joins. It plays a dual role: it supports Oracle's internal order capture user interfaces and concurrent/reporting queries, and it is frequently referenced in custom extensions and inbound/outbound interfaces that need to read order line attributes such as ordered, shipped, cancelled, fulfilled, and shipping quantities. Because the view includes organization-level security filtering via the OE_PROFILE package and USERENV('CLIENT_INFO'), rows returned are constrained to the operating unit context of the session, which is a critical consideration for any report or integration that must return lines across multiple organizations.

Underlying Base Objects

The documented ETRM metadata lists the following referenced base objects: MTL_SYSTEM_ITEMS_VL (VIEW), OE_ORDER_LINES (SYNONYM, resolving to OE_ORDER_LINES_ALL), OE_PROFILE (PACKAGE), QP_PRICE_LISTS_V (VIEW), and QP_PRICE_LIST_PVT (PACKAGE). The view text confirms a three-way join:

• OE_ORDER_LINES_ALL OL — the driving table, supplying all line-level attributes including LINE_ID, HEADER_ID, quantities, dates, and flags.
• MTL_SYSTEM_ITEMS_VL IT — joined on INVENTORY_ITEM_ID and restricted by ORGANIZATION_ID = OE_PROFILE.VALUE('OE_ORGANIZATION_ID', OL.ORG_ID), providing SEGMENT1 (ITEM_NAME) and DESCRIPTION (ITEM_DESCRIPTION).
• QP_PRICE_LISTS_V PL — outer-joined on PRICE_LIST_ID, supplying PRICE_LIST_ID, NAME, and CURRENCY_CODE. The (+) outer join means lines without a valid price list still return.

The OE_PROFILE package is used both for the item organization join and for the USERENV('CLIENT_INFO') based ORG_ID filter, which enforces multi-org security at the view level rather than relying on the caller.

Key Columns

Columns of particular interest to consumers searching on shipping quantity include:

• SHIPPING_QUANTITY and SHIPPING_QUANTITY_UOM — the quantity shipped or scheduled to ship, with its unit of measure. This is the column most relevant to the "shipping_quantity" search.
• SHIPPED_QUANTITY — quantity actually shipped against the line.
• ORDERED_QUANTITY and ORDER_QUANTITY_UOM — original ordered quantity and UOM.
• FULFILLED_QUANTITY and CANCELLED_QUANTITY — fulfilled and cancelled portions of the line.
• PRICING_QUANTITY / PRICING_QUANTITY_UOM — quantity basis used for pricing.
• Identifiers: LINE_ID, HEADER_ID, LINE_NUMBER, INVENTORY_ITEM_ID, SHIP_FROM_ORG_ID, SHIP_TO_ORG_ID, INVOICE_TO_ORG_ID.
• Dates: SCHEDULE_SHIP_DATE, ACTUAL_SHIPMENT_DATE, SCHEDULE_ARRIVAL_DATE, ACTUAL_ARRIVAL_DATE, PROMISE_DATE, REQUEST_DATE, CREATION_DATE, LAST_UPDATE_DATE.
• Flags and codes: SHIPPABLE_FLAG, CANCELLED_FLAG, OPEN_FLAG, BOOKED_FLAG, SHIPPING_METHOD_CODE, SHIPMENT_PRIORITY_CODE.
• Additional context: ITEM_NAME, ITEM_DESCRIPTION, price list NAME and CURRENCY_CODE.

Common Use Cases and Queries

Typical uses include shipping performance reports, backlog and fulfilment reconciliation, order capture integrations, and iStore line reads. A representative query retrieving shipping and ordered quantities is:

• SELECT line_id, header_id, line_number, item_name, ordered_quantity, shipping_quantity, shipped_quantity, fulfilled_quantity, cancelled_quantity, shipping_quantity_uom, schedule_ship_date FROM aso_i_order_lines_v WHERE shipping_quantity > 0 ORDER BY header_id, line_number;

Because of the USERENV('CLIENT_INFO') security predicate, callers must ensure the correct operating unit context is initialized (for example via FND_GLOBAL or MO_GLOBAL) before querying, or rows for other organizations will be silently excluded. For cross-org reporting, a custom view or direct query against OE_ORDER_LINES_ALL with explicit ORG_ID filtering is usually preferable.