Search Results search_table_index
Overview
APPS.AHL_WORKORDER_SEARCH_PUB is a public PL/SQL API within the Oracle Enterprise Asset Management (eAM) and Complex Maintenance, Repair and Overhaul (CMRO) modules of Oracle E-Business Suite. It is declared with AUTHID CURRENT_USER, indicating that it executes with the privileges of the invoking schema rather than the owning APPS schema, which is a common convention for APIs invoked from self-service or restricted-access contexts. The package provides the programmatic foundation for the Work Order Search functionality, enabling users and applications to query work orders based on a broad set of filter criteria and to retrieve structured result sets for display or downstream processing. In the context of Release 12.1.1 and 12.2.2, this package is one of the supporting public APIs behind the Maintenance Workbench and related eAM self-service pages, where searching for work orders by number, status, visit, dates, project, department, unit, employee, and other attributes is a core user activity.
Key Procedures and Functions
The ETRM metadata documents a single public procedure:
- GET_WO_SEARCH_RESULTS — Executes a work order search using the criteria supplied through the
WORKORDERS_SEARCH_REC_TYPErecord and returns matching work orders in theWORK_ORDERS_RESULT_TBL_TYPEcollection. This procedure is the primary entry point for the package and is designed to accept a flexible search record that mirrors the fields exposed on the Work Order Search user interface.
The package also declares several supporting PL/SQL types that define the API contract. The WORKORDERS_SEARCH_REC_TYPE record holds search criteria such as WORKORDER_NUMBER, DESCRIPTION, STATUS_CODE, VISIT_NUMBER, SCHEDULED_START_DATE, SCHEDULED_END_DATE, paging fields (START_ROW_INDEX, NUMBER_OF_ROWS, SEARCH_TABLE_INDEX), ACCOUNTING_CLASS, DEPARTMENT_CLASS_CODE, PROJECT, PROJECT_TASK, OPERATION_CODE, PRIORITY, and crucially for the user's search, WORKORDER_TYPE. The result structure WORK_ORDER_REC_TYPE returns fields including WORKORDER_ID, OBJECT_VERSION_NUMBER, WORKORDER_NUMBER, STATUS_CODE, VISIT_NUMBER, UNIT_NAME, MODEL, ATA_CODE, and various enablement flags (IS_COMPLETE_ENABLED, IS_UPDATE_ENABLED, IS_RES_TXN_ENABLED) that drive UI button and action availability.
Tables Accessed
The ETRM metadata for this object does not enumerate base tables accessed through APPS synonyms. Functionally, the package must read from the core work order tables in the AHL schema, most notably AHL_WORKORDERS and its associated visit and task structures, to satisfy the search predicates defined in WORKORDERS_SEARCH_REC_TYPE. Additional joins are implied by the search fields (project, department, unit, employee, item, organization, maintenance requirement) against the corresponding eAM and Oracle Projects entities. Because the metadata documents no explicit table list, integrators should treat table access as read-only and confirm dependencies through the actual package body in their environment.
Usage Notes
This package is typically invoked from eAM/CMRO self-service pages and the Maintenance Workbench, where user-entered search criteria are mapped into WORKORDERS_SEARCH_REC_TYPE and passed to GET_WO_SEARCH_RESULTS. The paging attributes (START_ROW_INDEX, NUMBER_OF_ROWS) support result-set pagination for large work order populations. The WORKORDER_TYPE attribute allows callers to restrict results by work order type. The package is referenced by zero other packages per the metadata, so it is a leaf-level public API intended for direct invocation. Custom code should call it rather than querying base tables directly, and should respect the AUTHID CURRENT_USER privilege model so that row-level security and MOAC (Multi-Org Access Control) filters apply correctly.