Search Results eam_pm_set_names_pk
Overview
EAM_PM_SET_NAMES is a table in the EAM (Enterprise Asset Management) schema of Oracle E-Business Suite, holding the definition of Preventive Maintenance (PM) set names. In Oracle EBS, a PM "set" functions as a named grouping construct that organizes preventive maintenance programs, most commonly used to bundle PM schedules for a piece of equipment, an asset hierarchy, or a maintenance program template. The table provides the master list of valid set name definitions that downstream PM scheduling records reference.
Because the EAM_PM_SET_NAMES table serves as the source of a foreign key consumed by EAM_PM_SCHEDULINGS, its heuristic Data Vault classification is hub-leaning. Under a Data Vault modeling approach, this table would naturally map to a hub entity keyed by SET_NAME_ID, with descriptive attributes such as SET_NAME and DESCRIPTION carried in a companion satellite. This classification is a modeling suggestion drawn from the foreign key topology and does not reflect physical implementation in the EBS database.
Key Information Stored
The table contains 27 documented columns in the ETRM 12.2.2 schema. Its most significant attributes include:
- SET_NAME_ID — The surrogate primary key (EAM_PM_SET_NAMES_PK) and the column also exposed through the unique index EAM_PM_SET_NAMES_U1, making it the single documented business-key candidate. It is the value propagated into child records.
- SET_NAME — The user-visible name of the PM set, used for identification in forms and reports.
- DESCRIPTION — Free-text description of the set's purpose or contents.
- END_DATE — Date on which the set name definition becomes inactive or invalid.
- OWNING_ORGANIZATION_ID — Identifies the inventory or maintenance organization that owns the definition, supporting multi-organization data partitioning.
- LOCAL_FLAG — Indicates whether the definition is local to the owning organization or shared from a global level.
- ATTRIBUTE_CATEGORY, ATTRIBUTE1 through ATTRIBUTE15 — The descriptive flexfield (DFF) segment columns that extend the table with client-specific attributes.
- CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit "WHO" columns tracking record creation and modification.
The separation of the surrogate SET_NAME_ID from the human-readable SET_NAME reflects standard EBS design: the surrogate is the stable join key, while SET_NAME carries the business meaning visible to users.
Common Use Cases and Queries
The primary use case is resolving the descriptive content of a PM set behind the scheduling records that reference it. A typical query joins the child to the parent to produce reporting output:
- Listing all active set names for a given organization: select SET_NAME_ID, SET_NAME, DESCRIPTION from EAM_PM_SET_NAMES where OWNING_ORGANIZATION_ID = :org_id and (END_DATE is null or END_DATE > sysdate).
- Reporting PM schedules with their set name context: select s.SET_NAME_ID, n.SET_NAME, n.DESCRIPTION from EAM_PM_SCHEDULINGS s, EAM_PM_SET_NAMES n where s.SET_NAME_ID = n.SET_NAME_ID.
- Identifying orphaned schedules whose set name has ended: join on SET_NAME_ID and filter on END_DATE to detect schedules tied to expired definitions.
- DFF reporting: extracting ATTRIBUTE_CATEGORY and ATTRIBUTE1-15 for organization-specific analysis, using the registered flexfield definition to apply segment labels.
- Duplicate or naming audits: grouping by SET_NAME and OWNING_ORGANIZATION_ID to detect collisions before data loading.
Because SET_NAME_ID is the only documented unique index, queries filtering on SET_NAME should be validated against potential duplicates unless the naming convention is known to guarantee uniqueness.
Related Objects
The documented foreign key relationship establishes EAM_PM_SCHEDULINGS as the principal dependent table:
- EAM_PM_SCHEDULINGS — References EAM_PM_SET_NAMES through the column SET_NAME_ID; this is the direct FK relationship documented in the ETRM metadata.
- EAM_PM_SCHEDULINGS.SET_NAME_ID — The child column carrying the foreign key; the join condition is EAM_PM_SCHEDULINGS.SET_NAME_ID = EAM_PM_SET_NAMES.SET_NAME_ID.
- EAM_PM_SET_NAMES_PK — The primary key constraint on SET_NAME_ID, enforced as the parent key for the FK above.
- EAM_PM_SET_NAMES_U1 — Unique index on SET_NAME_ID, the documented business-key candidate and supporting lookup efficiency.
- EAM_PM_SET_NAMES DFF — The descriptive flexfield registered against ATTRIBUTE_CATEGORY and ATTRIBUTE1-15, which references the table through the application's flexfield metadata rather than a physical constraint.
- OWNING_ORGANIZATION_ID join — Resolves to the organization definition (HR_OPERATING_UNITS / ORG_ORGANIZATION_DEFINITIONS) to describe the owning organization in reports.
Together these objects establish EAM_PM_SET_NAMES as the parent reference point for PM scheduling data in the EAM module.
-
Table: EAM_PM_SET_NAMES
12.2.2
owner:EAM, object_type:TABLE, fnd_design_data:EAM.EAM_PM_SET_NAMES, object_name:EAM_PM_SET_NAMES, status:VALID, product: EAM - Enterprise Asset Management , description: PM Set Names , implementation_dba_data: EAM.EAM_PM_SET_NAMES ,
-
Table: EAM_PM_SET_NAMES
12.1.1
owner:EAM, object_type:TABLE, fnd_design_data:EAM.EAM_PM_SET_NAMES, object_name:EAM_PM_SET_NAMES, status:VALID, product: EAM - Enterprise Asset Management , description: PM Set Names , implementation_dba_data: EAM.EAM_PM_SET_NAMES ,
-
eTRM - EAM Tables and Views
12.1.1
description: Table for storing workflow item type and keys corresponding to a work order ,
-
eTRM - EAM Tables and Views
12.2.2
description: Table for storing workflow item type and keys corresponding to a work order ,
-
eTRM - EAM Tables and Views
12.1.1
description: Table for storing workflow item type and keys corresponding to a work order ,
-
eTRM - EAM Tables and Views
12.2.2
description: Table for storing workflow item type and keys corresponding to a work order ,