Search Results entity_description




Overview
Explore in AI Chat

Overview

OE_PC_VENTITIES_V is a read-only consolidated view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Order Management (ONT) product family and forms part of the Oracle Enterprise Trading and Relationship Management (ETRM) data model. The view presents a unified list of "entities" and their related counterparts, which are the business objects registered for validation, processing, and cross-application referencing within Order Management and pricing/trade workflows.

Its principal role is to give reporting tools, concurrent programs, and integration interfaces a single flattened source from which both a primary entity and its related entity can be retrieved. Because the view exposes the APPLICATION_SHORT_NAME column alongside the numeric APPLICATION_ID, it is frequently used to translate internal identifiers into the human-readable application context that users and external systems recognise. The view is marked VALID and is defined entirely over other views rather than directly over base tables, which means it inherits the filtering and join logic of its parents.

Underlying Base Objects

The ETRM metadata documents two referenced objects for OE_PC_VENTITIES_V:

The view text performs a three-way UNION. The first branch selects the primary columns (APPLICATION_ID through DB_OBJECT_NAME) from OE_PC_ENTITIES_V. The second branch selects the primary columns plus the corresponding RELATED_* columns from OE_PC_RENTITIES_V. The third branch selects the RELATED_* columns mapped into the primary column positions, again from OE_PC_RENTITIES_V. The effect is a symmetrical result set in which every entity relationship appears from both directions. Because OE_PC_ENTITIES_V and OE_PC_RENTITIES_V are themselves views, the column list presented to consumers (APPLICATION_ID through VALIDATION_DB_OBJECT_NAME) is the documented projection, while the underlying SELECT list names only the first seven columns for each UNION branch.

Key Columns

The view exposes fourteen documented columns:

Collectively these columns allow a caller to resolve an application short name to an entity, then traverse to the associated validation entity without additional lookups.

Common Use Cases and Queries

Typical scenarios include resolving entity ownership for a given application, listing all entities registered under Order Management, and building cross-reference reports between primary and validation entities.

Sample query filtering on application short name:

  • SELECT application_short_name, entity_short_name, entity_display_name, db_object_name FROM oe_pc_ventities_v WHERE application_short_name = 'ONT' ORDER BY entity_short_name;

Sample query resolving a specific entity and its validation counterpart:

  • SELECT entity_id, entity_display_name, validation_entity_id, validation_entity_display_name FROM oe_pc_ventities_v WHERE entity_short_name = :p_entity;

Because the view is a UNION of views, queries should be filtered on indexed or highly selective columns where possible, and DISTINCT or GROUP BY applied when duplicate relationship rows are not meaningful. All access is read-only and governed by APPS schema privileges.