Results for “relief_flag”

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

Overview

MRPBV_MASTER_DEMAND_SCHEDS is an APPS-owned read-only view in the Oracle E-Business Suite Master Scheduling/MRP (MRP) product family. It presents the set of master demand schedules defined in MRP_SCHEDULE_DESIGNATORS, filtered to schedule type 1 (master production schedules), joined to organization and lookup reference data. The view is marked "Retrofitted," indicating it was carried forward into the 12.1.1 and 12.2.2 code lines to preserve backward compatibility for reports, concurrent programs, and integrations that reference the legacy object name.

Functionally, the view answers a recurring planning question: for a given organization, which master demand schedules exist, what demand class do they belong to, and is the schedule flagged to relieve the master production schedule? Because it resolves organization identifiers to human-readable codes and names, and decodes the raw lookup code into its display meaning, the view is suitable for direct use in reports, BI Publisher data templates, and custom inquiry forms without additional lookup joins.

Underlying Base Objects

The view is defined over four documented objects:

• MRP_SCHEDULE_DESIGNATORS (synonym) — the driving table, aliased SC. It supplies the schedule designator, description, demand class, MPS relief flag, disable date, organization identifier, and audit columns.
• MTL_PARAMETERS (synonym) — aliased PA, supplying ORGANIZATION_CODE for the owning inventory organization.
• HR_ALL_ORGANIZATION_UNITS (synonym) — aliased AL, supplying the organization NAME, exposed as ORGANIZATION_NAME.
• MFG_LOOKUPS (view) — aliased LKUP, used with LOOKUP_TYPE = 'SYS_YES_NO' to translate the stored MPS_RELIEF code into its meaning.

Joins are established on ORGANIZATION_ID across the schedule designator, MTL_PARAMETERS, and HR_ALL_ORGANIZATION_UNITS, guaranteeing that only schedules whose organization identifier is valid in both organization models are returned. The view restricts rows with SC.SCHEDULE_TYPE = 1 and applies a security predicate on SC.ORGANIZATION_ID, so results are naturally limited to organizations visible to the current responsibility. The definition terminates with WITH READ ONLY, preventing DML through the view.

Key Columns

• ORGANIZATION_CODE — inventory organization code from MTL_PARAMETERS.
• ORGANIZATION_NAME — organization name from HR_ALL_ORGANIZATION_UNITS.
• SCHEDULE_NAME — schedule designator (SCHEDULE_DESIGNATOR).
• SCHEDULE_DESCRIPTION — free-text description of the schedule.
• DEMAND_CLASS — demand class associated with the schedule.
• RELIEF_FLAG — decoded meaning of MPS_RELIEF from MFG_LOOKUPS (SYS_YES_NO), indicating whether the schedule relieves the MPS.
• INACTIVE_DATE — disable date beyond which the schedule is no longer active.
• ORGANIZATION_ID — owning organization identifier.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard audit columns.

It is important to note that the column names in the view differ from the underlying base column names; RELIEF_FLAG is derived from SC.MPS_RELIEF via MFG_LOOKUPS, and SCHEDULE_NAME maps to SCHEDULE_DESIGNATOR.

Common Use Cases and Queries

Typical uses include listing active master demand schedules by organization, auditing which schedules relieve the MPS, and validating schedule setup before running planning or scheduling programs.

All master demand schedules with their relief setting:

• SELECT organization_code, organization_name, schedule_name, relief_flag FROM mrp_master_demand_scheds WHERE relief_flag = 'Yes';

Filter by organization and exclude inactive schedules:

• SELECT schedule_name, schedule_description, demand_class, inactive_date FROM mrp_master_demand_scheds WHERE organization_code = :org AND (inactive_date IS NULL OR inactive_date > SYSDATE);

Because the view enforces organization-level security and carries WITH READ ONLY, it is safe to expose in inquiry-only custom concurrent programs and operational reports. Queries should always filter on ORGANIZATION_CODE or ORGANIZATION_ID to avoid scanning schedules across inaccessible organizations.