Results for “incident_reference”

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

Overview

The APPS.PAY_IE_SOCIAL_BENEFITS_V view exposes Irish social benefit (social welfare) absence and payment records maintained against employee assignments in Oracle E-Business Suite Payroll. It is a date-tracked (datetracked) view built over the PAY_IE_SOCIAL_BENEFITS_F base table, the date-effective entity that stores social benefit entries used by the Irish payroll legislative regime — for example Illness Benefit, Maternity Benefit, and similar Department of Social Protection payments that affect payroll processing and tax credit treatment.

In Oracle EBS 12.1.1 and 12.2.2 the view serves both reporting and integration purposes. Because it resolves the effective-dated row for the current application session, it delivers a consistent point-in-time snapshot of social benefit data without requiring callers to write their own effective-date logic. It is typically consumed by fast formulas, concurrent reports, extracts, and custom SQL that need a decoded, human-readable representation of benefit types and calculation options.

Underlying Base Objects

The view text is defined over four documented objects:

• PAY_IE_SOCIAL_BENEFITS_F — the primary date-effective base table holding social benefit records (aliased PSB in the view text).
• FND_SESSIONS — joined on SESSION_ID = USERENV('SESSIONID') to obtain the effective date of the current session, which is constrained between EFFECTIVE_START_DATE and EFFECTIVE_END_DATE. This is what makes the view datetrack-aware.
• PER_WORK_INCIDENTS — an outer join (PSB.INCIDENT_ID = PWI.INCIDENT_ID (+)) used to enrich the benefit row with incident reference, incident date, and incident type.
• HR_GENERAL — a package invoked for DECODE_LOOKUP calls that resolve the coded values BENEFIT_TYPE, CALCULATION_OPTION, and INCIDENT_TYPE into their displayed meanings.

Note that the physical table name is PAY_IE_SOCIAL_BENEFITS_F; the "_V" object wraps it with session-effective filtering and lookup decoding. Consequently only the row effective at the current session date is returned, and not the full history.

Key Columns

• SOCIAL_BENEFIT_ID — primary identifier of the social benefit record.
• ASSIGNMENT_ID — the assignment to which the benefit applies.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date-effective range for the record.
• BENEFIT_TYPE — the coded benefit type (the column sought by the query "benefit_type"); the lookup IE_BENEFIT_TYPE supplies its meaning.
• D_BENEFIT_TYPE — the decoded, display-friendly description of BENEFIT_TYPE, truncated to 80 characters.
• CALCULATION_OPTION / D_CALCULATION_OPTION — the coded and decoded calculation option (lookup IE_CALC_OPTION).
• ABSENCE_START_DATE / ABSENCE_END_DATE, BENEFIT_AMOUNT — the absence period and the benefit amount.
• REDUCED_TAX_CREDIT_AMOUNT, REDUCED_STANDARD_CUTOFF — tax credit–related attributes controlling reduced credit and cut-off treatment.
• INCIDENT_ID / INCIDENT_REFERENCE / INCIDENT_DATE / INCIDENT_TYPE / D_INCIDENT_TYPE — the linked work incident and its decoded type (lookup INCIDENT_TYPE).
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, plus the ROWID.

Common Use Cases and Queries

Typical use cases include payroll reporting on Irish social benefit absences, extracts feeding tax credit recalculation, and validation queries verifying that a benefit's benefit type is correctly classified for an assignment.

List benefits for an assignment:

• SELECT assignment_id, benefit_type, d_benefit_type, absence_start_date, absence_end_date, benefit_amount FROM apps.pay_ie_social_benefits_v WHERE assignment_id = :p_assignment_id;

Find all records for a specific benefit type by its decoded meaning:

• SELECT assignment_id, benefit_type, d_benefit_type, calculation_option, d_calculation_option FROM apps.pay_ie_social_benefits_v WHERE d_benefit_type LIKE '%Illness%';

Report on the effective social benefit type in use for assignments within a period, and join to work incident details:

• SELECT benefit_type, d_benefit_type, COUNT(*) FROM apps.pay_ie_social_benefits_v GROUP BY benefit_type, d_benefit_type ORDER BY 3 DESC;

Because the view filters on the current session's effective date via FND_SESSIONS, callers cannot retrieve historical rows directly; historical reporting must query PAY_IE_SOCIAL_BENEFITS_F without the session filter, applying explicit effective-date criteria.