Search Results eng_change_objects_v

Overview

ENG_CHANGE_OBJECTS_V is an APPS-owned reporting view in the Oracle E-Business Suite Engineering (ENG) module, exposed in release 12.1.1 and 12.2.2. It presents the metadata that drives the Engineering Change Order (ECO) object registration framework, describing which transactional entities (for example bills of material, routings, item revisions, or documents) are eligible for association with an engineering change order. Rather than storing the changed business data itself, the view publishes the descriptive and structural attributes that allow the ECO forms and concurrent programs to locate, query, and display those entities. The status of the object is VALID in the documented environment.

Each row identifies one change object through ENTITY_NAME and provides a stable, reusable definition of its primary keys, query columns, display labels, and navigation target. Because the definition is data-driven, new changeable entities can be registered without amending ECO form logic, and reports can enumerate the available change object types consistently across the instance.

Underlying Base Objects

The documented view text shows that ENG_CHANGE_OBJECTS_V is defined entirely over a single base object: ENG_CHANGE_OBJECTS_VL, the translatable ("_VL") view that holds the language-dependent and language-independent columns for change object definitions. The view is a straight projection, selecting all listed columns from ENG_CHANGE_OBJECTS_VL without joins, filters, or aggregation. Consequently, ENG_CHANGE_OBJECTS_V behaves as a thin, read-only synonym-like layer over its base, inheriting its row set and its translation behavior. The naming convention implies that a corresponding base table, ENG_CHANGE_OBJECTS_B, and translation table, ENG_CHANGE_OBJECTS_TL, sit beneath the _VL view, with the translatable attributes such as display names resolved for the session language.

Key Columns

The columns fall into four functional groups:

• Entity identification: ENTITY_NAME uniquely names the changeable business entity, and ENTITY_DISPLAY_NAME supplies the user-facing label. ENTITY_URL provides the navigation target used to open the entity from the ECO interface.
• Primary key mapping: PK1_COLUMN_NAME through PK5_COLUMN_NAME identify up to five key columns that uniquely locate an instance of the entity.
• Query definition: QUERY_OBJECT_NAME names the query object, while QUERY_COLUMN1_NAME through QUERY_COLUMN5_NAME and the matching QUERY_COLUMN1_TYPE through QUERY_COLUMN5_TYPE describe the columns used to retrieve and display candidate records, together with their data types. QUERY_COLUMN1_DISPLAY_NAME and QUERY_COLUMN2_DISPLAY_NAME carry the localized headings for the first two query columns.
• Audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN record who created and last maintained the definition, with LAST_UPDATE_LOGIN identifying the login session of the most recent change.

Common Use Cases and Queries

Typical uses include validating the ECO object registry after patching or an upgrade, building custom LOVs or report parameters that list changeable entities, and diagnosing why an entity fails to appear on the ECO form.

Enumerate all registered change objects with their display labels:

• SELECT entity_name, entity_display_name, entity_url FROM apps.eng_change_objects_v ORDER BY entity_display_name;

Inspect a single entity's key and query structure before writing integration code:

• SELECT entity_name, pk1_column_name, pk2_column_name, query_object_name, query_column1_name, query_column1_type FROM apps.eng_change_objects_v WHERE entity_name = :p_entity;

Review recently maintained definitions for audit purposes:

• SELECT entity_name, last_updated_by, last_update_date FROM apps.eng_change_objects_v WHERE last_update_date > SYSDATE - 30;

The view should be queried read-only; registrations are maintained through supported Engineering setup forms rather than direct DML.