Results for “repetitive_horizon1”

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

Overview

MRP_PARAMETERS is the master planning-parameters table within the MRP (Master Scheduling/MRP) product schema of Oracle E-Business Suite, present and valid in both release 12.1.1 and 12.2.2. It stores the organization-level configuration that governs how the Oracle planning engine (MRP/MPS/DRP) interprets demand, supply, time fences, scheduling horizons, and snapshot behavior for a given inventory organization. Because planning runs are executed per organization and rely on a consistent set of control flags and numeric horizons, MRP_PARAMETERS acts as the foundational control record that other scheduling objects reference by ORGANIZATION_ID.

Under the heuristic Data Vault classification provided in the metadata, this table is described as hub-leaning. In Data Vault modeling terms, ORGANIZATION_ID functions as the business key of a hub, since it uniquely identifies each planning organization and is the anchor referenced by surrounding dependent tables. The remaining descriptive and flag columns are best modeled as satellite attributes attached to that hub, because they change over time and carry the mutable planning configuration rather than the identity itself.

Key Information Stored

MRP_PARAMETERS is keyed by MRP_PARAMETERS_PK on ORGANIZATION_ID, and it is further constrained by the unique index MRP_PARAMETERS_U1 (ORGANIZATION_ID), making ORGANIZATION_ID both the surrogate/primary key and the sole documented business-key candidate. The table carries 47 documented columns. The most significant planning controls include:

• DEMAND_TIME_FENCE_FLAG and PLANNING_TIME_FENCE_FLAG — flags controlling how the planning engine treats demand and planning within the time fence.
• OPERATION_SCHEDULE_TYPE — defines the scheduling method applied to operations during planning.
• REPETITIVE_HORIZON1, REPETITIVE_HORIZON2, REPETITIVE_BUCKET_SIZE1, REPETITIVE_BUCKET_SIZE2, REPETITIVE_BUCKET_SIZE3, and REPETITIVE_ANCHOR_DATE — govern repetitive planning horizons and bucket granularity.
• CONSIDER_WIP, CONSIDER_PO, CONSIDER_RESERVATIONS, PLAN_SAFETY_STOCK — supply and demand inclusion controls.
• SNAPSHOT_LOCK — controls snapshot locking behavior during planning.
• PART_INCLUDE_TYPE and DEFAULT_ABC_ASSIGNMENT_GROUP — determine which items participate and the default ABC grouping.
• PERIOD_TYPE, RESCHED_ASSUMPTION, PLAN_DATE_DEFAULT_TYPE, INCLUDE_REP_SUPPLY_DAYS, INCLUDE_MDS_DAYS — additional horizon and rescheduling defaults.
• Standard audit columns (LAST_UPDATE_DATE, CREATED_BY, etc.) plus ATTRIBUTE1–ATTRIBUTE15 for flexfield extension.

Common Use Cases and Queries

Typical uses include verifying planning configuration before a planning run, auditing time-fence and supply-inclusion settings across organizations, and joining planning results back to the controlling parameters. A common reporting query retrieves the core configuration for one organization:

• SELECT ORGANIZATION_ID, DEMAND_TIME_FENCE_FLAG, PLANNING_TIME_FENCE_FLAG, CONSIDER_WIP, CONSIDER_PO, PLAN_SAFETY_STOCK FROM MRP_PARAMETERS WHERE ORGANIZATION_ID = :org_id;

Analysts also compare settings across organizations to confirm standardization, and join to MTL_PARAMETERS to correlate inventory-organization attributes with planning controls.

Related Objects

MRP_PARAMETERS references MTL_PARAMETERS via ORGANIZATION_ID and MTL_ABC_ASSIGNMENT_GROUPS via DEFAULT_ABC_ASSIGNMENT_GROUP. It is referenced by MRP_DESIGNATORS, MRP_FORECAST_DESIGNATORS, MRP_REPETITIVE_PERIODS, MRP_SALES_ORDER_UPDATES, and MRP_SCHEDULE_DESIGNATORS, each linking through ORGANIZATION_ID.