Search Results ahl_schedule_materials_pkg




Overview
Explore in AI Chat

Overview

APPS.AHL_SCHEDULE_MATERIALS_PKG is a PL/SQL package within the Oracle E-Business Suite Application Object Library schema, classified under the Oracle Enterprise Asset Management (eAM) and Asset Lifecycle Management (AHL) product family. Its principal business function is to provide the low-level data manipulation layer for records held in the AHL_SCHEDULE_MATERIALS entity, which stores the materials and spare parts associated with scheduled maintenance activities and maintenance work orders. The package encapsulates the standard insert, update, and delete operations required to maintain the integrity of these material scheduling records, shielding calling components from direct DML against the underlying tables and translation table. In the context of Oracle EBS 12.1.1 and 12.2.2, the package is a valid, compiled object owned by the APPS schema and is exposed as a public API classified as OTHER. It is referenced by other AHL maintenance packages and therefore participates in the broader maintenance scheduling and forecasting workflow. Because it operates beneath the user-facing forms and public APIs, it is generally not invoked directly by end users but instead supports the maintenance scheduling functions that manage material requirements.

Key Procedures and Functions

The documented interface consists of three procedures, each adhering to the standard Oracle EBS table-handler naming convention:

  • INSERT_ROW — Creates a new material scheduling record. This procedure populates the base entity with the material details associated with a given maintenance schedule line, and typically also maintains the corresponding translation or reference record where applicable.
  • UPDATE_ROW — Modifies an existing material scheduling record, allowing changes to quantities, material identifiers, or associated scheduling attributes while preserving the record's primary key identity.
  • DELETE_ROW — Removes a material scheduling record, including any associated child rows maintained in the translation table, when a scheduled material is no longer required.

No additional functions or procedures beyond these three are documented in the ETRM metadata. Parameter lists are intentionally not enumerated here; callers should obtain exact signatures from the packaged source in the APPS schema.

Tables Accessed

The package operates against two documented tables, resolved through APPS synonyms:

  • AHL_SCHEDULE_MATERIALS — The primary base table storing the scheduled material lines, including the material assignment, quantity, and linkage to the parent maintenance schedule.
  • AHL_SCHEDULE_MATERIALS_S — The companion translation or sequence-support table, which the package maintains in conjunction with the base table to preserve multilingual and referential consistency.

All read and write activity is confined to these two entities. The procedures act as the controlled gateway for DML, ensuring that both the base and translation records remain synchronized during insert, update, and delete operations.

Usage Notes

In typical EBS deployments, AHL_SCHEDULE_MATERIALS_PKG is invoked indirectly rather than through direct user action. It is referenced by two other AHL packages — AHL_UMP_FORECAST_REQ_PVT and AHL_UMP_PROCESSUNIT_EXTN_PVT — which are part of the maintenance forecasting and process unit extension logic. This dependency indicates that material scheduling records are created and maintained as a downstream consequence of maintenance forecasting and process unit processing. Customizations or extensions that must manipulate scheduled material data should call these procedures rather than issuing direct SQL against the tables, thereby preserving validation, translation maintenance, and referential integrity. Because the object is classified as OTHER and remains VALID in both 12.1.1 and 12.2.2, it is a stable internal component; however, it is not a formally published public API, so custom code should exercise caution and validate behavior against the specific patch level installed. Signature changes across releases are possible, and any direct dependency should be re-verified during upgrades.