Results for “full_time”

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

Overview

The APPS.HRFV_SCHOOL_COLL_ATTENDANCES view is a business view template delivered with the Oracle E-Business Suite PER — Human Resources product. It is generated as part of the flexfield view framework, meaning it functions as a read-only, denormalized presentation layer over the underlying establishment attendance data rather than as a transactional object. Its purpose is to expose school and college attendance records in a form suitable for reporting, ad-hoc querying, and integration, presenting each attendance row together with its related person name, business group name, and establishment name.

For users who search on the term school_or_college_name, this view is the principal deliverable object: SCHOOL_OR_COLLEGE_NAME is a column defined within this view, sourced from the establishment record rather than stored as a raw foreign key. This makes the view particularly convenient for reports that need to display the human-readable name of the educational institution an employee or applicant attended, without joining to the establishments table directly.

Underlying Base Objects

The view is defined over a set of documented base objects, combining translated organization data, person data, establishment data, and attendance data. The ETRM metadata lists the following referenced base objects: HR_ALL_ORGANIZATION_UNITS_TL (synonym), HR_BIS (package), HR_GENERAL (package), HR_PERSON_NAME (package), HR_SECURITY (package), PER_ESTABLISHMENTS (synonym), PER_ESTABLISHMENT_ATTENDANCES (synonym), and PER_PEOPLE_X (view).

In the view text, the business group name is drawn from HR_ALL_ORGANIZATION_UNITS_TL (aliased BGRT), the person name from PER_PEOPLE_X (aliased PEO), the school or college name from PER_ESTABLISHMENTS (aliased PE), and the attendance dates and flags from PER_ESTABLISHMENT_ATTENDANCES (aliased PEA). The join between attendance and establishment uses an outer join (PE.ESTABLISHMENT_ID(+)), so attendance rows persist even where the establishment record is missing. Language filtering is applied through BGRT.LANGUAGE = USERENV('LANG'), and data access is constrained by the security profile via HR_BIS.GET_SEC_PROFILE_BG_ID and the security packages. The view is defined WITH READ ONLY.

Key Columns

• BUSINESS_GROUP_NAME — Translated name of the business group (organization unit) owning the attendance record.
• PERSON_NAME — Full name of the person whose attendance is recorded, resolved through PER_PEOPLE_X.
• SCHOOL_OR_COLLEGE_NAME — Name of the educational establishment attended; this is the column most commonly searched for in reporting contexts.
• START_DATE — Attendance start date (ATTENDED_START_DATE).
• END_DATE — Attendance end date (ATTENDED_END_DATE).
• FULL_TIME — Yes/No lookup decode of the full-time attendance indicator via HR_BIS.BIS_DECODE_LOOKUP.
• BUSINESS_GROUP_ID, PERSON_ID — Identifiers supporting joins to other HR entities.
• SCHOOL_OR_COLLEGE_ID — Establishment identifier for the attended institution.
• "_DF" — Flexfield descriptor column containing the descriptive flexfield context reference _DF:PER:PER_ESTABLISHMENT_ATTENDANCES:PEA.

Common Use Cases and Queries

Typical scenarios include employee qualification and education reporting, applicant screening extracts, and HR data migration validation. A representative query listing attendance records with institution names is:

• SELECT person_name, school_or_college_name, start_date, end_date, full_time FROM apps.hrfv_school_coll_attendances WHERE school_or_college_name IS NOT NULL ORDER BY person_name;
• Filtering by institution for a specific school: SELECT person_name, start_date, end_date FROM apps.hrfv_school_coll_attendances WHERE school_or_college_name = :school_name;
• Restricting to current attendances using the security-profile-filtered business group: SELECT business_group_name, person_name, school_or_college_name FROM apps.hrfv_school_coll_attendances WHERE full_time = 'Y';

Because the view is read-only and security-filtered, it is safe for reporting users. It should not be used for direct DML; establishment attendance maintenance must target the underlying PER_ESTABLISHMENT_ATTENDANCES table through supported HR forms or APIs.