Search Results pay_value_result




Overview

APPS.PAY_ASSIGNMENT_ACTIONS_V3 is a supplementary database view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, owned by the APPS schema and registered under the FND Design Data reference PAY.PAY_ASSIGNMENT_ACTIONS_V3. The view is classified as VALID and is designated by Oracle as a supplementary view intended primarily to simplify forms coding. Oracle explicitly warns that this view should not be queried or altered for direct data manipulation, as its definition may change substantially in subsequent minor or major releases. Consequently, it is best treated as a read-only convenience construct rather than a supported integration interface.

The view consolidates payroll assignment action data with associated run result values, element type details, and payroll action attributes, presenting them in a flattened, human-readable form. For users searching on the column name "pay_value_result," this view is a principal location where that attribute is exposed. PAY_VALUE_RESULT is a VARCHAR2(4000) column that carries the textual representation of a payroll run result value—such as a monetary amount, a unit quantity, or a date—associated with a given assignment action. This makes the view useful for reporting on calculated payroll outcomes without joining directly to the underlying run result tables.

Underlying Base Objects

The view is defined over a set of payroll and HR base objects, all referenced through APPS synonyms: PAY_ASSIGNMENT_ACTIONS, PAY_ELEMENT_TYPES_F, PAY_INPUT_VALUES_F, PAY_PAYROLL_ACTIONS, PAY_RUN_RESULTS, PAY_RUN_RESULT_VALUES, and PER_ALL_ASSIGNMENTS_F. In addition, the definition depends on the HR_CHKFMT, HR_GENERAL, and HR_PAYROLLS packages, which supply formatting and general utility logic used to derive display values such as ACTION_TYPE_MEANING and PAY_VALUE_UOM_MEANING.

The central relationship flows from PAY_ASSIGNMENT_ACTIONS to PAY_RUN_RESULTS, linked via ASSIGNMENT_ACTION_ID, and onward to PAY_RUN_RESULT_VALUES to obtain the actual result value rendered in PAY_VALUE_RESULT. Assignment context is joined from PER_ALL_ASSIGNMENTS_F using ASSIGNMENT_ID, element definition from PAY_ELEMENT_TYPES_F using ELEMENT_TYPE_ID, and payroll process context from PAY_PAYROLL_ACTIONS. The view is not referenced by any database object, confirming its role as a terminal read-only layer.

Key Columns

  • ASSIGNMENT_ID – Numeric identifier of the assignment, linking to PER_ALL_ASSIGNMENTS_F.
  • ELEMENT_TYPE_ID – Identifier of the payroll element type producing the result.
  • EFFECTIVE_DATE – Date from which the assignment action record is effective.
  • PERIOD_NAME – Name of the payroll period in which the action falls.
  • ACTION_TYPE_MEANING – Decoded description of the assignment action type.
  • ASSIGNMENT_ACTION_ID – Identifier linking to PAY_ASSIGNMENT_ACTIONS and PAY_RUN_RESULTS.
  • OUTPUT_CURRENCY_CODE – Currency code applicable to the output value.
  • PAY_VALUE_UOM_MEANING – Unit of measure associated with the value.
  • RUN_RESULT_ID – Identifier of the payroll run result row.
  • PAY_VALUE_RESULT – The textual run result value; the column most commonly targeted in result-oriented reporting.
  • DATE_EARNED – Date on which the value was earned.

Common Use Cases and Queries

Typical usage includes reporting on payroll run results for a set of assignments, validating calculated values produced by element processing, and providing drill-down support in custom forms or concurrent programs. Because Oracle discourages direct dependency, production interfaces should preferentially query PAY_RUN_RESULTS and PAY_RUN_RESULT_VALUES directly.

A representative query retrieving assignment action results is shown below:

SELECT ASSIGNMENT_ID
     , ELEMENT_TYPE_ID
     , PERIOD_NAME
     , ACTION_TYPE_MEANING
     , PAY_VALUE_RESULT
     , OUTPUT_CURRENCY_CODE
     , DATE_EARNED
FROM   APPS.PAY_ASSIGNMENT_ACTIONS_V3
WHERE  PAY_VALUE_RESULT IS NOT NULL
AND    PERIOD_NAME = :period_name;