PAY_RULE_RESULTS_F

This table contains the sequence in which costing override rules are applied for a specific business rule.

Details

• Schema: FUSION

• Object owner: PAY

• Object type: TABLE

• Tablespace: APPS_TS_TX_DATA

Primary Key

Name	Columns
PAY_RULE_RESULTS_F_PK	RULE_RESULT_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE

Columns

Name	Datatype	Length	Precision	Not-null	Comments
RULE_RESULT_ID	NUMBER		18	Yes	RULE_RESULT_ID
EFFECTIVE_START_DATE	DATE			Yes	Date Effective Entity: indicates the date at the beginning of the date range within which the row is effective.
EFFECTIVE_END_DATE	DATE			Yes	Date Effective Entity: indicates the date at the end of the date range within which the row is effective.
RULE_ID	NUMBER		18	Yes	RULE_ID
RESULT_SEQUENCE	NUMBER		3	Yes	RESULT_SEQUENCE
CREATED_BY	VARCHAR2	64		Yes	Who column: indicates the user who created the row.
CREATION_DATE	TIMESTAMP			Yes	Who column: indicates the date and time of the creation of the row.
LAST_UPDATE_DATE	TIMESTAMP			Yes	Who column: indicates the date and time of the last update of the row.
LAST_UPDATE_LOGIN	VARCHAR2	32			Who column: indicates the session login associated to the user who last updated the row.
LAST_UPDATED_BY	VARCHAR2	64		Yes	Who column: indicates the user who last updated the row.
OBJECT_VERSION_NUMBER	NUMBER		9	Yes	Used to implement optimistic locking. This number is incremented every time that the row is updated. The number is compared at the start and end of a transaction to detect whether another session has updated the row since it was queried.
ENTERPRISE_ID	NUMBER		18	Yes	Foreign key to PER_ENTERPRISES.

Indexes

Index	Uniqueness	Tablespace	Columns
PAY_RULE_RESULTS_F_PK	Unique	Default	RULE_RESULT_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE