Search Results create_job_pre




Overview
Explore in AI Chat

Overview

APPS.AHL_PRD_WORKORDER_CUHK is a customization hook (the "CUHK" suffix denotes a client-specific extension) for the Oracle E-Business Suite Enterprise Asset Management / Complex Maintenance, Repair, and Overhaul (MRO) module. It resides in the AHL product schema, which governs asset lifecycle and maintenance work order processing. The package body provides pre- and post-processing hook points around the standard production work order APIs, specifically the Create Job and Update Job operations exposed by AHL_PRD_WORKORDER_PVT. These hooks allow site-specific business rules, validations, or side effects to be layered onto the seeded work order logic without modifying Oracle's delivered code. The package header is declared as AHL_PRD_WORKORDER_CUHK, and the body carries the standard `$Header` attribute recorded as 120.0.12010000.1, dated 2009/01/12, authored by sikumar and marked noship. The package is classified as an OTHER API and is referenced by one other package.

Key Procedures and Functions

  • CREATE_JOB_PRE — Executes before the standard work order creation logic. It establishes a savepoint and initializes the return status to FND_API.G_RET_STS_SUCCESS, providing an extension point for pre-creation validation or setup. Errors raised through the FND_API exception framework trigger a rollback to the savepoint and populate the standard message stack via FND_MSG_PUB.
  • CREATE_JOB_POST — Executes after work order creation completes. It receives the work order record together with operation, resource requirement, and material requirement collections, making it the appropriate hook for post-creation processing such as downstream updates or integration calls.
  • UPDATE_JOB_PRE — The pre-processing counterpart for work order updates, invoked before the standard update logic to apply custom validation or preparatory actions.
  • UPDATE_JOB_POST — The post-processing counterpart for work order updates, invoked after the standard update completes to perform follow-on activities.

Tables Accessed

The ETRM metadata for this package lists no directly referenced tables via APPS synonyms. All data interchange occurs through PL/SQL record and table types defined in companion packages: AHL_PRD_WORKORDER_PVT (prd_workorder_rec), AHL_PRD_OPERATIONS_PVT (prd_operation_tbl), AHL_PP_RESRC_REQUIRE_PVT (resrc_require_tbl_type), and AHL_PP_MATERIALS_PVT (req_material_tbl_type). Because these are parameter-based APIs, any persistent work order, operation, resource, or material data is read or written by the underlying private APIs rather than by this hook package directly. Customized implementations may add direct DML against the corresponding AHL base tables, but no such table usage is documented.

Usage Notes

The procedures are not intended to be invoked directly by end users or external code. Instead, they are called internally by the standard AHL_PRD_WORKORDER_PVT work order processing flow as hook points, which is why the package is referenced by one other package. Typical triggers include work order creation and update originating from the MRO maintenance workbench forms, concurrent programs, or inbound integration programs that create or amend production work orders. The naming convention (CUHK) confirms these are client-specific extensions that should remain consistent with the delivered API contract, including the FND_API return status and message-count conventions. Custom logic added inside the hook bodies must preserve the savepoint, rollback, and FND_MSG_PUB error-handling pattern shown in the documented source to avoid leaving the calling transaction or message stack in an inconsistent state.