Search Results start_time_date

Overview

IGSFV_PERSON_OFFICE_HOURS is a Business Intelligence System (BIS) view owned by the APPS schema in Oracle E-Business Suite, registered in FND Design Data as IGS.IGSFV_PERSON_OFFICE_HOURS and reported with a status of VALID. As the object type indicates, it is a view rather than a table, and it is documented as an extension mechanism built upon the Oracle Trading Community Architecture (TCA) contact preference infrastructure. Specifically, the view is described as an extension table of HZ_CONTACT_PREFERENCES, intended to store office hours for staff and faculty.

In practice, the view exposes office-hour records in a person-centric, denormalized form, joining office-hour scheduling data to the underlying party and person information so that consumers do not have to reconstruct those relationships themselves. It is typically deployed for institutional reporting around academe and student-system functionality, where administrators need to determine when a staff member or faculty member is available. Users searching for the "Time in Office 2.0 dashboard" should understand that this view is a data-access layer rather than a dashboard artifact: it supplies the office-hours rows and related person attributes that a custom dashboard, OBIEE report, or Oracle APEX application would consume.

Underlying Base Objects

The ETRM metadata documents no referenced base objects for this view, and the Query Text section is truncated, so the definitive FROM clause cannot be reproduced from the supplied documentation. What is authoritative in the metadata is the stated relationship: the view is an extension of HZ_CONTACT_PREFERENCES, the TCA table that records a party's contact permissions, preferences, and related constraints.

Because it extends HZ_CONTACT_PREFERENCES, the view necessarily derives its contact-preference identifiers, contact types, preference codes, and topic types from that table, while person-level attributes (person identifier, person number, and formatted name) are resolved from the TCA person/party model, most commonly HZ_PARTIES and its person-related extensions such as HZ_PERSON_PROFILES or PER_ALL_PEOPLE_F depending on the deployment. The office-hour-specific attributes — day of week, start time, and end time — are the extension payload layered over the contact preference record. Consumers should confirm the exact join topology against the live view definition in their environment, since the excerpt does not enumerate the FROM clause.

Key Columns

• OFFICE_HRS_IDENTIFIER — Unique identifier for the office-hours record; the primary key for reporting joins.
• CONTACT_PREFERENCE_IDENTIFIER — Foreign key to the underlying contact preference, tying the office hours to the HZ_CONTACT_PREFERENCES record.
• PERSON_IDENTIFIER / PERSON_NUMBER / PERSON_NAME — The person's internal identifier, the business-facing person number, and the formatted display name (up to 360 characters).
• CONTACT_TYPE, PREFERENCE_CODE, PREFERENCE_TOPIC_TYPE — Lookup-backed (_LA) columns describing the type of contact, the permission to use a contact method, and the subject matter of the preference.
• PREFERENCE_START_DATE / PREFERENCE_END_DATE — The effective window during which the contact preference applies.
• REASON_CODE — Free-text coded reason for the preference.
• DAY_OF_WEEK_CODE — Lookup-backed (_LA) day of the week for the office hours.
• START_TIME_DATE / END_TIME_DATE — Start and end of the visit window, storing both date and time components.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns.

Common Use Cases and Queries

The principal use case is availability reporting: determining the days and time windows during which a given staff or faculty member is in the office. A representative query projects the person identity alongside the scheduling attributes:

SELECT person_number, person_name, day_of_week_code, start_time_date, end_time_date FROM apps.igsfv_person_office_hours WHERE person_identifier = :p_person_id ORDER BY day_of_week_code, start_time_date;

Because the time columns store a date component as well, reporting layers typically truncate or format them to a time-only display. A second common pattern joins the view to person or assignment tables to produce a departmental office-hours listing, filtering on PREFERENCE_START_DATE and PREFERENCE_END_DATE to exclude expired preferences. Dashboards such as the referenced "Time in Office 2.0" scenario would treat this view as the office-hours fact source, aggregating rows by person and day of week. As with all BIS views, queries should be issued against the APPS synonym with appropriate responsibilities and grants.