Search Results oe_pc_rentities_v




Overview
Explore in AI Chat

Overview

OE_PC_RENTITIES_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Order Management (ONT) product family. The object is documented as VALID at both the 12.1.1 and 12.2.2 releases. Its purpose is to expose the related entity relationship graph defined by the Order Management entity-registration framework — the metadata layer that describes which database objects participate in the order capture and order processing data model, and how they connect to one another through foreign keys.

The "R" prefix in the view name designates it as the "related entities" projection: rather than listing entities in isolation, the view returns each entity paired with the target entity it references. This makes it a metadata enumeration view rather than a transactional one. It is consumed by configuration, extensibility, and diagnostic tooling that must understand the referential structure of the Order Management tables without hard-coding object relationships.

Underlying Base Objects

The view is defined over two underlying views, both documented in the ETRM metadata and both owned by APPS:

  • OE_PC_ENTITIES_V — the entity registration view. It supplies the entity identity columns (application, entity short name, display name, description) and the physical database object name for each registered entity.
  • OE_PC_FKEYS_V — the foreign-key registration view. It supplies the linking information that associates a foreign-key column with the unique key it references, including the referenced application and database object.

The defining query joins OE_PC_ENTITIES_V twice — once aliased as the driving entity (E) and once aliased as the related entity (RE) — with OE_PC_FKEYS_V (EFK) acting as the bridge. The join predicates constrain the driving entity's application ID, DB object name, and DB object type to the corresponding foreign-key attributes in EFK, and then constrain EFK's unique-key attributes (UK_APPLICATION_ID and UK_DB_OBJECT_NAME) to the related entity's application and object name. The result is a flattened, denormalised list of entity-to-entity relationships.

Key Columns

The view exposes fourteen columns, organised as two parallel groups of seven. The first group describes the source (child-side) entity:

The second group mirrors the first with a RELATED_ prefix, describing the referenced (parent-side) entity: RELATED_APPLICATION_ID, RELATED_APPLICATION_SHORT_NAME, RELATED_ENTITY_ID, RELATED_ENTITY_SHORT_NAME, RELATED_ENTITY_DISPLAY_NAME, RELATED_ENTITY_DESCRIPTION, and RELATED_DB_OBJECT_NAME. In practice the first seven columns describe the child object and the RELATED_ columns identify the parent object that its foreign key points to.

Common Use Cases and Queries

Because the view is metadata rather than transactional data, it is principally used for impact analysis, data-model exploration, and validation of entity registrations after upgrades or patches. A typical query lists every entity and its parent:

  • SELECT entity_short_name, db_object_name, related_entity_short_name, related_db_object_name FROM oe_pc_rentities_v ORDER BY 1, 3;
  • Filtering by child object — WHERE db_object_name = 'OE_ORDER_HEADERS_ALL' — reveals the parent objects referenced by a specific table, useful when tracing foreign-key dependencies.
  • Filtering by parent object — WHERE related_db_object_name = 'OE_ORDER_HEADERS_ALL' — lists all child entities that point at that object, a common requirement during schema-impact assessments.
  • Joining back to dictionary views such as ALL_TAB_COLUMNS using DB_OBJECT_NAME and RELATED_DB_OBJECT_NAME supports column-level lineage documentation.

As with all APPS-owned views, query it with the APPS schema or an appropriately granted responsibility; the underlying registrations are maintained by Oracle and should not be modified directly.