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]

TABLE: HR.HR_CALENDAR_USAGES

Object Details

Object Name:	HR_CALENDAR_USAGES
Object Type:	TABLE
Owner:	HR
FND Design Data:	PER.HR_CALENDAR_USAGES
Subobject Name:
Status:	VALID

A calendar may be used by many different kinds of entity, for example,
a person or an organization. The kinds of entity which may use a
calendar, and the usages for the calendar are specifed in
HR_PATTERN_PURPOSE_USAGES.
For example, a person may be assigned to a calendar as a way of
determining his work pattern. He may also be assigned to a calendar
to determine his SSP qualifying pattern. He may change the calendar he
uses for each purpose over time, but he may not have two calendars
simultaneously for the same purpose.
By specifying the purpose_usage_id, the entity using the calendar is
identified as well as the purpose for which the calendar is being
used. The primary_key_value identifies the particular occurrence of
the entity. For example PERSON/WORK PATTERN and FRED BLOGGS
respectively.

Storage Details

Tablespace:	APPS_TS_TX_DATA
PCT Free:	20
PCT Used:

Primary Key: HR_CALENDAR_USAGES_PK

CALENDAR_USAGE_ID

Unique Key: HR_CAU_UK01

PRIMARY_KEY_VALUE
PURPOSE_USAGE_ID
START_DATE

Indexes

Index	Type	Uniqueness	Tablespace	Column
HR_CALENDAR_USAGES_PK	NORMAL	UNIQUE	APPS_TS_TX_IDX	CALENDAR_USAGE_ID
HR_CALENDAR_USAGES_UK1	NORMAL	UNIQUE	APPS_TS_TX_IDX	PRIMARY_KEY_VALUE PURPOSE_USAGE_ID START_DATE
HR_CALENDAR_USAGES_FK2	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	PURPOSE_USAGE_ID

Foreign Keys

Table		Foreign Table	Foreign Key Column
HR_CALENDAR_USAGES		HR_CALENDARS	HR_CALENDAR_USAGES CALENDAR_ID

Columns

Name	Datatype	Mandatory	Comments
CALENDAR_ID	NUMBER	Yes	Foreign key to HR_CALENDARS.
CALENDAR_USAGE_ID	NUMBER	Yes	System-generated primary key column.
PRIMARY_KEY_VALUE	NUMBER	Yes	Foreign key to the table/entity identified via the purpose_usage_id.
PURPOSE_USAGE_ID	NUMBER	Yes	Foreign key to HR_PATTERN_PURPOSE_USAGES.
START_DATE	DATE	Yes	The start (date and time) of the period of use of the calendar.
END_DATE	DATE	Yes	The end (date and time) of the period of use of the calendar.
OBJECT_VERSION_NUMBER	NUMBER		System-generated version of row. Increments by one with each update.
CREATED_BY	NUMBER		Standard Who column.
CREATION_DATE	DATE		Standard Who column.
LAST_UPDATED_BY	NUMBER		Standard Who column.
LAST_UPDATE_DATE	DATE		Standard Who column.
LAST_UPDATE_LOGIN	NUMBER		Standard Who column.

Query Text

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


SELECT CALENDAR_ID
,      CALENDAR_USAGE_ID
,      PRIMARY_KEY_VALUE
,      PURPOSE_USAGE_ID
,      START_DATE
,      END_DATE
,      OBJECT_VERSION_NUMBER
,      CREATED_BY
,      CREATION_DATE
,      LAST_UPDATED_BY
,      LAST_UPDATE_DATE
,      LAST_UPDATE_LOGIN
FROM HR.HR_CALENDAR_USAGES;

Dependencies

[top of page]

HR.HR_CALENDAR_USAGES does not reference any database object

HR.HR_CALENDAR_USAGES is referenced by following:

APPS: HR_CALENDAR_USAGES; HR_CALENDAR_USAGES_WHO
PUBLIC: HR_CALENDAR_USAGES