Search Results ego_item_revision




Overview
Explore in AI Chat

Overview

APPS.ENG_CHANGE_HDR_ITEM_SUBJECTS_V is an Oracle E-Business Suite view that flattens the change-subject associations attached to engineering change orders (ECOs) so that each affected item, and where applicable each affected item revision, is presented on a single row together with its change identifier. It belongs to the Engineering (ENG) product family and is commonly used by ECO reporting, workflow notifications, and integration extracts that need a denormalized list of "which item/revision is on which change." The view is defined in the APPS schema and is therefore subject to standard EBS security and synonym conventions.

The view is of particular interest to users searching for ego_item_revision, because the item revision association is stored in ENG_CHANGE_SUBJECTS under the entity name EGO_ITEM_REVISION. The view simplifies that relationship by resolving the revision identifier to a human-readable revision label and by ensuring items are not double-counted when a revision-level subject is also present for the same change.

Underlying Base Objects

The documented base objects referenced by this view are:

The view is a UNION ALL of two branches. The first branch returns item-level subjects where CHANGE_LINE_ID IS NULL and no corresponding revision-level subject (EGO_ITEM_REVISION with a non-null PK3_VALUE) exists for the same change, emitting a NULL ITEM_REVISION. The second branch returns revision-level subjects joined to MTL_ITEM_REVISIONS_B, emitting either REVISION_LABEL or, if that is null, REVISION as ITEM_REVISION.

Key Columns

  • CHANGE_ID — identifier of the engineering change order to which the subject row belongs; joins to the change header.
  • ITEM_NUMBER — the concatenated item key flexfield segments from MTL_SYSTEM_ITEMS_KFV for the affected item.
  • ITEM_REVISION — NULL for item-level-only subjects; otherwise the revision label (falling back to the revision value) resolved from MTL_ITEM_REVISIONS_B.

The absence of organization or item identifier columns beyond the concatenated number should be noted; consumers requiring inventory_item_id or organization_id must join back to the source tables or use alternative views.

Common Use Cases and Queries

Typical uses include listing all items and revisions impacted by a change, generating notification content, and feeding downstream PLM or quality systems. A representative query is:

SELECT change_id, item_number, item_revision
FROM   apps.eng_change_hdr_item_subjects_v
WHERE  change_id = :change_id
ORDER  BY item_number, item_revision NULLS FIRST;

To locate only revision-controlled subjects:

SELECT change_id, item_number, item_revision
FROM   apps.eng_change_hdr_item_subjects_v
WHERE  item_revision IS NOT NULL;

Because the view already suppresses duplicate item rows when a revision subject exists, it is well suited to ECO header reports that must display one line per affected item/revision without additional DISTINCT logic. Ensure the APPS schema and appropriate MO/ENG responsibilities are used when querying.