Results for “pay_ie_payment_values_v”
34 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
PAY_IE_PAYMENT_VALUES_V is an Oracle E-Business Suite view owned by the APPS schema and classified under the PAY — Payroll product family. In EBS 12.1.1 and 12.2.2 it is a read-only aggregation view that exposes payroll run result values for Irish (IE) legislative elements in a form suitable for payslip and advice (payment) reporting. Its documented purpose is to support the Irish Payslip Advice Report and, specifically, to feed the PAY_IE_EAR_DED_V view, which consumes its output for earnings and deduction presentation.
The view collapses the many-to-many relationship between element types, input values, and run result values into a single consolidated monetary amount per element and input value. It is therefore a reporting construct rather than a transactional entity, and it is intended to be queried by concurrent programs, BI Publisher data templates, and ad-hoc payroll reporting rather than updated directly.
Underlying Base Objects
Per ETRM 12.2.2 documentation, the view references the following base objects:
FND_NUMBER— a package supplyingCANONICAL_TO_NUMBER, used to convert stored canonical result strings to numeric values.FND_SESSIONS— a synonym used to constrain the query to the current user session and its effective date.PAY_ACTION_INTERLOCKS— links locking assignment actions to run results, exposingLOCKING_ACTION_ID.PAY_ELEMENT_TYPES_F— the element type definition (name, processing priority).PAY_INPUT_VALUES_F— the input value definitions (name, unit of measure, effective dates).PAY_RUN_RESULTS— the parent payroll run result rows, joined with status filter.PAY_RUN_RESULT_VALUES— the child rows carryingRESULT_VALUEper input value.
The join path is element type → input value → run result value → run result → action interlock, with effective-dating enforced against the session effective date. Only run results with status 'P' (processed) or 'PA' (partially processed) are returned.
Key Columns
ROW_ID— the ROWID of the underlying element type row, used as a row identifier.ELEMENT_TYPE_ID— identifies the payroll element (e.g. a BIK detail element, PAYE rate element, or net tax element).INPUT_VALUE_ID— identifies the specific input value consumed for the element.RESULT_VALUE— the aggregated numeric result. For the element IE BIK ARREARAGE DETAILS the summed value is multiplied by −1 to present the arrearage as a negative; all other elements return the positive sum.PROCESSING_PRIORITY— the element's processing priority, useful for ordering output on the payslip.ASSIGNMENT_ACTION_ID— supplied fromPAY_ACTION_INTERLOCKS.LOCKING_ACTION_ID, tying the result to the assignment action that locked it.
The WHERE clause restricts output to PAY VALUE inputs with UOM 'M' (money), plus specific BIK and PAYE elements, and explicitly excludes the element IE NET TAX. The GROUP BY consolidates on locking action, processing priority, element type, element name, and input value.
Common Use Cases and Queries
Typical uses include payslip advice production, BIK (benefit-in-kind) reporting for Irish Revenue submissions, and reconciliation of processed run results against assignment actions. A representative query for a payroll run is:
SELECT element_type_id, input_value_id, result_value FROM apps.pay_ie_payment_values_v ORDER BY processing_priority;SELECT t.element_name, v.result_value FROM apps.pay_ie_payment_values_v v, apps.pay_element_types_f t WHERE v.element_type_id = t.element_type_id AND t.element_name = 'IE BIK ACCOMMODATION DETAILS';- Joining to
PAY_ASSIGNMENT_ACTIONSonassignment_action_idto associate results with a specific assignment and action.
Because results are session- and effective-date sensitive, concurrent programs must execute in a session whose effective date falls within the effective range of the element and input value definitions. Reports should always filter or order by PROCESSING_PRIORITY to preserve the payslip sequence expected by the Irish payslip templates.
-
Used in IE Payslip Advice Report in PAY_IE_EAR_DED_V View
APPS.PAY_IE_PAYMENT_VALUES_V·↳ FND_NUMBER·↳ FND_SESSIONS·↳ PAY_ACTION_INTERLOCKS·Explore PAY module →
-
Used in IE Payslip Advice Report in PAY_IE_EAR_DED_V View
APPS.PAY_IE_PAYMENT_VALUES_V·↳ FND_NUMBER·↳ FND_SESSIONS·↳ PAY_ACTION_INTERLOCKS·Explore PAY module →
-
VIEW: APPS.PAY_IE_EAR_DED_V 12.2.2
-
View: PAY_IE_EAR_DED_V 12.2.2
Used in IE Payslip Advice Report
APPS.PAY_IE_EAR_DED_V·↳ FND_NUMBER·↳ PAY_ACTION_INFORMATION·↳ PAY_ACTION_INTERLOCKS·Explore PAY module →
-
View: PAY_IE_EAR_DED_V 12.1.1
Used in IE Payslip Advice Report
APPS.PAY_IE_EAR_DED_V·↳ FND_NUMBER·↳ PAY_ACTION_INFORMATION·↳ PAY_ACTION_INTERLOCKS·Explore PAY module →
-
VIEW: APPS.PAY_IE_EAR_DED_V 12.1.1
-
VIEW: APPS.PAY_IE_EAR_DED_V 12.2.2
-
VIEW: APPS.PAY_IE_EAR_DED_V 12.1.1
-
12.1.1 FND Design Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
SYNONYM: APPS.FND_SESSIONS 12.2.2
-
SYNONYM: APPS.FND_SESSIONS 12.1.1
-
eTRM - PAY Tables and Views 12.1.1
Temporary table used to hold invalid location addresses.
-
12.2.2 DBA Data 12.2.2
-
eTRM - PAY Tables and Views 12.2.2
Temporary table used to hold invalid location addresses.
-
12.1.1 DBA Data 12.1.1
-
eTRM - PAY Tables and Views 12.1.1
Temporary table used to hold invalid location addresses.
-
eTRM - PAY Tables and Views 12.2.2
Temporary table used to hold invalid location addresses.