Search Results extended_quantity

Overview

SO_INCLUDED_ITEMS_OEXORRSO_V is an APPS-owned database view within the Oracle Order Entry (OE) module, exposed for the Oracle Order Management (OM) and Bills of Material (BOM) integration layer. In Oracle EBS 12.1.1 and 12.2.2, the view presents a modeled, exploded picture of included (configuration) items on a sales order line. It combines the raw configuration explosion records held in BOM_CONFIG_EXPLOSIONS with descriptive item attributes and derived order-line quantities so that order entry, shipping, and fulfillment logic can evaluate component-level availability, reservations, scheduling, and revenue requirements without repeatedly joining the underlying tables.

The view's most prominent role is as the source of the EXTENDED_QUANTITY value — the searched term — together with related component quantities. Because the view also resolves item descriptions, ATP flags, reservable flags, and schedule status, it is a convenient reporting and integration surface for ATO/PTO (Assemble-to-Order / Pick-to-Order) configurations.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over the following referenced objects:

• BOM_CONFIG_EXPLOSIONS (SYNONYM) — the driving table, aliased EXP; supplies the exploded component rows, extended quantity, plan level, select flags, and line/header identifiers.
• MTL_SYSTEM_ITEMS_VL (VIEW) — aliased MSI; outer-joined on COMPONENT_ITEM_ID and ORGANIZATION_ID to provide item description, reservable type, and ATP flag. When ORGANIZATION_ID is null, the view substitutes the profile value from FND_PROFILE.VALUE('SO_ORGANIZATION_ID').
• BOM_INVENTORY_COMPONENTS (VIEW) — aliased BIC; outer-joined on COMPONENT_SEQUENCE_ID to supply the CHECK_ATP attribute.
• SO_LOOKUPS (SYNONYM) — aliased SOL; outer-joined on LOOKUP_TYPE = 'SCHEDULE STATUS' to translate the schedule status code into a meaning.
• OE_QUERY (PACKAGE) — invoked for II_RESERVED_QUANTITY, II_RELEASED_QUANTITY, and II_SCHEDULE_STATUS_CODE per (LINE_ID, COMPONENT_CODE).
• FND_PROFILE and FND_GLOBAL (PACKAGES) — used for profile value derivation and session context.

Key Columns

The view exposes the ROW_ID plus the full set of explosion and order-context columns. Notable entries include:

• EXTENDED_QUANTITY — the total component quantity for the exploded line, accounting for the configured item's usage and order quantity. This is the primary searched attribute.
• COMPONENT_QUANTITY — the per-unit component quantity from the bill.
• SELECT_QUANTITY and SELECT_FLAG — user-selected optional component quantities and inclusion indicator.
• COMPONENT_ITEM_ID / COMPONENT_SEQUENCE_ID — linkage to the item master and bill component definition.
• TOP_ITEM_ID, TOP_BILL_SEQUENCE_ID, BILL_SEQUENCE_ID, PLAN_LEVEL, SORT_ORDER — structure and hierarchy of the configuration.
• ITEM_DESCRIPTION, PRIMARY_UOM_CODE, ATP_FLAG, RESERVABLE_FLAG, REQUIRED_FOR_REVENUE_FLAG — derived descriptive and control flags.
• RESERVED_QUANTITY, RELEASED_QUANTITY, SCHEDULE_STATUS_CODE, SCHEDULE_STATUS — fulfillment-related values computed via OE_QUERY.
• HEADER_ID, LINE_ID, COMPONENT_CODE, SO_TRANSACTIONS_FLAG — order line context and transaction eligibility.

Common Use Cases and Queries

Typical uses include reporting on configured order lines, validating component availability, and feeding fulfillment workflows. A representative query lists exploded components with their extended quantity:

• SELECT line_id, component_item_id, item_description, extended_quantity, primary_uom_code FROM so_included_items_oexorrso_v WHERE header_id = :p_header_id;
• Filter by RESERVABLE_FLAG = 'Y' to identify reservable components for reservation processing.
• Filter by ATP_FLAG = 'Y' to identify components requiring availability checks.
• Use SCHEDULE_STATUS and RELEASED_QUANTITY to monitor shipment readiness.

Because the view resolves profile and package logic at runtime, it should be queried with the correct operating unit context so that SO_ORGANIZATION_ID and OE_QUERY functions return valid results.