Results for “pqh_copy_entity_contexts”

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

Overview

PQH_COPY_ENTITY_CONTEXTS is a configuration table owned by the HR schema within the PQH (Public Sector HR) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to control the display, criteria resolution, and change behavior applied to the Application, Legislation, and Responsibility context under which a copy-entity operation is executed. In practice, the table acts as a context registry for the copy-entity framework, allowing administrators to scope which copy functions and transactions are visible or permitted for a given operating context.

Heuristic Data Vault classification derived from the foreign-key topology is hub-leaning. The table is referenced by multiple dependent tables through the CONTEXT column, which suggests it functions as a central reference or hub entity rather than a transactional satellite or an associative link. This classification is offered as a modeling suggestion only; in native EBS terms the object is a standard seeded and configurable setup table.

Key Information Stored

• CONTEXT — The primary semantic identifier of the record and the column referenced by all dependent foreign keys. It is part of the primary key PQH_COPY_ENTITY_CONTEXTS_PK.
• APPLICATION_SHORT_NAME — Identifies the EBS application against which the context applies; participates in the unique business key.
• LEGISLATION_CODE — Restricts the context to a specific legislation; participates in the unique business key.
• RESPONSIBILITY_KEY — Associates the context with a responsibility; participates in the unique business key.
• TRANSACTION_SHORT_NAME — Names the transaction type associated with the context, used to drive change behavior.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the OAF/ADF framework to detect concurrent updates.
• ZD_EDITION_NAME — Editioning column supporting the EBS 12.2 online patching (Edition-Based Redefinition) architecture; it appears in both unique indexes.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN capture standard who/when audit information.

The surrogate primary key is PQH_COPY_ENTITY_CONTEXTS_PK, defined on (CONTEXT, ZD_EDITION_NAME). The business-key candidate is the unique index PQH_COPY_ENTITY_CONTEXTS_UK, defined on (APPLICATION_SHORT_NAME, LEGISLATION_CODE, RESPONSIBILITY_KEY, CONTEXT, ZD_EDITION_NAME), confirming that a context is meaningful only in combination with its application, legislation, and responsibility.

Common Use Cases and Queries

Typical administrative scenarios include verifying which contexts are configured for copy-entity operations, auditing responsibility-level restrictions, and troubleshooting why a copy function is unavailable for a user. A representative query joining the context to its dependent function records follows:

• SELECT c.CONTEXT, c.APPLICATION_SHORT_NAME, c.LEGISLATION_CODE, c.RESPONSIBILITY_KEY FROM HR.PQH_COPY_ENTITY_CONTEXTS c WHERE c.APPLICATION_SHORT_NAME = :app;
• SELECT f.* FROM HR.PQH_COPY_ENTITY_FUNCTIONS f JOIN HR.PQH_COPY_ENTITY_CONTEXTS c ON f.CONTEXT = c.CONTEXT WHERE c.LEGISLATION_CODE = :leg;
• SELECT t.* FROM HR.PQH_COPY_ENTITY_TXNS t JOIN HR.PQH_COPY_ENTITY_CONTEXTS c ON t.CONTEXT = c.CONTEXT WHERE c.RESPONSIBILITY_KEY = :resp;

In 12.2 environments, queries should account for ZD_EDITION_NAME to return the correct edition of the rows. Reporting use cases include context coverage audits across legislation and responsibility, and impact analysis before modifying seeded copy-entity configuration.

Related Objects

• PQH_COPY_ENTITY_FUNCTIONS — references PQH_COPY_ENTITY_CONTEXTS via CONTEXT; defines the functions available within each context.
• PQH_COPY_ENTITY_TXNS — references PQH_COPY_ENTITY_CONTEXTS via CONTEXT; records transactions scoped to a context.
• PQH_SPECIAL_ATTRIBUTES — references PQH_COPY_ENTITY_CONTEXTS via CONTEXT; stores special attribute definitions tied to the context.
• FND_APPLICATION — supplies APPLICATION_SHORT_NAME values used in the unique key.
• FND_RESPONSIBILITY — underlies RESPONSIBILITY_KEY values referenced by the context configuration.
• FND_LEGAL_ENTITIES / FND_TERRITORIES — contextual sources for LEGISLATION_CODE.

Because these dependent objects all carry a CONTEXT foreign key into this table, deletion or modification of context rows has cascading functional impact across the copy-entity framework and should be performed only through supported setup or patching mechanisms.