Search Results object_to_name

Overview

ENG_CHANGE_OBJ_RELATIONSHIPS_V is an APPS-owned Oracle EBS view in the Engineering (ENG) product module that exposes object-to-object relationships maintained between engineering change orders (ECOs) and the engineering items, revisions, projects, tasks, and other change objects they reference. In Oracle EBS 12.1.1 and 12.2.2, this view serves as the reporting and integration surface for the relationship model anchored on the ENG_CHANGE_OBJ_RELATIONSHIPS base table, translating raw relationship codes into user-facing meanings and status descriptions. The view is status VALID in the ETRM metadata and is defined as a UNION ALL of two symmetric SELECT blocks, which handle the relationship in both directions — a change referencing another object, and an object referenced by another change. This bidirectional design allows a single query to retrieve all related change objects from either perspective.

Underlying Base Objects

The documented base objects defining this view include ENG_CHANGE_OBJ_RELATIONSHIPS (the driving relationship table), ENG_CHANGE_ORDER_TYPES and ENG_CHANGE_ORDER_TYPES_TL (change order type and its translations), ENG_CHANGE_STATUSES_TL (status translations), ENG_ENGINEERING_CHANGES (the ECO header), and FND_LOOKUP_VALUES / FND_LOOKUP_VALUES_VL (the ENG_CHANGE_RELATIONSHIPS lookup set). Additional referenced objects per the ETRM metadata include MTL_ITEM_REVISIONS_VL, MTL_SYSTEM_ITEMS_KFV, PA_PROJECTS_ALL, and PA_TASKS, reflecting support for item revision, inventory item, project, and task relationship targets. Joins are language-filtered using USERENV('LANG') to return translated type and status names appropriate to the session language. The ENG_CHANGE_RELATIONSHIPS lookup provides both the MEANING (displayed as RELATIONSHIP) and TAG (exposed as RELATIONSHIP_TYPE) values.

Key Columns

• CHANGE_ID / OBJECT_TO_ID1 — The engineering change identifier and the identifier of the target object in the relationship; the UNION ALL swaps these depending on relationship direction.
• CHANGE_RELATIONSHIP_ID — Primary key of the underlying relationship record.
• RELATIONSHIP_CODE / RELATIONSHIP — The relationship lookup code and its translated meaning.
• OBJECT_TO_NAME / OBJECT_TO — The target object type code (for example, 'ENG_CHANGE') and its translated type name.
• OBJECT_TO_URL — A generated OAFunction URL (OAFUNC=ENG_CHANGE_SUMMARY_PAGE&CHANGEID=...) used by the Change Summary page.
• RELATIONSHIP_TO_NUMBER / RELATIONSHIP_TO_NAME — The change notice number and name of the related change.
• RELATIONSHIP_TYPE — The lookup TAG value classifying the relationship.
• WUSED_RELATIONSHIP — Flag ('Y' or 'N') indicating whether the relationship is used from the object-to-change perspective.
• STATUS / NEED_BY_DATE / CREATION_DATE / LAST_UPDATE_DATE — Status name and date attributes of the related change.
• REVISION / REVISION_LABEL — Exposed as NULL in the documented view text. Users searching for "revision_label" should note that this column exists in the view's projection but is not populated by the current definition; revision information must be obtained by joining to MTL_ITEM_REVISIONS_VL directly.

Common Use Cases and Queries

Typical uses include ECO impact reporting, change propagation analysis, and integration feeds that require resolved relationship descriptions. The following sample retrieves related change objects for a given change:

• SELECT change_id, relationship, object_to, relationship_to_number, status FROM eng_change_obj_relationships_v WHERE object_to_name = 'ENG_CHANGE';
• SELECT change_id, relationship_to_number, need_by_date FROM eng_change_obj_relationships_v WHERE wused_relationship = 'N' ORDER BY creation_date DESC;
• SELECT object_to_url FROM eng_change_obj_relationships_v WHERE change_relationship_id = :id;

Because REVISION_LABEL is projected as NULL, queries requiring revision labels should join MTL_ITEM_REVISIONS_VL on the relevant item and revision identifiers rather than relying on this view's column.