Results for “mrp_exception_version”

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

Overview

APPS.MRP_ITEM_EXCEPTION_V is a reporting view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that consolidates planning exceptions raised by Oracle MRP/MPS against inventory items, resources, departments, and production lines. It resolves the raw transactional rows stored in MRP_ITEM_EXCEPTIONS into a human-readable form by joining to lookup tables, item master and planning attributes, organization parameters, project/task descriptions, and WIP line and resource definitions.

The view is exposed under the APPS schema and is typically queried by planning personnel, exception dashboards, and custom integrations that need to surface "items at risk" — for example, items with negative projected available balance, late supply, or resource overloads. Because Oracle publishes it under APPS, it is treated as a supported reference object, though the underlying MRP_ITEM_EXCEPTIONS table remains the authoritative source maintained by the planning engine during a plan run.

Underlying Base Objects

The view is defined over the following documented base objects:

• MRP_ITEM_EXCEPTIONS — the primary fact table holding exception rows (exception type, count, version, organization, project, task).
• MRP_SYSTEM_ITEMS — provides planner code and planning group attributes for the inventory item.
• MTL_ITEM_FLEXFIELDS — supplies the concatenated item number (ITEM_NUMBER).
• MTL_PARAMETERS — returns the organization code.
• MFG_LOOKUPS — resolved three times: once for MRP_EXCEPTION_VERSION, once for MRP_EXCEPTION_CODE_TYPE (exception meaning), and once for resource type meaning.
• BOM_DEPARTMENTS — department code when the exception is department-related.
• BOM_RESOURCES — resource code and resource type for resource-level exceptions.
• WIP_LINES — line code for line-level exceptions.
• MRP_GET_PROJECT — package function calls that translate PROJECT_ID and TASK_ID into descriptive text.

The view body is a UNION ALL: the first branch handles exceptions where RESOURCE_ID = -1 (item-level), and the second branch handles resource-level rows where department, resource, and resource type columns are populated. Both branches filter on MIE.DISPLAY = 1 and join MFG_LOOKUPS for the exception version description.

Key Columns

• EXCEPTION_TYPE and its MEANING — the lookup code and description of the exception (e.g., "Item Below Safety Stock").
• VERSION — the plan version associated with the exception, with NVL(to_char(VERSION), ML.MEANING) providing a fallback description.
• ORGANIZATION_ID / ORGANIZATION_CODE, COMPILE_DESIGNATOR — identify the organization and plan context.
• INVENTORY_ITEM_ID, ITEM_NUMBER, PLANNER_CODE, CATEGORY_ID, PLANNING_GROUP — item identity and planning attributes.
• PROJECT_ID / TASK_ID resolved through MRP_GET_PROJECT.PROJECT and .TASK for project-manufacturing exceptions.
• EXCEPTION_COUNT — the number of occurrences aggregated for the combination.
• DEPARTMENT_ID, RESOURCE_ID, LINE_ID plus DEPARTMENT_CODE, RESOURCE_CODE, LINE_CODE, RESOURCE_TYPE — resource, department, and line context (populated in the resource branch).
• DISPLAY and ROWID — control flags and the physical row identifier of the underlying exception row.

Common Use Cases and Queries

Typical scenarios include exception dashboards for planners, supplier collaboration extracts, and custom BI reports that need exception counts by item or resource. A representative query:

• SELECT item_number, planner_code, organization_code, meaning AS exception, exception_count FROM apps.mrp_item_exception_v WHERE organization_id = :org AND planner_code = :planner ORDER BY exception_count DESC;

To view resource-level exceptions for a department:

• SELECT department_code, resource_code, line_code, meaning, exception_count FROM apps.mrp_item_exception_v WHERE resource_id > 0 AND department_id = :dept;

Because the view performs multiple lookup joins and calls MRP_GET_PROJECT functions, it should be filtered by ORGANIZATION_ID, COMPILE_DESIGNATOR, or PLANNER_CODE whenever possible to avoid full-scan overhead on large exception tables.