Search Results sys_yes

Overview

The package body APPS.MRP_VALID_PLAN_DESIG_PKG is a declarative validation utility within the Oracle E-Business Suite manufacturing and planning modules. Its principal responsibility is to resolve a set of user-supplied plan designator flags into the internal numeric codes that Oracle MRP uses to drive plan behavior. The designator flags describe whether a plan is to be exploded, whether an MRP snapshot is required, and which planner restrictions apply. The package converts these human-readable indicators into the canonical numeric test constants that the planning engine expects, while validating that the requested combination is internally consistent.

The package is classified under the ETRM taxonomy as OTHER, reflecting its role as a supporting internal library rather than a public business API. It is owned by APPS and is referenced by one other package, indicating a narrowly scoped but reusable validation helper.

Key Procedures and Functions

The ETRM metadata documents a single procedure, MRP_VALID_PLAN_DESIGNATOR. No other public routines are recorded for this package body, although the unit contains private constant and variable declarations that support this procedure.

• MRP_VALID_PLAN_DESIGNATOR — Validates the plan designator arguments passed by the caller and returns whether the explode, MRP snapshot, planner, and CRP planner tests should be applied. Its logic relies on the bit-flag constants TEST_EXPLODE (1), TEST_MRP_SNAPSHOT (2), TEST_PLANNER (4), and TEST_CRP_PLANNER (16), and on the SYS_YES (1) and SYS_NO (2) codes used to express the resolved result. The procedure accumulates the requested tests into a working counter and then extracts each flag from the highest to the lowest weight, decrementing the counter as each test is satisfied. The documented parameter list is intentionally not restated here; parameter names and purposes should be confirmed against the source header. The procedure also references MRP_PLANS%ROWTYPE for a local plan record and declares exceptions INVALID_ARG and INVALID_PLAN.

The presence of the SYS_YES constant explains why the search term sys_yes resolves to this object: SYS_YES CONSTANT NUMBER := 1; appears at line 20 of the package body and is used to assign the resolved flags for the CRPP planner, planner, snapshot, and explode tests.

Tables Accessed

The only documented table reference is MRP_PLANS, accessed through the APPS synonym. It is used to declare var_plan_rec mrp_plans%ROWTYPE, providing the procedural vocabulary for plan-header attributes used during validation. There is no documented evidence that this package writes to any table; the reference appears to support read-only inspection or validation against the plan designator configuration rather than data manipulation.

Usage Notes

MRP_VALID_PLAN_DESIGNATOR is an internal validation routine. It is not intended for ad-hoc invocation by end users and should not be called directly from custom code unless the flag semantics and return codes are fully understood. It is typically reached through the calling packages or forms that build and launch MRP plans, which supply the plan designator flags and consume the resolved numeric codes. Because the routine validates argument combinations and raises INVALID_ARG or INVALID_PLAN when the inputs are inconsistent, callers must handle those exceptions rather than assume a successful resolution. The package is compiled against the APPS schema and inherits the standard EBS dependency on MRP_PLANS. In 12.1.1 and 12.2.2 the package remains a low-level planning engine helper, and any change to its bit-flag constants or to the SYS_YES/SYS_NO semantics would affect every caller that depends on the designator resolution, so modification requires a full impact review.