Search Results get_sub_mat_detail

Overview

APPS.MRP_RESCHEDULE_CMRO_WO_PS is a public PL/SQL specification package in Oracle E-Business Suite that supports the rescheduling and release of work orders originating from Enterprise Asset Management (EAM) and from supply schedules created by EnterpriseOne. The package is declared with AUTHID CURRENT_USER, meaning its SQL executes under the privileges of the invoking session rather than the definer. Its header, marked MRPPSRELS.pls version 120.6 (last updated 12 May 2011), places it within the material planning and work order scheduling family of the MRP product, closely tied to the Work in Process (WIP) domain.

The package provides the general-purpose data structures used to pass work order, operation, resource, and material information between planning logic and the WIP release process. It defines several PL/SQL record types—WO_ORG_REC, JOBS_CUR_REC, OP_CUR_REC, RES_CUR_REC, and MAT_CUR_REC—that carry the attributes needed to describe discrete jobs, their operations, resources, and material requirements. These records allow the package to assemble and process complete work order definitions before invoking the underlying WIP APIs.

Key Procedures and Functions

The package exposes twelve documented procedures and functions. RESCHEDULE_CMRO_WO drives the rescheduling of a contract manufacturing or maintenance work order, coordinating the change in its planned dates and quantities. PROCESS_SINGLE_WO handles the processing of an individual work order, while PROCESS_SINGLE_WO_EAM applies the equivalent processing logic for EAM work orders. RELEASE_CMRO_WO performs the release activity that converts a work order into a releasable job.

The GET_* routines are extraction functions that populate the package record structures: GET_WO_DETAIL retrieves work order header information; GET_OP_DETAIL returns operation-level detail; GET_RES_DETAIL returns resource-level detail; GET_RES_INST_DETAIL and GET_RES_USAGE_DETAIL return instance-level and usage-level resource information respectively; GET_MAT_DETAIL returns parent material requirements; and GET_SUB_MAT_DETAIL returns sub-inventory or component-level material detail. POPULATE_MISSING_DETAILS fills in any gaps in the collected detail, ensuring the work order payload is complete before release or rescheduling proceeds. No parameter lists are documented, so these descriptions reflect only the purpose and functional role of each program unit.

Tables Accessed

The package references a small set of database objects through APPS synonyms. AHL_REQ_SUPPLY_SCHEDULE stores the requirement supply schedule that links work orders to the originating demand, which is the source mapped by the JOBS_CUR_REC SOURCE_CODE and SOURCE_LINE_ID attributes. WIP_OPERATIONS provides the operation sequence records used to build the OP_CUR_REC structure, including sequence numbers, departments, and scheduled start and completion dates. PLITBLM is an Oracle-supplied intermediate table commonly used in EBS for bulk data collection or dynamic operations. V$PARAMETER2 is queried, typically to read database or instance parameters that influence processing behavior. These references are consistent with a package that reads the requirement schedule and WIP operation data, then writes through the WIP release APIs rather than directly modifying base tables.

Usage Notes

MRP_RESCHEDULE_CMRO_WO_PS is a documented API classified as OTHER and is referenced by no other packages in the documented metadata. It is typically invoked from planning and scheduling flows—forms, concurrent programs, or custom code—that need to reschedule or release EAM and contract manufacturing work orders whose demand originates from a supply schedule. Because it is an AUTHID CURRENT_USER specification, callers must ensure the invoking session holds appropriate privileges on the referenced WIP and AHL objects. The version header indicates the package was maintained under patch level 120.6, and the same behavior applies in EBS 12.1.1 and 12.2.2. When extending or calling this package, developers should rely on the documented record structures and procedures rather than assume additional private routines.