Search Results validate_pm_day_interval_rule

Overview

APPS.EAM_PMDEF_PUB is the public PL/SQL API package for Preventive Maintenance (PM) definition management within Oracle Enterprise Asset Management (EAM). It provides the programmatic interface through which PM schedules, PM activities, and their associated scheduling rules are created, validated, instantiated, and maintained against asset counters and maintenance work orders. The package operates as a public (PUB) API, meaning its procedures are intended to be called from external consumers such as Oracle Forms, concurrent programs, other EAM utilities, and customer-written extensions, rather than being restricted to internal package use.

Its central responsibility is the transition from a defined PM template (the PM definition, including day-interval rules, runtime rules, and list-date rules) to concrete, executable PM schedulings attached to specific assets and meters. This is achieved through theINSTANTIATE_PM_DEF and INSTANTIATE_PM_DEFS procedures, which bridge the EAM PM definition layer and the scheduling layer. The package depends on the FND_API foundation package for standard API error handling, message stacking, and transaction control conventions, and it references the EAM_OBJECTINSTANTIATION_PUB package, which is closely related to the user's search term, indicating that PM instantiation is coordinated with the broader EAM object instantiation framework.

Key Procedures and Functions

The 21 documented procedures and functions fall into several functional groups:

• Instantiation: INSTANTIATE_PM_DEF and INSTANTIATE_PM_DEFS generate PM schedulings from PM definitions for a single or multiple PM definitions respectively. These are the primary entry points for materializing PM schedules onto assets.
• Definition maintenance: CREATE_PM_DEF and UPDATE_PM_DEF insert and modify PM definition records, enforcing the API's validation contract.
• Validation: A comprehensive set of validation routines — VALIDATE_PM_HEADER, VALIDATE_PM_DAY_INTERVAL_RULE, VALIDATE_PM_RUNTIME_RULE, VALIDATE_PM_LIST_DATE, VALIDATE_PM_DAY_INTERVAL_RULES, VALIDATE_PM_RUNTIME_RULES, VALIDATE_PM_LIST_DATE_RULES, VALIDATE_PM_HEADER_AND_RULES, VALIDATE_PM_ACTIVITY, and VALIDATE_PM_ACTIVITIES — verify PM header data, individual rule types, rule collections, and PM activities before persistence. These support both single-record and bulk validation patterns.
• Sorting and merging utilities: SORT_TABLE_BY_DATE, SORT_TABLE_BY_NUMBER, and MERGE_RULES provide in-memory ordering and consolidation of rule data, typically preparatory to instantiation.
• Scheduling-state maintenance: GET_PM_LAST_ACTIVITY retrieves the most recent activity for a PM scheduling; UPDATE_PM_LAST_CYCLIC_ACT and UPDATE_PM_LAST_SERVICE_READING update the last cyclic activity and last service reading markers used for interval computation.

No parameter signatures are documented in the ETRM metadata; callers should consult the package specification directly for exact parameter lists and return types.

Tables Accessed

The package reads and writes through APPS synonyms across the following documented tables:

• EAM PM definition and scheduling tables: EAM_PM_ACTIVITIES, EAM_PM_SCHEDULINGS, EAM_PM_SCHEDULINGS_S, EAM_PM_SCHEDULING_RULES, EAM_PM_SCHEDULING_RULES_S, EAM_PM_SET_NAMES, and EAM_PM_LAST_SERVICE store definitions, generated schedulings, rules, set naming, and last-service state.
• Asset and meter tables: CSI_COUNTERS_B, CSI_COUNTER_ASSOCIATIONS, and CSI_COUNTER_TEMPLATE_B support runtime and meter-based PM rules.
• Work order and job tables: EAM_JOB_COMPLETION_TXNS, MTL_EAM_ASSET_ACTIVITIES, WIP_DISCRETE_JOBS, and EAM_WO_STATUSES_V supply maintenance activity and work order context.
• DUAL is used for single-row expression evaluation.

Usage Notes

EAM_PMDEF_PUB is referenced by EAM_METERS_UTIL, EAM_OBJECTINSTANTIATION_PUB, EAM_PMDEF_PUB_W, and additional wrapper packages, confirming its role as a shared service called during meter processing and object instantiation. It is typically invoked from Oracle Forms in the Enterprise Asset Management module when users create, update, or instantiate PM definitions, from concurrent programs that automate PM scheduling generation, and from custom PL/SQL extensions. Because it follows the FND_API public API standard, callers must initialize the API context, check the returned x_return_status, and persist or roll back according to the API contract; direct DML against the underlying EAM_PM_* tables should be avoided in favor of this documented API.