BEN_ACTY_RT_PYMT_SCHED_F

BEN_ACTY_RT_PYMT_SCHED_F identifies the payment schedule(s) to use to control how frequently a distribution-related activity base rate is to be paid.

Details

• Schema: FUSION

• Object owner: BEN

• Object type: TABLE

• Tablespace: TRANSACTION_TABLES

Primary Key

Name	Columns
BEN_ACTY_RT_PYMT_SCHED_F_PK	ACTY_RT_PYMT_SCHED_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE

Columns

Name	Datatype	Length	Precision	Not-null	Comments
ACTY_RT_PYMT_SCHED_ID	NUMBER		18	Yes	System generated primary key column.
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.
BUSINESS_GROUP_ID	NUMBER		18	Yes	Foreign Key to HR_ORGANIZATION_UNITS
PYMT_SCHED_RL	NUMBER		18		Foreign key to FF_FORMULAS_F.
ACTY_BASE_RT_ID	NUMBER		18		Foreign Key to BEN_ACTY_BASE_RT_F.
PYMT_SCHED_CD	VARCHAR2	30		Yes	Payment schedule.
LAST_UPDATE_DATE	TIMESTAMP			Yes	Who column: indicates the date and time of the last update of the row.
LAST_UPDATED_BY	VARCHAR2	64		Yes	Who column: indicates the user who last updated the row.
LAST_UPDATE_LOGIN	VARCHAR2	32			Who column: indicates the session login associated to the user who last updated the row.
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.
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.

Indexes

Index	Uniqueness	Tablespace	Columns
BEN_ACTY_RT_PYMT_SCHED_F_N1	Non Unique	Default	ACTY_BASE_RT_ID
BEN_ACTY_RT_PYMT_SCHED_F_PK	Unique	Default	ACTY_RT_PYMT_SCHED_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE