Search Results eam_pmdef_pub_w




Overview
Explore in AI Chat

Overview

The APPS.EAM_PMDEF_PUB_W package body is a public wrapper package within the Oracle Enterprise Asset Management (EAM) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It serves as the procedural interface for managing Preventive Maintenance (PM) definitions — the templates that drive automatic generation of work orders for scheduled maintenance activities on assets. The package encapsulates the business logic required to create, update, and validate PM definitions, including the scheduling rules (day intervals, runtime rules, and list-based date rules) that govern when maintenance work should be triggered.

The "_W" suffix indicates this is a public wrapper (or "web" wrapper) package, a standard EBS convention for exposing PL/SQL logic to the middle tier and to Java-based or form-based clients. It is classified under the ETRM API category "OTHER" and is marked VALID in the APPS schema. It is not referenced by any other database object, meaning it is a top-level entry point invoked directly by external callers rather than being a dependency of other PL/SQL units.

Key Procedures and Functions

The package exposes 25 documented procedures and functions grouped into three functional areas:

Tables Accessed

The documented dependency set shows PLITBLM (reference via the APPS synonym), which is the standard Oracle PL/SQL integer-indexed table type used for bulk DML. The underlying persistent EAM PM tables (such as EAM_PM_DEFINITIONS and its child rule tables) are accessed indirectly through the base package EAM_PMDEF_PUB, which this wrapper depends on. Additional dependencies include EAM_OBJECTINSTANTIATION_PUB and EAM_OBJECTINSTANTIATION_PUB_W, confirming that instantiation of PM definitions is delegated to the object-instantiation API rather than being handled directly here.

Usage Notes

As a public wrapper, EAM_PMDEF_PUB_W is typically invoked from EAM forms, concurrent programs, or Java middle-tier services rather than from end-user SQL*Plus scripts. Custom code should call this package when programmatically creating PM definitions or triggering PM instantiation, relying on the validation routines to enforce rule correctness. Because the package is not referenced by any other database object, it is safe to treat as a stable, externally-facing API surface. Developers should avoid bypassing the validators and should be aware that the wrapper delegates heavy lifting to EAM_PMDEF_PUB, so errors surfaced will originate from the base package. In 12.1.1 and 12.2.2 the package is VALID and carries no known invalidation issues.