Search Results multi_seq

Overview

PAY_IE_ELEMENT_F_INFO_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PAY (Payroll) product. Its documented purpose is narrow and specific: it supplies formatted element information used by the Irish (IE) Payslip Advice Report. The view flattens and normalizes element definition and element value data that Oracle Payroll stores in the generic, key-value structure of PAY_ACTION_INFORMATION, so that a payslip reporting process can retrieve pre-joined, typed columns rather than decoding raw action-information rows itself.

The view exists in both EBS 12.1.1 and 12.2.2. It is not a business-facing entity view and is not intended for general payroll inquiry work; it is a report-support view whose contract is defined entirely by the layout requirements of the Irish payslip. Implementations that modify the IE payslip layout may encounter it, but direct modification is not supported because its definition is owned by the Payroll product.

Underlying Base Objects

The documented referenced base objects are FND_DATE (package), PAY_ACTION_INFORMATION, PAY_ACTION_INTERLOCKS, and PAY_ASSIGNMENT_ACTIONS. The latter three are accessed through APPS synonyms over the corresponding Payroll application tables.

• PAY_ACTION_INFORMATION — the central satellite table. It stores action context rows as key-value pairs, identified by ACTION_CONTEXT_TYPE, ACTION_INFORMATION_CATEGORY, and the ACTION_INFORMATION1..n columns. The view self-joins this table twice, aliased PAI1 and PAI2: PAI1 provides the element definition leg (category EMEA ELEMENT DEFINITION, ACTION_CONTEXT_TYPE 'PA'), and PAI2 provides the element instance values (category EMEA ELEMENT INFO, ACTION_CONTEXT_TYPE 'AAP').
• PAY_ASSIGNMENT_ACTIONS — links element entries to a payroll action and supplies the ASSIGNMENT_ACTION_ID that ties an element value to a specific assignment's payroll run.
• PAY_ACTION_INTERLOCKS — used in the second branch of the UNION to resolve the parent-child relationship between the element definition and its dependent element information rows.
• FND_DATE — the date conversion package; DATE_TO_DISPLAYDATE and CANONICAL_TO_DATE convert canonical date values into a displayable form for element values whose definition indicates a date type ('D').

The view is defined as a UNION of two SELECT statements, so an identical element value may be sourced through either the direct assignment-action path or the interlocked path.

Key Columns

• ASSIGNMENT_ACTION_ID — sourced from PAI2.ACTION_CONTEXT_ID. Identifies the assignment-level payroll action to which the element value belongs; the practical join key back to payroll run results.
• ELEMENT_NAME — SUBSTR of PAI1.ACTION_INFORMATION4, truncated to 30 characters. The element's display name as defined in the element definition leg.
• ELEMENT_VALUE — the element's value, returned as a number. A DECODE on PAI1.ACTION_INFORMATION6 determines the type: 'M' passes the raw value from PAI2.ACTION_INFORMATION4, while 'D' converts a canonical date to a display date via FND_DATE.
• MAIN_SEQ — from PAI2.ACTION_INFORMATION5. The primary sort sequence controlling position of the element on the payslip.
• MULTI_SEQ — from PAI2.ACTION_INFORMATION6. Handles elements that repeat within a payslip section.
• COLUMN_SEQ — from PAI2.ACTION_INFORMATION7. This is the column ordering attribute the user searched for; it controls which column of the payslip section the element occupies. Ordering by MAIN_SEQ, MULTI_SEQ, and COLUMN_SEQ reproduces the intended report layout.

Common Use Cases and Queries

Primary usage is as a data source for the IE Payslip Advice Report, but it is also used in diagnostic queries that reconstruct how an element will appear on an Irish payslip.

• Listing all elements for a payroll action in payslip order: SELECT element_name, element_value, column_seq FROM apps.pay_ie_element_f_info_v WHERE assignment_action_id = :p_action_id ORDER BY main_seq, multi_seq, column_seq;
• Identifying column placement for a named element: filter on ELEMENT_NAME and inspect COLUMN_SEQ to confirm which payslip column the element maps to.
• Verifying element definition setup: because ELEMENT_NAME derives from the EMEA ELEMENT DEFINITION leg, missing rows usually indicate absent or mis-categorized PAY_ACTION_INFORMATION setup rather than a view fault.

Queries should always constrain ASSIGNMENT_ACTION_ID or the underlying payroll action, since the view performs multiple joins across PAY_ACTION_INFORMATION and can otherwise scan a large volume of action-information rows.