Search Results auto_selected_quantity

Overview

ASO_I_OE_ORDER_LINES_V is an Oracle E-Business Suite view owned by the APPS schema and defined over Oracle Order Management order lines data. It resides in the ASO (Order Capture) product family and carries a VALID status in the ETRM reference for both 12.1.1 and 12.2.2. Its defining characteristic, as documented, is that it exposes all columns from the Oracle Order Management order line tables in a single, flat projection, making the full attribute set of OM order lines available through one object rather than requiring callers to join or widen the base entity themselves.

Although the view sits under the Order Capture module, ETRM explicitly records that it is currently used by Oracle Sales Compensation only. This is an important scoping note: the view is not a general-purpose Order Management inquiry object and should not be treated as a supported public interface for custom development. Its presence in the APPS schema means it is visible to any user with the appropriate grants, but its functional role is confined to the Sales Compensation integration path, where a denormalized line-level feed is required.

Underlying Base Objects

Per the documented metadata, the view references a single base object: OE_ORDER_LINES, accessed through an APPS synonym. In a standard EBS installation, OE_ORDER_LINES is the core transactional table that stores order line records belonging to OE_ORDER_HEADERS, with the two linked by HEADER_ID. The view therefore functions as a presentation layer over that table, projecting its columns without aggregation or significant transformation.

Because the lineage is a one-to-one mapping to OE_ORDER_LINES, row cardinality and data behavior track the base table directly. Any change to the underlying OE_ORDER_LINES structure or to order line data is immediately reflected in the view. The synonym indirection means the view resolves the base table through the APPS-owned synonym rather than a hard-coded schema reference, consistent with standard EBS object design.

Key Columns

• Line and header identifiers: LINE_ID, HEADER_ID, ORG_ID, and LINE_NUMBER uniquely locate each order line and its owning order within an operating unit.
• Quantities and units of measure: ORDERED_QUANTITY, SHIPPING_QUANTITY, SHIPPED_QUANTITY, FULFILLED_QUANTITY, CANCELLED_QUANTITY, PRICING_QUANTITY, and their associated UOM columns describe demand and fulfillment state.
• Dates: REQUEST_DATE, PROMISE_DATE, SCHEDULE_SHIP_DATE, PRICING_DATE, and TAX_DATE support scheduling, pricing, and tax determination.
• Pricing and tax: UNIT_SELLING_PRICE, UNIT_LIST_PRICE, TAX_VALUE, TAX_CODE, TAX_RATE, PRICE_LIST_ID, and TAX_EXEMPT_FLAG provide the monetary context consumed by Sales Compensation crediting.
• Party and location references: SOLD_TO_ORG_ID, SHIP_TO_ORG_ID, INVOICE_TO_ORG_ID, DELIVER_TO_ORG_ID, and their matching contact ID columns identify the sales and fulfillment parties.
• Item and project references: INVENTORY_ITEM_ID, ITEM_REVISION, PROJECT_ID, and TASK_ID tie the line to inventory and project accounting.
• Flexfield attributes: CONTEXT, ATTRIBUTE1 through ATTRIBUTE15, and GLOBAL_ATTRIBUTE_CATEGORY with GLOBAL_ATTRIBUTE1 through GLOBAL_ATTRIBUTE5 expose descriptive flexfield content.

Common Use Cases and Queries

The primary documented consumer is Oracle Sales Compensation, which reads order line values to derive credit and quota performance. Because the view is flat and complete, a typical access pattern filters on the identifiers and dates relevant to a compensation period:

• Retrieve lines for a specific order: SELECT line_id, line_number, ordered_quantity, unit_selling_price FROM aso_i_oe_order_lines_v WHERE header_id = :p_header_id;
• Aggregate sales by organization for a period: SELECT org_id, SUM(ordered_quantity * unit_selling_price) FROM aso_i_oe_order_lines_v WHERE request_date BETWEEN :p_from AND :p_to GROUP BY org_id;
• Inspect flexfield detail for a line: SELECT line_id, context, attribute1, attribute2 FROM aso_i_oe_order_lines_v WHERE line_id = :p_line_id;

Queries should be scoped by ORG_ID or HEADER_ID to avoid full scans of the base order line table, and access should be limited to the Sales Compensation context for which the view is documented. Custom integrations should query OE_ORDER_LINES directly rather than relying on this internally scoped object.