Results for “per_disabilities_v”

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

Overview

PER_DISABILITIES_V is a date-effective reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PER (Human Resources) product family. Its documented purpose is to return all disability records associated with a person, resolving the underlying date-tracked (datetracked) entities into a single queryable structure. The view is available in both EBS 12.1.1 and 12.2.2 as a VALID database object with no known invalidity issues.

Because it consolidates disability, incident, and medical assessment data for a person, the view is commonly consumed by HR reporting, extracts, and interfaces rather than by the core HR forms themselves. It hides the complexity of joining the date-effective disability table with the person, incident, organization, and medical assessment entities, exposing decoded lookup values for category, status, and reason so that downstream consumers receive human-readable descriptions rather than raw codes.

Underlying Base Objects

The view is defined over the following documented base objects: PER_DISABILITIES_F (the date-effective base table holding disability records), PER_PEOPLE_F (for person-level context), PER_MEDICAL_ASSESSMENTS, PER_WORK_INCIDENTS, HR_ALL_ORGANIZATION_UNITS and HR_ALL_ORGANIZATION_UNITS_TL (for the organization name), plus the HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY packages. FND_SESSIONS is referenced for session context (business group/security), and HR_ALL_ORGANIZATION_UNITS is exposed through synonyms.

The dependencies fall into three groups: the transactional disability entity (PER_DISABILITIES_F), the contextual entities it links to (people, incidents, medical assessments, organizations), and utility packages used for security enforcement and lookup decoding. HR_SECURITY is significant because disability data is person-sensitive; the view applies organizational security so that users see only records permitted by their security profile. HR_GENERAL.DECODE_LOOKUP is invoked to translate the C category, status, and reason codes.

Key Columns

• DISABILITY_ID, PERSON_ID, BUSINESS_GROUP_ID — Primary disability identifier and its person/organization context.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — Date-effective range for the disability record.
• INCIDENT_ID, INCIDENT_REFERENCE, INCIDENT_DATE — The associated work incident and its date/reference.
• MEDICAL_ASSESSMENT_ID, CONSULTATION_DATE — Linked medical assessment and consultation date.
• ORGANIZATION_ID, NAME — Owning organization (resolved via the organization units tables).
• REGISTRATION_ID, REGISTRATION_DATE, REGISTRATION_EXP_DATE — Disability registration details and expiry.
• CATEGORY, STATUS, REASON — Coded values, each accompanied by a decoded description up to 80 characters via HR_GENERAL.DECODE_LOOKUP.
• PRE_REGISTRATION_JOB — Previous job held prior to registration; directly relevant to pre-registration investigation and job-history reporting.
• DEGREE, QUOTA_FTE, WORK_RESTRICTION, DESCRIPTION — Severity degree, FTE quota for disabled employment schemes, work restrictions, and free-text description.
• DIS_INFORMATION1–30 — Descriptive flexfield (DFF) segments capturing flexfield information on the disability record.
• ATTRIBUTE1–19 — Standard attribute columns for additional customer-defined data.

Common Use Cases and Queries

The most frequent use is extracting disability data for a person or population, typically for compliance reporting on disabled employment quotas (using QUOTA_FTE) or for HR investigations. A typical query:

SELECT disability_id, person_id, incident_reference, consultation_date, category, status, pre_registration_job, quota_fte FROM apps.per_disabilities_v WHERE person_id = :p_person_id;

Because the view is date-effective, filtering on EFFECTIVE_START_DATE and EFFECTIVE_END_DATE returns the current applicable record. Analysts investigating job history before a disability registration commonly select PRE_REGISTRATION_JOB alongside REGISTRATION_DATE to determine the prior role. The decoded CATEGORY, STATUS, and REASON columns allow report builders to avoid repeated lookups, while DIS_INFORMATION1–30 and ATTRIBUTE1–19 support flexfield-based extracts. Security is inherited, so queries return only records permitted under the user's HR security profile.