AR_CC_ERROR_MAPPINGS
The AR_CC_ERROR_MAPPINGS table contains the mapping between credit card errors and their corresponding corrective actions. Based on these corrective mappings, Receivables will automatically correct any credit card error that occurs during automatic receipt or remittance batch processing.
Details
-
Schema: FUSION
-
Object owner: AR
-
Object type: TABLE
-
Tablespace: APPS_TS_TX_DATA
Primary Key
Name | Columns |
---|---|
AR_CC_ERROR_MAPPINGS_PK |
CC_ERROR_MAP_ID |
Columns
Name | Datatype | Length | Precision | Not-null | Comments |
---|---|---|---|---|---|
CC_ERROR_CODE | VARCHAR2 | 80 | Yes | Error code from credit card payment processor | |
CC_ERROR_MAP_ID | NUMBER | 18 | Yes | Identifier of credit card error mappings | |
CC_ERROR_TEXT | VARCHAR2 | 255 | User-enterable description for credit card error code | ||
RECEIPT_METHOD_ID | NUMBER | 18 | Yes | Identifier of receipt method.Foreign key to AR_RECEIPT_METHODS_ALL.RECEIPT_METHOD_ID. | |
CC_TRX_CATEGORY | VARCHAR2 | 15 | Yes | Transaction category for credit card errors. Based on lookup CC_TRX_CATEGORY. | |
CC_ACTION_CODE | VARCHAR2 | 30 | Yes | Corrective action to be performed on transactions with errors. Based on lookup AR_CC_ACTION_CODES. | |
NO_DAYS | NUMBER | Number of days after which a subsequent corrective action can be performed. If no subsequent action exists, transaction will appear for manual correction after specified number of days. | |||
SUBSEQUENT_ACTION_CODE | VARCHAR2 | 30 | Subsequent action that will be performed after first action is performed. | ||
ERROR_NOTES | VARCHAR2 | 255 | User-enterable notes, attached to corrected transaction | ||
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. | ||
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. | |
RULE_PRIORITY | NUMBER | 6 | Number that identifies the rule priority, with the lowest number equal to the highest priority. If a transaction falls under more than one rule, select the rule with the highest priority. | ||
RETRY_COUNT | NUMBER | 4 | Maximum number of retries for a rule with the Retry action. | ||
ENABLED_FLAG | VARCHAR2 | 1 | Identifies whether the rule is enabled. | ||
FINAL_ACTION_CODE | VARCHAR2 | 30 | Lookup codes under the AR_CC_ACTION_CODES lookup type that determine the final corrective action to take on the transaction if the maximum number of retires fails. Valid values are CLR PAY INFO and REV REC. | ||
RETRY_UOM_CODE | VARCHAR2 | 30 | Lookup codes under the ORA_AR_RCPT_RETRY_UOM lookup type that determine the chronological unit of measure to use to define the interval between retries. Valid values are Minutes, Hours, and Days. | ||
RETRY_INTERVAL | NUMBER | 6 | Number that identifies the length of the interval between retries according to the chronological unit of measure. | ||
RETRY_SCHEDULE_CODE | VARCHAR2 | 30 | Lookup code under the ORA_AR_RETRY_SCHEDULE lookup type that determines the name that identifies the retry schedule containing the Retry action definitions. Valid value is Incremental. |
Foreign Keys
Table | Foreign Table | Foreign Key Column |
---|---|---|
AR_CC_ERROR_MAPPINGS | ar_receipt_methods | RECEIPT_METHOD_ID |
Indexes
Index | Uniqueness | Tablespace | Columns |
---|---|---|---|
AR_CC_ERROR_MAPPINGS_U1 | Unique | Default | CC_ERROR_CODE, CC_TRX_CATEGORY, RECEIPT_METHOD_ID |