Search Results db_object_type




Overview
Explore in AI Chat

Overview

OE_PC_FKEYS_V is a dictionary-style 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, but its definition is not order-specific: it is a thin projection over the Application Object Library key-definition tables AK_FOREIGN_KEYS and AK_UNIQUE_KEYS. The view joins a registered foreign key to the unique key it references and surfaces both sides of that relationship — the foreign key name, the referencing database object, the referenced unique key name, and the object that owns the unique key.

The name prefix "PC" places it in the period-close / processing-control family of Order Management views used by the Order Management period-close and constraint-validation processes. Its runtime role is to give those processes, and any reporting layer built over them, a pre-joined, readable list of key relationships rather than requiring a hand-written join across the two AK tables. Because it is a view rather than a table, it holds no data of its own and always reflects the current contents of the AK key registry.

Underlying Base Objects

The ETRM 12.2.2 metadata for this object documents the view text explicitly. It is defined as a join of two synonyms, both resolving in the APPS schema:

The join predicate is FK.UNIQUE_KEY_NAME = UK.UNIQUE_KEY_NAME. The database object type is hard-coded to the literal 'VIEW' in the DB_OBJECT_TYPE column, so every row returned describes a view-level key relationship. The synonyms ultimately resolve to the AK product tables that store Oracle Application Object Library key registrations, which is why the view behaves as a metadata catalogue rather than a transactional data source. Only rows where a foreign key resolves to a matching unique key appear; orphaned or mismatched registrations are excluded by the inner join.

The documented status is VALID, and the object is proprietary Oracle information governed by the standard Oracle legal notices.

Key Columns

  • APPLICATION_ID — application owning the foreign key definition.
  • DB_OBJECT_NAME — database object (table or view) on which the foreign key is defined.
  • DB_OBJECT_TYPE — constant 'VIEW' for rows produced by this view.
  • FOREIGN_KEY_NAME — registered name of the foreign key constraint definition.
  • UNIQUE_KEY_NAME — the unique key that the foreign key references; this is the join column.
  • UK_APPLICATION_ID — application owning the referenced unique key.
  • UK_DB_OBJECT_NAME — database object that owns the referenced unique key.

Read together, APPLICATION_ID and DB_OBJECT_NAME versus UK_APPLICATION_ID and UK_DB_OBJECT_NAME show whether a foreign key references a key within the same object or across objects and applications, which is the principal analytical value of the view.

Common Use Cases and Queries

Typical scenarios include auditing AK key registrations, tracing which object a foreign key points to before a schema or upgrade change, and validating key relationships during period-close or constraint checks in Order Management.

List all key relationships:

SELECT FOREIGN_KEY_NAME, DB_OBJECT_NAME, DB_OBJECT_TYPE,
       UNIQUE_KEY_NAME, UK_DB_OBJECT_NAME
  FROM APPS.OE_PC_FKEYS_V
 ORDER BY DB_OBJECT_NAME, FOREIGN_KEY_NAME;

Find foreign keys referencing a specific object:

SELECT FOREIGN_KEY_NAME, DB_OBJECT_NAME, UK_DB_OBJECT_NAME
  FROM APPS.OE_PC_FKEYS_V
 WHERE UK_DB_OBJECT_NAME = :object_name;

Detect cross-application relationships:

SELECT FOREIGN_KEY_NAME, APPLICATION_ID, UK_APPLICATION_ID
  FROM APPS.OE_PC_FKEYS_V
 WHERE APPLICATION_ID <> UK_APPLICATION_ID;

Because the view is metadata and typically small, these queries are inexpensive and safe to run in production for diagnostic and reporting purposes.