Results for “eam_estimate_associations”

48 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The EAM.EAM_ESTIMATE_ASSOCIATIONS table is a transactional detail object within the Oracle E-Business Suite Enterprise Asset Management (EAM) module. It stores the individual association lines that belong to a single construction estimate, linking each estimate to the construction unit, activity, accounting class, and difficulty code that drive cost and resource rollups. In Oracle EBS 12.1.1 and 12.2.2, the table is owned by the EAM schema and carries a VALID status in the data dictionary, with 15 documented columns in the 12.2.2 physical schema.

From a Data Vault modeling perspective, the metadata's heuristic classification of this object is link. This is consistent with its structure: the table resolves a many-to-many style relationship between a construction estimate and the construction units, activities, and difficulty codes it references. Rather than storing descriptive business attributes on its own, it primarily captures the association and the quantities and multipliers that apply to each associated unit. Practitioners building a vault or dimensional model should treat ESTIMATE_ASSOCIATION_ID as the record grain key and the various foreign keys as the link endpoints.

Key Information Stored

The dominant identifier is ESTIMATE_ASSOCIATION_ID, the surrogate primary key (constraint EEN_PK) that uniquely identifies each association row. It is generated by the application and carries no business meaning of its own.

The composite of ESTIMATE_ID, CU_ID, and DIFFICULTY_ID functions as the meaningful business key candidate, since it uniquely describes the association in business terms. The audit columns follow standard EBS conventions and can be used for change tracking and audit reporting.

Common Use Cases and Queries

Typical reporting scenarios include estimating cost per construction unit, analyzing resource multipliers by difficulty code, and reconciling estimate lines against activities. A common query pattern joins the association table to its parent estimate and construction unit:

SELECT eea.estimate_association_id, eea.estimate_id, eea.cu_id, eea.cu_qty, eea.difficulty_id, eea.resource_multiplier
FROM eam.eam_estimate_associations eea, eam.eam_construction_estimates ece, eam.eam_construction_units ecu
WHERE eea.estimate_id = ece.estimate_id
AND eea.cu_id = ecu.cu_id
AND eea.organization_id = :org_id;

Analysts frequently aggregate CU_QTY and RESOURCE_MULTIPLIER grouped by DIFFICULTY_ID or ACCT_CLASS_CODE to produce cost simulation and rollup reports. Audit and reconciliation scripts filter on LAST_UPDATE_DATE to identify recently modified associations.

Related Objects

The most significant related objects, based on the documented foreign key and primary key relationships, are:

  • EAM_CONSTRUCTION_ESTIMATES — joined via EAM_ESTIMATE_ASSOCIATIONS.ESTIMATE_ID; the parent estimate header.
  • EAM_CONSTRUCTION_UNITS — joined via EAM_ESTIMATE_ASSOCIATIONS.CU_ID; the construction unit master.
  • EAM_DIFFICULTY_CODES — joined via EAM_ESTIMATE_ASSOCIATIONS.DIFFICULTY_ID; the difficulty code lookup.
  • EAM_ESTIMATE_ASSOCIATIONS itself, keyed by ESTIMATE_ASSOCIATION_ID (EEN_PK), acts as the child in each of these relationships.

These relationships define the core join paths used in EAM estimating and cost reporting, and any user-defined materialized view or custom report should preserve these documented key columns.