EXM_CC_UPLOAD_RULES
This table contains the rules applied to a corporate card transaction file upload, such as employee matching rule and automatic expense type derivation rule.
Details
-
Schema: FUSION
-
Object owner: EXM
-
Object type: TABLE
-
Tablespace: APPS_TS_TX_DATA
Primary Key
Name | Columns |
---|---|
EXM_CC_UPLOAD_RULES_PK |
CC_UPLOAD_RULE_ID |
Columns
Name | Datatype | Length | Precision | Not-null | Comments |
---|---|---|---|---|---|
CC_UPLOAD_RULE_ID | NUMBER | 18 | Yes | Identifier of the upload rule for a corporate card program. | |
CARD_PROGRAM_ID | NUMBER | 18 | Identifier of the corporate card program. | ||
COMPANY_ACCOUNT_ID | NUMBER | 18 | Identifier of the company account. | ||
OVERRIDE_CP_DEFAULTS_FLAG | VARCHAR2 | 1 | Indicator of whether to use company account-specific upload rules. | ||
FILE_FORMAT_CODE | VARCHAR2 | 30 | Format of the file provided by the corporate card issuer, such as GL 1025 and CDF3. | ||
DETAIL_WAITING_DURATION | NUMBER | 9 | Maximum number of days the application waits for transaction details before the transaction can be used in an expense report. | ||
CARD_EMP_MATCHING_RULE | VARCHAR2 | 30 | Rule used to automatically assign employees defined in the application to new corporate cards that arrive in the charge file. | ||
CC_EXP_TYP_SUM_SOURCE_COL | VARCHAR2 | 30 | Column in EXM_CREDIT_CARD_TRXNS table that stores the expense types, or merchant category codes, that come in the charge file for the summary transactions. The application applies the summary mapping rule to this column. | ||
CC_EXP_TYP_SUM_MAP_TYPE_ID | NUMBER | 18 | Identifier of the mapping rule that automatically populates expense type for summary transactions. | ||
CC_EXP_TYP_DTL_SOURCE_COL | VARCHAR2 | 30 | Column in EXM_CC_TRXN_DETAILS table that stores the expense types, or merchant category codes, that come in the charge file for the detail transactions. The application applies the detail mapping rule to this column. | ||
CC_EXP_TYP_DTL_MAP_TYPE_ID | NUMBER | 18 | Identifier of the mapping rule that automatically populates expense type for detail transactions. | ||
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. | ||
MATCH_EMPLOYEE_ACROSS_BU | VARCHAR2 | 1 | When this column is set to Y, employees are matched across all business units for assigning new corporate cards that arrive in the charge file. |
Foreign Keys
Table | Foreign Table | Foreign Key Column |
---|---|---|
EXM_CC_UPLOAD_RULES | exm_card_programs | CARD_PROGRAM_ID |
EXM_CC_UPLOAD_RULES | exm_cc_company_accounts | COMPANY_ACCOUNT_ID |
EXM_CC_UPLOAD_RULES | exm_map_types_b | CC_EXP_TYP_SUM_MAP_TYPE_ID |
EXM_CC_UPLOAD_RULES | exm_map_types_b | CC_EXP_TYP_DTL_MAP_TYPE_ID |
Indexes
Index | Uniqueness | Tablespace | Columns |
---|---|---|---|
EXM_CC_UPLOAD_RULES_N1 | Non Unique | Default | CARD_PROGRAM_ID, COMPANY_ACCOUNT_ID |
EXM_CC_UPLOAD_RULES_PK | Unique | Default | CC_UPLOAD_RULE_ID |