Search Results ahl_vwp_tasks_pvt_w




Overview
Explore in AI Chat

Overview

The APPS.AHL_VWP_TASKS_PVT_W package body is a private PL/SQL implementation unit within the Oracle E-Business Suite Enterprise Asset Management (EAM) product family, specifically belonging to the Asset Lifecycle (AHL) schema area that supports Visit Workbench and Preventive Maintenance functionality. The _W suffix convention indicates that this package serves as an internal worker or wrapper layer, providing the concrete implementation logic that the public interface packages (AHL_VWP_TASKS_PVT) expose to callers. In Oracle EBS 12.1.1 and 12.2.2, this package participates in the orchestration of visit tasks that drive maintenance scheduling, inspection execution, and service work associated with asset visits. Its primary responsibility is to encapsulate the business rules governing the creation, modification, search, and association of tasks, while also supporting data transfer objects passed between the UI and the database tier. The package is classified as OTHER in the API classification taxonomy and holds a VALID status in the APPS schema.

Key Procedures and Functions

The package body exposes eight documented procedures that together form its operational surface.

  • CREATE_TASK — Creates a new visit task record, applying the validation and defaulting rules required before persistence.
  • UPDATE_TASK — Modifies an existing task, typically invoked when task attributes such as status, assignment, or scheduling details change.
  • GET_TASK_DETAILS — Retrieves the full attribute set for one or more tasks, returning the data required by the calling form or integration layer.
  • SEARCH_TASK — Executes query logic to locate tasks based on caller-supplied filter criteria, supporting the workbench search UI.
  • CREATE_PUP_TASKS — Generates tasks associated with a planned unit of production or a comparable preventive maintenance construct, deriving them from a template or rule set.
  • ASSOCIATE_DEFAULT_MRS — Associates default Material Requirements Specifications with tasks, ensuring that the parts and quantities required for a maintenance activity are linked automatically.
  • ROSETTA_TABLE_COPY_IN_P1 — A Rosetta-style helper routine that copies incoming table-structured (JTF table type) data into the package's internal processing structures.
  • ROSETTA_TABLE_COPY_OUT_P1 — The complementary helper that copies result data back out into table-structured form for consumption by the caller.

Tables Accessed

Per the documented dependency metadata, the only table referenced through APPS synonyms is PLITBLM. In Oracle EBS, PLITBLM is a standard PL/SQL internal repository structure used by the PL/SQL toolkit rather than an application data table; it is not read or written as business data. The absence of direct application table references in the metadata confirms that AHL_VWP_TASKS_PVT_W performs its data manipulation indirectly, delegating table-level DML to the dependent worker and public packages it references. The documented dependencies include AHL_VWP_TASKS_PVT, AHL_VWP_VISITS_PVT, AHL_VWP_RULES_PVT, and AHL_VWP_RULES_PVT_W, along with FND_API, which supplies the standard EBS API error-handling and message framework. The package also depends on the JTF collection types JTF_DATE_TABLE, JTF_NUMBER_TABLE, and the JTF_VARCHAR2_TABLE_100/200/300/4000 types, which carry array-based parameters.

Usage Notes

Because AHL_VWP_TASKS_PVT_W is a private worker package, it is not intended to be invoked directly by custom code or integration scripts. Business flows reach it indirectly through AHL_VWP_TASKS_PVT, which is the supported public entry point. Typical invocations originate from the Visit Workbench and Preventive Maintenance HTML forms that display and manage visit tasks, from concurrent programs that generate recurring or preventive maintenance tasks, and from internal EBS processes that associate default material requirements with scheduled work. The ETRM metadata confirms that the package body is referenced by zero external database objects, reinforcing its role as an internal implementation unit positioned beneath the public API layer. Custom extensions should therefore target the public AHL_VWP_TASKS_PVT interface and rely on FND_API-based error reporting rather than calling the _W routines directly.