Results for “mrp_parameters_u1”

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

Overview

MRP.MRP_PARAMETERS is the planning-parameters master table for Oracle Master Scheduling/MRP and Advanced Supply Chain Planning in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the scheduling, forecasting, and planning behavior settings applied to a given inventory organization. Any organization that runs master scheduling, MRP, or a related planning activity must have exactly one row in MRP_PARAMETERS. Rows are created and maintained through the Define Planning Parameters form, which writes to the underlying MRP schema objects, and the table is stored in the APPS_TS_TX_DATA tablespace with PCT Free 35.

From a dimensional-modeling perspective, the mined Data Vault classification for this object is hub-leaning. That is a modeling suggestion rather than a physical fact: the single-column unique key on ORGANIZATION_ID and the absence of dependent child columns in the key make MRP_PARAMETERS behave like a business hub whose business key is the organization. Downstream designators and period tables attach to it as dependent satellites or links.

Key Information Stored

The table documents 47 columns. The most operationally significant are the following.

• ORGANIZATION_ID – The unique business key and the column behind the unique index MRP_PARAMETERS_U1. It identifies the inventory organization and is the foreign key to MTL_PARAMETERS.
• DEMAND_TIME_FENCE_FLAG / PLANNING_TIME_FENCE_FLAG – Controls whether demand and planning time fences are respected during the planning run.
• OPERATION_SCHEDULE_TYPE – Determines whether planned order demand is scheduled to the operation that requires it or to the planned order start date.
• REPETITIVE_HORIZON1 / REPETITIVE_HORIZON2 and REPETITIVE_BUCKET_SIZE1/2/3 – Define the repetitive planning horizons and their daily, weekly, and period bucket sizes.
• REPETITIVE_ANCHOR_DATE – The reference date from which repetitive buckets are aligned.
• CONSIDER_WIP / CONSIDER_PO – Flags that include work in process and purchase orders as supply during planning.
• PLAN_SAFETY_STOCK / CONSIDER_RESERVATIONS – Control whether safety stock and material reservations are considered by the plan.
• PART_INCLUDE_TYPE – Indicates whether all parts, master-scheduled parts only, or WIP parts are included.
• DEFAULT_ABC_ASSIGNMENT_GROUP – Foreign key to MTL_ABC_ASSIGNMENT_GROUPS, defining the default ABC compile group.
• PERIOD_TYPE, PLAN_DATE_DEFAULT_TYPE, RESCHED_ASSUMPTION, INCLUDE_REP_SUPPLY_DAYS, INCLUDE_MDS_DAYS – Govern planning bucket granularity, default plan dates, reschedule behavior, and inclusion of repetitive supply and MDS days.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY – Standard WHO audit columns used for change tracking.

Common Use Cases and Queries

MRP_PARAMETERS is read whenever the planning engine initializes a plan, so diagnostic and reporting queries typically join it to MTL_PARAMETERS to resolve organization names. A representative pattern is:

• Comparing planning options across organizations: SELECT p.organization_id, m.organization_code, p.plan_safety_stock, p.consider_wip, p.consider_po FROM mrp.mrp_parameters p, mtl_parameters m WHERE p.organization_id = m.organization_id WHERE p.consider_wip = 1;
• Auditing configuration drift: identifying organizations where time fences or ABC assignment groups differ from the corporate standard.
• Impact analysis before/after upgrade to 12.2.2: verifying that all 47 columns, particularly ATTRIBUTE1–ATTRIBUTE15 and the WHO columns, were preserved and populated.
• Debugging planning output: confirming whether CONSIDER_RESERVATIONS or PLAN_SAFETY_STOCK explains unexpected supply/demand results.

Related Objects

MRP_PARAMETERS is a referenced parent. The most significant dependencies are:

• MTL_PARAMETERS – Parent of ORGANIZATION_ID; supplies organization master data.
• MTL_ABC_ASSIGNMENT_GROUPS – Parent of DEFAULT_ABC_ASSIGNMENT_GROUP.
• MRP_DESIGNATORS.ORGANIZATION_ID – Child table holding designator assignments per organization.
• MRP_FORECAST_DESIGNATORS.ORGANIZATION_ID – Child table holding forecast designator assignments.
• MRP_SCHEDULE_DESIGNATORS.ORGANIZATION_ID – Child table for schedule designators.
• MRP_REPETITIVE_PERIODS.ORGANIZATION_ID – Child table for repetitive planning periods.
• MRP_SALES_ORDER_UPDATES.ORGANIZATION_ID – Child table for sales order update parameters.

Because these child tables inherit ORGANIZATION_ID, MRP_PARAMETERS functions as the hub from which all organization-level planning configuration is derived.