Search Results eam_org_maint_defaults




Overview
Explore in AI Chat

Overview

EAM.EAM_ORG_MAINT_DEFAULTS is a configuration table in Oracle Enterprise Asset Management (EAM) that stores maintenance organization–specific defaults for several types of objects. Unlike transactional EAM tables that record work orders, meter readings, or asset activity history, this table functions as a reference and defaulting layer. It allows an organization to predefine attributes such as accounting class, activity codes, work order type, and planning behavior for a given object, so that when maintenance documents are created, appropriate values can be derived automatically rather than entered manually.

The table is owned by the EAM schema and is documented as VALID in ETRM for releases 12.1.1 and 12.2.2, with a physical schema of 21 columns. A heuristic Data Vault classification mined from its foreign key structure identifies it as standalone, meaning it is neither a classic hub nor a dependent satellite in that modeling sense; it behaves as an independent configuration or reference entity keyed by organization and object. In practice, it is best treated as a maintenance-organization settings satellite whose grain is defined by object type, object identifier, and organization.

Key Information Stored

The table is defined at the grain of an object within a specific maintenance organization. The unique index EAM_ORG_MAINT_DEFAULTS_U1 on (OBJECT_ID, OBJECT_TYPE, ORGANIZATION_ID) constitutes the business-key candidate: a given object of a given type may hold at most one defaults row per organization. Note that no single surrogate primary key column is documented separately; the unique index acts as the effective identifying key.

The most significant columns are:

Common Use Cases and Queries

Primary use cases include retrieving default work order attributes for an asset before work order creation, validating that a maintenance organization has defaults defined for a set of assets, and reporting on planning or tagging policy by organization. A typical lookup joins the defaults to the asset definition:

  • Query defaults for an object: SELECT * FROM eam.eam_org_maint_defaults WHERE organization_id = :org AND object_type = :type AND object_id = :id
  • List all defaults for an organization: SELECT object_type, object_id, work_order_type, accounting_class_code FROM eam.eam_org_maint_defaults WHERE organization_id = :org
  • Resolve the functional area: SELECT d.*, f.* FROM eam.eam_org_maint_defaults d, pay.pay_functional_areas f WHERE d.area_id = f.functional_area_id
  • Policy audit: count objects where tagging_required_flag = 'Y' or notification_required = 'Y' by organization.

Because the table is keyed by organization, it is a natural source for cross-organization consistency reports comparing default work order types and accounting classes.

Related Objects

  • PAY_FUNCTIONAL_AREAS — referenced via AREA_ID; the only documented foreign key relationship.
  • EAM_ORG_MAINT_DEFAULTS_U1 — the unique index enforcing the (OBJECT_ID, OBJECT_TYPE, ORGANIZATION_ID) business key.
  • EAM Organizations / HR_OPERATING_UNITS — provide the ORGANIZATION_ID context for maintenance organizations.
  • EAM_WORK_ORDERS / WIP Entities — consume these defaults when work order attributes are defaulted.
  • EAM Assets (EAM_ASSETS_B or equivalent asset definition) — supply the OBJECT_ID/OBJECT_TYPE values resolved against these defaults.
  • FND Audit Columns — FND_USER references for CREATED_BY and LAST_UPDATED_BY.