Search Results entity_url




Overview
Explore in AI Chat

Overview

ENG_CHANGE_OBJECTS_VL is a validation view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Engineering (ENG) product module. It presents the translatable attributes of engineering change object definitions alongside the operational metadata required to drive the Oracle Engineering change management framework. In Oracle EBS 12.1.1 and 12.2.2, the view exposes a joined, language-filtered record set combining the base configuration table ENG_CHANGE_OBJECTS with its translation table ENG_CHANGE_OBJECTS_TL, restricted to the session language via USERENV('LANG').

The view does not store data. It is a reporting and integration access point that allows concurrent programs, forms, and external interfaces to retrieve the registered change objects — the business entities (such as items, bills of material, routings, and documents) that can be placed under engineering change order control — together with their primary key column mappings, query column mappings, display names, and entity URLs. Because the translation table is joined internally, consumers receive display-ready values without needing to know the underlying multilingual schema.

Underlying Base Objects

The view is defined over two documented base objects, both referenced as synonyms from APPS:

The two objects are joined on ENTITY_NAME, with the translation side filtered by ECOTL.LANGUAGE = USERENV('LANG'). This ensures each row returned reflects the current user's language setting, falling back to the base language where translations are installed. The view aliases ECO.ROWID as ROW_ID, providing a synthetic identifier for the joined result set.

Key Columns

  • ROW_ID — the ROWID of the underlying ENG_CHANGE_OBJECTS row, exposed for row-level identification.
  • ENTITY_NAME — the internal identifier of the change-controlled business entity; also the join key to the translation table.
  • QUERY_OBJECT_NAME — the database object (table or view) queried to resolve entity instances.
  • PK1_COLUMN_NAME through PK5_COLUMN_NAME — up to five primary key columns used to uniquely identify a change object instance.
  • QUERY_COLUMN1_NAME through QUERY_COLUMN5_NAME — columns available for query and search within the change object.
  • QUERY_COLUMN1_TYPE through QUERY_COLUMN5_TYPE — datatype indicators for the corresponding query columns.
  • ENTITY_DISPLAY_NAME, QUERY_COLUMN1_DISPLAY_NAME, QUERY_COLUMN2_DISPLAY_NAME — translated, user-facing labels.
  • ENTITY_URL — the navigation target used to open the entity from the Engineering workbench.
  • CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical uses include metadata discovery for change object configuration, building dynamic query regions in Engineering forms, and validating entity registration in multilingual environments.

To list all registered change objects with their display names:

  • SELECT entity_name, entity_display_name, query_object_name, entity_url FROM eng_change_objects_vl ORDER BY entity_name;

To retrieve key and query column mappings for a specific entity:

  • SELECT entity_name, pk1_column_name, pk2_column_name, query_column1_name, query_column1_display_name FROM eng_change_objects_vl WHERE entity_name = :entity;

To audit recently modified change object definitions:

  • SELECT entity_name, entity_display_name, last_update_date, last_updated_by FROM eng_change_objects_vl WHERE last_update_date > SYSDATE - 30;

Because the view enforces USERENV('LANG'), results vary by session language, making it suitable for locale-aware reporting without additional translation logic.