Results for “single_org”

50+ results




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

Overview

MRP_UPDATE_PLAN_OPTIONS_PK is an Oracle Application Object Library package owned by the APPS schema and shipped as part of the Oracle Manufacturing and Supply Chain Planning product family. Its role is to persist and maintain the runtime configuration associated with a Material Requirements Planning (MRP) plan definition, specifically the plan options and schedule attributes that drive how a given plan executes. During plan administration activities — creating a plan, editing an existing plan, or marking a plan for execution or compilation — the concurrent manager and the Oracle Forms user interface delegate the low-level DML against the plan repository tables to this package rather than issuing direct SQL statements. This encapsulation ensures that derived values, such as scheduling completion timestamps and organization scope records, remain consistent between the plan header and its associated child rows. The object is documented as VALID in the ETRM metadata for release 12.2.2 and remains present, with equivalent behavior, in the 12.1.1 schema. Its API classification is recorded as OTHER, indicating that it is an internal support package rather than one of the formally published public interfaces.

Key Procedures and Functions

  • MRP_UPDATE_OPTIONS — The principal entry point of the package. It writes the user-supplied plan option values back to the plan definition, keeping the MRP_PLANS record synchronized with the selections made in the Plan Options form. Invocations are triggered from plan maintenance screens and from internal code paths that adjust planner parameters before a plan refresh run.
  • MRP_SET_COMPLETION_TIME — Records the completion timestamp associated with a plan operation, most commonly the moment at which a planning or compile request finishes processing. This provides downstream consumers, such as plan status inquiries and the planner workbench, with an accurate completion reference for the affected plan and schedule.

The metadata documents exactly two procedures in this package. No public function signatures are enumerated, and no parameter lists are published in the reference material; callers should treat the package as an internal implementation detail and avoid direct invocation from custom code.

Tables Accessed

Three base tables are accessed through APPS synonyms:

  • MRP_PLANS — The master plan definition table. MRP_UPDATE_OPTIONS updates the option columns of the plan row, and MRP_SET_COMPLETION_TIME records the plan-level completion timestamp on the same row.
  • MRP_PLAN_ORGANIZATIONS — Maintains the organization scope of a plan, defining which inventory organizations participate in the planning run.
  • MRP_PLAN_SCHEDULES — Stores the schedule-level attributes and execution characteristics tied to each plan, including schedule completion information written by MRP_SET_COMPLETION_TIME.

Usage Notes

This package is invoked indirectly. The typical paths are the Plan Options and Plan Names forms within Oracle Master Scheduling/MRP and Oracle Supply Chain Planning, the plan compilation and plan run concurrent programs that update plan state after completion, and internal planner logic that adjusts option values programmatically. Because the package is classified as OTHER and exposes no documented public API contract, Oracle does not support calling it from custom concurrent programs, triggers, or interface tables. Customizations that require changing plan options should use the supported UI or the documented planning public APIs; for example, the FND_REQUEST.Submit_Request mechanism to launch standard plan maintenance concurrent programs. Direct calls carry a maintenance risk, since the procedure signatures are not published and may change between patch levels or between 12.1.1 and 12.2.2. The package is additionally notable in that it is self-referencing in the dependency listing and is not referenced by any other documented package, confirming its role as a leaf-level utility invoked only from the forms and concurrent program layer.