Results for “d_contribution_class”

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

Overview

The PAY_IE_PRSI_DETAILS_V view is an Oracle E-Business Suite (EBS) database object owned by the APPS schema and delivered as part of the PAY (Payroll) product. It is a user-interface support view rather than a standalone reporting entity, and its primary purpose is to present Pay Related Social Insurance (PRSI) detail records maintained for Irish payroll processing in a session-aware, decoded, and date-effective form. The view is defined over the Payroll interface table PAY_IE_PRSI_DETAILS_F and is filtered by the current user session so that only the record effective for the session's effective date is returned. This behaviour makes the view suitable for Forms-based maintenance screens and other UI components that must display the single active PRSI record for an assignment.

Because it exposes descriptive lookup values (such as decoded contribution classes and subclasses) alongside raw identifiers, the view is also useful for lightweight reporting and integrations that require human-readable Irish PRSI attributes without performing separate lookup joins. The column EXEMPTION_START_DATE, referenced in the underlying base table, records the commencement date of a PRSI exemption granted to an employee, and it is surfaced directly through this view for display and query purposes.

Underlying Base Objects

The view is defined with a join between PAY_IE_PRSI_DETAILS_F (referenced via a synonym) and FND_SESSIONS (also referenced via a synonym), and it calls the HR_GENERAL package for lookup decoding. The session join uses USERENV('SESSIONID') to match the runtime session, and the effective date from FND_SESSIONS is constrained between the record's EFFECTIVE_START_DATE and EFFECTIVE_END_DATE. The HR_GENERAL.DECODE_LOOKUP function is applied to expand the IE_PRSI_CONT_CLASS and IE_PRSI_CONT_SUBCLASS lookup types into their display meanings.

• PAY_IE_PRSI_DETAILS_F — the base PRSI details table supplying all PRSI attribute columns.
• FND_SESSIONS — provides the session context and effective date used for date-effective filtering.
• HR_GENERAL — package used to decode lookup values into descriptive text.

Key Columns

• ROW_ID — ROWID of the base table row, used by the UI for row identification.
• PRSI_DETAILS_ID — primary identifier of the PRSI detail record.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — date-effective range of the record.
• CONTRIBUTION_CLASS / D_CONTRIBUTION_CLASS — the PRSI contribution class code and its decoded description.
• OVERRIDDEN_SUBCLASS / D_OVERRIDDEN_SUBCLASS — an overriding subclass and its decoded description.
• SOC_BEN_FLAG / SOC_BEN_START_DATE — social benefit indicator and its start date.
• OVERRIDDEN_INS_WEEKS / NON_STANDARD_INS_WEEKS — insurance week adjustments.
• EXEMPTION_START_DATE / EXEMPTION_END_DATE — the start and end of any PRSI exemption period granted to the employee.
• CERT_ISSUED_BY / DIRECTOR_FLAG — certificate issuer and director indicator.
• ASSIGNMENT_ID and COMMUNITY_FLAG — assignment linkage and community employment indicator.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID and program identifiers.

Common Use Cases and Queries

Typical uses include UI display of current PRSI details, verification of exemption periods, and ad-hoc reporting on contribution classes. Because the view is session-filtered, queries executed outside a UI session may return no rows unless a matching FND_SESSIONS record exists.

Example: retrieve PRSI details and exemption data for an assignment.

• SELECT assignment_id, contribution_class, d_contribution_class, exemption_start_date, exemption_end_date FROM apps.pay_ie_prsi_details_v WHERE assignment_id = :assignment_id;

Example: list all records with an active exemption start date.

• SELECT prsi_details_id, assignment_id, exemption_start_date, exemption_end_date FROM apps.pay_ie_prsi_details_v WHERE exemption_start_date IS NOT NULL ORDER BY exemption_start_date;