Results for “pps_no”

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

Overview

PAY_IE_BIK_OTHER_BENEFITS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, classified under the PAY (Payroll) product family. It is documented as one of the Irish (IE) views used for WEB ADI reporting, meaning its primary purpose is to expose Benefit-in-Kind (BIK) data in a flattened, report-ready structure suitable for consumption by the Web Applications Desktop Integrator (ADI) upload/download framework. The view is marked VALID and is present in both the 12.1.1 and 12.2.2 environments referenced by the ETRM metadata.

The view consolidates payroll run result data for Irish BIK elements — specifically recurring reportable items, employer-provided assets, and non-recurring reportable items — and pivots input value names into discrete columns. The output combines monetary values with employee identification and assignment context, producing a denormalized row set that describes, per employee, the benefit description, benefit start and end dates, the calculated benefit value, the PPS number (Irish social insurance identifier), and payroll/assignment identifiers. Because it draws on effective-dated HR and payroll objects, the view reflects data as of the payroll action's date earned.

Underlying Base Objects

The view text joins a set of payroll and HR tables and views. The principal sources are PAY_ELEMENT_TYPES_F (element definitions), PAY_INPUT_VALUES_F (input value definitions), PAY_PAYROLLS_F, PAY_ASSIGNMENT_ACTIONS, PAY_PAYROLL_ACTIONS, PAY_RUN_RESULTS, and PAY_RUN_RESULT_VALUES — the last being the source of the pivoted RESULT_VALUE data. Employee identity and assignment context come from PER_PEOPLE_F and PER_ASSIGNMENTS_F, joined on PERSON_ID, ASSIGNMENT_ID, and BUSINESS_GROUP_ID, with additional effective-date filtering on PPA.DATE_EARNED against the assignment's effective start and end dates (per the documented view text).

The ETRM 12.2.2 metadata lists the referenced base objects as HR_API (PACKAGE), HR_GENERAL (PACKAGE), HR_LOOKUPS (VIEW), HR_PERSON_NAME (PACKAGE), HR_SECURITY (PACKAGE), PAY_ASSIGNMENT_ACTIONS (SYNONYM), PAY_ELEMENT_TYPES_F (SYNONYM), PAY_IE_BIK (PACKAGE), PAY_INPUT_VALUES_F (SYNONYM), PAY_PAYROLLS_F (VIEW), PAY_PAYROLL_ACTIONS (SYNONYM), PAY_RUN_RESULTS (SYNONYM), PAY_RUN_RESULT_VALUES (SYNONYM), PER_ASSIGNMENTS_F (VIEW), and PER_PEOPLE_F (VIEW). Notably, the APPLICATION logic is delegated to the PAY_IE_BIK package, whose GET_BALANCE_VALUES function computes the reportable amounts, and to HR_LOOKUPS for decoding the IE_BIK_ASSET_TYPE lookup into a meaningful asset type description.

Key Columns

• BENEFIT_START_DATE / BENEFIT_END_DATE — Derived from input value names such as 'BENEFIT START DATE', 'BENEFIT DATE', 'ASSET PROVISION START DATE', and their end-date counterparts, defaulting to '0' when absent.
• DESCRIPTION — Populated from 'ITEM DESCRIPTION' or, for employer assets, by decoding the 'ASSET TYPE' result value through HR_LOOKUPS against lookup type IE_BIK_ASSET_TYPE.
• VALUE — The reportable benefit amount, resolved via PAY_IE_BIK.GET_BALANCE_VALUES using the assignment action, source ID, date earned, and the appropriate balance name ('IE BIK OTHER REPORTABLE ITEM' or 'IE BIK ASSET TYPE'), or from the 'BENEFIT VALUE' input value for non-recurring items.
• PPS_NO — The employee's national identifier (Irish PPS number) from PER_PEOPLE_F.
• SURNAME / FIRST_NAME — Employee name components.
• ASSIGNMENT_NUMBER / ASSIGNMENT_ID — The assignment context for the benefit record.
• PAYROLL_ID / CONSOLIDATION_SET_ID / ASSIGNMENT_SET_ID — Payroll processing identifiers used to scope the reportable run.

Common Use Cases and Queries

Typical usage is through the WEB ADI Irish BIK reporting process, but ad hoc extraction is common. A straightforward query to retrieve all benefits for a given payroll run would resemble:

• SELECT pps_no, surname, first_name, description, benefit_start_date, benefit_end_date, value FROM apps.pay_ie_bik_other_benefits_v WHERE payroll_id = :payroll_id ORDER BY surname, first_name;
• SELECT * FROM apps.pay_ie_bik_other_benefits_v WHERE assignment_id = :assignment_id AND benefit_end_date >= :effective_date;

Because the view uses MAX with DECODE aggregation and calls PL/SQL functions, queries against it should be restricted by payroll, assignment, or date predicates to avoid performance degradation. Access is normally controlled by HR security and payroll business group, so results may be filtered implicitly by the user's security profile.