Results for “mrpbv_plan_exception_sets”

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

Overview

The APPS.MRPBV_PLAN_EXCEPTION_SETS view is a read-only reporting object within the Oracle E-Business Suite Master Scheduling/MRP (MRP) product family. It exposes planning exception set definitions configured at the inventory organization level, presenting exception thresholds that drive exception messaging during material requirements planning runs. Exception sets determine what qualifies as a reportable plan exception — for example the excess quantity threshold beyond which a supply is flagged as excess, or the repetitive variance percentage that triggers a repetitive manufacturing exception. The view is designated as retrofitted, meaning it was migrated from an earlier form-based or client/server construct into the current release's multi-org, date-effective, and language-aware architecture. Because it is a view rather than a base table, it carries no storage of its own; it is a queryable presentation layer intended for use in reports, BI Publisher data models, and inbound integration extracts where exception configuration must be validated against operational data. In Oracle EBS 12.1.1 and 12.2.2 it is available in the APPS schema with VALID status and should always be queried through the APPS application user, never directly against the underlying synonym targets.

Underlying Base Objects

The view is defined over three documented base objects, each referenced as an APPS synonym: MRP_PLANNING_EXCEPTION_SETS, MTL_PARAMETERS, and HR_ALL_ORGANIZATION_UNITS. The primary driving table is MRP_PLANNING_EXCEPTION_SETS (aliased PL), which holds one row per exception set per organization, including all threshold columns. MTL_PARAMETERS (aliased PA) supplies the inventory organization context through its ORGANIZATION_ID, while HR_ALL_ORGANIZATION_UNITS (aliased AL) provides the organization NAME displayed alongside the organization code. The three are joined on ORGANIZATION_ID, producing a single denormalized result set that combines exception thresholds with human-readable organization identifiers. The final predicate enforces multi-org security via the '_SEC:PL.ORGANIZATION_ID' token, so results are automatically filtered to the organizations the operating user is authorized to access under the current organization security profile. The WITH READ ONLY clause prevents any DML against the view.

Key Columns

• EXCEPTION_SET_NAME — the user-defined name of the exception set, the primary descriptive identifier.
• ORGANIZATION_CODE / ORGANIZATION_NAME — organization identifiers drawn from MTL_PARAMETERS and HR_ALL_ORGANIZATION_UNITS respectively.
• EXCESS_QUANTITY — the threshold quantity above which on-hand or projected supply is reported as an excess exception; directly relevant to the "excess_quantity" search that surfaced this object.
• REPETITIVE_VARIANCE — the tolerance applied when evaluating repetitive schedule variances.
• UNDER_UTILIZED_PERCENT / OVER_UTILIZED_PERCENT — resource utilization boundaries that trigger under- and over-utilization exceptions.
• USER_TIME_FENCE — the planning horizon within which the exception set applies.
• Fourteen lookup-token columns (prefixed "_LA:") map exception type codes such as SHORTAGE_TYPE, EXCESS_TYPE, RESOURCE_SHORTAGE_TYPE, RESOURCE_EXCESS_TYPE, OVERPROMISED_TYPE, and REP_VARIANCE_TYPE to MFG_LOOKUPS values in the MRP_EXCEPTION_TIME_PERIOD lookup type, resolving internal codes to their MEANING.
• Audit columns — ORGANIZATION_ID, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY.

Common Use Cases and Queries

Typical uses include auditing exception configuration across organizations, extracting thresholds for reporting, and joining exception sets to plan names or exception messages. A basic query to inspect excess quantity thresholds by organization is:

SELECT exception_set_name, organization_code, organization_name, excess_quantity, repetitive_variance, user_time_fence FROM apps.mrpbv_plan_exception_sets ORDER BY organization_code, exception_set_name;

To locate only sets that actually enforce an excess-quantity exception:

SELECT organization_code, exception_set_name, excess_quantity FROM apps.mrpbv_plan_exception_sets WHERE excess_quantity IS NOT NULL;

For integration extracts, the audit columns support incremental pulls, though the view lacks a row-level unique key and should be joined to MRP_PLANNING_EXCEPTION_SETS on ORGANIZATION_ID and EXCEPTION_SET_NAME when a stable key is required.