Search Results validation_entity_display_name




Overview
Explore in AI Chat

Overview

APPS.OE_PC_VENTITIES_V is a consolidated reporting view in the Oracle E-Business Suite Order Management module. It belongs to the Oracle Enterprise Trade Management (ETRM) family of objects and exposes a unified catalogue of the "entities" registered within the Order Capture / Process Configuration framework. In EBS 12.1.1 and 12.2.2, the view is owned by the APPS schema and is intended for read-only reporting and integration access rather than for direct transactional manipulation.

The view presents each entity together with its owning application and its related (cooperating) entity, so it exposes both sides of an entity-to-entity relationship. The column name entity_short_name that users frequently search for is one of the primary identifiers surfaced here. Because it is a view and not a table, it carries no storage of its own; every row is derived at runtime from its underlying sources.

Underlying Base Objects

The documented view metadata identifies two referenced base objects, both of which are themselves views: OE_PC_ENTITIES_V and OE_PC_RENTITIES_V. OE_PC_VENTITIES_V is defined as a three-way UNION of these two sources:

  • The first branch selects the standard entity columns from OE_PC_ENTITIES_V.
  • The second branch selects the standard entity columns and the related_ columns from OE_PC_RENTITIES_V.
  • The third branch selects the related columns and the standard entity columns, in reversed order, from OE_PC_RENTITIES_V.

This structure means the view produces two rows for every entity relationship recorded in OE_PC_RENTITIES_V: one in the direction of the primary entity and one in the direction of the related entity. The result is a bidirectional, undirected catalogue of entity relationships, supplemented by the standalone entities from OE_PC_ENTITIES_V.

Key Columns

The view exposes fourteen columns in the data portion, arranged as two parallel sets of seven:

  • application_id — numeric identifier of the application that owns the entity.
  • application_short_name — the application's short code (for example, the product abbreviation used across EBS).
  • entity_id — numeric identifier of the entity.
  • entity_short_name — the short name of the entity; this is the key lookup value used to resolve an entity programmatically.
  • entity_display_name — the user-facing label of the entity.
  • entity_description — descriptive text explaining the entity's purpose.
  • db_object_name — the database object that backs the entity.
  • related_* — the corresponding seven attributes for the related entity (related_application_id, related_application_short_name, related_entity_id, related_entity_short_name, related_entity_display_name, related_entity_description, related_db_object_name).

Because the UNION projects the related columns into the same seven positions as the primary columns in the first branch, callers should rely on column position and alias consistently when querying.

Common Use Cases and Queries

The view is typically queried to resolve an entity_short_name to its display name and backing object, to enumerate all entities belonging to a given application, and to discover which entities are related to one another.

  • Resolve a short name: SELECT entity_short_name, entity_display_name, db_object_name FROM apps.oe_pc_ventities_v WHERE entity_short_name = :p_name;
  • List entities for an application: SELECT entity_id, entity_short_name, entity_display_name FROM apps.oe_pc_ventities_v WHERE application_short_name = :p_app ORDER BY entity_short_name;
  • Find related entities: SELECT entity_short_name, related_entity_short_name FROM apps.oe_pc_ventities_v WHERE entity_short_name = :p_name ORDER BY related_entity_short_name;

Note that duplicate rows may appear where an entity participates in multiple relationships, and DISTINCT or GROUP BY should be applied where a single row per entity is required.