Results for “ie_benefit_type”

16 results




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

Overview

APPS.PAY_IE_SOCIAL_BENEFITS_V is a reporting view within the Oracle E-Business Suite Payroll (PAY) schema, delivered specifically for the Irish (IE) legislative localization. It presents data recorded in the Irish Social Benefits datetracked entity, allowing social welfare benefit records tied to employee assignments to be queried through a single, join-complete interface. The view is defined over the transactional table PAY_IE_SOCIAL_BENEFITS_F and enriches each row with human-readable lookup descriptions, session-effective filtering, and incident context. In Oracle EBS 12.1.1 and 12.2.2, this view is used principally for reporting, extracts, and integration with downstream payroll or statutory reporting processes, rather than as a base for data entry. Because the Effective Start/End dates are constrained against the current FND_SESSIONS effective date, the view returns only the row version valid for the active application session, which is the standard datetrack pattern in Oracle HRMS and Payroll.

Underlying Base Objects

The view is documented in ETRM 12.2.2 as being owned by APPS and defined over four referenced base objects:

  • PAY_IE_SOCIAL_BENEFITS_F (synonym) — the primary transactional table holding Irish social benefit entries. The view aliases this as PSB.
  • PER_WORK_INCIDENTS (synonym) — the incident/absence record table, aliased as PWI, joined on INCIDENT_ID to provide incident reference, date, and type.
  • FND_SESSIONS (synonym) — the applications session table, aliased as FS, used to obtain the current session effective date for datetrack filtering.
  • HR_GENERAL (package) — the HRMS utility package, specifically HR_GENERAL.DECODE_LOOKUP, invoked to translate stored lookup codes into descriptive text.

The join to PER_WORK_INCIDENTS is an outer join (psb.incident_id = pwi.incident_id (+)), so benefit rows without an associated incident are still returned. The FND_SESSIONS predicate is an inner join against userenv('SESSIONID'), meaning the view always reflects the effective state of the current EBS session.

Key Columns

Beyond the standard datetrack and audit columns (SOCIAL_BENEFIT_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE, OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE), the view exposes:

Decoded columns are truncated to 80 characters via SUBSTR, consistent with standard EBS lookup display widths.

Common Use Cases and Queries

Typical usage includes auditing active social benefit records for an assignment, extracting data for Irish payroll statutory reporting, and reconciling benefits against absence or incident records. A simple query selects the decoded columns for the current session:

  • SELECT assignment_id, benefit_amount, d_benefit_type, d_calculation_option, incident_reference, incident_date FROM apps.pay_ie_social_benefits_v;
  • SELECT v.* FROM apps.pay_ie_social_benefits_v v WHERE v.assignment_id = :p_assignment_id;
  • SELECT v.incident_reference, v.benefit_amount FROM apps.pay_ie_social_benefits_v v WHERE v.reduced_tax_credit = 'Y';

Because the effective row is determined by the caller's session, developers should not attempt to query historical versions through this view; the underlying datetracked table must be used when a point-in-time history is required.