Search Results expand_master_wo_dates




Overview

AHL_PP_RESRC_REQUIRE_PVT is a private PL/SQL package in the Oracle E-Business Suite (EBS) Applications schema (APPS) belonging to the Complex Maintenance, Repair, and Overhaul (CMRO) / Enterprise Asset Management family — internally referred to as AHL. The package name indicates its role in "Provider" (PP) processing of resource requirements for maintenance work orders and visit tasks. In the context of Oracle EBS 12.1.1 and 12.2.2, this package supports the materialization, expansion, and synchronization of resource demand derived from maintenance work order operations so that downstream costing, scheduling, and work-in-process (WIP) integration processes can consume that demand consistently.

Specifically, AHL_PP_RESRC_REQUIRE_PVT encapsulates the record structures and business logic required to translate operation-level resource assignments into AHL operation resource requirement rows, while keeping the associated WIP discrete job, WIP operation, and cost transaction interface tables aligned. Because it is classified as a Private (PVT) API, it is not exposed directly to end users or external integrations; it is instead called by other public CMRO packages and internal concurrent processes.

Key Procedures and Functions

The documented package exposes two procedure-level entry points:

  • PROCESS_RESRC_REQUIRE — The primary processing routine for resource requirements. It reads operation resource definitions and assignments associated with maintenance work orders and visits, resolves resource instances, unit of measure, cost basis, charge type, and scheduled type details, and writes or updates the corresponding rows required by the resource requirement and WIP cost transaction interface structures. It also derives total required, applied, and open quantities along with requirement start and end dates. This is the procedure most commonly associated with the search term "process_resrc_require" and the focus of this package's integration role.
  • EXPAND_MASTER_WO_DATES — A supporting routine that expands or propagates date ranges for master work orders, ensuring that operation and resource requirement windows (OPER_START_DATE, OPER_END_DATE, REQ_START_DATE, REQ_END_DATE) are correctly derived and rolled out across the work order hierarchy. This enables consistent scheduling of child operations and their resource demand.

The package also defines the Resrc_Require_Rec_Type record structure, which carries identifiers such as OPERATION_RESOURCE_ID, RESOURCE_SEQ_NUMBER, OPERATION_SEQ_NUMBER, SCHEDULE_SEQ_NUM, WORKORDER_ID, WIP_ENTITY_ID, resource and department attributes, quantity, UOM, cost basis, charge type, scheduled type, standard rate flag, and standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATED_DATE, OBJECT_VERSION_NUMBER, and DFF attributes). This record type underpins the parameter passing between the package's internal routines.

Tables Accessed

The package reads and writes several CMRO and Oracle Manufacturing tables via APPS synonyms:

Usage Notes

AHL_PP_RESRC_REQUIRE_PVT is a Private API and is not intended to be called directly from forms, Oracle Workflows, or customer extensions. It is invoked internally by other CMRO packages — the ETRM metadata records that it is referenced by seven other packages — typically from public work order or visit processing APIs. In practice, PROCESS_RESRC_REQUIRE is reached whenever a maintenance work order operation is released, updated, or rescheduled and resource demand must be re-derived and pushed to WIP for costing and variance tracking. EXPAND_MASTER_WO_DATES is invoked when master work order date ranges require expansion so that child operations and their resource requirement windows reflect the revised schedule.

Because the package writes to WIP_COST_TXN_INTERFACE, calling applications must ensure that WIP costing concurrent processes (such as Cost Transaction Manager) are scheduled to consume the interface rows. Developers reviewing customizations on 12.1.1 or 12.2.2 should treat this package as an internal implementation detail behind the supported CMRO public APIs, preserving upgrade safety across patch levels referenced in the source header (120.1.12010000.3).