Results for “so_lookups”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.SO_SCHEDULE_DETAILS is a reporting view in the Oracle E-Business Suite Order Management (ONT) schema. It flattens the relationship between order lines in SO_LINES and their associated component or schedule detail records in SO_LINE_DETAILS, exposing a unified result set of order line components, quantities, ratios, and descriptive attributes. The view is defined as a UNION of multiple SELECT statements, each producing a ROW_LEVEL discriminator that distinguishes the parent component rows (ROW_LEVEL = 0) from the released schedule or detail rows (ROW_LEVEL = 1). This design allows downstream reports, concurrent programs, and integration interfaces to retrieve both header-level component definitions and their detailed scheduling breakdowns within a single query.

Within EBS 12.1.1 and 12.2.2, the view is registered under the APPS schema and is referenced by order-management inquiries, shipping and picking reports, and custom extensions that need a consolidated picture of configured items and their components. Because it resolves lookup meanings inline, it eliminates the need for client code to join SO_LOOKUPS separately for status and source-type decoding.

Underlying Base Objects

The view is defined over the following documented objects:

The joins are driven principally by L.LINE_ID = LD.LINE_ID, with organization context enforced through MTL_SYSTEM_ITEMS_VL.ORGANIZATION_ID and MTL_PARAMETERS.ORGANIZATION_ID.

Key Columns

  • LINE_ID — identifier of the parent order line; repeated across component rows.
  • OPTION_LINE_NUMBER — the line number of an option or parent line, blank for top-level lines.
  • PARENT_LINE_ID — reference to the parent configured line, used to reconstruct hierarchy.
  • COMPONENT_CODE — code identifying the component within a configuration.
  • INVENTORY_ITEM_ID — inventory item of the component.
  • QUANTITY — for ROW_LEVEL 0, derived as ORDERED_QUANTITY * COMPONENT_RATIO; for ROW_LEVEL 1, the detail quantity from SO_LINE_DETAILS.
  • RATIO — the COMPONENT_RATIO value.
  • DESCRIPTION — item description from MTL_SYSTEM_ITEMS_VL, or a concatenated organization/schedule/revision/lot string for detail rows.
  • ROW_LEVEL — discriminator (0 = component header row, 1 = schedule detail row).
  • ID_COLUMN — the LINE_ID or LINE_DETAIL_ID depending on row level.
  • RECEIPT_STATUS and SOURCE_TYPE — decoded MEANING values from SO_LOOKUPS.
  • END_ITEM_UNIT_NUMBER — unit number of the configured end item.

Common Use Cases and Queries

Typical uses include configured-item component reporting, schedule-date reporting for unreleased lines, and integration extracts feeding manufacturing or shipping systems.

SELECT LINE_ID,
       OPTION_LINE_NUMBER,
       COMPONENT_CODE,
       INVENTORY_ITEM_ID,
       QUANTITY,
       RATIO,
       DESCRIPTION,
       ROW_LEVEL,
       RECEIPT_STATUS,
       SOURCE_TYPE
  FROM APPS.SO_SCHEDULE_DETAILS
 WHERE LINE_ID = :p_line_id
 ORDER BY ROW_LEVEL, COMPONENT_CODE;

For schedule-level analysis of unreleased detail rows:

SELECT LINE_ID, COMPONENT_CODE, QUANTITY, DESCRIPTION
  FROM APPS.SO_SCHEDULE_DETAILS
 WHERE ROW_LEVEL = 1
   AND RECEIPT_STATUS IS NULL;

Because the view resolves lookup meanings through SO_LOOKUPS, it is frequently the subject of the search term "so_lookups" — users searching for lookup-driven views land here expecting decoded status and source-type columns without writing additional joins.