Results for “pqh_copy_entity_contexts_uk”

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

Overview

HR.PQH_COPY_ENTITY_CONTEXTS is a reference and configuration table within the Oracle HRMS (HR) schema that governs the behavior of the Oracle E-Business Suite copy-entity framework. The copy-entity mechanism allows administrators to replicate HR configuration and transactional data from one operating context to another, typically during implementation, multi-organization rollouts, or template-driven deployment. This table defines the named contexts under which copy operations are permitted, associating each context with an application, a legislation, and a responsibility so that the framework can resolve the correct copying rules for the active user session.

Under the heuristic Data Vault classification derived from its foreign-key topology, HR.PQH_COPY_ENTITY_CONTEXTS is hub-leaning. It supplies the durable business key (CONTEXT) that dependent objects reference, and the three foreign-key relationships terminating at this table confirm that it functions as the integration point for the copy-entity framework rather than as a transactional child. This classification should be treated as a modeling suggestion, since the physical implementation is a conventional third-normal-form EBS table, not a formal Data Vault construct.

Key Information Stored

The table contains twelve documented columns, of which the following are the most significant:

• CONTEXT (VARCHAR2, 27) — the surrogate primary key and the identifier propagated to all dependent tables; it defines a single eponymous copy context.
• APPLICATION_SHORT_NAME (VARCHAR2, 50) — the owning application for the context, driving which product's copy entities are eligible.
• LEGISLATION_CODE (VARCHAR2, 30) — the legislation under which the context applies, enabling country-specific copy behavior.
• RESPONSIBILITY_KEY (VARCHAR2, 30) — the responsibility identifier that scopes the context to a functional role.
• TRANSACTION_SHORT_NAME (VARCHAR2, 30) — the transaction the context is associated with.
• OBJECT_VERSION_NUMBER — optimistic-locking column used by the EBS framework to detect concurrent modification.
• LAST_UPDATE_DATE, CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard Who columns providing audit lineage.

Two unique indexes are documented. PQH_COPY_ENTITY_CONTEXTS_PK enforces uniqueness on CONTEXT (with ZD_EDITION_NAME in the 12.2.2 schema). PQH_COPY_ENTITY_CONTEXTS_UK is the business-key candidate, enforcing uniqueness over APPLICATION_SHORT_NAME, LEGISLATION_CODE, RESPONSIBILITY_KEY, CONTEXT, and ZD_EDITION_NAME. The user's search term, pqh_copy_entity_contexts_uk, corresponds precisely to this unique constraint. The ZD_EDITION_NAME column in the 12.2.2 physical schema supports the edition-based redefinition (EBR) architecture introduced in EBS 12.2, which is absent in 12.1.1.

Common Use Cases and Queries

Typical scenarios include auditing which copy contexts are enabled for a given application and legislation, and diagnosing why a copy operation fails to resolve for a particular responsibility. A representative query filtering by application and legislation is:

SELECT context, responsibility_key, transaction_short_name
FROM   hr.pqh_copy_entity_contexts
WHERE  application_short_name = 'PER'
AND    legislation_code = 'US';

To resolve a session context against the full business key, query on the UK columns directly. Reporting use cases include cross-referencing contexts with PQH_COPY_ENTITY_TXNS to enumerate executed copy transactions, and joining to PQH_COPY_ENTITY_FUNCTIONS to enumerate the functions permitted within each context.

Related Objects

• PQH_COPY_ENTITY_FUNCTIONS — joins on CONTEXT; lists the functions available for each copy context.
• PQH_COPY_ENTITY_TXNS — joins on CONTEXT; records copy transactions performed under a context.
• PQH_SPECIAL_ATTRIBUTES — joins on CONTEXT; stores supplemental attributes keyed to the context.
• FND_APPLICATION — resolved via APPLICATION_SHORT_NAME for application names.
• FND_RESPONSIBILITY — resolved via RESPONSIBILITY_KEY for responsibility metadata.

Collectively these relationships establish HR.PQH_COPY_ENTITY_CONTEXTS as the hub object through which copy-entity configuration and transactional activity are coordinated in Oracle EBS 12.1.1 and 12.2.2.