Search Results date_provided

Overview

APPS.HRFV_ADA_DIS_ACCOMMODATIONS is a read-only Oracle EBS view that presents person-level records of disability accommodation requests and their handling under United States Americans with Disabilities Act (ADA) reporting. It joins the person analysis infrastructure (PER_PERSON_ANALYSES and PER_ANALYSIS_CRITERIA) restricted to a specific flexfield context — id_flex_num = 50130 — and projects the descriptive flexfield segments used by HR to capture accommodation details. The view is defined WITH READ ONLY and is intended exclusively for query and reporting, not for DML.

Its primary role is to expose the ADA accommodation flexfield structure in a denormalized, human-readable form. In particular, the segment3 column, which stores the accommodation status code, is passed through HR_BIS.BIS_DECODE_LOOKUP('US_ADA_STATUSES', ...) so that raw lookup codes are rendered as their meaningful lookup meanings. This is directly relevant to users searching for "us_ada_statuses", since the view is the principal delivered object that decodes that lookup type within the ADA accommodation context. The view also enforces business group security through HR_BIS.GET_SEC_PROFILE_BG_ID and multi-language organization name resolution through the userenv('LANG') predicate.

Underlying Base Objects

The documented base objects are HR_ALL_ORGANIZATION_UNITS_TL (synonym), HR_BIS (package), HR_GENERAL (package), HR_PERSON_NAME (package), HR_SECURITY (package), PER_ANALYSIS_CRITERIA (synonym), PER_PEOPLE_X (view), and PER_PERSON_ANALYSES (synonym).

• PER_PERSON_ANALYSES is the driving transactional table; it links a person_id to an analysis_criteria_id and id_flex_num and supplies the comments, date_from, and date_to columns.
• PER_ANALYSIS_CRITERIA holds the flexfield segment definitions and values (segment1 through segment7), joined to PER_PERSON_ANALYSES on both analysis_criteria_id and id_flex_num.
• PER_PEOPLE_X supplies the person attributes, including full_name (resolved via HR_PERSON_NAME) and employee_number.
• HR_ALL_ORGANIZATION_UNITS_TL provides the translated business_group_name, restricted by language.
• HR_BIS provides BIS_DECODE_LOOKUP for the US_ADA_STATUSES lookup and GET_SEC_PROFILE_BG_ID for security filtering.
• HR_SECURITY and HR_GENERAL support the security predicate and standard HR utilities.

Key Columns

• BUSINESS_GROUP_NAME — translated name of the business group owning the record.
• PERSON_NAME and EMPLOYEE_NUMBER — identity of the affected person.
• DESCRIPTION (segment1) — description of the accommodation request.
• DATE_REQUESTED (segment2) — the date the accommodation was requested.
• STATUS (segment3) — the decoded US_ADA_STATUSES value, the column most commonly sought.
• CONFIRMED_BY (segment4), DATE_CONFIRMED (segment5), DATE_PROVIDED (segment6), COST (segment7) — confirmation and delivery details.
• START_DATE / END_DATE — effective range of the analysis record.
• ANALYSIS_CRITERIA_ID, ID_FLEX_NUM, PERSON_ID, PERSON_ANALYSIS_ID, BUSINESS_GROUP_ID — surrogate keys for joining back to base tables.

Common Use Cases and Queries

Typical uses include ADA accommodation status reporting, compliance tracking, and reconciliation of accommodation requests by business group. Because the view already decodes US_ADA_STATUSES and applies security, it is preferred over direct queries against the underlying analysis tables.

• Listing all open accommodation requests by status and business group.
• Auditing confirmation and provisioning dates against request dates.
• Extracting data for regulatory ADA reporting and HR dashboards.

Illustrative query returning all decoded statuses:

• SELECT person_name, employee_number, description, date_requested, status, date_provided FROM apps.hrfv_ada_dis_accommodations WHERE status IS NOT NULL ORDER BY business_group_name, person_name;

Filtering by a specific accommodation status:

• SELECT person_name, status, date_confirmed FROM apps.hrfv_ada_dis_accommodations WHERE status = :status_code AND TRUNC(date_requested) >= :from_date;

Because the view is READ ONLY and enforces the security business group predicate, it can be granted to reporting responsibilities and used in BI Publisher data models without additional security logic.