Results for “hard_pegging_level”

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

Overview

MSC_PLAN_PARAMETERS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the MSC (Advanced Supply Chain Planning) product family. Its purpose is to present the effective planning parameters that govern a specific plan run against a specific organization. Rather than exposing a single source table, the view resolves a three-way precedence model: plan-level defaults stored in MSC_PLANS, per-organization runtime overrides stored in MSC_PARAMETERS, and structural attributes of the organization designator held in MSC_DESIGNATORS.

The view is central to any diagnostic or integration scenario where the question is "what settings will the plan actually use for this organization?" — including the column frequently searched as curr_plan_safety_stock. Implemented largely through NVL and DECODE expressions, it returns the override value when one exists, otherwise the plan default, otherwise a hard-coded fallback. Because it is a view and not a table, it carries no data of its own and always reflects current configuration at query time.

Underlying Base Objects

Documented base objects include MSC_PLANS, MSC_PARAMETERS, MSC_DESIGNATORS, MSC_PLANS_OTHER, MSC_PLAN_ORGANIZATIONS, MSC_ASSIGNMENT_SETS, MSC_CATEGORY_SETS, MSC_EXCEPTION_GROUPS, MSC_ITEM_SIMULATION_SETS, MSC_SERVICE_LEVEL_SETS, MSC_SCHEDULING_RULES, and MFG_LOOKUPS, together with the MSC_GET_NAME package.

• MSC_PLANS (M) — supplies the plan definition and defines the alias for plan-level parameter columns.
• MSC_DESIGNATORS (D) — drives the organization/instance scope. DESIGNATOR_TYPE controls the DECODE branches that select alternate defaults.
• MSC_PARAMETERS (P) — provides plan-level defaults used as the second-tier fallback in each NVL chain.
• MSC_ASSIGNMENT_SETS, MSC_CATEGORY_SETS, MSC_EXCEPTION_GROUPS, MSC_ITEM_SIMULATION_SETS, MSC_SERVICE_LEVEL_SETS, MSC_SCHEDULING_RULES — resolve the various named set identifiers referenced by the parameter columns.
• MFG_LOOKUPS — translates code values into user-facing meanings.
• MSC_GET_NAME — package called inline to derive meanings and lookup text (for example, LOOKUP_MEANING('MRP_PLAN_TYPE', …) and ABC_CLASS_ID).

Because the view contains DECODE and NVL logic referencing multiple objects, it is non-trivial to tune; queries should filter aggressively on PLAN_ID and ORGANIZATION_ID to avoid full materialization of the join set.

Key Columns

• CURR_PLAN_SAFETY_STOCK — the operative safety stock parameter, expressed as NVL(M.CURR_PLAN_SAFETY_STOCK, P.PLAN_SAFETY_STOCK). This is the column returned when users search "curr_plan_safety_stock". It reflects the organization-level override if present, otherwise the plan-level setting.
• PLAN_SAFETY_STOCK — the plan-level (non-CURR) safety stock value, returned directly from MSC_PLANS.
• CURR_OVERWRITE_OPTION / CURR_APPEND_PLANNED_ORDERS — control how newly planned orders interact with existing supply; defaults resolved to 1 and to a DECODE on the overwrite option respectively.
• CURR_CUTOFF_DATE — computed from SYSDATE plus daily, weekly, and period cutoff buckets, providing a bucket-aware horizon.
• CURR_PART_INCLUDE_TYPE — DECODE on DESIGNATOR_TYPE selects either the ABC class or the plan/parameter default, governing which items enter the plan.
• CURR_PLANNING_TIME_FENCE_FLAG, CURR_DEMAND_TIME_FENCE_FLAG — fence settings that determine firm versus unconstrained planning regions.
• CURR_CONSIDER_RESERVATIONS, CURR_CONSIDER_WIP, CURR_CONSIDER_PO, CURR_SNAPSHOT_LOCK — supply/demand inclusion switches affecting the netting engine.
• CURR_OPERATION_SCHEDULE_TYPE, CURR_ASSIGNMENT_SET_ID — scheduling and assignment set resolution, again with designator-type-sensitive defaults.
• PLAN_TYPE — decoded to a meaningful MRP plan type via MSC_GET_NAME.

Common Use Cases and Queries

Typical uses include validating configuration before a plan run, reconciling planning output against stated parameters, and exposing parameters to external planning or data-warehouse integrations.

Retrieve the effective safety stock for a given plan and organization:

• SELECT plan_id, organization_id, curr_plan_safety_stock, plan_safety_stock FROM apps.msc_plan_parameters_v WHERE plan_id = :p_plan_id AND organization_id = :p_org_id;

Audit where an override exists versus where the plan default is inherited:

• SELECT organization_id, curr_plan_safety_stock, plan_safety_stock, CASE WHEN curr_plan_safety_stock <> plan_safety_stock THEN 'OVERRIDE' ELSE 'DEFAULT' END AS source FROM apps.msc_plan_parameters_v WHERE plan_id = :p_plan_id;

Inspect the full effective parameter set for an organization:

• SELECT organization_id, curr_part_include_type, curr_planning_time_fence_flag, curr_demand_time_fence_flag, curr_consider_wip, curr_consider_po, curr_plan_safety_stock FROM apps.msc_plan_parameters_v WHERE plan_id = :p_plan_id AND organization_id = :p_org_id;

All such queries should bind PLAN_ID and ORGANIZATION_ID to constrain the row set and avoid excessive evaluation of the underlying DECODE/NVL logic.