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.PAY_TRIGGER_EVENTS

Object Details

Object Name:	PAY_TRIGGER_EVENTS
Object Type:	TABLE
Owner:	HR
FND Design Data:	PAY.PAY_TRIGGER_EVENTS
Subobject Name:
Status:	VALID

PAY_TRIGGER_EVENTS is the base table for holding information
about dynamically generated triggers. The trigger name will be
derived from information in this table.

Storage Details

Tablespace:	APPS_TS_TX_DATA
PCT Free:	10
PCT Used:

Primary Key: PAY_TRIGGER_EVENTS_PK

EVENT_ID

Unique Key: PAY_TRIGGER_EVENTS_UK1

SHORT_NAME

Indexes

Index	Type	Uniqueness	Tablespace	Column
PAY_TRIGGER_EVENTS_PK	NORMAL	UNIQUE	APPS_TS_TX_IDX	EVENT_ID
PAY_TRIGGER_EVENTS_UK1	NORMAL	UNIQUE	APPS_TS_TX_IDX	SHORT_NAME

Foreign Keys

Table	Foreign Table	Foreign Key Column
PAY_FUNCTIONAL_TRIGGERS	PAY_TRIGGER_EVENTS	PAY_FUNCTIONAL_TRIGGERS EVENT_ID
PAY_TRIGGER_COMPONENTS	PAY_TRIGGER_EVENTS	PAY_TRIGGER_COMPONENTS EVENT_ID
PAY_TRIGGER_DECLARATIONS	PAY_TRIGGER_EVENTS	PAY_TRIGGER_DECLARATIONS EVENT_ID
PAY_TRIGGER_INITIALISATIONS	PAY_TRIGGER_EVENTS	PAY_TRIGGER_INITIALISATIONS EVENT_ID
PAY_TRIGGER_SUPPORT	PAY_TRIGGER_EVENTS	PAY_TRIGGER_SUPPORT EVENT_ID

Columns

Name	Datatype	Length	Mandatory	Comments
EVENT_ID	NUMBER	(15)	Yes	System-generated primary key column.
TABLE_NAME	VARCHAR2	(30)	Yes	Name of the table on which the trigger will be created. This value may not be updated once the record has been created. The trigger name will be dynamically derived according to the following format; __DYT, where TABLE_NAME is this value (with underscores removed and truncated to prevent the whole trigger name exceeding 20 characters). TYPE is the single letter representing the triggering action, either Insert (I), Update (U) or Delete (D). The DYT suffix indicates that it is a DYnamically generated Trigger.
SHORT_NAME	VARCHAR2	(80)	Yes	The user-key or pseudo-key of the triggers table. Allows users to allocate short descriptive names totriggers providing an easy method of searching the list of trigger definitions for maintenance purposes.
DESCRIPTION	VARCHAR2	(240)		A textual description of the trigger which will be added, as a comment, to the trigger body code.
GENERATED_FLAG	VARCHAR2	(1)	Yes	Holds Y if the trigger has been generated into the database, otherwise holds N.
ENABLED_FLAG	VARCHAR2	(1)	Yes	Holds Y if the trigger has been generated in to the database and is enabled. If the trigger is not generated or is disabled this flag will hold the value N.
PROTECTED_FLAG	VARCHAR2	(1)		Designed to allow seeded triggers that aren't necessarily created dynamically, to be treated as if they were. I.e. Viewed within the forms but no changes can be made.
TRIGGERING_ACTION	VARCHAR2	(1)	Yes	Contains I, U or D to determine whether the trigger fires on Insert, Update or Delete. This value cannot be updated once the row has been created. This character makes up part of the trigger name. All triggers will fire after the row has been updated, this is because we are only interested in the fact that the row has changed, not in changing any values before the update takes place.
LAST_UPDATE_DATE	DATE			Standard Who column - date when a user last updated this row.
LAST_UPDATED_BY	NUMBER	(15)		Standard who column - user who last updated this row (foreign key to FND_USER.USER_ID).
LAST_UPDATE_LOGIN	NUMBER	(15)		Standard who column - operating system login of user who last updated this row (foreign key to FND_LOGINS.LOGIN_ID).
CREATED_BY	NUMBER	(15)		Standard who column - user who created this row (foreign key to FND_USER.USER_ID).
CREATION_DATE	DATE			Standard who column - date when this row was created.

Query Text

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


SELECT EVENT_ID
,      TABLE_NAME
,      SHORT_NAME
,      DESCRIPTION
,      GENERATED_FLAG
,      ENABLED_FLAG
,      PROTECTED_FLAG
,      TRIGGERING_ACTION
,      LAST_UPDATE_DATE
,      LAST_UPDATED_BY
,      LAST_UPDATE_LOGIN
,      CREATED_BY
,      CREATION_DATE
FROM HR.PAY_TRIGGER_EVENTS;

Dependencies

[top of page]

HR.PAY_TRIGGER_EVENTS does not reference any database object

HR.PAY_TRIGGER_EVENTS is referenced by following:

APPS: PAY_TRIGGER_EVENTS; PAY_TRIGGER_EVENTS_ARD; PAY_TRIGGER_EVENTS_WHO
PUBLIC: PAY_TRIGGER_EVENTS