Search Results scheduled_start

Overview

APPS.AHL_WIP_JOB_PVT is a private (PVT) PL/SQL package in the Oracle E-Business Suite Discrete Manufacturing and Oracle Complex Maintenance, Repair and Overhaul (CMRO / AHL) product family. Its role is to create and maintain WIP discrete jobs generated from AHL work orders, mapping maintenance work order data onto the Oracle Work in Process job, operation, resource, and scheduling model. The package is the internal implementation layer beneath the public AHL work order APIs: it encapsulates the transformation of AHL work order records into WIP job headers, job operations, and resource requirements, and then submits or loads that data through the standard WIP interface tables.

The scheduled_start field appears twice in the package specification, once in the ahl_wo_rec_type record and once in the ahl_wo_op_rec_type record, indicating that job-level and operation-level scheduling dates are both handled by this package. These record types carry a dml_type indicator of 'I' for insert, 'U' for update, and (for resource requirements) 'D' for delete, giving the package controlled insert/update/delete semantics over the underlying WIP data.

Key Procedures and Functions

• LOAD_WIP_JOB — Drives the loading of a single AHL work order into the WIP job structure, interpreting the job-level record type and populating the appropriate WIP interface and job tables.
• LOAD_WIP_BATCH_JOBS — Provides the set-based counterpart to LOAD_WIP_JOB, processing a collection of AHL work orders as a batch load into WIP.
• INSERT_RESOURCE_TXN — Inserts resource transaction data associated with the job, using the resource requirement record type and its insert/update/delete semantics to synchronize job resource requirements.
• WIP_MASSLOAD_PENDING — Handles the mass-load / pending processing path by which accumulated WIP job data is validated and pushed into the WIP job details and schedule interface tables for the standard WIP mass load programs.

Tables Accessed

The package reads and writes WIP interface and base tables. WIP_JOB_DTLS_INTERFACE and WIP_JOB_SCHEDULE_INTERFACE (with its _S sequence) receive the staged job, operation, and scheduling data — including scheduled_start and scheduled_end — for the WIP mass load. WIP_DISCRETE_JOBS, WIP_OPERATIONS, and WIP_ENTITIES represent the base WIP tables against which jobs and operations are created or matched, while WIP_COST_TXN_INTERFACE and WIP_INTERFACE_ERRORS support costing transactions and error capture.

Resource and department data is drawn from BOM_DEPARTMENTS, BOM_DEPARTMENT_RESOURCES, BOM_DEPT_RES_INSTANCES, and BOM_RESOURCE_EMPLOYEES. MTL_PARAMETERS supplies organization-level defaults, FND_USER resolves the acting user, and DUAL is used for single-row evaluations.

Usage Notes

As a PVT package, AHL_WIP_JOB_PVT is not intended for direct customer invocation; it is called by the AHL public APIs and by three other packages within the application. It supports both single-record and batch processing paths, including a mass load / pending pattern, and is typically driven from AHL work order forms or concurrent programs that release maintenance work orders into WIP. Customizations should target the supported AHL public APIs rather than this private layer, since its signatures may change across releases such as 12.1.1 and 12.2.2.