Search Results mrp_ap_rel_plan_pub




Overview
Explore in AI Chat

Overview

MRP_AP_REL_PLAN_PUB is a public PL/SQL package in the APPS schema that forms part of the Oracle Advanced Supply Chain Planning (ASCP) and Oracle Manufacturing planning integration layer. Its primary business function is to load and maintain planning-related data that originates outside the core planning engine but which must be reflected in the plan — specifically WIP job schedules, lot-based job schedules, Enterprise Asset Management (EAM) work order schedules, complex maintenance repair overhaul (CMRO) schedules, and purchasing requisition and reschedule information. In effect, the package serves as a controlled interface between execution and planning systems (WIP, EAM, Purchasing) and the planning data model, allowing scheduling and resource changes in those source systems to be propagated into the planner workbench without direct manipulation of planning tables.

The package is classified as a PUB (public) API, meaning it is intended to be called from outside its own schema and is documented for supported use in Oracle EBS 12.1.1 and 12.2.2. The object is VALID and owned by APPS.

Key Procedures and Functions

The ETRM metadata documents eleven procedures and functions, which cluster into distinct functional areas:

  • INITIALIZE — Establishes the runtime session context required by the load routines that follow, typically resolving instance, user, and parameter setup for the current invocation.
  • LD_WIP_JOB_SCHEDULE_INTERFACE — Loads WIP job scheduling information, bringing discrete job and schedule detail into the planning interface.
  • LD_LOT_JOB_SCHEDULE_INTERFACE — Loads lot-based job schedule information, supporting process or lot-controlled manufacturing schedules.
  • LD_EAM_CMRO_SCHEDULE_INTERFACE — Loads EAM and CMRO work order schedule data into the planning interface for maintenance-driven activities.
  • LD_EAM_RESCHEDULE_INTERFACE — Loads EAM reschedule information, propagating revised maintenance dates into planning.
  • LD_CMRO_RESCHEDULE_INTERFACE — Loads CMRO reschedule data, propagating revised overhaul/repair scheduling.
  • LD_PO_REQUISITIONS_INTERFACE — Loads purchasing requisition information so that planned or suggested supply from requisitions is visible to the planning engine.
  • LD_PO_RESCHEDULE_INTERFACE — Loads purchase order reschedule information, reflecting date changes on existing orders.
  • MODIFY_RESOURCE_REQUIREMENT — Modifies a resource requirement record, allowing adjustment of resource demand associated with the loaded schedules.
  • MODIFY_COMPONENT_REQUIREMENT — Modifies a component requirement record, adjusting dependent material demand associated with the loaded schedules.

Tables Accessed

The package references a wide set of APPS synonyms spanning bills of material, cost, item master, project, and planning tables. Bill of material tables — BOM_OPERATIONAL_ROUTINGS, BOM_OPERATION_RESOURCES, BOM_OPERATION_SEQUENCES, BOM_RESOURCES, and BOM_SUB_OPERATION_RESOURCES — provide routing, operation, resource, and sub-resource detail used to derive resource requirements. CST_COST_GROUP_ACCOUNTS supplies cost group accounting context. FND_USER identifies the acting user. MRP_AP_APPS_INSTANCES_ALL and MRP_WORKBENCH_QUERY_S support planning instance and workbench query context. MTL_ITEM_REVISIONS, MTL_PARAMETERS, MTL_SYSTEM_ITEMS, and MTL_SYSTEM_ITEMS_B supply item and revision attributes plus organization-level parameters. PA_PROJECTS_ALL and PJM_PROJECT_PARAMETERS provide project and project parameter data for project-related scheduling. Together these reads support the derivation and validation of schedule, resource, and component requirement records before they are surfaced in the plan.

Usage Notes

This package is a load/interface API rather than an interactive form-level API. It is typically invoked by concurrent programs and planning-collection processes that gather scheduling, requisition, and maintenance data and push it into the planning interface. It is also available for custom code that needs to seed or refresh planning data programmatically. Because it is a PUB package, calls should be made with a properly initialized session (via INITIALIZE) and with attention to the order of the load routines, which are grouped by source system. The package references no other documented packages and is referenced by zero other packages, making it a leaf consumer in the APPS dependency graph; external dependencies are limited to SYS and STANDARD built-ins.