Search Results default_implement

Overview

EAM_PM_SCHEDULINGS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, part of the Enterprise Asset Management (EAM) module. It presents individual Preventive Maintenance (PM) schedules, denormalizing the core scheduling definition in EAM_PM_SCHEDULINGS against asset instances, master item information, set names, work order statuses, and reviewing personnel. Its purpose is to give report and integration developers a single, human-readable row per active PM schedule without requiring knowledge of the underlying join logic.

The view filters out templates (NVL(PM.TMPL_FLAG,'N') = 'N') and non-maintainable assets, so it returns only operational schedules applied to real maintainable asset instances. It is valid and available in both 12.1.1 and 12.2.2; in the latter the documented base object list is expanded to include HR and MTL lookups that support secure, formatted output. For users searching the term pm_source_code, this is the view that exposes that column directly — PM.SOURCE_CODE is aliased as PM_SOURCE_CODE.

Underlying Base Objects

The view is defined primarily over the EAM_PM_SCHEDULINGS synonym, with joins to the following documented objects:

• EAM_PM_SCHEDULINGS — the driving table holding the PM schedule header (effective dates, rescheduling point, lead time, source code/line, scheduling method, cycles).
• CSI_ITEM_INSTANCES — supplied for asset number, instance number, serial, description, and organization context, joined on PM.MAINTENANCE_OBJECT_ID = CII.INSTANCE_ID.
• MTL_SYSTEM_ITEMS_VL — master item number, concatenated segments, description and item type for the asset.
• MTL_PARAMETERS — master organization context, joined on the asset's last valid organization.
• EAM_PM_SET_NAMES — the named PM set providing scheduling interval and set name plus localized flags.
• EAM_WO_STATUSES_V — resolves the work order status code into a display value.
• PER_PEOPLE_F / FND_USER / HR packages — resolve reviewer identity (FULL_NAME) and creation/update user details; HR_GENERAL, HR_PERSON_NAME and HR_SECURITY support name formatting and security.
• MFG_LOOKUPS and EAM_PM_ACTIVITIES — legacy lookups and activity references retained in the documented object list.

Key Columns

• PM_SCHEDULE_ID — unique identifier of the PM schedule; the join key to schedule lines, activities, and work orders.
• PM_SOURCE_CODE / PM_SOURCE_LINE — the origin of the schedule (the column users search as pm_source_code); source_line is its companion sequence.
• ORGANIZATION_ID, INVENTORY_ITEM_ID, INSTANCE_ID, ASSET_NUMBER, SERIAL_NUMBER — asset identity and asset group context.
• SCHEDULING_METHOD_CODE, TYPE_CODE, INTERVAL_PER_CYCLE, CURRENT_CYCLE, CURRENT_SEQ, BASE_DATE, BASE_READING — scheduling definition and progress within the current cycle.
• FROM_EFFECTIVE_DATE / TO_EFFECTIVE_DATE, LEAD_TIME, RESCHEDULING_POINT, WHICHEVER_FIRST, NON_SCHEDULED_FLAG — timing and trigger rules.
• SET_NAME, SCHEDULING_METHOD_CODE, DEFAULT_IMPLEMENT, AUTO_INSTANTIATION_FLAG, GENERATE_NEXT_WORK_ORDER — set and automation attributes.
• GENERATE_WO_STATUS, WORK_ORDER_STATUS, MAINTENANCE_OBJECT_TYPE, EAM_ITEM_TYPE — output/status flags that indicate whether the schedule generates work orders and in what state.
• ATTRIBUTE1–15, ATTRIBUTE_CATEGORY, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_REVIEWED_DATE, FULL_NAME — descriptive flexfields, audit, and reviewer identity.

Common Use Cases and Queries

The view is commonly used for PM schedule inquiries, asset PM reports, work order generation audits, and integrations that need to know whether a schedule is automated and which source it originated from. A typical query lists PM schedules by asset or organization using PM_SOURCE_CODE:

SELECT pm_schedule_id, organization_id, inventory_item_id, asset_number, name, pm_source_code, pm_source_line, scheduling_method_code, current_cycle, from_effective_date, to_effective_date, set_name FROM eam_pm_schedulings_v WHERE pm_source_code = :p_source_code AND organization_id = :p_org ORDER BY asset_number, name;

Another frequent pattern reports schedules that will generate work orders, or those reviewed after a given date, by filtering on generate_next_work_order, auto_instantiation_flag, or last_reviewed_date and joining pm_schedule_id to EAM_PM_ACTIVITIES or EAM_WORK_ORDERS for detail. Because the view resolves item, asset, set name, and status descriptions in one pass, it is a preferred source for custom concurrent programs and EAM operational dashboards rather than querying the base tables individually.