Results for “pqh_copy_entity_contexts_v”

30 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The PQH_COPY_ENTITY_CONTEXTS_V view is an Oracle E-Business Suite 12.1.1 / 12.2.2 reporting and integration object owned by the APPS schema in the Public Sector HR (PQH) product family. It is a denormalized, read-only presentation layer defined over the PQH_COPY_ENTITY_CONTEXTS configuration table. Its purpose is to expose the "copy entity context" rules that govern how Oracle HRMS copies or replicates business entities, while resolving foreign key identifiers into human-readable descriptive text.

In its raw table form, PQH_COPY_ENTITY_CONTEXTS stores only short codes, keys, and IDs. That is unsuitable for reports, extracts, or integration payloads that must be interpreted by end users or downstream systems. This view therefore joins four descriptive lookup views so that each context row carries the application name, responsibility name, legislation (territory) description, and transaction name rather than opaque codes. The prominently exposed TRANSACTION_NAME column, which the user searched for, is one of these resolved descriptions: it is derived from PQH_TRANSACTION_CATEGORIES_VL.NAME via the transaction short name, giving the readable label for the transaction category the context applies to.

Because it resides in APPS and conforms to standard EBS conventions (ROW_ID, OBJECT_VERSION_NUMBER, WHO columns), it can be consumed directly by Oracle Reports, BI Publisher, OAF pages, and external integrations through the APPS schema or a synonym.

Underlying Base Objects

ETRM documents the following referenced base objects:

All descriptive joins except the transaction category are outer joins (+) in the view text. This means a context row is always returned from the base table even when the application, responsibility, or territory lookup fails to match; only the transaction category join is inner, so a row without a valid transaction short name is filtered out. The _VL views are MLS-enabled, so descriptions respect the session language.

Key Columns

  • ROW_ID — the base table ROWID, used as the unique row identifier.
  • CONTEXT — the context code identifying the copy-entity context occurrence.
  • APPLICATION_SHORT_NAME / APPLICATION_NAME — the owning application code and its resolved name.
  • RESPONSIBILITY_KEY / RESPONSIBILITY — the responsibility identifier and resolved description.
  • LEGISLATION_CODE / LEGISLATION_DESC — the territory/legislation code and its short name.
  • TRANSACTION_SHORT_NAME / TRANSACTION_NAME — the transaction category code and its resolved, user-facing name; central to reporting on which transaction types are context-enabled.
  • OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO/audit and optimistic-locking columns.

Common Use Cases and Queries

Typical uses include auditing which transaction categories are configured under a given responsibility or legislation, seeding copy-entity setup, and validating configuration during upgrades from 12.1.1 to 12.2.2.

  • List all contexts with readable transaction labels:
    SELECT context, transaction_name, application_name, responsibility, legislation_desc FROM apps.pqh_copy_entity_contexts_v;
  • Filter by transaction, the user's search term:
    SELECT * FROM apps.pqh_copy_entity_contexts_v WHERE transaction_name LIKE '%'||:term||'%';
  • Isolate contexts by responsibility and legislation:
    SELECT responsibility, legislation_desc, transaction_name FROM apps.pqh_copy_entity_contexts_v WHERE legislation_code = :leg;
  • Audit changes since a date using the WHO column:
    SELECT * FROM apps.pqh_copy_entity_contexts_v WHERE last_update_date > SYSDATE-30;

Because the transaction category join is inner, queries relying on TRANSACTION_NAME inherently exclude rows whose transaction short name is not in the categories lookup, which is a useful consistency check.