Results for “ie_paye_info_source”

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

Overview

APPS.PAY_IE_PAYE_DETAILS_V is a reporting and integration view in the Oracle E-Business Suite Payroll module that exposes Irish PAYE (Pay As You Earn) tax configuration details for payroll assignments. The view is defined over the PAY_IE_PAYE_DETAILS_F table and resolves the effective-dated records relevant to the current user session by joining to FND_SESSIONS. Its primary function is to present both the stored lookup codes and their decoded, user-readable descriptions side by side, making it suitable for concurrent program reports, BI Publisher data models, and inbound/outbound interfaces that require decoded Irish statutory tax attributes.

The presence of the column info_source — and its decoded counterpart d_info_source, produced via HR_GENERAL.DECODE_LOOKUP('IE_PAYE_INFO_SOURCE', ppd.info_source) — explains why a search for "ie_paye_info_source" surfaces this view. That lookup type identifies the origin or source of the PAYE information held on a PAYE details record, such as whether the data was entered manually, received from a Revenue Commissioners file, or derived from another payroll process.

Underlying Base Objects

The view is defined over the following documented base objects:

• PAY_IE_PAYE_DETAILS_F — the core effective-dated table holding Irish PAYE details per assignment. It supplies virtually every column in the view.
• FND_SESSIONS — used in the WHERE clause to constrain rows so that the session's effective date falls between the record's effective_start_date and effective_end_date. This returns the currently effective version of each PAYE record rather than its full history.
• HR_GENERAL — a PL/SQL package whose decode_lookup function translates stored lookup codes into descriptive text, applied to info_source, tax_basis, tax_assess_basis, and their USC counterparts.

Because the view enforces the session effective date through userenv('SESSIONID'), callers automatically receive the date-effective row appropriate to their session context without additional filtering.

Key Columns

• paye_details_id, assignment_id — primary key and the payroll assignment to which the PAYE record applies.
• effective_start_date, effective_end_date — the date-effective window of the record.
• info_source / d_info_source — the PAYE information source code and its decoded description from lookup type IE_PAYE_INFO_SOURCE.
• tax_basis / d_tax_basis, tax_assess_basis / d_tax_assess_basis — tax basis and assessment basis codes with decoded descriptions.
• comm_period_no — the communication or notification period number associated with the record.
• weekly_tax_credit, monthly_tax_credit, weekly_std_rate_cut_off, monthly_std_rate_cut_off — standard PAYE credits and rate cut-off thresholds.
• certificate_start_date, certificate_end_date, certificate_issue_date — tax credit certificate validity and issue dates.
• usc_info_source, usc_tax_basis and USC rate/cutoff columns — Universal Social Charge configuration, including USC_RATE_1 through USC_RATE_5 and the associated yearly, monthly, and weekly cutoffs.
• YRLY_TAX_CRED, YRLY_TAX_RATE_1..4, MTHLY_TAX_RATE_2..4, WKLY_TAX_RATE_2..4, TAX_RATE_3..5 — statutory tax credit and rate values at yearly, monthly, and weekly frequencies.
• Audit columns — created_by, creation_date, last_updated_by, last_update_date, last_update_login, request_id, program_application_id, program_id, and program_update_date.

Common Use Cases and Queries

Typical uses include Irish payroll tax reports, verification of effective PAYE and USC rates for a given assignment, integration extracts to external payroll or Revenue reporting systems, and troubleshooting the origin of a PAYE record through d_info_source.

Retrieve the effective PAYE details for a specific assignment:

• SELECT assignment_id, effective_start_date, effective_end_date, d_info_source, d_tax_basis, weekly_tax_credit, monthly_tax_credit, d_tax_assess_basis FROM apps.pay_ie_paye_details_v WHERE assignment_id = :p_assignment_id;

List all assignments whose information source matches a given code:

• SELECT assignment_id, info_source, d_info_source, effective_start_date FROM apps.pay_ie_paye_details_v WHERE info_source = :p_info_source ORDER BY assignment_id, effective_start_date;

Summarise current USC rate configuration across assignments:

• SELECT assignment_id, d_usc_info_source, d_usc_tax_basis, usc_rate_1, usc_rate_2, usc_mthly_cutoff_1 FROM apps.pay_ie_paye_details_v WHERE usc_info_source IS NOT NULL;

Because the view already constrains rows by session effective date, queries generally need only assignment, source, or date-range predicates rather than explicit effective-date joins against PAY_IE_PAYE_DETAILS_F.