Search Results process_material_req

Overview

APPS.AHL_RM_MATERIAL_AS_PVT is a private PL/SQL package within the Oracle E-Business Suite Enterprise Asset Management (EAM) and Complex Maintenance, Repair and Overhaul (CMRO) modules. It belongs to the Oracle Maintenance application family (AHL schema identifiers) and provides the underlying programmatic engine for maintaining runtime operation material requirements associated with routes and item compositions. In effect, the package encapsulates the logic needed to persist, validate, and reconcile material demand records generated against route operations.

The package is classified as a "PVT" (private) API, meaning it is not intended as a public integration surface. It functions as an internal companion to the public AHL APIs that front the material requirements functionality, and it is referenced by three other packages that consume its processing routines. The $Header stamp indicates a last revision of 120.1 dated 2008/01/30, with the source carrying a modification to introduce disposition list attributes and an IN_SERVICE flag added for the OGMA issue.

Key Procedures and Functions

The recorded metadata documents two procedures within the package specification:

• PROCESS_MATERIAL_REQ — This is the primary entry point and corresponds directly to the "process_material_req" search term. It drives creation, update, and deletion of material requirement records for a given route operation. It relies on the material_req_rec_type record structure and the material_req_tbl_type associative array, which together carry identifiers such as RT_OPER_MATERIAL_ID, OBJECT_VERSION_NUMBER, item and organization keys, quantities, UOM values, a full set of fifteen descriptive flexfield attributes, and a DML_OPERATION flag indicating the row-level action to perform. Additional fields support position paths, item component detail linkage, rework and replace percentages, and the composition material flag.
• PROCESS_ROUTE_EFCTS — Handles the route effectivity dimension of the same maintenance data, operating on the route_efct_rec_type structure. That record carries route effectivity identifiers, route numbers, inventory and master organization references, item description, and a rich set of maintenance/CMRO context columns including maintenance campaign (MC_ID), campaign name, version, revision, and header identifiers.

Both procedures are internal processors rather than user-facing flows; parameter details are not published in the specification excerpt and should not be assumed.

Tables Accessed

The package reads and writes against a focused set of EAM/CMRO and inventory tables accessed through APPS synonyms:

• AHL_RT_OPER_MATERIALS and AHL_RT_OPER_MATERIALS_S — the base and sequence tables holding operation material requirement rows.
• AHL_ROUTE_EFFECTIVITIES and AHL_ROUTE_EFFECTIVITIES_S — route effectivity definitions consumed and maintained by PROCES_ROUTE_EFCTS.
• AHL_ITEM_COMPOSITIONS and AHL_ITEM_COMP_DETAILS — item composition and component detail definitions that supply material structure context.
• AHL_ROUTES_B and AHL_OPERATIONS_B — base tables for routes and their operations, providing the parent context for material rows.
• AHL_MC_HEADERS_B and AHL_MC_RELATIONSHIPS — maintenance campaign header and relationship data used to resolve CMRO context.
• MTL_SYSTEM_ITEMS, MTL_SYSTEM_ITEMS_KFV, and MTL_PARAMETERS — inventory item master, key flexfield concatenation, and organization parameter lookups for validation and defaults.
• PLITBLM — the standard EBS PL/SQL table/bulk DML helper which is used internally to manage bulk operations within the package.

Usage Notes

As a private package, AHL_RM_MATERIAL_AS_PVT is normally invoked indirectly. Typical call paths include the Oracle EAM and CMRO maintenance web forms that manage route operations and their material requirements, public wrapper APIs in the AHL family, and concurrent programs that build or refresh route effectivity and material demand. The package is also called by three other documented packages, confirming its role as a shared internal service.

The record types embed OBJECT_VERSION_NUMBER and audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN), indicating the procedures enforce optimistic locking and standard WHO column maintenance. Because these are internal processing routines, custom code should prefer the public AHL APIs; direct invocation requires exact adherence to the record structures and DML_OPERATION conventions, and no guarantees of interface stability apply across releases such as 12.1.1 and 12.2.2.