Search Results mrp_update_mrp_cols

Overview

The APPS.MRP_UPDATE_MRP_INFO_PK package is a PL/SQL package in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that belongs to the Oracle Material Requirements Planning (MRP) application module. It is defined with AUTHID CURRENT_USER, meaning its SQL statements execute under the privileges of the invoking schema rather than the package owner. The package provides the interface used to refresh and synchronize planning-related column values on MRP records for a given organization and inventory item, most likely within the context of a planner-driven update or plan regeneration request. Its header carries the identifier $Header: MRPPUPDS.pls 115.1 2002/06/07 12:58:12 pkm ship $, indicating the source file is MRPPUPDS.pls. The object is classified as OTHER in the ETRM repository and is not referenced by any other package, which suggests it is either invoked directly or called from a limited set of higher-level processes.

Key Procedures and Functions

The package exposes a single documented procedure: MRP_UPDATE_MRP_COLS. As the name implies — and matching the mrp_update_mrp_cols search term — this procedure is responsible for updating MRP column information. Based on the parameter signatures declared in the package specification, it accepts inbound arguments for organization, item, user, and concurrent request context (documented as identifiers such as organization ID, item ID, user ID, and request ID). No additional procedures or functions are declared in the header text beyond this one.

The procedure does not return a value; it operates as a maintenance/refresh routine. It is expected to recalculate or propagate planning attributes across the MRP schema tables that fall within its scope.

Tables Accessed

Per the ETRM metadata, the package references the following tables through APPS synonyms:

• MRP_RECOMMENDATIONS — stores MRP planning recommendations generated for items, likely updated to reflect current plan state.
• MRP_RELIEF_INTERFACE — the interface table through which supply relief is communicated, suggesting the procedure may reconcile relief data.
• MRP_SCHEDULE_DATES and MRP_SCHEDULE_DESIGNATORS — schedule master tables used to validate and apply calendar/schedule context.
• MTL_SUPPLY — supply records used in netting and supply/demand calculations.
• MTL_UNITS_OF_MEASURE — UOM conversions applied to quantities.
• WIP_DISCRETE_JOBS, WIP_FLOW_SCHEDULES, and WIP_REQUIREMENT_OPERATIONS — work-in-process manufacturing records whose requirements may require synchronization.
• DBMS_LOCK — used to serialize concurrent access, ensuring that two invocations do not update the same records simultaneously.

Usage Notes

The procedure is typically invoked with an explicit organization ID, item ID, user ID, and concurrent request ID, allowing the caller to scope the update precisely and trace execution to a concurrent request. Because the package uses AUTHID CURRENT_USER, callers must have appropriate privileges on the underlying tables.

In practice, invocation occurs from within MRP planning flows, from custom concurrent programs that need to refresh MRP column values for a defined item/organization combination, or from application code that requires MRP metadata to be brought in line after a supply, WIP, or schedule change. The inclusion of DBMS_LOCK indicates the routine is designed to be safe under concurrent execution, but long-running or bulk invocations should be scheduled carefully to avoid lock contention on the MRP and WIP tables. Because external references are limited, direct invocation from custom code should be validated against the specific EBS patch level in use (12.1.1 versus 12.2.2) before deployment.