Search Results eam_pm_scheduling_rules_s

Overview

EAM_PMDEF_PUB is the public API package body for Preventive Maintenance (PM) definitions within Oracle Enterprise Asset Management (EAM). It belongs to the APPS schema and is classified as a public (PUB) API, meaning it is exposed for external invocation by forms, concurrent programs, and custom extensions. The package encapsulates the business logic required to create, validate, schedule, and instantiate PM definitions for maintainable assets. Because preventive maintenance is driven by scheduling rules — day interval, runtime, and list-date based — the package plays a central role in translating maintenance strategy configuration into executable work orders.

This object is directly relevant to installations querying eam_pm_scheduling_rules_s. EAM_PMDEF_PUB references the EAM_PM_SCHEDULING_RULES and EAM_PM_SCHEDULING_RULES_S tables, making it the primary API through which scheduling rule records are created, validated, merged, and applied during PM instantiation.

Key Procedures and Functions

The package exposes 21 documented procedures and functions. Creation and maintenance entry points include CREATE_PM_DEF and UPDATE_PM_DEF, which persist PM definition headers and associated activities. INSTANTIATE_PM_DEF and INSTANTIATE_PM_DEFS generate PM instances (schedulings) from existing definitions.

• VALIDATE_PM_HEADER — validates PM definition header attributes.
• VALIDATE_PM_DAY_INTERVAL_RULE / VALIDATE_PM_DAY_INTERVAL_RULES — validate day-interval scheduling rules, singly and in sets.
• VALIDATE_PM_RUNTIME_RULE / VALIDATE_PM_RUNTIME_RULES — validate runtime (meter/counter based) scheduling rules.
• VALIDATE_PM_LIST_DATE / VALIDATE_PM_LIST_DATE_RULES — validate list-date scheduling rules.
• VALIDATE_PM_HEADER_AND_RULES — combined validation of the header and all attached rules.
• VALIDATE_PM_ACTIVITY / VALIDATE_PM_ACTIVITIES — validate individual and multiple PM activities.
• SORT_TABLE_BY_DATE / SORT_TABLE_BY_NUMBER — PL/SQL table sorting utilities (PLITBLM) used to order rules or activities.
• MERGE_RULES — consolidates scheduling rules, resolving overlaps into an effective rule set.
• GET_PM_LAST_ACTIVITY, UPDATE_PM_LAST_CYCLIC_ACT, UPDATE_PM_LAST_SERVICE_READING — maintain last-service state used by runtime and cyclic scheduling calculations.

Tables Accessed

The package reads and writes core EAM PM tables via APPS synonyms. Scheduling rule persistence and validation target EAM_PM_SCHEDULING_RULES and EAM_PM_SCHEDULING_RULES_S. Generated PM instances are held in EAM_PM_SCHEDULINGS and EAM_PM_SCHEDULINGS_S, with last-service state in EAM_PM_LAST_SERVICE and activities in EAM_PM_ACTIVITIES. Set membership is resolved through EAM_PM_SET_NAMES. Counter and meter data — required by runtime rules — comes from CSI_COUNTERS_B, CSI_COUNTER_ASSOCIATIONS, and CSI_COUNTER_TEMPLATE_B. Completion and status information is drawn from EAM_JOB_COMPLETION_TXNS, EAM_WO_STATUSES_V, WIP_DISCRETE_JOBS, MTL_EAM_ASSET_ACTIVITIES, and MTL_SYSTEM_ITEMS_B_KFV.

Usage Notes

EAM_PMDEF_PUB is invoked whenever a PM definition is created, updated, or instantiated through the EAM maintenance UI. It is called by four other database packages, and it delegates shared utility work to EAM_COMMON_UTILITIES_PVT, EAM_OBJECTINSTANTIATION_PUB, and Oracle foundation APIs such as FND_API, FND_MSG_PUB, FND_MESSAGE, FND_FILE, and FND_GLOBAL. Because validation and merge logic is exposed publicly, custom code should call the VALIDATE_* and MERGE_RULES interfaces rather than manipulating EAM_PM_SCHEDULING_RULES_S directly, ensuring scheduling-rule integrity is preserved.