Search Results eam_pm_set_names_u1

Overview

The EAM.EAM_PM_SET_NAMES table stores set name definitions used by Oracle Enterprise Asset Management (EAM) Preventive Maintenance schedules. It functions as a lookup and grouping structure within the Preventive Maintenance module, allowing organizations to organize PM schedules into named sets that share a common purpose, asset class, or maintenance strategy. The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and is registered under the FND Design Data EAM.EAM_PM_SET_NAMES.

The central business rule attached to this table is that within EAM_PM_SCHEDULINGS, only one Preventive Maintenance Schedule may exist for a unique combination of asset activity association and set name. This makes EAM_PM_SET_NAMES the controlling reference for set-level uniqueness in PM scheduling. Based on the mined foreign key and structural data, the table is heuristically classified as hub-leaning, meaning it behaves primarily as a primary-key-driven entity referencing downstream transactional data rather than as a link or satellite.

Key Information Stored

The table contains 27 documented columns, of which the following are most operationally significant:

• SET_NAME_ID (NUMBER) — The surrogate primary key, defined by EAM_PM_SET_NAMES_PK and enforced by the unique index EAM_PM_SET_NAMES_U1 on the APPS_TS_TX_IDX tablespace. This is the column referenced by dependent tables.
• SET_NAME (VARCHAR2 80) — The descriptive business name assigned to the PM set. It carries the user-facing identity of the set.
• DESCRIPTION (VARCHAR2 240) — Free-text description of the set's purpose or scope.
• END_DATE (DATE) — Effective end date of the PM set, supporting date-effective life cycle management.
• OWNING_ORGANIZATION_ID (NUMBER) — The organization that currently owns the PM set, enabling multi-org data separation.
• LOCAL_FLAG — Indicates whether the set is local to the owning organization.
• Standard who columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN provide auditability.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 (VARCHAR2 150) — Descriptive Flexfield (DFF) columns that allow customer-specific extensibility on each set name record.

While SET_NAME_ID is the documented unique index, SET_NAME combined with OWNING_ORGANIZATION_ID typically serves as the functional business-key candidate for lookups.

Common Use Cases and Queries

EAM implementers and developers query this table to list available PM sets for selection, to validate that a set exists before creating schedules, and to report on scheduling coverage.

• Listing active sets for an organization:

  SELECT set_name_id, set_name, description
  FROM eam.eam_pm_set_names
  WHERE owning_organization_id = :org_id
    AND (end_date IS NULL OR end_date > SYSDATE);

• Resolving the set name for a schedule:

  SELECT s.set_name, sc.schedule_name
  FROM eam.eam_pm_set_names s,
       eam.eam_pm_schedulings sc
  WHERE sc.set_name_id = s.set_name_id;

• Extracting DFF values for reporting by concatenating ATTRIBUTE_CATEGORY with the relevant ATTRIBUTE columns.
• Detecting orphaned or expired sets by comparing END_DATE with current schedules.

Related Objects

The most significant dependent object is EAM_PM_SCHEDULINGS, which references this table through the SET_NAME_ID column (FK: EAM_PM_SCHEDULINGS.SET_NAME_ID → EAM.EAM_PM_SET_NAMES). Any query joining schedules to their parent set relies on this relationship. Beyond the documented FK, related EAM objects typically include preventive maintenance program and template tables, asset activity associations used to enforce the uniqueness rule, EAM organization definitions referenced by OWNING_ORGANIZATION_ID, and standard Oracle Applications audit and DFF views generated from the ATTRIBUTE columns. Because the table behaves as a hub, its primary integration path is inbound key resolution from EAM_PM_SCHEDULINGS rather than outbound reference fan-out.