Results for “mrp_exception_type”

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

Overview

APPS.MRP_WORKBENCH_MESSAGES_V is a consolidated reporting view used by the Oracle Materials Requirements Planning (MRP) workbench across Oracle E-Business Suite 12.1.1 and 12.2.2. Its purpose is to present a uniform "message" record set to the MRP workbench and associated inquiry screens, regardless of whether the message originates from an ad hoc form query or from the exception engine. The view achieves this by combining two distinct data streams through a UNION ALL: rows from MRP_FORM_QUERY, which carry user-supplied search criteria from the workbench form, and rows derived from MRP_ITEM_EXCEPTIONS, which carry plan-generated exception messages associated with a specific item, organization, and compile designator.

Because the view normalizes heterogeneous data into a fixed column layout, it functions as a presentation-layer integration point. Downstream workbench logic can consume a single cursor without branching on the source of the message. The inclusion of a literal discriminator column (values 1, 2, and 3 in the documented text) allows the consumer to distinguish form-query rows from the two exception-based branches.

Underlying Base Objects

The view is defined over five documented referenced objects:

• MRP_FORM_QUERY (synonym) — supplies form-driven query rows, including QUERY_ID and positional NUMBER1/NUMBER2/CHAR1 bind values.
• MRP_ITEM_EXCEPTIONS (synonym) — the primary source of exception messages, providing EXCEPTION_TYPE, ORGANIZATION_ID, COMPILE_DESIGNATOR, INVENTORY_ITEM_ID, and DISPLAY.
• MRP_SYSTEM_ITEMS (synonym) — keyed by organization, compile designator, and inventory item, contributing planning attributes such as PLANNER_CODE and ROWID.
• MTL_ITEM_FLEXFIELDS (view) — provides the concatenated ITEM_NUMBER and DESCRIPTION used for display.
• MFG_LOOKUPS (view) — supplies the MEANING for each exception type, joined via LOOKUP_TYPE = 'MRP_EXCEPTION_TYPE'.

This is directly relevant to the searched term mrp_exception_type: the view joins MFG_LOOKUPS on LOOKUP_TYPE = 'MRP_EXCEPTION_TYPE' and LOOKUP_CODE = MIE.EXCEPTION_TYPE, translating numeric exception codes into their human-readable MEANING. Exception type 5 is explicitly excluded in both exception branches, and rows are restricted to DISPLAY = 1.

Key Columns

• QUERY_ID / NUMBER1 / NUMBER2 / CHAR1 / NUMBER3 / NUMBER15 / CHAR8 — positional carrier columns populated for form-query rows.
• EXCEPTION_TYPE (mapped to NUMBER2 in the exception branch) — the numeric code matching MFG_LOOKUPS.LOOKUP_CODE for lookup type MRP_EXCEPTION_TYPE.
• CHAR1 — carries L1.MEANING, the decoded exception description.
• ORGANIZATION_ID, COMPILE_DESIGNATOR, INVENTORY_ITEM_ID — the composite planning key identifying the item within a plan.
• Item display — ITEM_NUMBER concatenated with DESCRIPTION from MTL_ITEM_FLEXFIELDS.
• PLANNER_CODE — the planner responsible for the item.
• DISPLAY — controls whether an exception row surfaces to the workbench.

Common Use Cases and Queries

Typical scenarios include workbench message retrieval, exception reporting, and planner-level triage. A representative query filtered to a single organization and item is:

• SELECT exception_type, char1, organization_id, inventory_item_id, planner_code FROM apps.mrp_workbench_messages_v WHERE organization_id = :org AND inventory_item_id = :item;
• Reporting all decoded exception meanings for a plan: join to MFG_LOOKUPS on LOOKUP_TYPE = 'MRP_EXCEPTION_TYPE' where the decoded column is null.
• Planner workload analysis: GROUP BY planner_code over exception rows to count outstanding messages.
• Distinguishing source rows via the literal discriminator column (1, 2, or 3) to isolate form-query versus exception output.

Because MRP_FORM_QUERY and the synonym-backed base objects are session- and plan-dependent, queries should always constrain ORGANIZATION_ID and COMPILE_DESIGNATOR to avoid cross-plan or cross-organization noise.