Search Results eam_construction_estimates




Overview
Explore in AI Chat

Overview

EAM_CONSTRUCTION_ESTIMATES is a transactional table in the Oracle E-Business Suite Enterprise Asset Management (EAM) module, residing in the EAM schema. It stores estimate header records that capture cost and effort estimations derived from construction units—the constituent work packages, operations, or resources assembled to define the scope of a maintenance or construction activity. In EBS 12.1.1 and 12.2.2, this table functions as the master header for estimates that can subsequently be associated with work orders, service incidents, repairs, and other downstream EAM and CRM transactions.

From a Data Vault modeling perspective, the metadata's heuristic classification identifies this object as hub-leaning. This suggests the table behaves primarily as a business entity hub: its ESTIMATE_ID uniquely identifies each estimate, and the surrounding foreign key infrastructure connects it outward as a referenced parent rather than as a dependent child. The table's role is thus foundational—many satellite-style details and link-style associations hang off the ESTIMATE_ID key rather than being embedded within the header itself. Note this classification is a modeling suggestion, not an Oracle-defined construct.

Key Information Stored

The documented physical schema (ETRM 12.2.2) contains 28 columns. The most significant are:

  • ESTIMATE_ID — The surrogate primary key (constraint ECE_PK), a system-generated identifier that uniquely distinguishes each estimate record and serves as the target of all foreign key references.
  • ORGANIZATION_ID — Identifies the inventory or asset organization under which the estimate is defined, critical for multi-organization EAM deployments.
  • ESTIMATE_NUMBER — The user-facing business identifier for the estimate; a natural business-key candidate for lookups and reporting.
  • ESTIMATE_DESCRIPTION — Free-text description of the estimate's purpose or scope.
  • GROUPING_OPTION — Controls how construction units are grouped when the estimate is expanded or rolled up.
  • PARENT_WO_ID — References a parent work order, supporting hierarchical estimation structures.
  • CREATE_PARENT_WO_FLAG — Indicates whether a parent work order should be generated from this estimate.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS WHO audit columns tracking insert and update provenance.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — The DFF (descriptive flexfield) extension columns reserved for client-specific customization without schema changes.

Common Use Cases and Queries

Typical reporting patterns include retrieving estimates for a given organization, tracing estimates to their downstream work orders, and reconciling estimate headers with their detail rows.

  • Lookup by business key: SELECT * FROM EAM.EAM_CONSTRUCTION_ESTIMATES WHERE ESTIMATE_NUMBER = :num;
  • Organization-scoped listing: SELECT ESTIMATE_ID, ESTIMATE_NUMBER, ESTIMATE_DESCRIPTION FROM EAM.EAM_CONSTRUCTION_ESTIMATES WHERE ORGANIZATION_ID = :org_id;
  • Header-to-association join: SELECT e.ESTIMATE_NUMBER, a.* FROM EAM.EAM_CONSTRUCTION_ESTIMATES e, EAM.EAM_ESTIMATE_ASSOCIATIONS a WHERE e.ESTIMATE_ID = a.ESTIMATE_ID;
  • Work-order linkage: join to EAM_WORK_ORDER_DETAILS on ESTIMATE_ID to report estimates that spawned work order detail lines.

Analysts commonly use these queries for cost-estimation audits, work-order planning reports, and service-repair estimate traceability across EAM and CRM modules.

Related Objects

The following objects reference EAM_CONSTRUCTION_ESTIMATES through ESTIMATE_ID foreign keys:

  • EAM_ESTIMATE_ASSOCIATIONS — Links estimates to associated entities; join on ESTIMATE_ID.
  • EAM_WORK_ORDER_DETAILS — Detail lines of work orders tied to estimates.
  • CS_ESTIMATE_DETAILS — CRM/service estimate detail records referencing the EAM estimate header.
  • CS_INCIDENTS_ALL_B — Service incidents that carry an ESTIMATE_ID reference.
  • CS_REPAIRS_ALL — Repair records associated with estimates.

Together these dependencies confirm the table's hub-leaning position as a shared estimate master consumed across EAM and Service (CS) functionality in Release 12.