Search Results mandatory_flag_meaning




Overview
Explore in AI Chat

Overview

The PAY_RUN_RESULT_VALUES_V2 view is an Oracle E-Business Suite database object owned by the APPS schema in the Payroll (PAY) product family. It is designated as a user interface-support view, meaning it is not a base transactional table but rather a denormalized, presentation-oriented construct that flattens and translates the raw payroll run result data stored across several payroll tables. Its status is VALID in both 12.1.1 and 12.2.2, and it is documented in the ETRM repository with the description "Used to support user interface."

The view exposes payroll run result values in a form that is immediately consumable by Oracle Forms-based payroll screens and by external reporting or integration layers. It performs three distinct transformations that make the underlying data usable: it joins the run result values to their parent run results, assignment actions, and payroll actions to provide context; it applies the HR_CHKFMT.CHANGEFORMAT function to render the raw result value in the appropriate unit of measure and output currency; and it translates the MANDATORY_FLAG lookup code into a human-readable meaning. This last translation is directly relevant to users searching for mandatory_flag_meaning, since the view surfaces that meaning as an explicit column.

Underlying Base Objects

The view is defined over the following documented base objects: PAY_INPUT_VALUES_F_TL, PAY_ELEMENT_TYPES_F, PAY_INPUT_VALUES_F, HR_LOOKUPS (aliased twice), PAY_RUN_RESULT_VALUES, PAY_RUN_RESULTS, PAY_ASSIGNMENT_ACTIONS, and PAY_PAYROLL_ACTIONS. It also references the PL/SQL packages HR_CHKFMT and HR_API. The core join path links each run result value to its owning run result, then to the assignment action and payroll action that produced it, and finally to the input value definition and its translatable name.

Two important filter conditions appear in the view text. First, date-effective filtering is enforced through PPA.EFFECTIVE_DATE BETWEEN PIV.EFFECTIVE_START_DATE AND PIV.EFFECTIVE_END_DATE and the equivalent predicate against PAY_ELEMENT_TYPES_F, ensuring that only the input value and element type versions valid as of the payroll action's effective date are returned. Second, the MANDATORY_FLAG is decoded so that non-user-enterable input values are reported as not mandatory: DECODE(PIV.MANDATORY_FLAG, 'X', 'N', PIV.MANDATORY_FLAG).

Key Columns

  • PAYROLL_ACTION_ID — Identifier of the payroll action, providing the top-level run context.
  • ASSIGNMENT_ACTION_ID — Identifier of the assignment-level action associated with the run result.
  • RUN_RESULT_ID — Identifier of the parent run result row.
  • INPUT_VALUE_ID — Identifier of the input value definition that the result value corresponds to.
  • DISPLAY_RESULT_VALUE — The result value formatted via HR_CHKFMT.CHANGEFORMAT using the input value's unit of measure and the element type's output currency code.
  • INPUT_VALUE_NAME — The translated (language-specific) name of the input value, drawn from PAY_INPUT_VALUES_F_TL.
  • MANDATORY_FLAG_MEANING — The meaning of the mandatory flag resolved from the YES_NO lookup (HR_LOOKUPS), derived from the decoded MANDATORY_FLAG value. This is the column users seek when researching mandatory_flag_meaning.
  • UOM_MEANING — The meaning of the unit of measure resolved from the UNITS lookup.
  • DISPLAY_SEQUENCE — The ordering sequence used to position the input value in the user interface.

Common Use Cases and Queries

The view is typically queried to display the input value results of a payroll run for a specific assignment action, in the correct display order, with readable values and flags. A representative query that retrieves the mandatory flag meaning alongside the input value name and formatted result is:

SELECT input_value_name,
       display_result_value,
       mandatory_flag_meaning,
       uom_meaning,
       display_sequence
FROM   apps.pay_run_result_values_v2
WHERE  assignment_action_id = :p_assignment_action_id
ORDER  BY display_sequence;

Because it already joins through PAY_PAYROLL_ACTIONS and PAY_ASSIGNMENT_ACTIONS, the view can also be filtered by payroll action to report all results produced by a given run:

SELECT payroll_action_id,
       assignment_action_id,
       input_value_name,
       display_result_value,
       mandatory_flag_meaning
FROM   apps.pay_run_result_values_v2
WHERE  payroll_action_id = :p_payroll_action_id
ORDER  BY assignment_action_id, display_sequence;

Typical consumers include payroll result inquiry screens, custom concurrent programs that export run results, and integration interfaces that need the formatted display value rather than the raw numeric result. Developers should treat the view as read-only and avoid modifications, since it is an APPS-owned dictionary object maintained by Oracle.