Results for “explosion_completion_date”

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

Overview

The APPS.MRP_PLANS_SC_V view is a Master Scheduling/MRP (MRP) reporting and integration object that exposes the plan options associated with MRP, MPS, and DRP schedules in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented description is "MRP or MPS plan options view." The view joins the core plan definition rows in MRP_PLANS to designator, organization, and lookup information, presenting both the "current" plan option set (columns prefixed with CURR_) and the compiled or saved option set (columns without the prefix). This dual projection allows consumers to compare what is currently defined for a plan against the values captured at the last compile, which is materially useful for plan administration and reconciliation. Because the object is a view owned by APPS with a VALID status in the ETRM repository, it is intended to be queried directly by custom reports, concurrent programs, and integration extracts rather than being treated as a base table.

Underlying Base Objects

The view is defined over six documented base objects: MRP_PLANS (synonym), MRP_SCHEDULE_DESIGNATORS (synonym), MRP_DESIGNATORS_VIEW (view), MRP_ORGANIZATIONS_V (view), MTL_PARAMETERS (synonym), and MFG_LOOKUPS (view). MRP_PLANS supplies the primary business columns, including the current and compiled option values, planner batch number, request identifiers, and the descriptive flexfield attribute columns (ATTRIBUTE1 through ATTRIBUTE15, plus ATTRIBUTE_CATEGORY). MRP_SCHEDULE_DESIGNATORS and MRP_DESIGNATORS_VIEW provide the MPS/MRP designator and description, while MRP_ORGANIZATIONS_V and MTL_PARAMETERS resolve the organization identifier and organization code. MFG_LOOKUPS supplies the translated meaning columns joined through lookup types for plan type, schedule type, and organization selection, appearing as multiple aliased joins (L1 through L4) in the view text. The view is therefore a denormalized read model that unifies plan options with their descriptive lookup values.

Key Columns

• CURR_SNAPSHOT_LOCK and SNAPSHOT_LOCK — the current and compiled snapshot lock indicators, governing whether a plan snapshot may be taken or modified.
• CURR_SCHEDULE_DESIGNATOR, SCHEDULE_DESIGNATOR, and CURR_SCHEDULE_TYPE, SCHEDULE_TYPE — designator and lookup meaning pairs identifying the active and saved schedule.
• CURR_PLAN_TYPE, PLAN_TYPE and their lookup meanings — distinguish MRP, MPS, and DRP plans.
• CURR_CUTOFF_DATE, CUTOFF_DATE — the planning horizon cutoff for the current versus compiled option set.
• CURR_PART_INCLUDE_TYPE, CURR_PLANNING_TIME_FENCE_FLAG, CURR_DEMAND_TIME_FENCE_FLAG, CURR_CONSIDER_RESERVATIONS, CURR_PLAN_SAFETY_STOCK, CURR_CONSIDER_WIP, CURR_CONSIDER_PO — current planning behavior flags controlling what the plan considers.
• EXPLOSION_START_DATE, EXPLOSION_COMPLETION_DATE, DATA_START_DATE, DATA_COMPLETION_DATE, PLAN_START_DATE, PLAN_COMPLETION_DATE, CRP_PLAN_START_DATE, CRP_PLAN_COMPLETION_DATE — timestamps for the plan's explosion, data collection, planning, and capacity runs.
• CURRENT_PLANNER_LEVEL, PLANNER_BATCH_NUMBER — planner execution state and batch identity.
• USE_NEW_PLANNER, FULL_PEGGING, CURR_FULL_PEGGING (returned via NVL with default 2), ORGANIZATION_SELECTION (default 1) and its lookup meaning — functional flags with defaulted values.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — concurrency context for the last program that updated the plan.
• Standard WHO columns and ROWID from MRP_PLANS.

Common Use Cases and Queries

Typical uses include plan option reporting, snapshot lock auditing, and extracting the compiled versus current option set for comparison. A reviewer investigating snapshot behavior might run:

• SELECT organization_code, designator, curr_snapshot_lock, snapshot_lock, curr_schedule_type, schedule_type FROM apps.mrp_plans_sc_v WHERE curr_snapshot_lock = 1; — locate plans whose snapshots are currently locked.
• SELECT designator, curr_plan_type, plan_type, curr_full_pegging, full_pegging, use_new_planner FROM apps.mrp_plans_sc_v ORDER BY organization_code, designator; — audit planner option settings across organizations.
• Joining REQUEST_ID to FND_CONCURRENT_REQUESTS to identify the concurrent program that last updated each plan's options.
• Extracting CURR_* versus non-prefixed option columns to detect drift between the active plan definition and the last compiled option set.

Because the view resolves lookup meanings and organization codes, it is well suited as a single-source query for ad hoc reports, Discoverer workbooks, and integration staging tables, eliminating the need to replicate the multiple lookup joins manually.