Results for “item_segments”

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

Overview

The APPS.MRP_WORKBENCH_MESSAGES_V view is a consolidated presentation layer used by the Oracle Master Scheduling/MRP (MRP) workbench to surface planning exception messages and related query definitions. It is a UNION ALL view that combines rows from the MRP workbench form query construct with exception-driven rows derived from item exception records and item master information. Its primary role is to feed the MRP/MPS workbench with the textual and numeric context required to display planning exceptions — such as late orders, excess inventory, or overcommitted supply — alongside the item and organization identifiers that drive navigation within the workbench.

Because the workbench is one of the principal interfaces for planners to review and act upon plan output, this view acts as a bridge between normalized transactional tables and the flattened, display-ready result set the workbench expects. It is not an end-user table and should be treated strictly as a read-only reporting and integration object.

Underlying Base Objects

The view is defined over five referenced base objects within the APPS schema. These are MFG_LOOKUPS (a view), MRP_FORM_QUERY (a synonym), MRP_ITEM_EXCEPTIONS (a synonym), MRP_SYSTEM_ITEMS (a synonym), and MTL_ITEM_FLEXFIELDS (a view). Each UNION ALL branch draws from a distinct combination of these objects.

• MRP_FORM_QUERY contributes the first branch, supplying workbench query definition rows with query identifiers and generic numeric and character columns.
• MRP_ITEM_EXCEPTIONS (MIE) is the core exception source, joined to MFG_LOOKUPS (L1) on LOOKUP_TYPE = 'MRP_EXCEPTION_TYPE' to translate the numeric exception code into a human-readable meaning.
• MTL_ITEM_FLEXFIELDS (KFV) supplies the item number and description, concatenated into the ITEM_SEGMENTS column.
• MRP_SYSTEM_ITEMS (MSI) provides the planning organization, compile designator, inventory item identifier, and planner code required for workbench context.

Joins are performed on ORGANIZATION_ID, INVENTORY_ITEM_ID, and COMPILE_DESIGNATOR across the exception, flexfield, and system item objects. Exception type 5 is explicitly excluded and only rows flagged with DISPLAY = 1 are returned, ensuring the workbench presents active, displayable messages.

Key Columns

• ROW_ID — ROWID-derived surrogate used for row identification within the result set.
• QUERY_ID — Identifies the originating workbench form query for MRP_FORM_QUERY rows.
• EXCEPTION_TYPE — Numeric exception code from MRP_ITEM_EXCEPTIONS, sourced from lookup MRP_EXCEPTION_TYPE.
• EXCEPTION_TYPE_TEXT — The lookup meaning text for the exception type; this is the column most commonly searched when filtering messages by description, such as "late order" or "excess".
• NUM_ITEMS / NUM_ORDERS — Counters describing the scope of the message, typically the number of items or orders affected.
• ORGANIZATION_ID, COMPILE_DESIGNATOR, INVENTORY_ITEM_ID — Planning keys that uniquely identify the item and plan context.
• ITEM_SEGMENTS — Concatenation of ITEM_NUMBER and DESCRIPTION for display in the workbench grid.
• DISPLAY_TYPE — Distinguishes row categories (for example, item header versus exception detail).
• PLANNER_CODE — Planner responsible for the item, enabling planner-oriented filtering.
• DISPLAY — Display indicator carried from the exception record.

Common Use Cases and Queries

Typical use cases include building custom workbench reports, extracting exception messages for a given plan or planner, and joining exception output to item attributes for downstream analytics. Because EXCEPTION_TYPE_TEXT is derived from MFG_LOOKUPS, searches against that column effectively filter by exception category.

• Listing all displayable exceptions for an organization:

  SELECT ORGANIZATION_ID, INVENTORY_ITEM_ID, ITEM_SEGMENTS,
         EXCEPTION_TYPE_TEXT, NUM_ORDERS, PLANNER_CODE
  FROM   APPS.MRP_WORKBENCH_MESSAGES_V
  WHERE  ORGANIZATION_ID = :org_id
  AND    EXCEPTION_TYPE IS NOT NULL;

• Filtering by exception description:

  SELECT ITEM_SEGMENTS, EXCEPTION_TYPE_TEXT
  FROM   APPS.MRP_WORKBENCH_MESSAGES_V
  WHERE  UPPER(EXCEPTION_TYPE_TEXT) LIKE '%LATE%';

• Grouping messages by planner to gauge workload:

  SELECT PLANNER_CODE, EXCEPTION_TYPE_TEXT, COUNT(*)
  FROM   APPS.MRP_WORKBENCH_MESSAGES_V
  WHERE  ORGANIZATION_ID = :org_id
  GROUP  BY PLANNER_CODE, EXCEPTION_TYPE_TEXT;

Queries should bind ORGANIZATION_ID and, where possible, COMPILE_DESIGNATOR to limit the volume of rows returned, since the view spans all plans and items visible to the exception tables.