Search Results mrp_cutoff_date_offset

Overview

MRP_LAUNCH_PLAN_PK is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It encapsulates the server-side logic used to launch an Oracle Master Scheduling/MRP or Advanced Supply Chain Planning plan that has been previously compiled but not yet released for execution. Launching a plan transitions it from a compiled designator state into an active supply plan, sets the plan horizon and cutoff dates, and submits the concurrent requests that explode the bill of materials, capture the snapshot, run the planner, and relieve master production schedule demand.

The package belongs to the wider MRP planning engine architecture and is referenced by one other package within the ETRM repository. Its API classification is documented as OTHER, meaning it is not published as a formally supported public API but is invoked internally by the planning infrastructure.

Key Procedures and Functions

• MRP_LAUNCH_PLAN — The primary entry point for launching a plan. It accepts the organization identifier, compile designator, launch-snapshot flag, launch-planner flag, anchor date, and an optional plan horizon argument. Internally it resolves the plan horizon by reading the MRP_CUTOFF_DATE_OFFSET profile option when no horizon is supplied, computes the next valid work day through MRP_CALENDAR.NEXT_WORK_DAY, and updates the MRP_PLANS row with the new cutoff date while clearing the plan and data completion dates. It then submits the downstream concurrent programs (exploder, snapshot, planner, MPS relief, and optional auto-release) and returns the standard concurrent-program OUT parameters errbuf and retcode.
• GET_CRP_STATUS — Returns capacity requirements planning status information for the plan being processed, allowing the launcher to determine whether capacity planning has completed before proceeding. This supports sequencing decisions when the plan is launched from a concurrent manager chain.

Of particular relevance to the search term g_mrp_debug, both the procedure and the package body declare a package-level variable G_MRP_DEBUG VARCHAR2(1). It is populated at the start of MRP_LAUNCH_PLAN by FND_PROFILE.VALUE('MRP_DEBUG'). When the returned value equals 'Y', diagnostic messages are written through MRP_UTIL.MRP_DEBUG, such as the "About to Launch Plan" trace. This pattern allows a DBA or implementer to enable verbose tracing of the launch sequence by setting the MRP_DEBUG profile option at the site or user level without recompiling the package.

Tables Accessed

• MRP_PLANS — The control table for plan definitions. The package updates CURR_CUTOFF_DATE, PLAN_COMPLETION_DATE, and DATA_COMPLETION_DATE for the row matching the organization and compile designator.
• MRP_DESIGNATORS / MRP_SCHEDULE_DESIGNATORS — Compile designator definitions that identify which compiled plan version is being launched.
• MRP_PARAMETERS — Plan-level and organization-level parameters that influence launch behavior and horizon defaults.
• MRP_SUB_INVENTORIES — Subinventory definitions used by the planning engine during netting and relief processing.
• MTL_SECONDARY_INVENTORIES — Secondary inventory (subinventory) master data required when the launch expands into inventory-aware processing.

Usage Notes

MRP_LAUNCH_PLAN_PK is normally invoked from the Oracle Planning launch form or from a concurrent program that wraps MRP_LAUNCH_PLAN with the standard errbuf/retcode signature. It can also be called from custom PL/SQL when an implementation needs to automate plan launches as part of a scheduled chain, provided the caller is aware that internal behavior around G_MRP_DEBUG, MRP_CALENDAR, and concurrent-request submission is not contractually guaranteed.

To troubleshoot a launch, set the MRP_DEBUG profile option to 'Y'; MRP_UTIL.MRP_DEBUG will emit trace output to the concurrent request log, including the pre-launch message keyed by G_MRP_DEBUG.