Search Results plan_end_min

Overview

APPS.AHL_VWP_VISITS_PUB is a public PL/SQL API package in Oracle E-Business Suite that exposes procedures for managing visits within the Complex Maintenance, Repair, and Overhaul (CMRO) module, part of the Enterprise Asset Management (EAM) family of products under the AHL application. The package is classified as public in the ETRM repository, meaning its procedures form a supported integration surface for external and custom callers. Its header comment defines its scope as "Package containing public APIs to manage CMRO visits," and the package is registered against the business entity AHL_MAINT_VISIT with the display name "VWP Visits." The package is marked as active, indicating it remains a supported, non-obsolete interface in Oracle EBS 12.1.1 and 12.2.2. The header revision (120.1.12010000.2, dated 2008/10/27) reflects a long-stable signature with minimal churn across the 12.x release line. In practice, this package serves as the sanctioned entry point for programmatically creating maintenance visits — the scheduling construct that groups units, resources, and, where applicable, project templates for CMRO execution.

Key Procedures and Functions

The ETRM metadata documents a single public procedure for this package:

• CREATE_VISIT — Creates a visit record. The procedure is a public API and represents the primary documented mechanism for visit creation. Its single parameter is an IN OUT NOCOPY record of type AHL_VWP_VISITS_PVT.Visit_Rec_Type, through which all input attributes are supplied and the generated identifier (VISIT_ID) is returned to the caller. Because the parameter is an IN OUT record, the caller populates the record fields before invoking the procedure and reads back the assigned visit identifier afterward. The documented record attributes cover visit identity (VISIT_NAME, mandatory), descriptive data (DESCRIPTION), organizational context (ORGANIZATION_ID/ORG_NAME, DEPARTMENT_ID/DEPT_NAME), service request linkage (SERVICE_REQUEST_ID/SERVICE_REQUEST_NUMBER), visit scheduling (START_DATE, START_HOUR, START_MIN, PLAN_END_DATE, PLAN_END_HOUR, PLAN_END_MIN), visit classification (VISIT_TYPE_CODE/VISIT_TYPE_NAME), unit association (UNIT_HEADER_ID/UNIT_NAME, UNIT_SCHEDULE_ID), project template (PROJ_TEMPLATE_ID/PROJ_TEMPLATE_NAME), priority (PRIORITY_CODE/PRIORITY_VALUE), and the creation mode (VISIT_CREATE_TYPE, permitting null, PRODUCTION_UNRELEASED, or PRODUCTION_RELEASED). Optional ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 support descriptive flexfield capture. The documentation notes that most other input attributes are ignored, and that START_DATE and UNIT_SCHEDULE_ID are mandatory for transit visits.

Tables Accessed

The package operates against the following tables, reached through APPS synonyms:

• AHL_UNIT_CONFIG_HEADERS — Stores unit configuration header information, providing the unit and configuration context associated with a visit (UNIT_HEADER_ID/UNIT_NAME). CREATE_VISIT references this table to validate and resolve the unit being scheduled.
• PA_PROJECTS — The Oracle Projects project table. When a visit is associated with a project template (PROJ_TEMPLATE_ID/PROJ_TEMPLATE_NAME), the procedure relies on Projects data to relate the visit to its project structure.

Per the ETRM metadata, no other packages are documented as referencing AHL_VWP_VISITS_PUB; the referencing count is zero.

Usage Notes

CREATE_VISIT is intended to be invoked from custom PL/SQL code, integration layers, or Oracle Forms-based CMRO visit maintenance screens that require programmatic visit creation rather than the standard user interface. Typical callers declare a local variable of AHL_VWP_VISITS_PVT.Visit_Rec_Type, populate the mandatory and optional attributes, call the procedure, and then read VISIT_ID from the record for subsequent processing. Because VISIT_NAME is mandatory and START_DATE and UNIT_SCHEDULE_ID are mandatory specifically for transit visits, callers must branch their attribute population logic by visit type. The VISIT_CREATE_TYPE attribute allows the caller to control whether the visit is created as production-unreleased or production-released, which affects downstream visibility and workflow. Because the API is public and the package is active, it is the supported route for visit creation; direct DML against the underlying CMRO tables should be avoided. Given the single documented procedure and the absence of inbound package references, integration designs should treat this package as a boundary API and handle error propagation from the underlying AHL_VWP_VISITS_PVT implementation.