Results for “per_nl_wao_list_v”

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

Overview

The PER_NL_WAO_LIST_V view is an Oracle E-Business Suite database object owned by the APPS schema within the PER (Human Resources) module. It is documented as the Dutch WAO List View, where WAO refers to the Dutch Wet op de Arbeidsongeschiktheidsverzekering (Work and Income (Capacity for Work) Act), the statutory disability insurance scheme in the Netherlands. The view consolidates Dutch disability registration data — including work restrictions, disability degree, and work resumption details — into a single queryable structure that reporting tools, concurrent programs, and integrations can consume without directly joining the underlying transactional tables.

For a user searching on the term work_restriction, this view is directly relevant: the WORK_RESTRICTION column is exposed explicitly, sourced from PER_DISABILITIES_F.WORK_RESTRICTION. The view therefore serves as the primary read-only access point for Dutch WAO records that carry restrictions on the employee's remaining work capacity.

Underlying Base Objects

The view is defined over four referenced base objects, joined as documented in the ETRM metadata:

• PER_ALL_PEOPLE_F — the people/person datelateral table, supplying FULL_NAME, EMPLOYEE_NUMBER, NATIONAL_IDENTIFIER, and PERSON_ID.
• PER_DISABILITIES_F — the disability detail table, providing the WAO registration attributes and the effective-dated periods.
• PER_WORK_INCIDENTS — the work incident table, providing incident reference and date information and linking the disability to its originating incident.
• HR_ALL_ORGANIZATION_UNITS — the organization definition table, supplying the registration organization name.
• HR_GENERAL — a PL/SQL package referenced in the view definition, typically used for date/effective-date logic within HR.

The join is predicate-bound by PD.CATEGORY = 'NL_WAO', restricting output to Dutch WAO records only. The person, disability, and incident rows are correlated on PERSON_ID, and the organization is matched via ORGANIZATION_ID. A date-range condition on PD.EFFECTIVE_END_DATE ensures the disability period falls within the person's effective-dated record, preserving temporal consistency between the two effective-dated entities.

Key Columns

• EMPLOYEE_NAME, EMPLOYEE_NUMBER, EMPLOYEE_SOFI_NUMBER — identity fields from the person record; the SOFI number corresponds to the Dutch social-fiscal (tax) identifier.
• PERSON_ID, DISABILITY_ID — primary surrogate keys used for joining to other HR entities.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the validity period of the disability registration.
• WORK_RESTRICTION — a descriptive indicator of the restrictions applicable to the employee's remaining work capacity; central to the user's search.
• DIABILITY_DEGREE — the assessed degree of disability (note the documented spelling in the column list).
• WORK_RESUMPTION, REMAINING_HOURS, REMAINING_HOURS_UNITS — work resumption details and the residual hours the employee can perform, with units.
• FTE — the quota in full-time-equivalent terms, sourced from QUOTA_FTE.
• DISABILITY_REASON, STATUS, DESCRIPTION — registration reason, current status, and free-text description.
• REGISTRATION_ID, REGISTRATION_DATE, REGISTRATION_EXPIRY_DATE — registration reference and validity dates.
• CASUAL_INCIDENT, INCIDENT_DATE — incident reference and date from PER_WORK_INCIDENTS.
• REGISTRATION_ORGANIZATION — the organization name from HR_ALL_ORGANIZATION_UNITS.
• ATTRIBUTE1–ATTRIBUTE30 — the standard DFF (Descriptive Flexfield) columns, alongside DIS_INFORMATION1, 3, 4, 5.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — audit columns.

Common Use Cases and Queries

The view is typically used for statutory and HR reporting on Dutch disability records, particularly where work restrictions must be communicated to occupational health, payroll, or benefits systems. A representative query listing active WAO records with work restrictions is:

• SELECT employee_name, employee_number, effective_start_date, effective_end_date, work_restriction, diability_degree, remaining_hours, remaining_hours_units FROM apps.per_nl_wao_list_v WHERE work_restriction IS NOT NULL ORDER BY employee_name;
• SELECT employee_number, registration_date, registration_expiry_date, registration_organization, status FROM apps.per_nl_wao_list_v WHERE TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date;
• SELECT person_id, disability_id, casual_incident, incident_date, disability_reason FROM apps.per_nl_wao_list_v WHERE person_id = :p_person_id;

Because the view is a read-only projection over effective-dated base tables, queries should consider effective-date filtering to avoid returning multiple historical rows per person. The view should not be updated directly; DML must target PER_DISABILITIES_F and related base tables through the supported HR APIs.