Search Results eam_org_maint_defaults_u1

Overview

EAM.EAM_ORG_MAINT_DEFAULTS is an Enterprise Asset Management (EAM) seed table that stores organization-specific maintenance default attributes for multiple types of maintenance objects. When a new Work Order is created against a supported object, Oracle EBS uses the rows in this table to pre-populate the Work Order with default values such as accounting class, activity codes, work order type, planner, and notification flags. The table resides in the APPS_TS_SEED tablespace, which is consistent with its role as a setup and reference data store rather than a high-volume transactional table. It is owned by the EAM schema, holds 21 documented columns, and is classified as VALID in the 12.2.2 ETRM schema.

The maintenance objects for which defaults may be stored are: Maintenance Organization, Asset Category, Asset Group, Asset Group Activity Association, Asset Number, and Asset Number Activity Association. This polymorphic scope is achieved through the OBJECT_TYPE and OBJECT_ID column pair, which identifies which business entity a given default row applies to, further qualified by ORGANIZATION_ID. Based on the FK and index structure mined from the schema, the heuristic Data Vault classification for this table is standalone. In a Data Vault model this suggests treating the table as a self-contained reference or setup entity rather than as a hub, link, or satellite, since its dependent relationships are limited (a single foreign key to PAY_FUNCTIONAL_AREAS) and its primary identity is defined by a composite business key rather than a surrogate key.

Key Information Stored

The table's identity is defined by the unique index EAM_ORG_MAINT_DEFAULTS_U1, which spans OBJECT_ID, OBJECT_TYPE, and ORGANIZATION_ID. This composite is the business-key candidate: no separate surrogate primary key column is documented, so these three columns together enforce uniqueness and scope each default row to a single maintenance object within an operating organization.

• OBJECT_TYPE and OBJECT_ID — identify the maintenance entity to which the defaults apply (e.g., asset category, asset group, asset number, or organization).
• ORGANIZATION_ID — the operating organization context for the default set.
• OWNING_DEPARTMENT_ID — the default owning department assigned to new Work Orders.
• ACCOUNTING_CLASS_CODE — the maintenance accounting class defaulted onto the Work Order.
• AREA_ID — the functional area default; this is the only documented foreign key, referencing PAY_FUNCTIONAL_AREAS.
• ACTIVITY_CAUSE_CODE, ACTIVITY_TYPE_CODE, ACTIVITY_SOURCE_CODE — standard work order activity classification defaults.
• SHUTDOWN_TYPE_CODE — default shutdown classification for the maintenance activity.
• WORK_ORDER_TYPE — the default Work Order type code applied at creation.
• PLANNER_MAINTENANCE — default planner code for the Work Order.
• FIRM_PLANNED_FLAG, PLAN_MAINTENANCE — indicators controlling planning firmness and planned status.
• NOTIFICATION_REQUIRED, TAGGING_REQUIRED_FLAG — flags controlling whether notifications or tagging are required for the resulting Work Order.

Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) provide audit and concurrency tracking.

Common Use Cases and Queries

Typical uses include reporting on the default values that drive Work Order creation, validating that setup rows exist for each asset category or organization, and diagnosing why a new Work Order received unexpected default attributes. A representative query to retrieve defaults for a specific object and organization is:

SELECT OBJECT_TYPE, OBJECT_ID, ORGANIZATION_ID,
       ACCOUNTING_CLASS_CODE, WORK_ORDER_TYPE,
       PLANNER_MAINTENANCE, NOTIFICATION_REQUIRED
FROM   EAM.EAM_ORG_MAINT_DEFAULTS
WHERE  OBJECT_TYPE = :p_object_type
AND    OBJECT_ID   = :p_object_id
AND    ORGANIZATION_ID = :p_org_id;

A completeness check across all maintenance object types can be written by grouping on OBJECT_TYPE and ORGANIZATION_ID to detect missing default sets intended to cover every asset category or asset number. Because the table is seed data, joins to master data such as asset categories, asset groups, or functional areas by OBJECT_ID and AREA_ID are common in reporting extracts.

Related Objects

• PAY_FUNCTIONAL_AREAS — the only documented foreign key target; joined via EAM_ORG_MAINT_DEFAULTS.AREA_ID = PAY_FUNCTIONAL_AREAS.FUNCTIONAL_AREA_ID.
• EAM_ASSET_NUMBERS — potential OBJECT_ID target for asset-number scoped defaults.
• EAM_ASSET_CATEGORIES — potential OBJECT_ID target for asset-category scoped defaults.
• EAM_ASSET_GROUPS — potential OBJECT_ID target for asset-group scoped defaults, including group/activity associations.
• EAM_WORK_ORDERS — the transactional table that consumes these defaults at Work Order creation.
• EAM_ORGANIZATIONS — supplies ORGANIZATION_ID context used to scope default rows.
• HR_ALL_ORGANIZATION_UNITS — source of owning department and organization identifiers.