Results for “mrpbv_plan_exception_details”

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

Overview

MRPBV_PLAN_EXCEPTION_DETAILS is a read-only database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the MRP (Master Scheduling/MRP) product family and presents planning exception messages generated during a material requirements planning or master production scheduling run. The view is a retrofitted, backward-compatible interface maintained for reporting and integration consumers that were originally coded against earlier releases of the planning engine.

The view consolidates exception detail rows from the MRP_EXCEPTION_DETAILS table and enriches them with organizational context, lookup meanings, order references, and exception-specific qualifiers. Its most characteristic behavior is the extensive use of DECODE expressions keyed on EXCEPTION_TYPE. Because a single physical table stores heterogeneous exception rows, the view normalizes each exception category into a consistent output shape, projecting the appropriate date, quantity, planner, and source-object values only for the exception types that populate them. The columns are ordered so that date fields correspond to exchangeable exception categories (for example, one slot for types 1, 8, 9, 10, 15, 16, 19, and 23; another for type 12; another for types 13 and 14).

In the context of a search for "utilization_percent", this view does not expose a utilization percentage directly. Utilization-related content typically resides in resource load or capacity reporting, not in the exception detail projection. However, exception messages that relate to resource overload or capacity compression (for example, type 9, which maps to SCHEDULE_COMPRESSION_DAYS) are surfaced here and are frequently used alongside capacity and utilization metrics to explain why a plan was compressed or a resource was over-committed.

Underlying Base Objects

The view is defined over the following documented base objects:

• MRP_EXCEPTION_DETAILS (synonym) — the primary driver table supplying exception rows, dates, quantities, and type codes.
• MRP_RECOMMENDATIONS (synonym) — provides disposition, planning group, order type, schedule compression, and related recommended actions.
• MRP_GROSS_REQUIREMENTS (synonym) — supplies gross requirement context used in the exception detail projection.
• MRP_FULL_PEGGING (synonym) — supports pegging relationships between exception rows and their originating supply or demand.
• MRP_ONHAND_QUANTITIES (synonym) and MRP_INVENTORY_LOTS (synonym) — supply on-hand and lot-level context.
• MTL_PARAMETERS (synonym) — provides the organization code used to identify the planning organization.
• HR_ALL_ORGANIZATION_UNITS (synonym) — resolves the organization identifier to its descriptive name.
• MFG_LOOKUPS (view) — resolves exception type codes to user-facing meanings.
• MRP_GET_ORDER (package) — a PL/SQL package invoked directly inside the view text to resolve sales order and supply order references from disposition identifiers.

The dependency on MRP_GET_ORDER means the view is not purely declarative; it calls packaged functions at query time, which can affect performance when large exception sets are retrieved without filtering.

Key Columns

• COMPILE_DESIGNATOR — identifies the plan (plan name) to which the exception belongs.
• ORGANIZATION_CODE and NAME — the planning organization code and its descriptive organization name.
• Exception date columns — multiple TO_DATE columns populated conditionally by EXCEPTION_TYPE, reflecting the differing date semantics of each exception (for example, receipt date, need-by date, or lot expiration date).
• MEANING — the decoded exception message text from MFG_LOOKUPS.
• Order reference columns — values returned by MRP_GET_ORDER.SALES_ORDER and MRP_GET_ORDER.SUPPLY_ORDER for types such as 13, 14, and 15.
• QUANTITY — the exception quantity, projected except for types 21, 22, and 23.
• SCHEDULE_COMPRESSION_DAYS — populated for exception type 9 and central to compression/capacity diagnostics.
• INVENTORY_LOT_NUMBER — populated for type 12, tying the exception to a specific lot.
• PLANNING_GROUP — sourced from recommendation, requirement, or MRP-dependent values depending on exception type.

Common Use Cases and Queries

Planners and reporting teams query this view to list all exception messages for a given plan and organization, to isolate capacity- or compression-related exceptions, and to join exceptions back to pegging and recommendation detail. A representative query filtering by plan and organization is:

• SELECT compile_designator, organization_code, name, meaning, quantity, schedule_compression_days FROM apps.mrpbv_plan_exception_details WHERE compile_designator = :plan AND organization_code = :org ORDER BY name;
• SELECT compile_designator, organization_code, meaning, schedule_compression_days FROM apps.mrpbv_plan_exception_details WHERE schedule_compression_days IS NOT NULL; — surfaces schedule-compression exceptions, often reviewed with resource utilization data even though utilization_percent is not projected here.
• SELECT meaning, COUNT(*) FROM apps.mrpbv_plan_exception_details WHERE compile_designator = :plan GROUP BY meaning; — exception summary by type for exception dashboards.

Because MRP_GET_ORDER is invoked inline, queries should always filter on COMPILE_DESIGNATOR and ORGANIZATION_CODE to limit the function-call volume. Where utilization or capacity percentage metrics are required, this view should be joined to capacity and resource-load reporting sources rather than expected to supply utilization_percent itself.