eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

DBA Data [Home] [Help] [Dependency Information]

VIEW: APPS.IGSFV_PERSON_OFFICE_HOURS

Object Details

Object Name:	IGSFV_PERSON_OFFICE_HOURS
Object Type:	VIEW
Owner:	APPS
FND Design Data:	IGS.IGSFV_PERSON_OFFICE_HOURS
Subobject Name:
Status:	VALID

View Type

A Business Intelligence System view

Extension table of HZ_CONTACT_PREFERENCES. This would be useful to store office hours for a staff, Faculty

[View Source]

Columns

Name	Datatype	Length	Mandatory	Comments
OFFICE_HRS_IDENTIFIER	NUMBER		Yes	Unique identifier for Office Hours.
CONTACT_PREFERENCE_IDENTIFIER	NUMBER	(15)	Yes	Unique identifier for the contact preference
PERSON_IDENTIFIER	NUMBER	(15)	Yes	Person identifier
PERSON_NUMBER	VARCHAR2	(30)	Yes	Unique identification number for this person
PERSON_NAME	VARCHAR2	(360)	Yes	Name of this person
_LA:CONTACT_TYPE	CHAR	(59)		Type of contact that should or should not be made with the party. Uses the CONTACT_TYPE lookup.
_LA:PREFERENCE_CODE	CHAR	(65)		Permission to use or not to use a particular contact method. Uses the PREFERENCE_CODE lookup.
_LA:PREFERENCE_TOPIC_TYPE	CHAR	(77)		Appropriate subjects to send or not to send to the party that the preference is created for. Uses the PREFERENCE_TOPIC_TYPE lookup.
PREFERENCE_START_DATE	DATE		Yes	Starting date of the period during which a party should or should not be contacted.
PREFERENCE_END_DATE	DATE			Ending date of the period during which a party should or should not be contacted.
REASON_CODE	VARCHAR2	(30)		Reason that this type of contact should or should not be made.
_LA:DAY_OF_WEEK_CODE	CHAR	(64)		Day of the week
START_TIME_DATE	DATE		Yes	Start time of visit, will be storing Date and Time component.
END_TIME_DATE	DATE		Yes	End time of visit, will be storing Date and Time component.
CREATED_BY	NUMBER	(15)	Yes	Standard WHO Column
CREATION_DATE	DATE		Yes	Standard WHO Column
LAST_UPDATED_BY	NUMBER	(15)	Yes	Standard WHO Column
LAST_UPDATE_DATE	DATE		Yes	Standard WHO Column
LAST_UPDATE_LOGIN	NUMBER	(15)		Standard WHO Column

Query Text

Cut, paste (and edit) the following text to query this object:


SELECT OFFICE_HRS_IDENTIFIER
,      CONTACT_PREFERENCE_IDENTIFIER
,      PERSON_IDENTIFIER
,      PERSON_NUMBER
,      PERSON_NAME
,      _LA:CONTACT_TYPE
,      _LA:PREFERENCE_CODE
,      _LA:PREFERENCE_TOPIC_TYPE
,      PREFERENCE_START_DATE
,      PREFERENCE_END_DATE
,      REASON_CODE
,      _LA:DAY_OF_WEEK_CODE
,      START_TIME_DATE
,      END_TIME_DATE
,      CREATED_BY
,      CREATION_DATE
,      LAST_UPDATED_BY
,      LAST_UPDATE_DATE
,      LAST_UPDATE_LOGIN
FROM APPS.IGSFV_PERSON_OFFICE_HOURS;

Dependencies

[top of page]

APPS.IGSFV_PERSON_OFFICE_HOURS references the following:

APPS: HZ_CONTACT_PREFERENCES; HZ_PARTIES; IGS_PE_OFFICE_HRS

APPS.IGSFV_PERSON_OFFICE_HOURS is not referenced by any database object