Search Results extended_quantity

Overview

OE_OPTION_ITEMS_V is a seeded Oracle E-Business Suite view owned by the APPS schema and classified under the ONT (Order Management) product family. Its documented purpose is to serve as a List of Values (LOV) source for option items. In Oracle Order Management, configurable and model items may carry optional components whose availability and hierarchy are defined within the bill of materials. This view exposes those optional components in a flattened, display-ready form suitable for selection in Order Management user interfaces and for downstream reporting.

The view is defined over a join between bill of materials explosion data and item flexfield data, filtered to optional explosion lines that exist beneath a parent level. Because it presents a controlled, order-entry-oriented projection of configuration data, it is commonly referenced by order entry forms, extensibility hooks, and custom reporting that must resolve selectable option items against a specific organization and model structure. The view is documented as VALID in the ETRM repository and is available in both 12.1.1 and 12.2.2 environments.

Underlying Base Objects

The documented base objects referenced by OE_OPTION_ITEMS_V are:

• BOM_EXPLOSIONS (SYNONYM) — the primary driver of the view, supplying optional component rows, bill/component identifiers, quantities, effectivity and disable dates, UOM data, plan level, sort order, and the top bill sequence identifier.
• MTL_ITEM_FLEXFIELDS (VIEW) — supplies item descriptive and identifying attributes, including DESCRIPTION and ITEM_NUMBER, joined by organization and inventory item.
• MTL_SYSTEM_ITEMS_TL (SYNONYM) — the translated item master, underlying the description and item number attributes surfaced through the flexfields join.

The join condition links BOM.EXPLOSION_TYPE = 'OPTIONAL', BOM.PLAN_LEVEL > 0, BOM.ORGANIZATION_ID = MIF.ORGANIZATION_ID, and MIF.INVENTORY_ITEM_ID = BOM.COMPONENT_ITEM_ID. Results are ordered by BOM.SORT_ORDER. The view text applies a NO_EXPAND hint and a filter restricting rows where OPTIONAL = 2 combined with BOM_ITEM_TYPE = 4, which prevents certain inclusion-type components from appearing in the LOV.

Key Columns

The view exposes the following documented columns, several of which are derived or renamed for order-entry presentation:

• ITEM / ITEM_DESCRIPTION — the component item number and its description, sourced from the item flexfields layer.
• PLAN_LEVEL1 — a visual indentation string built from PLAN_LEVEL using RPAD, used to represent hierarchy depth in the LOV.
• CUSTOMER_ORDER_ENABLED_FLAG — indicates whether the option item is orderable by customers.
• COMPONENT_ITEM_ID, COMPONENT_SEQUENCE_ID, COMPONENT_CODE, SORT_ORDER, PLAN_LEVEL — structural identifiers describing the component within the bill explosion.
• COMPONENT_QUANTITY_D — the component quantity converted to character for display purposes.
• EXTENDED_QUANTITY (aliased as ORDERED_QUANTITY) — the extended (rolled-up) quantity for the option item. This column is significant because it renames the source extended quantity to ORDERED_QUANTITY, giving order-entry consumers a quantity measure expressed in ordering terms.
• PRIMARY_UNIT_OF_MEASURE / PRIMARY_UOM_CODE — the unit of measure for the component.
• BOM_ITEM_TYPE — the bill item type, with a DECODE mapping value 1 to 2 for order-entry consistency.
• TOP_BILL_SEQUENCE_ID, EFFECTIVITY_DATE, DISABLE_DATE — the top-level bill reference and the effective and disable date range for the option component.

Common Use Cases and Queries

The principal use case is populating an LOV of selectable optional items for a given model or configuration. Reporting and integration scenarios include extracting optional component structures, validating option availability against effectivity dates, and reconciling ordered option quantities against BOM extended quantities.

A representative query selecting the relevant option items for an organization follows:

• SELECT item, item_description, plan_level1, component_quantity_d, ordered_quantity, primary_uom_code FROM oe_option_items_v WHERE customer_order_enabled_flag = 'Y' ORDER BY sort_order;
• SELECT component_item_id, top_bill_sequence_id, ordered_quantity, effectivity_date, disable_date FROM oe_option_items_v WHERE top_bill_sequence_id = :p_top_bill_id;

The second pattern is common in version and date-effective validation, where the effectivity and disable dates determine whether an optional item remains valid for a given configuration context. Reports frequently use PLAN_LEVEL1 and SORT_ORDER to reproduce the hierarchical ordering presented to users. Because the view is a single-layer projection with no bind parameters, flexible filtering is applied by the calling form, concurrent program, or custom SQL.