Search Results so_included_items_oexorrso_v




Overview
Explore in AI Chat

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:

Key Columns

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

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.