Search Results restrict_subinventories_code




Overview
Explore in AI Chat

Overview

SO_LINE_DETAILS_V is a VALID view owned by the APPS schema in Oracle E-Business Suite, classified under the Order Entry (OE) product family. It exposes the component-level detail records that underpin configured and kits-based order lines, presenting the exploded structure of an order line as a set of shippable, transactable, or revenue-required components. In ETRM 12.2.2 metadata the view is documented over a denominator set of source objects that includes SO_LINE_DETAILS, MTL_SYSTEM_ITEMS_VL, MTL_SYSTEM_ITEMS_KFV, MTL_PARAMETERS, SO_LOOKUPS, and the FND_GLOBAL and FND_PROFILE packages.

The view is primarily used for reporting, integration, and diagnostic purposes rather than as a transactional interface. Because it resolves surrogate identifiers and joins to item and warehouse master data, it is well suited to extract programs that need to report component quantities and scheduling attributes without duplicating the OE schema joins. The user search term "quantity_svrid" maps directly to one of the view's exposed columns, QUANTITY_SVRID, which carries the surrogate identifier associated with the component quantity attribute used by Oracle's attribute-level value resolution.

Underlying Base Objects

The FROM clause of the view is rooted on the SO_LINE_DETAILS synonym, aliased D, which supplies the core component rows including LINE_DETAIL_ID, LINE_ID, INVENTORY_ITEM_ID, COMPONENT_SEQUENCE_ID, COMPONENT_CODE, COMPONENT_RATIO, QUANTITY, and the scheduling and demand classification columns. MTL_SYSTEM_ITEMS_KFV (MTLV) supplies the concatenated ITEM segment value, MTL_SYSTEM_ITEMS_VL (MTLVL) supplies ITEM_DESCRIPTION, and MTL_SYSTEM_ITEMS (MTLT) supplies control attributes such as REVISION_QTY_CONTROL_CODE, LOT_CONTROL_CODE, INVENTORY_ASSET_FLAG, and RESTRICT_SUBINVENTORIES_CODE. MTL_PARAMETERS (MTLP) contributes ORGANIZATION_CODE as the WAREHOUSE column. SO_LOOKUPS is referenced twice (LUP, LUP1) to resolve SCHEDULE_STATUS_CODE and RECEIPT_STATUS_CODE into their MEANING text. FND_GLOBAL and FND_PROFILE support session and profile-dependent resolution logic embedded in the view definition.

Key Columns

Common Use Cases and Queries

Typical uses include configured-item component reporting, kit explosion extracts, shipping and departure planning analysis, and reconciliation of component quantities before pick release. The following example returns the component structure of a given order line with decoded statuses:

SELECT line_id, line_detail_id, item, item_description,
       quantity, unit_code, warehouse,
       component_sequence_id, component_code, component_ratio,
       schedule_status, receipt_status, schedule_date
  FROM apps.so_line_details_v
 WHERE line_id = :p_line_id
 ORDER BY component_sequence_id;

To inspect surrogate identifier values for a component, including the search term quantity_svrid:

SELECT line_detail_id, inventory_item_id, quantity, quantity_svrid,
       warehouse_svrid, demand_class_svrid, date_svrid
  FROM apps.so_line_details_v
 WHERE line_id = :p_line_id;

For shippable component analysis by warehouse:

SELECT warehouse, COUNT(*) components, SUM(quantity) total_qty
  FROM apps.so_line_details_v
 WHERE shippable_flag = 'Y'
 GROUP BY warehouse;