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_INITIALISATIONS

Object Details

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

PAY_TRIGGER_INITIALISATIONS contains details of any initialisation
code which is to be executed before the main processing takes place.
Changing any of the values in this table will result in the trigger being
marked as requiring re-generation. If the table against which the trigger
will be generated contains the not null business_group_id column then
initialisation code for the business_group_id and legislation_code
variables will automatically be generated. Users will not be permitted to remove or modify this code, or to insert extra initialisation steps before this code. Advanced users will be able to define their own initialisation steps. Much of the code which can be entered here is not true PL/SQL. The mapping between return values, input parameters, $_$ placeholders, select list items, local variables and bind values will be determined via the PAY_TRIGGER_PARAMETERS table.

Storage Details

Tablespace:	APPS_TS_TX_DATA
PCT Free:	10
PCT Used:

Indexes

Index	Type	Uniqueness	Tablespace	Column
PAY_TRIGGER_INITIALISATIONS_PK	NORMAL	UNIQUE	APPS_TS_TX_IDX	INITIALISATION_ID ZD_EDITION_NAME
PAY_TRIGGER_INITIALISATIONS_FK	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	EVENT_ID

Columns

Name	Datatype	Length	Mandatory	Comments
INITIALISATION_ID	NUMBER	(15)	Yes	System-generated primary key column.
EVENT_ID	NUMBER	(15)	Yes	Foreign key to PAY_TRIGGER_EVENTS.
PROCESS_ORDER	NUMBER	(9)	Yes	Because one initialisation can depend on the value of another variable, the user can specify the order in which these processing steps will take place.
PLSQL_CODE	VARCHAR2	(2000)	Yes	The code to be executed for this step. Depending on the value of the PROCESS_TYPE column this will be interpreted in the following ways;F - This is the name of a function which returns the value to be used for initialisation.P - This is the name of a procedure which will return values via OUT parameters. IN OUT parameters are not permitted.S - This is the SELECT statement without an INTO clause (that will be added automatically), it may reference local variables and bind variables by using placeholders formatted in the same way as those used in assignment initialisations.A - This is a valid PL/SQL statement making up the right hand side of an assignment statement. Placeholders which reference local variables in the format $L_$ or bind variables (named as either $OLD_$ or $NEW_$) may be used.e.g. UPPER($L_$). Only a single PL/SQL statement is permitted using only built-in functions.
PROCESS_TYPE	VARCHAR2	(1)	Yes	This determines how the PLSQL_CODE value is interpreted. It can take one of the following values;F - The initialisation is done via a function call.P - The initialisation is done via a procedure call.S - A SQL SELECT statement is used for initialisationA - The initialisation code will be a simple assignment statement.
ZD_EDITION_NAME	VARCHAR2	(30)	Yes

Query Text

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


SELECT INITIALISATION_ID
,      EVENT_ID
,      PROCESS_ORDER
,      PLSQL_CODE
,      PROCESS_TYPE
,      ZD_EDITION_NAME
FROM HR.PAY_TRIGGER_INITIALISATIONS;

Dependencies

[top of page]

HR.PAY_TRIGGER_INITIALISATIONS does not reference any database object

HR.PAY_TRIGGER_INITIALISATIONS is referenced by following:

HR: PAY_TRIGGER_INITIALISATIONS#