Search Results fk5_column_name

Overview

The view APPS.ENG_SUBJECT_ENTITIES_V is a reporting and integration object within the Oracle E-Business Suite Engineering (ENG) module. Its primary role is to unify metadata describing Engineering Change Order (ECO) subject entities — the business objects that may be placed under engineering change control — with the query and column-mapping definitions required to resolve those entities at runtime. In EBS 12.1.1 and 12.2.2, the view is exposed in the APPS schema with a status of VALID, making it available to concurrent programs, Oracle Forms, OAF pages, and external integration layers that consume engineering change metadata.

The view serves as a consolidated dictionary of subject entities. Each row describes a distinct entity (for example, an item, bill of materials, or routing) together with the query object, primary key columns, foreign key columns, display names, and the bean type used by the change management framework. Because it joins a change-object definition view to the stored subject-entity definitions, it allows callers to enumerate what can be changed and how each entity is identified and rendered without querying multiple tables independently.

Underlying Base Objects

Per the documented ETRM metadata, ENG_SUBJECT_ENTITIES_V is defined over two base objects:

• ENG_CHANGE_OBJECTS_V (VIEW) — supplies the query object name, primary key column names, query column names and types, display names, and the entity URL.
• ENG_SUBJECT_ENTITIES (SYNONYM) — supplies subject identifiers, subject levels, entity and parent entity names, foreign key column names, bean type, and standard WHO audit columns.

The two sources are joined on ESE.ENTITY_NAME = ECOV.ENTITY_NAME. This join means every row returned by the view represents an entity that is both registered as a subject entity and defined in the change-objects view. The engineering change framework relies on this correspondence to map a logical subject (such as an item) to a concrete queryable database object and its key structure.

Key Columns

The view exposes a wide column set. The most significant columns include:

• SUBJECT_ID / SUBJECT_LEVEL — identify the subject and its level in the entity hierarchy, supporting parent-child relationships.
• ENTITY_NAME / PARENT_ENTITY_NAME — the entity and its parent, used to navigate hierarchical subject structures.
• QUERY_OBJECT_NAME — the database object queried to retrieve instances of the entity.
• PK1_COLUMN_NAME … PK5_COLUMN_NAME — up to five primary key columns that uniquely identify an instance.
• FK1_COLUMN_NAME … FK5_COLUMN_NAME — foreign key columns linking the entity to its parent or related structures.
• QUERY_COLUMN1_NAME … QUERY_COLUMN5_NAME with corresponding _TYPE and _DISPLAY_NAME columns — describe the display columns, their data types, and user-facing labels.
• ENTITY_URL / BEAN_TYPE — the navigation URL and Java bean type used when rendering or launching the entity in the change management UI.
• CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical uses include dynamically building ECO subject pickers, driving generic change-object queries, and validating which entities are subject to change control.

• Listing all subject entities: SELECT ENTITY_NAME, SUBJECT_LEVEL FROM ENG_SUBJECT_ENTITIES_V ORDER BY ENTITY_NAME;
• Retrieving the key and query mapping for a specific entity: SELECT QUERY_OBJECT_NAME, PK1_COLUMN_NAME, FK1_COLUMN_NAME FROM ENG_SUBJECT_ENTITIES_V WHERE ENTITY_NAME = :p_entity;
• Inspecting display configuration: SELECT QUERY_COLUMN1_NAME, QUERY_COLUMN1_TYPE, QUERY_COLUMN1_DISPLAY_NAME FROM ENG_SUBJECT_ENTITIES_V WHERE ENTITY_NAME = :p_entity;

Because the view encapsulates both definitional and query metadata, it is the preferred access point for custom extensions and integration programs that must interact with engineering change subjects without hard-coding entity structures.