Search Results get_wo_assoc_documents

Overview

The APPS.AHL_PRD_WO_PUB package is a public PL/SQL API within the Oracle E-Business Suite Enterprise Asset Management (EAM) and Complex Maintenance, Repair and Overhaul (cMRO) product family. Its primary responsibility is to expose work order information maintained in the AHL schema to external callers, forms, concurrent programs, and custom extensions. Work orders in this context represent maintenance, repair, and overhaul activities performed against units, routes, visits, and non-routine tasks within the Oracle Complex MRO and Depot Repair domains.

The package is classified as a PUB (public) API, meaning its interface is intended for supported, upwardly compatible consumption by customers and integrators rather than for internal use only. The package header declares a WO_DETAILS_REC_TYPE record type that aggregates more than forty attributes describing a work order, including identifiers, scheduling dates, status information, unit and serial context, visit and visit task linkage, document associations, and numerous enablement flags such as IsCompleteEnabled and IsPartsChangeEnabled. This record type serves as the common payload shape returned by several of the package's read APIs.

Key Procedures and Functions

The package exposes ten documented procedures and functions:

• GET_WORKORDER_DETAILS — Returns the primary work order record, populated into the WO_DETAILS_REC_TYPE structure. It is the central read API for header-level work order attributes.
• GET_WO_OPERATIONS_DETAILS — Retrieves the operation-level detail associated with a work order.
• GET_WO_MTL_REQMTS — Returns material requirements linked to the work order, supporting parts planning and issuance.
• GET_WO_ASSOC_DOCUMENTS — Returns documents associated with the work order. This is the procedure most relevant to the user's search term, and it surfaces document metadata such as the Enigma document identifier and title fields embedded in the work order record.
• GET_WO_TURNOVER_NOTES — Retrieves shift turnover or handover notes recorded against the work order.
• GET_WO_RES_TXNS — Returns resource transactions booked to the work order.
• GET_QA_PLAN_RESULTS — Returns quality assurance plan results collected during execution of the work order.
• PROCESS_WORKORDER — Performs a write or state-changing operation on a work order, subject to API validation and commit control.
• GET_MSG_DATA — Retrieves message or diagnostic data, typically used to surface errors from the FND message stack.
• INIT_USER_AND_ROLE — Initializes the application user and responsibility context required for the API session.

Tables Accessed

The package reads and writes through APPS synonyms. Core work order data resides in AHL_WORKORDERS and AHL_WORKORDER_OPERATIONS. Route and maintenance requirement context comes from AHL_ROUTES_B, AHL_MR_HEADERS_B, and AHL_MR_ROUTES. Visit scheduling is drawn from AHL_VISITS_B and AHL_VISIT_TASKS_B. Document and object associations are resolved through AHL_PC_ASSOCIATIONS. Material and resource data is sourced from AHL_SCHEDULE_MATERIALS, BOM_RESOURCES, and MTL_SYSTEM_ITEMS_KFV. Configuration item relationships use CSI_II_RELATIONSHIPS. Status transition rules are governed by AHL_STATUS_ORDER_RULES. Security and project context are obtained from FND_USER and PA_PROJECTS_ALL.

Usage Notes

AHL_PRD_WO_PUB is typically invoked from cMRO and Depot Repair forms, from concurrent programs that synchronize or report on work order data, and from custom PL/SQL extensions that need to retrieve work order, operation, material, document, turnover, resource transaction, or QA result data. Because it is a public API, callers should observe the standard Oracle API conventions exposed in the header, including the API version, initialization of the message list, commit control, and validation level parameters. The INIT_USER_AND_ROLE procedure should generally be called before other procedures in a session to establish the correct user and role context. The package is referenced by three other packages, indicating its role as a shared foundation for higher-level work order logic within the AHL module.