Search Results mrp_valid_plan_designator




Overview
Explore in AI Chat

Overview

The APPS.MRP_VALID_PLAN_DESIG_PKG package is a validation utility within the Oracle E-Business Suite manufacturing and planning modules. Its business function is to determine whether a given plan designator is valid, and to establish the processing context under which that plan designator may subsequently be used. In the Oracle MRP/MPS architecture, a "plan designator" is the short textual identifier that names a plan defined in the MRP_PLANS table. Before a plan can be exploded, snapshotted, or assigned to a planner or capacity (CRP) planner, the application must confirm that the designator exists, belongs to the correct operating unit, and is compatible with the requested processing mode. The package provides a single, centralized entry point for that verification, ensuring that concurrent programs, forms, and other interfaces apply consistent validation rules rather than duplicating the logic. The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user, so the effective data access is governed by the caller's schema grants and the APPS synonyms at runtime. The ETRM metadata classifies it as "OTHER" and confirms it references one table, MRP_PLANS, and that it is referenced by one other package.

Key Procedures and Functions

The package exposes exactly one documented procedure:

  • mrp_valid_plan_designator — The sole procedure in the package's specification. Its purpose is to validate a plan designator supplied by the caller and to carry out the checks required to confirm the plan is usable in the indicated context. The argument list captures a compile/plan designator along with organization and mode indicators, including an exploder flag, a snapshot flag, a planner flag, and a capacity planner flag. These parameters indicate that validation is not limited to the mere existence of the designator; the procedure also assesses whether the plan is appropriate for explosion, for snapshot generation, or for association with a material planner or a CRP planner. The procedure does not return an explicit value in the specification shown; validation outcomes are therefore communicated through the procedure's internal logic (for example, by raising an exception or by leaving status to be interrogated by the calling code). The header comment identifies the source as MRPPVPDS.pls with version 115.0, dated 99/07/16, indicating the code lineage predates Release 12 and has been carried forward into the 12.1.1 and 12.2.2 code lines.

Because the specification is minimal, callers should treat this procedure as a gatekeeper that must be invoked before downstream plan processing; no other public functions or overloads are documented.

Tables Accessed

The only documented base table referenced by this package (through APPS synonyms) is:

  • MRP_PLANS — The master table of planning definitions, holding the plan designator, associated organization, plan type, and planner-related attributes. The package reads this table to confirm that the supplied designator corresponds to a defined plan and that the plan's attributes are consistent with the exploder, snapshot, planner, and CRP planner flags passed in. No inserts, updates, or deletes are implied by the metadata; the package's role is read-only validation of plan metadata.

Any additional tables required for full planner or CRP validation are not identified in the ETRM excerpt and should not be assumed.

Usage Notes

This package is typically invoked indirectly rather than called directly by end users. Typical invocation points include:

  • Oracle planning forms and concurrent programs (for example, the MRP/MPS plan execution, plan explosion, and snapshot workflows) that must confirm a plan designator before launching a run.
  • Other PL/SQL packages: the ETRM metadata records that this package is referenced by one other package, meaning an existing application package delegates its plan-designator validation to this routine. Custom code should follow the same pattern rather than reimplementing the check.
  • Custom concurrent programs or interface routines that accept a plan designator as a parameter and need to validate it against MRP_PLANS before proceeding.

Considerations for extender and customization work: because the package is AUTHID CURRENT_USER, the invoking database user must hold appropriate privileges on the underlying objects (normally satisfied by operating as APPS or through APPS synonym grants). Callers should also be aware of the legacy origin of the code — the dated header and the "porting ship" comment reflect its migration history — and should therefore revalidate behavior after Release 12.2 upgrades before relying on edge-case outcomes. No javadoc or inline documentation beyond the specification header is available, so the precise validation rules should be confirmed by direct inspection of the package body in the target instance.