Search Results oe_pc_entities_v




Overview
Explore in AI Chat

Overview

The OE_PC_ENTITIES_V view is a reporting and integration object owned by the APPS schema within the Order Management (ONT) product family of Oracle E-Business Suite. It presents a consolidated, denormalized list of registered business entities that participate in Order Management's process and constraint framework, joining the Order Management entity extension table to the Application Object Library's object definitions. In practice, the view exposes the set of database objects for which Order Management has defined processing constraints, entity-based workflow routing, and item-key derivation rules, filtered to only those whose underlying database constraints are enabled.

It is not a transactional view. Instead, it is a metadata view used by reports, diagnostic queries, extensions, and personalizations that need to resolve an entity identifier (ENTITY_ID) or database object name back to a human-readable application name, entity name, and description. Because it already resolves the APPLICATION_ID to an application name and short name, the view is convenient for ad hoc DBA queries and custom concurrent programs that enumerate constraint-enabled Order Management entities.

Underlying Base Objects

Per the documented ETRM metadata for 12.2.2, OE_PC_ENTITIES_V is defined over two referenced base objects:

  • OE_AK_OBJECTS_EXT (SYNONYM) — the Order Management extension table that stores the entity registration records, including the entity identifier, the owning application, the underlying database object name and type, the workflow item type, and the item-key column and delimiter definitions. The synonym resolves to the underlying APPS table.
  • AK_OBJECTS_VL (VIEW) — the Application Object Library's multi-language view of registered application objects, which supplies the application name, application short name, object name, and object description.

The two objects are joined on both APPLICATION_ID and DATABASE_OBJECT_NAME. An additional predicate, CONSTRAINTS_ENABLED_FLAG = 'Y', restricts the result set to entities whose constraints are active. This join logic explains why the view is described as exposing constraint-enabled entities only: records in OE_AK_OBJECTS_EXT that lack a matching AK_OBJECTS_VL row, or that carry a disabled constraints flag, are excluded from the output.

Key Columns

The view exposes the following columns. ENTITY_ID is the surrogate key for the registered Order Management entity and is the value most commonly passed into constraint and workflow APIs. APPLICATION_ID, APPLICATION_NAME, and APPLICATION_SHORT_NAME identify the owning application and make the view self-describing without a further join to FND_APPLICATION. ENTITY_DISPLAY_NAME and ENTITY_DESCRIPTION carry the user-facing labels, while ENTITY_SHORT_NAME provides a compact identifier. ENTITY_CODE, DB_OBJECT_NAME, and DB_OBJECT_TYPE identify the physical database object the entity represents.

The workflow-related columns — WF_ITEM_TYPE, ITEMKEY_COLUMN1 through ITEMKEY_COLUMN4, and ITEMKEY_DELIMITER — describe how Order Management constructs a workflow item key for records of the entity, a mechanism used when entity records drive workflow processes. Audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) record row provenance. ROW_ID exposes the ROWID of the underlying OE_AK_OBJECTS_EXT row, which is useful for locking or for locating the base record.

Common Use Cases and Queries

Typical usage includes resolving an entity ID to a readable name, auditing which entities have constraints enabled, and driving data-driven extensions. A representative query is:

  • SELECT entity_id, entity_display_name, db_object_name, wf_item_type FROM oe_pc_entities_v WHERE application_short_name = 'ONT' ORDER BY entity_display_name; — enumerates Order Management entities and their workflow item types.
  • SELECT entity_display_name, db_object_name, itemkey_column1, itemkey_column2 FROM oe_pc_entities_v WHERE wf_item_type IS NOT NULL; — lists workflow-enabled entities and their item-key column mappings.
  • SELECT entity_id, entity_description FROM oe_pc_entities_v WHERE db_object_name = 'OE_ORDER_HEADERS_ALL'; — resolves the header entity identifier for use in constraint or workflow API calls.

Because the view is read-only metadata, it should be queried rather than modified; entity registration itself is maintained through the underlying OE_AK_OBJECTS_EXT table and Application Object Library setup. The view remains valid and is documented against ETRM 12.2.2, and the same structure applies to the 12.1.1 code line.