Results for “ahl_rm_rt_oper_resource_pvt”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.AHL_RM_RT_OPER_RESOURCE_PVT is a private (PVT) PL/SQL package within the Oracle Enterprise Asset Management (eAM) / Asset Lifecycle Management (ALM) module of Oracle E-Business Suite. It belongs to the AHL product schema, which governs maintenance management functionality including routes, operations, resources, and resource mappings. The package encapsulates the business logic that supports definition and maintenance of operation-level resource assignments on maintenance routes, together with the cost parameters that drive resource costing during work order and route execution.

The package is declared with AUTHID CURRENT_USER, meaning that its SQL statements execute with the privileges of the invoking user rather than the definer, a pattern typical of EBS private APIs that are exposed only through public wrapper packages. Its header defines strongly typed PL/SQL record and collection structures, notably rt_oper_resource_rec_type and its associated rt_oper_resource_tbl_type indexed-by table, plus a companion rt_oper_cost_rec_type record. These structures mirror the AHL_RT_OPER_RESOURCES entity and carry attributes such as ASO_RESOURCE_ID and ASO_RESOURCE_NAME, RESOURCE_TYPE, QUANTITY, DURATION, ACTIVITY, COST_BASIS, SCHEDULED_TYPE, AUTOCHARGE_TYPE, STANDARD_RATE_FLAG, and the full ATTRIBUTE1 through ATTRIBUTE15 descriptive flexfield columns. A SCHEDULE_SEQ element was added via the fix for Bug 7644260 (ER # 6998882), reflecting the sequencing of resources within a scheduled operation. Each record also includes the standard DML_OPERATION flag used to signal insert, update, or delete intent to the processing routine.

Key Procedures and Functions

Three documented procedures constitute the public interface of this private package:

• PROCESS_RT_OPER_RESOURCE — The principal processing routine. It accepts the operation-resource record or collection and applies the requested DML operation, validating and persisting resource assignments (quantity, duration, activity, cost basis, scheduling type, autocharge behavior, and standard rate) against the underlying route operation resource tables.
• DEFINE_COST_PARAMETER — Establishes or maintains cost parameters associated with a route operation resource. It supports the cost computation attributes referenced by the rt_oper_cost_rec_type structure, such as cost basis, scheduled type, autocharge type, and standard rate flag.
• PROCESS_ALTERNATE_RESOURCE — Handles assignment or maintenance of alternate resources that may substitute for a primary resource on a route operation, driving the corresponding alternate resource records and mappings.

Tables Accessed

Through APPS synonyms, the package reads and writes the following documented tables:

• AHL_RT_OPER_RESOURCES and AHL_RT_OPER_RESOURCES_S — the base and translated (MLS) tables storing route operation resource definitions, the primary persistence targets of PROCESS_RT_OPER_RESOURCE.
• AHL_OPERATIONS_B and AHL_ROUTES_B — operation and route base tables supplying the parent context (operation and route definitions) to which resources are attached.
• AHL_RESOURCES — the resource master, used for validating resource identifiers and names.
• AHL_ALTERNATE_RESOURCES and AHL_ALTERNATE_RESOURCES_S — base and translated tables supporting alternate resource assignments via PROCESS_ALTERNATE_RESOURCE.
• AHL_RESOURCE_MAPPINGS — mapping definitions linking resources to operations or cost elements.
• PLITBLM — a standard EBS PL/SQL table used for bulk DML and error-tracking during multi-row processing.

Usage Notes

As a PVT-classified API, this package is not intended for direct invocation by customer code. It is referenced by three other packages—typically the corresponding public API wrapper and validation packages in the AHL schema—and is invoked indirectly from eAM maintenance route and operation setup forms and from concurrent programs that create or update route operation resources. Because it executes under AUTHID CURRENT_USER and relies on APPS synonyms, callers must operate in a properly initialized EBS environment with FND_GLOBAL context set. Customizations should target the public wrapper rather than this private package, as its signature and internals are subject to change across patch levels (as evidenced by the header revision tied to Bug 7644260). The metadata does not document parameter lists; integrators should consult the corresponding public API specification for supported entry points.