Results for “eam_construction_units”

50+ results




Overview
Explore in AI Chat

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

Overview

EAM_CONSTRUCTION_UNITS is the master (header) table for construction units used within Oracle Enterprise Asset Management (EAM) in Oracle E-Business Suite 12.1.1 and 12.2.2. A construction unit represents a logical grouping of assets, activities, or work scope that can be budgeted, estimated, and tracked as a single unit of capital or maintenance work. The table stores the construction unit name, its effectivity period, the operating organization in which it was created, and descriptive flexfield information.

The table resides in the EAM schema and is classified as VALID, meaning it is an actively maintained dictionary object. From a Data Vault modeling perspective, the heuristic classification of this table is hub-leaning: CU_ID functions as the durable business key surrogate that anchors the construction unit entity, while the referenced detail and association tables act as satellites or links. This makes EAM_CONSTRUCTION_UNITS the natural integration point for construction-unit-centric reporting.

Key Information Stored

The table contains 27 documented columns. The most operationally significant are:

  • CU_ID — Surrogate primary key (constraint CU_ID_PK) that uniquely identifies each construction unit and is the join key to all dependent tables.
  • CU_NAME — The business-facing construction unit name; the strongest candidate for a natural/business key.
  • DESCRIPTION — Free-text description of the construction unit's purpose.
  • ORGANIZATION_ID — The organization in which the construction unit was created; supports multi-org security and reporting.
  • CU_EFFECTIVE_FROM and CU_EFFECTIVE_TO — The effectivity (start and end) dates controlling when the unit is active.
  • ATTRIBUTE_CATEGORY through ATTRIBUTE15 — Descriptive flexfield (DFF) segments used to capture customer-specific attributes.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns for change tracking and accountability.

Note that while CU_NAME is the logical business identifier, the documented PK is the surrogate CU_ID; no separate unique index on CU_NAME is documented in the supplied metadata.

Common Use Cases and Queries

Typical scenarios include listing active construction units by organization, enforcing effectivity windows during estimate creation, and joining to estimates for cost rollups.

  • Active units for an organization:
    SELECT cu_id, cu_name, cu_effective_from, cu_effective_to FROM eam.eam_construction_units WHERE organization_id = :org_id AND TRUNC(SYSDATE) BETWEEN cu_effective_from AND NVL(cu_effective_to, SYSDATE + 1);
  • Construction unit with associated estimates: join EAM_ESTIMATE_ASSOCIATIONS on CU_ID to retrieve all estimates tied to a unit.
  • Detail-level reporting: join EAM_CONSTRUCTION_UNIT_DETAILS on CU_ID to expand line items within each unit.
  • DFF reporting: select ATTRIBUTE_CATEGORY and applicable ATTRIBUTE columns for organization-specific classification.

These patterns underpin capital project dashboards, maintenance budgeting reports, and audit extracts verifying effectivity compliance.

Related Objects

The FK metadata identifies two tables that reference EAM_CONSTRUCTION_UNITS via CU_ID:

  • EAM_CONSTRUCTION_UNIT_DETAILS — Child table holding the detail lines that compose a construction unit; joined by EAM_CONSTRUCTION_UNIT_DETAILS.CU_ID = EAM_CONSTRUCTION_UNITS.CU_ID.
  • EAM_ESTIMATE_ASSOCIATIONS — Associates estimates with construction units; joined by EAM_ESTIMATE_ASSOCIATIONS.CU_ID = EAM_CONSTRUCTION_UNITS.CU_ID.

Related EBS objects frequently joined in EAM reporting include HR_ALL_ORGANIZATION_UNITS (via ORGANIZATION_ID), EAM_ESTIMATES, and the standard EAM asset and work order tables. Together these objects form the construction-unit data model: a hub (EAM_CONSTRUCTION_UNITS) surrounded by detail and association satellites keyed on CU_ID.