Search Results reorder_point_planning

Overview

MRP_PLANNER_PK is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is a core component of the Material Requirements Planning (MRP) and Master Production Scheduling (MPS) engine. Its principal business function is the creation, refresh, and maintenance of planner workbench entries — the transient schedule records that the planning manager consumes when reviewing planned orders, recommendations, and supply/demand pegging.

The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user rather than the definer. This design supports the planning engine's need to operate under the runtime identity of the concurrent request owner while still resolving the APPS synonyms for the underlying planning tables. A header comment dates the source to a 1999 revision (115.2), indicating that the package has remained largely stable across releases and exists primarily to serve the legacy MPS/MRP planner workbench. The package exposes a set of defined constants covering schedule levels, inventory planning codes, demand types, origination types, and order types, which are used by callers to drive consistent classification of planning data.

Key Procedures and Functions

The ETRM metadata documents five procedures within the package:

• MB_DELETE_MS_OUTSIDE_TF — Removes master schedule entries that fall outside the planning time fence for a given organization and compile designation. An overload accepts an additional query identifier so that deletion can be scoped to a specific planner workbench query.
• CREATE_NEW_PLANNER_MPS_ENTRIES — Generates new planner MPS entries for an organization, driven by a compile designation and a schedule designation. This is the primary entry point for populating the planner workbench with fresh master production schedule records.
• CREATE_ORIG_MPS_ENTRIES — Creates original (unmodified) MPS entries for a schedule designation and organization. It establishes the baseline set of schedule rows before planner edits are applied.
• CREATE_MBP_ORIG_MPS_ENTRIES — Creates original MPS entries specifically for the Master Production Scheduling / MRP boundary context, keyed by schedule designation and organization. This corresponds to the create_mbp_orig_mps_entries search term and is the procedure most commonly referenced when diagnosing planner workbench initialization issues.
• Additional related routines — The package header also declares supporting procedures and a block of constants for schedule levels (ORIG_SCHEDULE, UPDATED_SCHEDULE, MRP_SCHEDULE), planning codes (REORDER_POINT_PLANNING through NO_PLANNING), demand types, origination types, and order types.

Tables Accessed

The package reads and writes the following tables through APPS synonyms:

• MRP_SCHEDULE_DATES and MRP_SCHEDULE_DATES_S — the principal repository of schedule date rows that the create procedures insert and the delete procedure removes.
• MRP_SYSTEM_ITEMS and MTL_SYSTEM_ITEMS — supply item attributes, planning flags, and organization-level item definitions that determine which items qualify for schedule entry creation.
• MRP_RECOMMENDATIONS — planner recommendations generated as a byproduct of the planning run.
• MRP_FORM_QUERY — stores the planner workbench query definition used to scope deletions and entry creation.
• BOM_CALENDAR_DATES — provides the manufacturing calendar used to align schedule dates with valid working days.
• MTL_PARAMETERS — organization parameters that establish the planning context for each invocation.

Usage Notes

MRP_PLANNER_PK is invoked internally by the Oracle planning engine rather than being called directly by end users. It is typically executed from within the MRP/MPS concurrent programs — for example, the Planner Workbench and the MPS/MRP planning manager — which call create_mbp_orig_mps_entries and its sibling procedures during the schedule generation phase. The delete procedure is called during regeneration or time-fence boundary processing to purge stale entries before new ones are created. Because the package is documented as referenced by zero other packages, it functions as a leaf-level engine routine rather than a shared utility library. Custom code should avoid calling these procedures directly; the supported path for extending planning behavior is through the documented public APIs and concurrent program interfaces. Any direct invocation risks violating schedule integrity and should be confined to controlled, ETRM-supported scenarios.