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_COMPONENTS

Object Details

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

PAY_TRIGGER_COMPONENTS contains a list of procedures (standalone or in a database package) that may be called during trigger execution depending on the legislation code and business group of the current row. Changing any values in this table will mark the trigger for re-generation, creating a new record will not mark the trigger for re-generation until the enable flag is switched on. The module name is the name of a database procedure or database packaged rocedure. It''s parameter list may not contain any out or in out parameters. The actual mapping of local and bind variables to the parameter list items is determined by the trigger parameters entity. The enabled flag is set to N when the row is first created indicating that although the component is a part of the trigger it has not been generated into the trigger''s code. Switching this value on for a new row (or disabled existing row) or off for an existing row will mark the trigger for re-generation. A row is permitted to be;
Global - both legislation_code and business_group_id are null,
Legislation Specific - a legislation code is supplied but business_group_id is null, or
Business Specific - a business group is supplied but legislation_code is null.
It is not permitted for both legislation_code and business_group_id to be specified. The PL/SQL IF...THEN statements will be generated so that the required components are executed only when necessary. Legislation and business specific components may only be created when the trigger contains declarations for the legislation_code and business_group_id local variables.Otherwise only global components can be created.

Storage Details

Tablespace:	APPS_TS_TX_DATA
PCT Free:	10
PCT Used:

Primary Key: PAY_TRIGGER_COMPONENTS_PK

COMPONENT_ID

Indexes

Index	Type	Uniqueness	Tablespace	Column
PAY_TRIGGER_COMPONENTS_PK	NORMAL	UNIQUE	APPS_TS_TX_IDX	COMPONENT_ID
PAY_TRIGGER_COMPONENTS_FK	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	EVENT_ID

Foreign Keys

Table		Foreign Table	Foreign Key Column
PAY_TRIGGER_COMPONENTS		PAY_TRIGGER_EVENTS	PAY_TRIGGER_COMPONENTS EVENT_ID

Columns

Name	Datatype	Length	Mandatory	Comments
COMPONENT_ID	NUMBER	(15)	Yes	System-generated primary key column.
EVENT_ID	NUMBER	(15)	Yes	Foreign key to PAY_TRIGGER_EVENTS.
LEGISLATION_CODE	VARCHAR2	(30)		Foreign key to FND_TERRITORIES.
BUSINESS_GROUP_ID	NUMBER	(15)		The business_group_id value for the current row. Only required for business specific components. Foreign key to HR_ORGANIZATION_UNITS.
PAYROLL_ID	NUMBER	(9)		A foreign key to PAY_ALL_PAYROLLS_F indicating whether this component is relevant to a particular payroll or not.
MODULE_NAME	VARCHAR2	(240)	Yes	The name of the procedure to call if this component is in context. (I.e. The legislation and business are correct for this component.) This can be a standalone procedure name or a package.procedure type reference to a procedure stored in a database package. This procedure must not utilise IN OUT parameters.
ENABLED_FLAG	VARCHAR2	(1)	Yes	Allows separate parts of the trigger to be switched on and off whilst still maintaining a record of a components' definition. The trigger will require re-generation if any component is switched on or if an existing component is switched off. This value can be Y or N.
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 COMPONENT_ID
,      EVENT_ID
,      LEGISLATION_CODE
,      BUSINESS_GROUP_ID
,      PAYROLL_ID
,      MODULE_NAME
,      ENABLED_FLAG
,      LAST_UPDATE_DATE
,      LAST_UPDATED_BY
,      LAST_UPDATE_LOGIN
,      CREATED_BY
,      CREATION_DATE
FROM HR.PAY_TRIGGER_COMPONENTS;

Dependencies

[top of page]

HR.PAY_TRIGGER_COMPONENTS does not reference any database object

HR.PAY_TRIGGER_COMPONENTS is referenced by following:

APPS: PAY_TRIGGER_COMPONENTS; PAY_TRIGGER_COMPONENTS_WHO
PUBLIC: PAY_TRIGGER_COMPONENTS