Search Results preference_start_date

Overview

APPS.IGSFV_PERSON_OFFICE_HOURS is a read-only Oracle E-Business Suite view owned by the APPS schema and delivered as part of the IGS – Student System product family. In Oracle EBS 12.1.1 and 12.2.2 the object carries a VALID status and is defined as an extension view over person-level contact preference data, specifically intended to expose office hours maintained against staff and faculty records. The underlying extension entity, IGS_PE_OFFICE_HRS, extends HZ_CONTACT_PREFERENCES, the Trading Community Architecture (TCA) table that stores contact preferences for parties. By joining the office-hours extension to the contact preference and party records, the view presents a denormalized, human-readable result set that combines scheduling information (day of week, start and end time) with party identification and the descriptive meaning of TCA lookup codes.

Within the Oracle Student System, the view functions as the reporting and integration surface for office-hour information. Institutional portals, advising applications, and custom concurrent programs can query the view directly rather than reconstructing the three-way join themselves, and because the view substitutes lookup-code columns for their meanings, downstream consumers receive legible values without additional lookup resolution.

Underlying Base Objects

The view text identifies three base objects:

• IGS_PE_OFFICE_HRS POH — the extension table storing one row per office-hours record, keyed by OFFICE_HRS_ID and linked to a contact preference through CONTACT_PREFERENCE_ID. It contributes the day-of-week code and the start and end time columns.
• HZ_CONTACT_PREFERENCES HCP — the TCA contact preference record, supplying the contact type, preference code, preference topic type, preference date range, reason code, and the polymorphic contact-level reference.
• HZ_PARTIES HP — the TCA party master, supplying the party number and party name.

The join is constrained so that only preferences whose CONTACT_LEVEL_TABLE is HZ_PARTIES are returned, and the preference is matched to the party via CONTACT_LEVEL_TABLE_ID = PARTY_ID. This restricts the result set to person-level contact preferences and excludes preferences recorded against other contact levels. The view is declared WITH READ ONLY, so no DML may be issued against it; maintenance must occur through the base extension table and the standard TCA contact preference APIs.

Key Columns

• OFFICE_HRS_IDENTIFIER — primary identifier of the office-hours extension record, sourced from IGS_PE_OFFICE_HRS.
• CONTACT_PREFERENCE_IDENTIFIER — foreign key to HZ_CONTACT_PREFERENCES, linking the office hours to the governing contact preference.
• PERSON_IDENTIFIER, PERSON_NUMBER, PERSON_NAME — party identifier, party number, and party name from HZ_PARTIES.
• _LA:CONTACT_TYPE, _LA:PREFERENCE_CODE, _LA:PREFERENCE_TOPIC_TYPE, _LA:DAY_OF_WEEK_CODE — lookup-resolved columns. The underscore-prefixed names denote that the view substitutes the MEANING from IGS_LOOKUP_VALUES (or IGS_WEEK_DAYS for the day code) for the stored code.
• PREFERENCE_START_DATE, PREFERENCE_END_DATE, REASON_CODE — the validity window and reason for the contact preference itself.
• START_TIME_DATE, END_TIME_DATE — the office-hours interval boundaries.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns for the extension record.

Common Use Cases and Queries

The view is typically used to publish faculty office hours on self-service pages, to feed scheduling or advising integrations, and to produce administrative listings of availability by party. The following query retrieves current office hours for a named faculty member:

SELECT person_number,
       person_name,
       "_LA:DAY_OF_WEEK_CODE" AS day_of_week,
       start_time_date,
       end_time_date
FROM   apps.igsfv_person_office_hours
WHERE  person_name LIKE 'SMITH%'
ORDER  BY person_name, day_of_week, start_time_date;

A second common pattern lists all office hours whose governing contact preference is presently effective:

SELECT person_name,
       "_LA:PREFERENCE_CODE" AS preference_code,
       start_time_date,
       end_time_date
FROM   apps.igsfv_person_office_hours
WHERE  TRUNC(SYSDATE) BETWEEN preference_start_date AND preference_end_date;

Because the view is read only and its joins span the IGS and TCA schemas, queries should be executed with the APPS schema or an appropriate synonym and grants in place. Reported inconsistencies between office hours and contact preferences generally originate in the base tables and must be corrected through the supported extension and TCA maintenance paths.