Search Results output_currency_code




Overview
Explore in AI Chat

Overview

PAY_ASSIGNMENT_ACTIONS_V3 is an APPS-owned database view in the Oracle E-Business Suite Payroll (PAY) product. Per the ETRM 12.2.2 metadata, the object is registered with a status of VALID and its documented description is simply "Used to support user interface." In practice, this view is a denormalized, pre-joined projection that exposes completed assignment actions together with the corresponding run result, input value, and element type context. It is used primarily by payroll-facing forms, concurrent programs, and reporting layers that need to present payroll action results — particularly the calculated pay value and its currency — without requiring the caller to assemble the multi-table join manually.

The view is not itself the source of truth for payroll processing; it is a read-only, query-only construct intended to surface a specific slice of payroll results. Because it is defined in the APPS schema and references SYNONYM-wrapped base tables, it is available to any EBS responsibility whose data grants permit access to the APPS objects.

Underlying Base Objects

The ETRM metadata lists the following referenced base objects for PAY_ASSIGNMENT_ACTIONS_V3:

The view joins the assignment action header (PAY_ASSIGNMENT_ACTIONS) to the payroll action (PAY_PAYROLL_ACTIONS) via PAYROLL_ACTION_ID, to the run result (PAY_RUN_RESULTS) via ASSIGNMENT_ACTION_ID, and from the run result to PAY_RUN_RESULT_VALUES via RUN_RESULT_ID. The input value definition (PAY_INPUT_VALUES_F) and element type (PAY_ELEMENT_TYPES_F) supply the unit of measure and output currency. Employee assignment attributes come from PER_ALL_ASSIGNMENTS_F. The HR_GENERAL and HR_PAYROLLS packages are invoked as PL/SQL functions (DECODE_LOOKUP, DISPLAY_PERIOD_NAME) to translate codes into display values, and HR_CHKFMT.CHANGEFORMAT is used to format the numeric pay value with the correct UOM and currency.

Key Columns

The view exposes the following significant columns, all derived from the join described above:

  • ASSIGNMENT_ID — from PAY_ASSIGNMENT_ACTIONS; identifies the employee assignment.
  • ASSIGNMENT_ACTION_ID — the assignment action being reported.
  • ELEMENT_TYPE_ID — the payroll element associated with the input value.
  • EFFECTIVE_DATE — the effective date of the payroll action.
  • PERIOD_NAME — derived via HR_PAYROLLS.DISPLAY_PERIOD_NAME(PAC.PAYROLL_ACTION_ID); the descriptive payroll period.
  • ACTION_TYPE_MEANING — derived via HR_GENERAL.DECODE_LOOKUP('ACTION_TYPE', PAC.ACTION_TYPE); translated action type.
  • PAY_VALUE_UOM_MEANING — derived via HR_GENERAL.DECODE_LOOKUP('UNITS', PIV.UOM).
  • OUTPUT_CURRENCY_CODE — from PAY_ELEMENT_TYPES_F; the currency of the element's pay value. This is the column most relevant to the search term "output_currency_code", as it is the currency in which the result is denominated.
  • PAY_VALUE_RESULT — the formatted pay value produced by HR_CHKFMT.CHANGEFORMAT, using the UOM and OUTPUT_CURRENCY_CODE.
  • RUN_RESULT_ID — the run result contributing to balances.
  • DATE_EARNED — the date the pay value was earned.

Common Use Cases and Queries

The view is typically queried to present completed payroll action results for a given assignment, element, or period, most often when reconciling balances or displaying a payroll run summary. Because the view filters to ACTION_TYPE in ('B','Q','V','R') and ACTION_STATUS='C', only completed balance adjustments, quickpays, reversals, and runs are returned, and only run results with status 'P' or 'PA'.

A representative query retrieving the output currency and pay value for an assignment is:

  • SELECT ASSIGNMENT_ID, ELEMENT_TYPE_ID, PERIOD_NAME, ACTION_TYPE_MEANING, OUTPUT_CURRENCY_CODE, PAY_VALUE_RESULT, DATE_EARNED FROM PAY_ASSIGNMENT_ACTIONS_V3 WHERE ASSIGNMENT_ID = :p_assignment_id AND EFFECTIVE_DATE BETWEEN :p_start AND :p_end ORDER BY EFFECTIVE_DATE;
  • SELECT OUTPUT_CURRENCY_CODE, SUM(PAY_VALUE_RESULT) FROM PAY_ASSIGNMENT_ACTIONS_V3 WHERE PERIOD_NAME = :p_period GROUP BY OUTPUT_CURRENCY_CODE;

Because PAY_VALUE_RESULT is a formatted character string rather than a numeric, aggregation is only meaningful when the formatting is consistent within a currency group; numeric analysis is more reliable against the underlying PAY_RUN_RESULT_VALUES table. Consumers should also note the outer join on PAY_ELEMENT_TYPES_F, which allows input values without a matching element type to remain in the result set with a NULL OUTPUT_CURRENCY_CODE.