Search Results action_information4




Overview
Explore in AI Chat

Overview

The APPS.PAY_IE_ELEMENT_F_INFO_V view is a payroll reporting construct within Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that exposes Irish (IE) legislative element information associated with assignment actions. It is not a base table but a query-layer object that resolves the normalized key-value storage of PAY_ACTION_INFORMATION into a set of typed, assignment-action-scoped columns. The view is intended for consumption by Oracle Payroll processes and by external reporting/integration consumers that require the identity and monetary value of an element processed against an assignment action.

Its central role is to join the payroll-action context (PA) that defines an EMEA element definition to the assignment-action context (AAP) that carries the EMEA element information, returning the element name, its value, and a set of sequence attributes used for positioning. Because the underlying data is stored as generic action information attributes rather than strongly typed columns, the view performs the necessary DECODE, SUBSTR, and date-conversion logic to present the payload in a consumable form.

Underlying Base Objects

The view is defined over the following documented base objects:

  • PAY_ACTION_INFORMATION (synonym) — the principal source, referenced twice as aliases PAI1 and PAI2. PAI1 supplies the element definition row (category EMEA ELEMENT DEFINITION, context type PA), while PAI2 supplies the per-assignment element information row (category EMEA ELEMENT INFO, context type AAP).
  • PAY_ASSIGNMENT_ACTIONS (synonym) — supplies the assignment action linkage (APAA and PPAA aliases) that ties the element information back to a payroll action.
  • PAY_ACTION_INTERLOCKS (synonym) — used only in the second UNION branch to reconcile related payroll and assignment actions.
  • FND_DATE (package) — provides DATE_TO_DISPLAYDATE and CANONICAL_TO_DATE for converting date-typed element values.

The definition is a UNION of two branches: the first selects direct matches where PAI1.ACTION_INFORMATION1 is null; the second, using PAY_ACTION_INTERLOCKS, resolves interlocks between the payroll action and assignment actions. Join predicates match PAI1.ACTION_INFORMATION2 to PAI2.ACTION_INFORMATION1 and PAI1.ACTION_INFORMATION3 to PAI2.ACTION_INFORMATION2, with PAI2.ACTION_CONTEXT_ID equated to the assignment action identifier.

Key Columns

  • ASSIGNMENT_ACTION_ID — derived from PAI2.ACTION_CONTEXT_ID; identifies the assignment action to which the element information applies.
  • ELEMENT_NAME — the first 30 characters of PAI1.ACTION_INFORMATION4; identifies the element (this is the attribute matched by the user search term "action_information4").
  • ELEMENT_VALUE — a numeric value resolved via DECODE on PAI1.ACTION_INFORMATION6: for 'M' the monetary amount is taken directly from PAI2.ACTION_INFORMATION4; for 'D' the value is a date converted from canonical to display format.
  • MAIN_SEQ, MULTI_SEQ, COLUMN_SEQ — numeric sequence attributes from PAI2.ACTION_INFORMATION5, 6, and 7, used to order and position element values.

Common Use Cases and Queries

Typical usage is to report Irish element values for a given assignment action or set of actions. For example:

SELECT element_name, element_value, main_seq, multi_seq, column_seq
FROM   apps.pay_ie_element_f_info_v
WHERE  assignment_action_id = :p_assignment_action_id
ORDER  BY main_seq, multi_seq, column_seq;

The view supports payroll audit reports, legislative element extracts, and integration feeds that must present element values in a deterministic order. Because it joins on payroll and assignment action identifiers, it is commonly combined with PAY_ASSIGNMENT_ACTIONS and PAY_PAYROLL_ACTIONS to constrain results by payroll run, period, or assignment. Consumers should note that values are limited to the numeric and date forms handled by the DECODE and FND_DATE logic, and that element names are truncated to 30 characters.