Search Results ahl_vwp_plan_tasks_pvt




Overview
Explore in AI Chat

Overview

APPS.AHL_VWP_PLAN_TASKS_PVT is a private PL/SQL package within the Oracle Enterprise Asset Management (eAM) and Asset Tracking module (AHL schema) of Oracle E-Business Suite. The "VWP" naming convention indicates that the package belongs to the Visit Work Planning (VWP) subsystem, which governs the scheduling, execution, and tracking of maintenance tasks associated with asset visits. The "_PVT" suffix identifies the package as a private API, meaning that it is intended for internal consumption by other AHL packages rather than for direct invocation by external or customer-written code.

The package encapsulates the core business logic for managing planned tasks that are generated against a visit. Its purpose is to create, update, and delete planned task records that drive the maintenance workload for a given visit, integrating rule-based planning logic with the underlying eAM visit and work order data model. In Oracle EBS 12.1.1 and 12.2.2, this package operates beneath the public AHL_VWP public APIs and the associated visit planning forms. The ETRM metadata confirms the package is VALID in the APPS schema with API classification PVT.

Key Procedures and Functions

The documented package exposes three procedures, each responsible for a distinct phase of the planned task lifecycle:

  • CREATE_PLANNED_TASK — Creates a new planned task record associated with a visit. It is the primary entry point for introducing task-level detail into a visit plan, translating planning rules and unit effectiveness data into discrete, actionable task rows.
  • UPDATE_PLANNED_TASK — Modifies the attributes of an existing planned task, allowing changes to task scheduling, relationships, or associated unit effectivity information without recreating the record.
  • DELETE_PLANNED_TASK — Removes a planned task from a visit, supporting replanning and exception handling when tasks are cancelled, rescheduled, or superseded by revised planning rules.

The package depends on APPS.AHL_VWP_RULES_PVT, which supplies rule evaluation logic, and on FND_API, the standard Oracle Application Object Library API used for message handling, error stacking, and transaction control. Exact parameter lists are not documented in the ETRM metadata and should be confirmed against the package specification in the target environment.

Tables Accessed

The package interacts with the following base tables through APPS synonyms, as documented in the ETRM metadata:

  • AHL_MR_HEADERS_B — Maintenance requirement headers, providing the master maintenance definition from which planned tasks are derived.
  • AHL_UE_RELATIONSHIPS — Unit effectivity relationships, used to resolve which asset instances and effectivity ranges apply to a task.
  • AHL_UNIT_EFFECTIVITIES_B — Unit effectivity records that determine when a maintenance task is valid for a given unit.
  • AHL_VISITS_B — The visit header, the parent context within which planned tasks are created and managed.
  • AHL_VISIT_TASKS_B — Visit task detail, the principal target table written by the create, update, and delete operations.
  • CSI_ITEM_INSTANCES — Installed base item instances, supplying asset identity and configuration context.
  • CS_INCIDENTS_ALL_B and CS_INCIDENT_STATUSES_TL — Service incident records and their translated statuses, linking planned tasks to the service request or incident that initiated the visit.

Usage Notes

Because AHL_VWP_PLAN_TASKS_PVT is a private API, it is not intended for direct call from customer extensions. The ETRM metadata records that it is referenced by three other packages: AHL_VWP_PLAN_TASKS_PVT_W (a wrapper that exposes selected functionality), AHL_VWP_TASKS_PVT, and AHL_VWP_UNPLAN_TASKS_PVT. These relationships indicate that task planning, task execution, and unplanned task handling all route through this package, making it a central component of the Visit Work Planning flow.

Typical invocation occurs indirectly through the eAM visit planning user interface, the Visit Work Planning concurrent programs, and higher-level public APIs that orchestrate visit task generation. Custom code requiring planned task manipulation should call the supported public wrapper rather than this package directly. As with all PVT packages, upgrades and patches may alter its internal signature without notice.