Search Results ar_cc_error_mappings_u1

Overview

The AR.AR_CC_ERROR_MAPPINGS table is an Oracle Receivables (AR) seed and configuration table that stores the mapping between credit card processing errors and their corresponding corrective actions. When a credit card transaction fails during AutoReceipts processing or Remittance batch processing, Receivables consults this table to determine whether the error can be automatically corrected and, if so, which action to perform. The corrective behavior is therefore data-driven: the mappings defined in this table govern how the application responds to specific error codes returned by the payment processor, combined with the receipt method and transaction category in use.

The table resides in the APPS_TS_SEED tablespace with a PCT Free of 10, which is consistent with its role as a seeded configuration object rarely modified by transactional activity. From a Data Vault modeling perspective, the mined metadata classifies this object as satellite-leaning — it functions as a descriptive attribute set attached to a business key formed by the error code, transaction category, and receipt method, rather than as a standalone hub or an associative link.

Key Information Stored

The primary key of the table is defined by AR_CC_ERROR_MAPPINGS_PK on (CC_ERROR_CODE, RECEIPT_METHOD_ID). A unique index, AR_CC_ERROR_MAPPINGS_U1, covers (CC_ERROR_CODE, CC_TRX_CATEGORY, RECEIPT_METHOD_ID) and represents the documented business-key candidate. Note that the unique index and the primary key differ by the inclusion of CC_TRX_CATEGORY, meaning the index enforces uniqueness across the combination of error, category, and receipt method.

• CC_ERROR_CODE — The error code returned by the credit card payment processor; a mandatory VARCHAR2(80) column and part of both the primary key and unique index.
• CC_ERROR_TEXT — A user-enterable description of the error code, used for reporting and operational clarity.
• RECEIPT_METHOD_ID — The receipt method identifier, forming a foreign key to AR_RECEIPT_METHODS_ALL.RECEIPT_METHOD_ID; also part of the primary key and unique index.
• CC_TRX_CATEGORY — The transaction category for the error, validated against the CC_TRX_CATEGORY lookup; part of the unique index.
• CC_ACTION_CODE — The corrective action to perform, validated against the AR_CC_ACTION_CODES lookup. This is the operative column that drives automatic correction.
• NO_DAYS — The number of days after which a subsequent corrective action becomes eligible. If no subsequent action exists, the transaction surfaces for manual correction after this many days.
• SUBSEQUENT_ACTION_CODE — A follow-up action performed after the initial CC_ACTION_CODE is applied, supporting multi-step correction logic.
• ERROR_NOTES — Free-form notes that are attached to the corrected transaction for audit and reference.

The table also carries standard Who columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY) and OBJECT_VERSION_NUMBER, which provides optimistic locking during concurrent updates.

Common Use Cases and Queries

Typical uses involve reviewing the corrective rules in force for a given receipt method, auditing which errors lead to automatic versus manual correction, and diagnosing why a specific credit card transaction was corrected (or not corrected) during AutoReceipts or Remittance processing.

• Listing all corrective mappings for a receipt method, joining to AR_RECEIPT_METHODS to resolve the method name.
• Identifying error codes that have no subsequent action (SUBSEQUENT_ACTION_CODE null) and therefore route to manual correction after NO_DAYS.
• Producing a reference report of error codes with their CC_ERROR_TEXT and CC_ACTION_CODE for operations teams.

A representative query pattern:

SELECT m.CC_ERROR_CODE, m.CC_ERROR_TEXT, m.CC_ACTION_CODE, m.NO_DAYS, m.SUBSEQUENT_ACTION_CODE, rm.NAME
FROM AR.AR_CC_ERROR_MAPPINGS m, AR.AR_RECEIPT_METHODS_ALL rm
WHERE m.RECEIPT_METHOD_ID = rm.RECEIPT_METHOD_ID
ORDER BY rm.NAME, m.CC_ERROR_CODE;

Because the table is seeded, queries are predominantly read-only. Any update should be performed through supported configuration or data-fix procedures rather than direct DML.

Related Objects

• AR.AR_RECEIPT_METHODS (AR_RECEIPT_METHODS_ALL) — Referenced by RECEIPT_METHOD_ID; supplies the payment receipt method context for each mapping.
• AR_CC_ERROR_MAPPINGS_U1 — The unique index enforcing the business key on (CC_ERROR_CODE, CC_TRX_CATEGORY, RECEIPT_METHOD_ID).
• AR_CC_ERROR_MAPPINGS_PK — The primary key constraint on (CC_ERROR_CODE, RECEIPT_METHOD_ID).
• CC_TRX_CATEGORY lookup — Oracle Application Object Library lookup validating the CC_TRX_CATEGORY column.
• AR_CC_ACTION_CODES lookup — Lookup validating both CC_ACTION_CODE and SUBSEQUENT_ACTION_CODE.
• AutoReceipts and Remittance batch processes — The concurrent programs that consume these mappings to apply automatic credit card error correction at runtime.