Search Results action_parameter_group_id




Overview
Explore in AI Chat

Overview

APPS.PAY_ACTION_PARAMETERS is a reporting and integration view in the Oracle E-Business Suite Payroll (PAY) module. It exposes the runtime parameter name/value pairs that govern the behaviour of a payroll action — such as a payroll run, a costing process, a prepayment, a reversal, or a legislative or business-group-specific process. Rather than presenting every parameter row defined in the underlying storage table, the view applies a resolution rule that returns the parameter set appropriate to the current execution context.

The view is defined over PAY_ACTION_PARAMETER_VALUES and calls the PAY_CORE_UTILS package function GET_PAP_GROUP_ID. This makes it a context-sensitive view: the rows returned depend on the action parameter group currently in effect for the session or process. In Oracle EBS 12.1.1 and 12.2.2 the object is owned by APPS and is generally consumed read-only by concurrent programs, PL/SQL APIs, and custom reporting rather than being maintained directly.

Underlying Base Objects

The view is defined over two referenced objects documented in the ETRM metadata:

  • PAY_ACTION_PARAMETER_VALUES (SYNONYM) — the base storage object holding individual parameter rows, each carrying a PARAMETER_NAME, a PARAMETER_VALUE, and an ACTION_PARAMETER_GROUP_ID that associates the row with a specific action parameter group.
  • PAY_CORE_UTILS (PACKAGE) — providing the function GET_PAP_GROUP_ID, which dynamically resolves the action parameter group identifier applicable to the current context.

The view text filters PAY_ACTION_PARAMETER_VALUES using the predicate NVL(PAY_CORE_UTILS.GET_PAP_GROUP_ID, -1) = NVL(PAPV.ACTION_PARAMETER_GROUP_ID, -2), plus an OR branch that returns rows where ACTION_PARAMETER_GROUP_ID is null provided no grouped override exists for the same parameter name. This implements a layered resolution model: a grouped (specific) value takes precedence, and an ungrouped (default) row is returned only when no grouped value has been defined.

Key Columns

The view exposes a narrow, two-column projection of the underlying group-parameter data:

  • PARAMETER_NAME — the identifier of the parameter, such as a process option or run-control attribute. Together with the resolved group it forms the logical key consulted by calling code.
  • PARAMETER_VALUE — the value assigned to that parameter for the resolved action parameter group. Values are typically stored and returned as character strings and interpreted by the consuming process according to the parameter's data type.

Note that ACTION_PARAMETER_GROUP_ID is present in the base table and is central to the view's WHERE clause, but it is not projected as an output column of APPS.PAY_ACTION_PARAMETERS. This is the column a user searching on "action_parameter_group_id" should understand as the grouping discriminator that the view resolves internally through GET_PAP_GROUP_ID.

Common Use Cases and Queries

The view is most often queried to inspect which parameter values are effective for the current action context, or to verify that a specific parameter has been configured at the appropriate grouping level. A typical lookup of a single parameter is:

  • SELECT parameter_name, parameter_value FROM apps.pay_action_parameters WHERE parameter_name = :p_name;
  • SELECT parameter_name, parameter_value FROM apps.pay_action_parameters ORDER BY parameter_name;

Because the resolution of the applicable group is performed dynamically, results can differ from a direct query against PAY_ACTION_PARAMETER_VALUES, which returns all grouping levels unconditionally. When diagnosing configuration issues, developers commonly compare the two sources: the base table reveals every stored group row, while the view shows only the row that the resolution logic would actually supply. Integration code should therefore rely on the view when it needs the effective value, and on the base table when it needs the full configuration picture across all action parameter groups.