EXM_SUBMISSION_LIMITS

This table contains corporate card usage rules by business unit. An example of a rule is that employees must charge all hotel expenses above $24.99 to their corporate credit cards.

Details

• Schema: FUSION

• Object owner: EXM

• Object type: TABLE

• Tablespace: Default

Primary Key

Name	Columns
EXM_SUBMISSION_LIMITS_PK	ORG_ID, EXPENSE_TYPE_CATEGORY_CODE

Columns

Name	Datatype	Length	Precision	Not-null	Comments
ORG_ID	NUMBER		18	Yes	Indicates the identifier of the business unit associated to the row.
EXPENSE_TYPE_CATEGORY_CODE	VARCHAR2	30		Yes	Expense category code for which the corporate card usage rules are defined.
LIMIT_AMOUNT	NUMBER				Maximum amount per expense category that can be paid by cash for each business unit, above which a policy violation occurs.
WARNING_TOLERANCE_PERC	NUMBER				Percentage that, when added to the cash limit, defines the warning amount.
ERROR_TOLERANCE_PERC	NUMBER				Percentage that, when added to the cash limit, defines the error amount.
DISPLAY_TO_USER_FLAG	VARCHAR2	1			Indicator of whether a submission limit policy violation warning is displayed to user.
CREATION_DATE	TIMESTAMP			Yes	Who column: indicates the date and time of the creation of the row.
CREATED_BY	VARCHAR2	64		Yes	Who column: indicates the user who created 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.
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.

Indexes

Index	Uniqueness	Tablespace	Columns
EXM_SUBMISSION_LIMITS_PK	Unique	Default	ORG_ID, EXPENSE_TYPE_CATEGORY_CODE