Search Results pay_action_parameter_values_uk




Overview
Explore in AI Chat

Overview

HR.PAY_ACTION_PARAMETER_VALUES is a child table within the Oracle E-Business Suite Payroll (PAY) schema, owned by the HR schema and registered under FND Design Data as PAY.PAY_ACTION_PARAMETER_VALUES. The table stores the individual parameter values that belong to a row in PAY_ACTION_PARAMETER_GROUPS, allowing a set of action parameters to be bundled and controlled as a single group for a given user. This design enables parameter "striping," where the group definition governs the presentation and applicability of parameters rather than each parameter being configured independently.

From a heuristic Data Vault modeling perspective, the mined metadata classifies this object as standalone, meaning it carries no foreign key relationships in the documented physical schema. Absent a formal dependency link, this object is best treated as a satellite of the broader action-parameter configuration, with the grouping identity forming part of its natural key rather than a separately modeled hub or link.

Key Information Stored

The table is narrow and purpose-built, containing four documented columns. The most important elements are:

  • ACTION_PARAMETER_GROUP_ID — NUMBER. Identifies the parent parameter group, functionally tying each stored value to a row in PAY_ACTION_PARAMETER_GROUPS.
  • PARAMETER_NAME — VARCHAR2(30), mandatory. The name of the parameter being set for that group.
  • PARAMETER_VALUE — VARCHAR2(80). The value assigned to the named parameter.
  • ZD_EDITION_NAME — the editioning discriminator present in the 12.2.2 physical schema, supporting the multi-tenant editioning model introduced in EBS 12.2.

The documented business key is the unique index PAY_ACTION_PARAMETER_VALUES_UK, defined over ACTION_PARAMETER_GROUP_ID and PARAMETER_NAME in 12.1.1, and extended to include ZD_EDITION_NAME in 12.2.2. Consequently, a parameter name must be unique within its action parameter group. There is no separate surrogate primary key; the group identifier combined with the parameter name (and edition name) acts as the effective row identifier.

Common Use Cases and Queries

Typical usage centres on retrieving, auditing, or replicating parameter configurations that drive payroll action processing. A direct query returns the full configuration:

SELECT PARAMETER_NAME, PARAMETER_VALUE, ACTION_PARAMETER_GROUP_ID
FROM HR.PAY_ACTION_PARAMETER_VALUES;

A more common pattern filters by group to reconstruct a single parameter set:

SELECT PARAMETER_NAME, PARAMETER_VALUE
FROM HR.PAY_ACTION_PARAMETER_VALUES
WHERE ACTION_PARAMETER_GROUP_ID = :group_id;

Reporting scenarios include auditing parameter changes for compliance, comparing groups across environments during a clone or upgrade, and extracting parameter-driven settings into external configuration repositories. Because the table is narrow, joins to the parent group and to action definitions are essential to give the parameter data business meaning.

Related Objects

The primary relationship is to PAY_ACTION_PARAMETER_GROUPS, which acts as the parent, joined on ACTION_PARAMETER_GROUP_ID. The ETRM dependency data also shows the following objects referencing this table:

  • PAY_ACTION_PARAMETERS_ARI — APPS-owned interface/view object dependent on the parameter values.
  • PAY_ACTION_PARAMETERS_ARU — APPS-owned update object dependent on the parameter values.
  • PAY_ACTION_PARAMETER_VALUES (APPS synonym) — public access path to the HR table.

The table does not itself reference any further database object, confirming its role as a dependent, value-holding child of the action parameter group structure.