Results for “eng_change_logs_b”

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

Overview

ENG_CHANGE_LOGS_B is a base table in the ENG (Engineering) schema of Oracle E-Business Suite, documented as valid in both release 12.1.1 and 12.2.2. Its stated purpose is to store change log information generated by the Engineering Change Management (ECM) functionality. In practice, the table records the audit trail of revisions and change orders applied to engineered items, capturing which change affected which item revision, in which organization, and how that change propagated through the product structure. Because engineering changes flow from change orders into revised items, bills of material, and routings, this table functions as a transactional ledger of change history rather than as a master data repository.

The ETRM relationship data classifies this object heuristically as standalone within a Data Vault model. That classification reflects a narrow foreign-key footprint: the only documented outbound reference is REVISED_ITEM_SEQUENCE_ID pointing to ENG_REVISED_ITEMS. As a modeling suggestion, a standalone classification indicates the table could be treated as an independent satellite or transaction-style entity keyed by its own surrogate identifier, rather than as a pure hub or link, since it carries descriptive change attributes alongside its own identity.

Key Information Stored

The documented physical schema for 12.2.2 contains 16 columns. The most operationally significant are:

• CHANGE_LOG_ID — the surrogate primary key uniquely identifying each change log record.
• CHANGE_ID — the engineering change order identifier that produced the log entry; a business-key candidate when combined with line-level attributes.
• CHANGE_LINE_ID — the specific line of the change order to which the log row relates.
• LOG_CLASSIFICATION_CODE and LOG_TYPE_CODE — controlled codes describing the category and nature of the logged change event.
• LOCAL_CHANGE_ID and LOCAL_CHANGE_LINE_ID — the change and change line identifiers as known in the local (source) organization, supporting multi-organization propagation.
• LOCAL_ORGANIZATION_ID — the organization in which the originating change was defined.
• REVISED_ITEM_SEQUENCE_ID — the documented foreign key to ENG_REVISED_ITEMS, linking the log to a specific item revision.
• LOCAL_REVISED_ITEM_SEQUENCE_ID — the corresponding revised item in the local organization.
• CHANGE_PROPAGATION_MAP_ID — identifies the propagation mapping used when a change is distributed across organizations or structures.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard EBS WHO audit columns.

The surrogate key is CHANGE_LOG_ID; the natural composite of CHANGE_ID, CHANGE_LINE_ID, and REVISED_ITEM_SEQUENCE_ID is the most likely business-key candidate for uniqueness in practice.

Common Use Cases and Queries

Typical usage centers on change history reporting and revision traceability. Analysts join this table to ENG_REVISED_ITEMS to reconstruct which revisions were affected by a given change order:

• Change-order audit reports listing all affected item revisions and their organizations.
• Multi-organization propagation analysis using LOCAL_ORGANIZATION_ID and CHANGE_PROPAGATION_MAP_ID.
• Reconciliation of local versus global change identifiers.

A representative query pattern selects CHANGE_ID, CHANGE_LINE_ID, LOG_TYPE_CODE, and REVISED_ITEM_SEQUENCE_ID from ENG_CHANGE_LOGS_B, filtering on LOCAL_ORGANIZATION_ID and joining to ENG_REVISED_ITEMS on the sequence identifier to resolve the revised item and its parent item. Because ECM data is organization-sensitive, queries should always constrain on organization to avoid cross-organization duplication.

Related Objects

The documented foreign key establishes the primary dependency on ENG_REVISED_ITEMS. Beyond that, meaningful relationships include:

• ENG_REVISED_ITEMS — joined via REVISED_ITEM_SEQUENCE_ID; the parent revision record for each log entry.
• ENG_CHANGE_ORDERS / change order headers — referenced through CHANGE_ID and CHANGE_LINE_ID.
• ENG_CHANGE_ORDER_LINES — the line-level detail underlying CHANGE_LINE_ID.
• ORG_ORGANIZATION_DEFINITIONS — resolves LOCAL_ORGANIZATION_ID to an organization name.
• FND_USER — resolves CREATED_BY and LAST_UPDATED_BY.
• Engineering change propagation components referenced by CHANGE_PROPAGATION_MAP_ID.

These relationships make ENG_CHANGE_LOGS_B a supporting audit table for ECM reporting rather than a primary transaction driver.