Results for “eng_change_order_revisions”

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

Overview

ENG_CHANGE_ORDER_REVISIONS is a table in the ENG (Engineering) schema of Oracle E-Business Suite, present and valid in both release 12.1.1 and 12.2.2. It stores the revision records associated with engineering change orders (ECOs), capturing the specific revision identifiers that an ECO applies to within a given organization. In this sense it corresponds to the "ECO reasons"/revision cross-reference maintained by the Engineering module, linking each change notice to the item revisions it governs. Its documented column count is 34, and it carries a surrogate primary key plus two unique indexes that serve as business-key candidates. From a data-modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification, meaning the table most plausibly behaves as a satellite recording descriptive and versioned attributes about an ECO/revision relationship, rather than as a standalone hub or a pure link. This classification is a heuristic recommendation, not an authoritative designation.

Key Information Stored

The table distinguishes a system-generated surrogate key from business-meaningful identifiers:

• REVISION_ID — the surrogate primary key (ENG_CHANGE_ORDER_REVISIONS_PK) and also the target of unique index U2, ensuring each revision record is uniquely addressable.
• CHANGE_NOTICE, ORGANIZATION_ID, REVISION — the composite business-key candidate defined by unique index ENG_CHANGE_ORDER_REVISIONS_U1, guaranteeing that a given revision is recorded once per change notice and organization.
• CHANGE_ID — an additional reference to the change context.
• START_DATE, END_DATE — effective-dating columns indicating the validity period of the revision assignment.
• COMMENTS — free-text descriptive notes.
• ORIGINAL_SYSTEM_REFERENCE — a reference to the originating source system, useful for migration and multi-source reconciliation.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard EBS flexfield (DFF) columns for extensibility.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN record who created and last modified each row.
• Program/concurrent columns — PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, and REQUEST_ID capture the concurrent program context that inserted or updated the row.

Common Use Cases and Queries

Typical reporting scenarios include retrieving all revisions affected by a given ECO, validating that revision dates fall within expected windows, and joining revision data to item and change-notice information for engineering audit reports. A common pattern is to resolve the ECO through the change notice and then list its revisions:

• Join ENG_CHANGE_ORDER_REVISIONS to ENG_ENGINEERING_CHANGES on CHANGE_NOTICE and ORGANIZATION_ID to obtain ECO-level descriptive data alongside revision detail.
• Filter by REVISION and ORGANIZATION_ID to trace the lifecycle of a specific item revision.
• Use START_DATE/END_DATE to build effective-dated revision histories.
• Query the DFF columns for organization-specific extension attributes.

A representative SQL pattern joins on the documented foreign-key columns:

• SELECT r.REVISION_ID, r.CHANGE_NOTICE, r.ORGANIZATION_ID, r.REVISION, c.* FROM ENG.ENG_CHANGE_ORDER_REVISIONS r JOIN ENG.ENG_ENGINEERING_CHANGES c ON r.CHANGE_NOTICE = c.CHANGE_NOTICE AND r.ORGANIZATION_ID = c.ORGANIZATION_ID;

Related Objects

The principal documented relationship is a foreign-key reference from this table to ENG_ENGINEERING_CHANGES. The most significant related objects are:

• ENG_ENGINEERING_CHANGES — referenced via CHANGE_NOTICE and ORGANIZATION_ID; the parent change-notice table providing ECO master data.
• ENG_CHANGE_ORDER_REVISIONS_PK — the primary-key constraint/index on REVISION_ID.
• ENG_CHANGE_ORDER_REVISIONS_U1 — the unique business-key index on (CHANGE_NOTICE, ORGANIZATION_ID, REVISION).
• ENG_CHANGE_ORDER_REVISIONS_U2 — the unique index on REVISION_ID.
• The Engineering module ECO and revision maintenance APIs/concurrent programs that consume PROGRAM_ID, PROGRAM_UPDATE_DATE, and REQUEST_ID.

Because the ETRM metadata for this object is concise, the above relationships are grounded in the documented primary keys, unique indexes, and foreign keys; broader integration points should be confirmed against the specific EBS instance.