Results for “eng_change_reasons”

50+ results




Overview
Explore in AI Chat

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

Overview

The ENG.ENG_CHANGE_REASONS table is a reference (lookup) table within the Oracle E-Business Suite Engineering (ENG) module that stores the valid reasons an engineering change order (ECO) may be raised. It provides standardized, organization-scoped reason codes that are attached to change orders created in ENG_ENGINEERING_CHANGES, supporting consistent categorization, approval routing, and reporting of engineering changes across a given inventory organization.

The table is owned by the ENG schema and is documented as VALID in ETRM 12.2.2. Based on the provided foreign key and unique key structure, the heuristic Data Vault classification is hub-leaning. This is a modeling suggestion rather than a product-declared fact: the table carries its own business key (ENG_CHANGE_REASON_CODE, ORGANIZATION_ID) and is referenced by other tables, which is characteristic of a hub entity in a Data Vault model. In EBS terms, however, it functions as a simple organization-specific lookup rather than a transactional entity.

Key Information Stored

The physical schema documents 30 columns. The following are the most significant for integration and reporting purposes:

  • ENG_CHANGE_REASON_CODE — the business identifier for the reason (e.g., a user-defined code describing why the change is being made).
  • ORGANIZATION_ID — scopes the reason to a specific inventory organization, allowing different reason lists per organization.
  • DESCRIPTION — the human-readable text of the reason displayed to users and printed on change order reports.
  • DISABLE_DATE — the date on which the reason becomes inactive; used to prevent selection of obsolete reasons.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns for change tracking and accountability.
  • REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context identifying the process that last touched the row.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle Flexfield enablement columns, available for client-specific descriptive attributes.
  • ZD_EDITION_NAME — a partitioning/edition column documented in the unique index, used to distinguish logical editions of the data.

The primary key is ENG_CHANGE_REASONS_PK, defined on the composite of ENG_CHANGE_REASON_CODE and ORGANIZATION_ID. This composite key is therefore both the surrogate primary key and the natural business key. A separate unique index, ENG_CHANGE_REASONS_U1, is defined on ENG_CHANGE_REASON_CODE, ORGANIZATION_ID, and ZD_EDITION_NAME, reinforcing the same business-key combination while accounting for the edition discriminator.

Common Use Cases and Queries

The most frequent requirement is populating a validation or list-of-values for ECO entry, and reporting on change activity by reason. A typical active-reason lookup is:

  • Querying active reasons for an organization: SELECT eng_change_reason_code, description FROM eng.eng_change_reasons WHERE organization_id = :org_id AND (disable_date IS NULL OR disable_date > SYSDATE);
  • Joining to change orders to report reason usage: SELECT c.change_notice, r.description FROM eng.eng_engineering_changes c, eng.eng_change_reasons r WHERE c.reason_code = r.eng_change_reason_code AND c.organization_id = r.organization_id;
  • Auditing recent setup changes: SELECT eng_change_reason_code, last_update_date, last_updated_by FROM eng.eng_change_reasons WHERE last_update_date > :from_date;

Other uses include driving approvals or workflow conditions based on reason, feeding data warehouses that analyze change volume by cause, and validating ECO imports against the defined reason list.

Related Objects

The documented foreign key relationship shows that this table is referenced by the engineering change transaction table:

  • ENG_ENGINEERING_CHANGES — the primary dependent table; its REASON_CODE and ORGANIZATION_ID columns join back to ENG_CHANGE_REASONS.ENG_CHANGE_REASON_CODE and ENG_CHANGE_REASONS.ORGANIZATION_ID respectively. This is the principal integration point.
  • ORG_ORGANIZATION_DEFINITIONS — the standard organization validation source for the ORGANIZATION_ID foreign key.
  • FND_LOOKUPS / FND_FLEX_VALUES — commonly referenced indirect sources providing related lookup or flexfield validation behavior.
  • ENG_ENGINEERING_CHANGE_* revision and routing tables — downstream consumers of the change entity that inherit the reason for reporting purposes.

Because the table is a hub-leaning lookup, it should be treated as a small, stable reference dimension in extraction and warehouse designs, joined to change order facts through the composite key.