Search Results ahl_rt_oper_materials_s




Overview

The APPS.AHL_RM_ROUTE_PVT package body is a private ("PVT" classified) PL/SQL API belonging to the Oracle E-Business Suite Enterprise Asset Management (EAM) and Asset Lifecycle Management (AHL) product family. It encapsulates the core business logic for managing routing structures used in maintenance and overhaul environments. In Oracle EBS, a "route" represents a reusable, ordered sequence of operations, resources, materials, and dependencies that describe how a maintainable asset or assembly is processed through a maintenance or repair workflow. The AHL_RM_ROUTE_PVT package serves as the internal implementation layer behind the public route API surface, orchestrating the validation, creation, revision, and deletion of route definitions and their associated child entities. Because it is designated PRIVATE, it is not intended to be called directly by external integrations; rather, it is invoked by public-facing packages such as AHL_ROUTES_PKG, which was confirmed in the dependency metadata as a caller. The object resides in the APPS schema with a status of VALID, indicating a compiled and operational package body on both 12.1.1 and 12.2.2 releases.

Key Procedures and Functions

The documented interface exposes three callable units, each central to the route lifecycle:

  • PROCESS_ROUTE — The primary validation and persistence routine. It accepts route header data together with its dependent child collections (operations, resources, materials, dependencies, and access panels) and applies the appropriate insert, update, or delete logic. It enforces referential integrity across the route hierarchy and invokes supporting utilities to normalize and stage the transactional payload.
  • DELETE_ROUTE — Removes a route definition and its associated child records. It cascades deletion across the related _S (sequence/attribute) tables and dependent cross-references such as document title associations and alternate resources, ensuring no orphaned rows remain.
  • CREATE_ROUTE_REVISION — Produces a new revision of an existing route. It copies the header and its full set of operations, resources, materials, and dependencies into a fresh revision context, allowing engineering change control and version tracking of maintenance routings over time.

No parameter signatures are asserted here, as the metadata documents only procedure names and purposes.

Tables Accessed

The package reads and writes the principal AHL route tables through APPS synonyms. The header-level tables AHL_ROUTES_B, AHL_ROUTES_B_S, and the key flexfield view AHL_ROUTES_B_KFV store the route definition and its descriptive flexfield attributes. AHL_ROUTE_OPERATIONS and AHL_ROUTE_OPERATIONS_S hold the ordered operation steps, while AHL_RT_OPER_RESOURCES and AHL_RT_OPER_MATERIALS (referenced by the searched term ahl_rt_oper_materials_s) capture the resources and material requirements tied to each operation. AHL_RT_OPER_DEPENDENCIES stores precedence relationships between operations, and AHL_RT_OPER_ACCESS_PANELS records panel access details. Effectivity dates are maintained in AHL_ROUTE_EFFECTIVITIES. AHL_ALTERNATE_RESOURCES supports resource substitution, and the document association tables AHL_DOC_TITLE_ASSOS_B and AHL_DOC_TITLE_ASSOS_VL link routes to supporting documentation.

Usage Notes

AHL_RM_ROUTE_PVT is normally invoked indirectly through the public routing API (AHL_ROUTES_PKG) when users create or modify routings in the Maintenance Management responsibility's route definition forms, or when batch processes generate or revise routings. Its use of FND_API, FND_MSG_PUB, and FND_MESSAGE provides a standard error-handling and message stack compatible with Oracle's API best practices. Custom code should call the public API rather than this private package to remain upgrade-safe. It is referenced by eight other database objects, reflecting its role as an internal building block. Logging via AHL_DEBUG_PUB and FND_LOG supports diagnostics during development and troubleshooting.