Results for “office_hrs_identifier”

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

Overview

IGSBV_PERSON_OFFICE_HOURS is a read-only database view shipped within the Oracle E-Business Suite IGS – Student System product family, a module classified as obsolete in the ETRM repository for releases 12.1.1 and 12.2.2. The view consolidates person-level office hours information maintained against contact preferences, exposing a denormalized, reporting-friendly projection suitable for querying staff and faculty availability without joining the underlying transactional tables directly. Its role is primarily informational: it supports concurrent-program style reporting, integration extracts, and ad hoc enquiry by presenting office-hour records alongside their owning contact preference attributes.

The view is documented in the ETRM metadata as an extension construct over HZ_CONTACT_PREFERENCES, with the stated business purpose of storing office hours for staff and faculty. The metadata explicitly records that the object is not implemented in this database, meaning it is a legacy/documented-only artifact rather than an active schema element in the target environment. Any reference to preference_start_date in a report or interface therefore resolves against the HCP.PREFERENCE_START_DATE column carried into the view, not against a column physically present in the view's own storage.

Underlying Base Objects

The view text defines a join between two tables:

• IGS_PE_OFFICE_HRS POH — the office-hours detail table, contributing the office hours identifier, day-of-week code, and start/end time values.
• HZ_CONTACT_PREFERENCES HCP — the contact preference header, contributing contact level, contact type, preference code, preference topic type, and the preference start and end dates.

The join predicate is POH.CONTACT_PREFERENCE_ID = HCP.CONTACT_PREFERENCE_ID, filtered by HCP.CONTACT_LEVEL_TABLE = 'HZ_PARTIES' so that only party-level contact preferences are surfaced. The view is declared WITH READ ONLY, confirming it is not a DML-capable object. The ETRM metadata lists no separately documented referenced base objects, so the view text itself is the authoritative definition. The obsolete classification means these objects may be absent or non-functional in 12.1.1 and 12.2.2 instances.

Key Columns

• OFFICE_HRS_IDENTIFIER — primary identifier of the office-hours record (POH.OFFICE_HRS_ID).
• CONTACT_PREFERENCE_IDENTIFIER — foreign key to the contact preference (POH.CONTACT_PREFERENCE_ID).
• _LA:CONTACT_TYPE, _LA:PREFERENCE_CODE, _LA:PREFERENCE_TOPIC_TYPE — label-based lookups resolving IGS_LOOKUP_VALUES meanings for the corresponding HCP columns.
• PREFERENCE_START_DATE — the start date of the contact preference period (HCP.PREFERENCE_START_DATE). This is the column most relevant to the search term "preference_start_date".
• PREFERENCE_END_DATE — the end date of the contact preference period (HCP.PREFERENCE_END_DATE).
• REASON_CODE, _LA:DAY_OF_WEEK_CODE, START_TIME_DATE, END_TIME_DATE — the reason for the preference, the translatable day-of-week meaning from IGS_WEEK_DAYS, and the office-hour time boundaries.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN from the office-hours record.

Common Use Cases and Queries

The typical scenario is retrieving office hours currently in force for a staff or faculty member, filtered by the preference period. The following pattern selects active office hours using preference_start_date:

SELECT office_hrs_identifier,
       contact_preference_identifier,
       preference_start_date,
       preference_end_date,
       "_LA:DAY_OF_WEEK_CODE" AS day_of_week,
       start_time_date,
       end_time_date
  FROM igsbv_person_office_hours
 WHERE preference_start_date <= SYSDATE
   AND NVL(preference_end_date, SYSDATE) >= SYSDATE
 ORDER BY preference_start_date, start_time_date;

Because the view is documented as not implemented, validation against the target 12.1.1 or 12.2.2 instance is required before use; where absent, equivalent data must be sourced directly from IGS_PE_OFFICE_HRS and HZ_CONTACT_PREFERENCES. This view should not be used for DML operations under any circumstance.