Results for “remuneration_regulation”

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

Overview

The HR.PQH_DE_WRKPLC_VLDTNS table is a Public Sector HR (PQH) configuration table that stores workplace validation definitions. In the Oracle E-Business Suite 12.1.1 and 12.2.2 data model, it belongs to the Oracle Public Sector Human Resources (formerly Oracle HRMS for the Public Sector) functional area and serves as a rules repository for workplace-related validations used by the DE (Data Element) engine. Each row defines a named validation that can be applied during workplace assignment processing.

Under the heuristic Data Vault classification mined from the foreign key structure, this table is assessed as a standalone entity rather than a hub, link, or satellite. This classification is a modeling suggestion: the table has no outgoing foreign keys to other parent tables within the documented schema, although it is referenced by a version/child table. In practice, it behaves as a small reference/lookup table holding business rules rather than transactional data.

Key Information Stored

The table contains 11 documented columns. The most important are:

• WRKPLC_VLDTN_ID — Surrogate primary key, enforced by the PQH_DE_WRKPLC_VLDTNS_PK constraint. This value is the sole unique index and therefore the documented business-key candidate. It is referenced by the child table PQH_DE_WRKPLC_VLDTN_VERS.
• VALIDATION_NAME — The user-facing name of the workplace validation rule. This is the primary descriptive attribute and is typically displayed in setup forms and validation lists.
• BUSINESS_GROUP_ID — Identifies the HR security business group under which the validation is defined. It is a standard partitioning/security column in HR tables and is essential for multi-organization filtering.
• EMPLOYMENT_TYPE — Classifies the validation by the employment category to which it applies, allowing rules to be scoped to specific staff populations.
• REMUNERATION_REGULATION — Holds the remuneration regulation reference associated with the validation, tying the rule to pay/regulatory conditions.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Application Object Library (AOL) and OA Framework to detect concurrent updates.

The remaining columns (CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) are standard WHO/audit columns populated automatically by the framework and are not meaningful business attributes.

Common Use Cases and Queries

Typical use cases include reporting on configured validations for a business group, verifying that a validation exists before assigning it to a version record, and auditing changes to validation names or employment-type scoping.

Sample query listing validations for a business group:

• SELECT w.WRKPLC_VLDTN_ID, w.VALIDATION_NAME, w.EMPLOYMENT_TYPE, w.REMUNERATION_REGULATION FROM HR.PQH_DE_WRKPLC_VLDTNS w WHERE w.BUSINESS_GROUP_ID = :p_bg_id ORDER BY w.VALIDATION_NAME;

Sample join to find versions referencing each validation:

• SELECT v.WRKPLC_VLDTN_ID, w.VALIDATION_NAME, v.* FROM HR.PQH_DE_WRKPLC_VLDTNS w, HR.PQH_DE_WRKPLC_VLDTN_VERS v WHERE w.WRKPLC_VLDTN_ID = v.WRKPLC_VLDTN_ID;

Analysts should be aware that VALIDATION_NAME is not documented as uniquely indexed, so duplicate display names are possible across business groups; always filter on BUSINESS_GROUP_ID.

Related Objects

The documented relationship data identifies the following dependent object:

• PQH_DE_WRKPLC_VLDTN_VERS — The child table holding version rows for each workplace validation. It carries the foreign key WRKPLC_VLDTN_ID referencing PQH_DE_WRKPLC_VLDTNS.WRKPLC_VLDTN_ID. This is the deterministic parent-child relationship for the object.

Beyond the explicitly documented FK, related objects in the same PQH_DE family and the broader HR schema include the Data Element configuration tables and the HR_ALL_ORGANIZATION_UNITS / business group reference tables implied by BUSINESS_GROUP_ID and EMPLOYMENT_TYPE. Because the metadata lists no other foreign keys, integrators should treat PQH_DE_WRKPLC_VLDTNS as a lookup master and resolve additional join semantics through the application's datamodel rather than assuming undocumented constraints.