Results for “curr_planning_time_fence_flag”

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

Overview

MRP_PLANS is the MRP schema table that stores the settings and control attributes for a specific master scheduling or material requirements plan. Each row represents a plan definition identified by the combination of a schedule designator and an organization. The table is central to the MRP and MPS planning engines, holding the parameters that govern how a plan explosion is executed, including plan type, scheduling direction, cutoff dates, time fences, reservation and WIP/PO consideration flags, safety stock, pegging levels, and capacity planning options.

The table also carries both "current run" and prior run values for many attributes, allowing the planning engine to record the parameters actually used by the most recent compile while preserving the user-configured values. Columns with the CURR_ prefix reflect the settings underlying the current plan execution, while their counterparts without the prefix represent the configuration entered by the planner. Execution timestamps such as EXPLOSION_START_DATE, EXPLOSION_COMPLETION_DATE, PLAN_START_DATE, and PLAN_COMPLETION_DATE record plan run history.

Applying the heuristic Data Vault classification supplied in the metadata, MRP_PLANS is satellite-leaning: it primarily holds descriptive, non-key attributes attached to a plan business key, with the surrogate primary key MRP_PLANS_PK defined on ORGANIZATION_ID and COMPILE_DESIGNATOR. This classification should be treated as a modeling suggestion rather than a normative statement.

Key Information Stored

The 95 documented columns capture plan identity, configuration, execution control, and audit data. The most functionally significant columns include:

• ORGANIZATION_ID and COMPILE_DESIGNATOR — the composite primary key (MRP_PLANS_PK) that uniquely identifies a plan. The unique index MRP_PLANS_U1 covers COMPILE_DESIGNATOR and ORGANIZATION_ID and is the primary business-key candidate.
• SCHEDULE_DESIGNATOR and CURR_SCHEDULE_DESIGNATOR — the configured schedule and the schedule used in the current compile.
• PLAN_TYPE and CURR_PLAN_TYPE — whether the plan is an MRP, MPS, or DRP plan.
• CUTOFF_DATE and CURR_CUTOFF_DATE — the date that bounds demand included in the plan.
• SCHEDULE_TYPE and CURR_SCHEDULE_TYPE — backward or forward scheduling direction.
• PART_INCLUDE_TYPE and CURR_PART_INCLUDE_TYPE — which items are included in the plan.
• OVERWRITE_OPTION, APPEND_PLANNED_ORDERS, and their CURR_ counterparts — behavior when a new plan compile runs.
• CONSIDER_WIP, CONSIDER_PO, CONSIDER_RESERVATIONS, and CURR_ equivalents — supply and demand inclusion flags.
• PLAN_SAFETY_STOCK / CURR_PLAN_SAFETY_STOCK — safety stock application during planning.
• PLANNING_TIME_FENCE_FLAG and DEMAND_TIME_FENCE_FLAG — time fence enforcement for planning and demand.
• RESERVATION_LEVEL and HARD_PEGGING_LEVEL with CURR_ counterparts — pegging and reservation granularity.
• ASSIGNMENT_SET_ID and CURR_ASSIGNMENT_SET_ID — the assignment set associated with the plan.
• REQUEST_ID and the PROGRAM_ID / PROGRAM_APPLICATION_ID columns — concurrent request context for the plan compile.
• The 15 ATTRIBUTE columns and ATTRIBUTE_CATEGORY — DFF extensibility slots.

Common Use Cases and Queries

Typical uses include identifying all plans defined in an organization, retrieving the parameters used by the last plan compile, and joining plan metadata to results in MRP_FILES or the planner workbench.

Listing plans for an organization:

SELECT compile_designator, schedule_designator, plan_type, description
FROM mrp.mrp_plans
WHERE organization_id = :org_id;

Comparing configured versus current-run settings:

SELECT compile_designator, plan_type, curr_plan_type,
  schedule_type, curr_schedule_type, cutoff_date, curr_cutoff_date
FROM mrp.mrp_plans
WHERE organization_id = :org_id AND compile_designator = :plan;

Joining to plan files for a report:

SELECT p.compile_designator, f.file_id, f.last_update_date
FROM mrp.mrp_plans p, mrp.mrp_files f
WHERE p.organization_id = f.organization_id
  AND p.compile_designator = f.compile_designator;

These patterns support plan inventory, audit of recent compiles, and diagnostic review of time fence or reservation configuration.

Related Objects

MRP_PLANS sits between reference tables it depends on and operational tables that reference it.

• MRP_DESIGNATORS — joined on COMPILE_DESIGNATOR and ORGANIZATION_ID; defines the plan designator.
• MRP_SCHEDULE_DESIGNATORS — joined on SCHEDULE_DESIGNATOR, CURR_SCHEDULE_DESIGNATOR, and COMPILE_DESIGNATOR; defines schedule context.
• MRP_ASSIGNMENT_SETS — joined on ASSIGNMENT_SET_ID; the assignment set used for plan output.
• MRP_FILES — references ORGANIZATION_ID and COMPILE_DESIGNATOR; stores the plan output work files.
• MRP_PLAN_ORGANIZATIONS — references ORGANIZATION_ID and COMPILE_DESIGNATOR; defines the organizations included in a plan.
• MTL_ABC_COMPILE_HEADERS — references ORGANIZATION_ID and MRP_PLAN_NAME; links ABC compiles to a plan.

These relationships make MRP_PLANS the primary configuration anchor for MRP and MPS plan execution and reporting in Oracle EBS 12.1.1 and 12.2.2.