Search Results associate_default_mrs

Overview

APPS.AHL_VWP_TASKS_PVT is a private PL/SQL API within the Oracle E-Business Suite Complex Maintenance, Repair and Overhaul (CMRO) module. Its purpose is to manage the tasks associated with a Visit Work Package (VWP) — specifically, the individual tasks that belong to a visit in a maintenance planning and execution context. The package specification header identifies it as a "Private API for managing Planning --> Visit Work Package --> Visit's TASKS related procedures in Complex Maintainance, Repair and Overhauling (CMRO)."

Although the object is classified as PVT (private), meaning it is not intended as a public integration surface, it encapsulates the core business logic used by the CMRO application to create, maintain, search, and display visit task records. The package also declares PL/SQL record and table types used internally, such as Srch_Task_Rec_Type (holding Task_ID, Task_Start_Time, and Task_End_Time) and the associated Srch_Task_Tbl_Type collection, which support the task search functionality. The package has evolved since its creation in May 2002, with an 11.5.10 revision in August 2003, and remains documented in ETRM for both 12.1.1 and 12.2.2.

Key Procedures and Functions

The ETRM metadata documents nine procedures and functions within this package:

• GET_TASK_DETAILS — Displays task details associated with a visit, primarily to populate the update UI screen. This is the procedure relevant to the user's search term.
• CREATE_TASK — Creates a new task record associated with a visit.
• UPDATE_TASK — Modifies an existing visit task.
• DELETE_TASK — Removes a task from a visit.
• SEARCH_TASK — Searches for tasks based on the search record type defined in the specification.
• DELETE_SUMMARY_TASK — Handles removal of summary-level tasks.
• CREATE_PUP_TASKS — Creates tasks related to PUP (planned unit processing) scenarios.
• ASSOCIATE_DEFAULT_MRS — Associates default maintenance requirement records with tasks or visits.
• CREATE_STAGE_TASKS — Creates tasks at the stage level of a visit work package.

The specification documents the standard API parameter conventions used throughout, including the IN parameters p_api_version (required), p_init_msg_list, p_commit, p_validation_level, p_default, and p_module_type, and the standard OUT parameter x_return_status. These follow the Oracle Application Object Library API framework, enabling consistent error handling and message list management. Detailed parameter lists for each procedure are defined in the package body and the full specification, which the ETRM excerpt only partially captures for GET_TASK_DETAILS.

Tables Accessed

The package reads and writes a broad set of CMRO tables via APPS synonyms. Visit and task-level data is stored in AHL_VISITS_B, AHL_VISIT_TASKS_B, and AHL_VISIT_TASKS_TL (the translatable column table for task descriptions). Work package stage data resides in AHL_VWP_STAGES_B, while task relationships are held in AHL_TASK_LINKS. Maintenance requirement structures — AHL_MR_HEADERS_B, AHL_MR_INTERVALS, AHL_MR_ROUTES, and AHL_ROUTES_B — support the association of default maintenance rules. AHL_APPLICABLE_MRS and AHL_UNIT_EFFECTIVITIES_B provide applicability and unit effectivity context. Warranty-related logic draws on AHL_WARRANTY_CLAIMS_B, AHL_WARRANTY_CONTRACTS_B, and AHL_WARRANTY_ENTITLEMENTS. AHL_WORKORDERS links visit tasks to execution work orders.

Usage Notes

As a private API, AHL_VWP_TASKS_PVT is not designed for direct invocation by external or customer-written integrations. It is referenced by fifteen other packages within the CMRO codebase, which consume its procedures as part of higher-level visit work package processing. The most common invocation paths are Oracle Forms-based UI screens in the Maintenance Planning module, where actions such as viewing, updating, or deleting a visit task trigger calls to the corresponding procedures. GET_TASK_DETAILS in particular is invoked when the update screen is rendered, to retrieve and display task information. Concurrent programs and background processes may invoke the creation and association procedures (CREATE_TASK, CREATE_PUP_TASKS, CREATE_STAGE_TASKS, ASSOCIATE_DEFAULT_MRS) to generate tasks in bulk. Customizations should avoid calling this package directly; developers requiring task management functionality should use the supported public APIs or the documented business flows instead, as the private API signature may change between 12.1.1 and 12.2.2 without notice.