Search Results ego_item




Overview
Explore in AI Chat

Overview

APPS.ENG_CHANGE_SUBJECTS_V is an Oracle E-Business Suite view that presents a unified list of the "subjects" attached to an engineering change order (ECO). In the Oracle Engineering (ENG) and Product Lifecycle Management (PLM) data model, an engineering change is linked to the items and related entities it affects through subject records. This view consolidates those records so that a single query yields every subject associated with a given CHANGE_ID, regardless of whether the subject originates from the revised-items table (item-level and item-revision-level changes) or from the generic change-subjects table (other entity types).

The view returns a consistent projection of subject identity columns — an entity name, a set of primary-key value columns (PK1 through PK5), and a subject level indicator — which allows consuming programs and reports to resolve what an ECO affects without joining multiple heterogeneous tables. Its role is primarily read-only reporting and integration: change-order browsers, revision history inquiries, and downstream interfaces that must enumerate ECO subjects query this view rather than the base tables directly.

Underlying Base Objects

According to the ETRM metadata for 12.2.2, the view is owned by APPS and is defined over three referenced base objects, each accessed via an APPS synonym:

  • ENG_REVISED_ITEMS — the table holding the items that an engineering change revises, including the revised item identifier, organization, and the new item revision.
  • MTL_ITEM_REVISIONS_B — the base table of item revisions, used to resolve a revision name to its internal revision identifier.
  • ENG_CHANGE_SUBJECTS — the generic change-subject table that stores subjects for entity types other than the revised-item rows handled above, carrying ENTITY_NAME, PK1_VALUE through PK5_VALUE, and SUBJECT_LEVEL.

The view is a UNION of three branches. The first selects from ENG_REVISED_ITEMS, emitting an entity name of EGO_ITEM with the revised item ID mapped to PK1_VALUE and the organization ID mapped to PK2_VALUE, and a subject level of 1. The second branch joins ENG_REVISED_ITEMS to MTL_ITEM_REVISIONS_B (matching on organization, revised item, and revision) to emit an entity name of EGO_ITEM_REVISION, with the revision identifier mapped to PK3_VALUE. The third branch selects directly from ENG_CHANGE_SUBJECTS, passing through its entity name and PK values unchanged. The first two branches set CHANGE_LINE_ID to -1, reflecting that they are synthesized at the change level rather than tied to a specific change line.

Key Columns

  • CHANGE_ID — the engineering change order the subject belongs to; the primary correlation key for reporting.
  • CHANGE_LINE_ID — the change line identifier where applicable; returns -1 for the revised-item derived branches.
  • ENTITY_NAME — the subject type. The documented literal values are EGO_ITEM and EGO_ITEM_REVISION; the third branch passes through other entity names from ENG_CHANGE_SUBJECTS.
  • PK1_VALUE — for item subjects, the revised item ID (converted to character).
  • PK2_VALUE — for item subjects, the organization ID.
  • PK3_VALUE — for revision subjects, the revision ID; NULL for the plain item branch.
  • PK4_VALUE / PK5_VALUE — additional primary-key slots, NULL in the item branches and populated only by the generic subject branch.
  • SUBJECT_LEVEL — the granularity of the subject; 1 is used by the item/revision branches.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard audit columns inherited from each source branch.

Common Use Cases and Queries

The most common use is enumerating the subjects of an engineering change, optionally filtered by entity type. For example, to list all item-level subjects for a change:

  • SELECT change_id, entity_name, pk1_value AS item_id, pk2_value AS org_id, subject_level FROM apps.eng_change_subjects_v WHERE change_id = :change_id AND entity_name = 'EGO_ITEM';
  • To list revision-level subjects: SELECT change_id, pk1_value AS item_id, pk2_value AS org_id, pk3_value AS revision_id FROM apps.eng_change_subjects_v WHERE change_id = :change_id AND entity_name = 'EGO_ITEM_REVISION';
  • To count subjects by type across changes: SELECT entity_name, COUNT(*) FROM apps.eng_change_subjects_v GROUP BY entity_name;

The view is also used as a lookup source when rendering change-order detail pages, since the entity name plus PK values can be resolved to display names by the consuming form or concurrent program. Note that PK1_VALUE and PK2_VALUE are character-converted, so joins to numeric item or organization columns require an explicit TO_NUMBER conversion.