Results for “overridden_subclass”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PAY_IE_SOE_PRSI_DETAILS_V is a read-only database view owned by the APPS schema and defined within the Payroll (PAY) product family of Oracle E-Business Suite. It is documented as being used by the Irish Statement of Earnings (IE SOE) forms, which are the statutory payroll reporting artifacts produced for employees subject to Irish Pay Related Social Insurance (PRSI). The view surfaces the PRSI contribution class and any overridden subclass recorded against an assignment action for the Irish "IE PRSI DETAIL" element, keyed by ASSIGNMENT_ACTION_ID.

The object holds VALID status in the ETRM repository for both 12.1.1 and 12.2.2 and is a reporting/integration layer rather than a transactional table. Application code, concurrent programs, and custom BI Publisher or Oracle Reports outputs that need to reproduce the PRSI classification used on an Irish SOE can query the view directly instead of re-deriving the decode logic from the underlying payroll run result tables. Because the view is owned by APPS and reads core payroll data, it is not intended to be modified; it is exposed purely as a query surface.

Underlying Base Objects

The view text reveals a five-table join, resolved through APPS synonyms:

• FND_SESSIONS — supplies the current session context, used to resolve the effective date driving element-type and input-value lookups via USERENV('SESSIONID').
• PAY_ELEMENT_TYPES_F — the element type definition; filtered to ELEMENT_NAME = 'IE PRSI DETAIL' and LEGISLATION_CODE = 'IE'.
• PAY_RUN_RESULTS — the per-assignment-action run results for that element, joined on ELEMENT_TYPE_ID.
• PAY_INPUT_VALUES_F — the input value definitions for the element, restricted to the input value names 'CONTRIBUTION CLASS' and 'SUBCLASS'.
• PAY_RUN_RESULT_VALUES — the actual input value results, linked by RUN_RESULT_ID and INPUT_VALUE_ID.

The joins are governed by explicit hints (ORDERED and named indexes such as FND_SESSIONS_U1, PAY_ELEMENT_TYPES_F_UK2, PAY_RUN_RESULTS_N50, PAY_INPUT_VALUES_F_N50, and PAY_RUN_RESULT_VALUES_PK), indicating the view was tuned for direct lookup performance rather than bulk extraction.

Key Columns

The view exposes three columns:

• ASSIGNMENT_ACTION_ID — the grouping key and the primary correlation point back to PAY_ASSIGNMENT_ACTIONS and, through it, to the assignment and payroll run. A single row is returned per assignment action.
• CONTRIBUTION_CLASS — the PRSI contribution class value (for example, the class letter applicable to the employee), derived by a MAX(DECODE(PIV.NAME, 'CONTRIBUTION CLASS', PRRV.RESULT_VALUE, NULL)) aggregate over the run result values.
• OVERRIDDEN_SUBCLASS — the manual subclass override value entered against the PRSI detail element, derived by the equivalent MAX(DECODE(PIV.NAME, 'SUBCLASS', ...)) aggregate. Where no override exists, this column returns NULL.

The MAX/DECODE/CASE pattern, combined with the GROUP BY on ASSIGNMENT_ACTION_ID, collapses the multiple input value rows into one row per assignment action, which is the form expected by the SOE reporting layout.

Common Use Cases and Queries

Typical usage is to enrich Irish SOE output with the PRSI classification actually applied at payroll run time. A simple projection retrieves all classifications for an assignment action:

• SELECT assignment_action_id, contribution_class, overridden_subclass FROM apps.pay_ie_soe_prsi_details_v WHERE assignment_action_id = :p_action_id;
• SELECT prsi.assignment_action_id, prsi.contribution_class, prsi.overridden_subclass FROM apps.pay_ie_soe_prsi_details_v prsi, apps.pay_assignment_actions paa WHERE prsi.assignment_action_id = paa.assignment_action_id AND paa.assignment_id = :p_assignment_id;
• SELECT contribution_class, COUNT(*) FROM apps.pay_ie_soe_prsi_details_v GROUP BY contribution_class; for distribution reporting.

Because the view is session-date sensitive — its effective-date filter derives from FND_SESSIONS and USERENV('SESSIONID') — ad-hoc queries must be executed through an EBS session (for example, via SQL*Plus after FND_GLOBAL initialization or through a concurrent program) rather than from a disconnected client, otherwise no effective-date row will match and the view will return no data. Joins should be limited to the columns needed, as the ORDERED and index hints are calibrated for targeted access by ASSIGNMENT_ACTION_ID.