Search Results query_object_name




Overview
Explore in AI Chat

Overview

APPS.ENG_SUBJECT_ENTITIES_V is a Web view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 data model. Its registered FND Design Data name is ENG.ENG_SUBJECT_ENTITIES_V, its owner is the APPS schema, and its status is VALID. Oracle classifies it as a Web view designed to simplify access from Oracle Self-Service Web Applications, meaning it is intended primarily as a read-only presentation layer for browser-based Oracle Applications rather than as a transactional base table.

Functionally, the view stores and exposes engineering subject entity information. In the Oracle Engineering (ENG) module, a "subject" is the generic container through which entities participate in engineering change management. Each subject entity defines the descriptive metadata that tells the application how a particular business object — such as an item, a bill of material, or a routing — is identified and queried. The view therefore plays a metadata role in reporting and integration: it answers the question of which underlying table or view holds a given entity, which columns act as its primary key, and which display columns should be shown to the user.

Because it is a Web view, ENG_SUBJECT_ENTITIES_V should be treated as a query-only interface. It is suited to self-service screens, concurrent program extracts, and custom reporting, but not as a target for DML.

Underlying Base Objects

The documented dependency information identifies two referenced base objects: ENG_CHANGE_OBJECTS_V (a view) and ENG_SUBJECT_ENTITIES (a synonym). The view is defined over these objects, joining or projecting the entity metadata held against the engineering change object model. ENG_SUBJECT_ENTITIES supplies the core subject-to-entity definitions, while ENG_CHANGE_OBJECTS_V contributes the change-object perspective that links engineering change orders to the entity types they govern.

Consistent with standard EBS practice, references are made through the APPS synonym layer rather than directly to the underlying ENG schema tables, which preserves the multi-org and editioning-safe access path used throughout Release 12. The ENG design data registration confirms the view is shipped and versioned as part of the Engineering application's FND design data, so it is upgraded and validated alongside the rest of the ENG family.

Key Columns

Together these columns form a self-describing dictionary: given a subject entity, the view states what to query, how to key it, and how to label the output.

Common Use Cases and Queries

Typical uses include discovering which object holds a given engineering entity, generating dynamic self-service queries, and performing impact analysis across engineering change subjects.

SELECT subject_id, subject_level, entity_name, parent_entity_name,
       query_object_name
FROM   apps.eng_subject_entities_v
ORDER  BY subject_id, subject_level;

SELECT entity_name, query_object_name,
       pk1_column_name, pk2_column_name,
       query_column1_name, query_column1_display_name
FROM   apps.eng_subject_entities_v
WHERE  query_object_name = :p_object_name;

Because the view is read-only and web-facing, custom code should join it to change-order data for reporting and avoid DML. Its metadata columns make it particularly valuable for generic, data-driven utilities that must render engineering entities without hard-coding table names.