Search Results ar_cc_error_mappings_pk

Overview

AR_CC_ERROR_MAPPINGS is a Receivables (AR) module configuration table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores credit card processing errors together with the corrective actions used to automate their resolution. It acts as the control repository consulted by the Receivables credit card processing engine when a payment gateway, processor, or settlement routine returns a failure code. Rather than forcing manual intervention for every error, the application looks up the error against this table and determines the automated next step, the number of days to wait, and any subsequent fallback action.

From a data modeling perspective, the ETRM relationship metadata classifies this object as satellite-leaning (heuristic, mined from the foreign key structure). In practical terms, it behaves as a configuration satellite attached to the AR_RECEIPT_METHODS parent, holding descriptive and behavioral attributes (error text, categories, action codes, day intervals) keyed by the receipt method and error code. The physical table resides in the AR schema with a documented column count of fourteen in the 12.2.2 reference schema.

Key Information Stored

The primary key, AR_CC_ERROR_MAPPINGS_PK, is a composite business key rather than a generated surrogate. It comprises CC_ERROR_CODE and RECEIPT_METHOD_ID, meaning each mapping row is uniquely identified by the combination of a specific error and the receipt method through which the credit card transaction was processed. A second unique index, AR_CC_ERROR_MAPPINGS_U1, extends this to CC_ERROR_CODE, CC_TRX_CATEGORY, and RECEIPT_METHOD_ID, indicating that a given error may map to different corrective actions depending on the transaction category.

• CC_ERROR_CODE — the code identifying the credit card error returned by the processor or gateway; forms part of the primary key.
• CC_ERROR_TEXT — the human-readable description of the error, used in diagnostics and reporting.
• RECEIPT_METHOD_ID — foreign key to AR_RECEIPT_METHODS, tying each mapping to a specific credit card receipt method; part of the primary key.
• CC_TRX_CATEGORY — the transaction category to which the mapping applies, forming part of the unique business key.
• CC_ACTION_CODE — the corrective action the system should take when the error occurs, driving automation logic.
• NO_DAYS — the interval, in days, before the corrective action or retry is attempted.
• SUBSEQUENT_ACTION_CODE — the fallback action applied if the primary corrective action does not resolve the error.
• ERROR_NOTES — free-form annotation providing administrative guidance on the mapping.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the application to detect concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — the standard EBS Who columns providing audit lineage.

Common Use Cases and Queries

The primary use case is setup verification: administrators confirm that each credit card error a given receipt method can produce has an automated corrective action assigned. A typical query joins the mapping to the receipt method to render the actionable configuration:

• Error-to-action resolution: SELECT m.cc_error_code, m.cc_trx_category, m.cc_action_code, m.no_days, m.subsequent_action_code FROM ar_cc_error_mappings m WHERE m.receipt_method_id = :method_id AND m.cc_error_code = :error_code;
• Coverage audit: SELECT rm.name, m.cc_error_code, m.cc_error_text FROM ar_cc_error_mappings m, ar_receipt_methods rm WHERE rm.receipt_method_id = m.receipt_method_id ORDER BY rm.name, m.cc_error_code;
• Mapping inventory by transaction category: SELECT cc_trx_category, COUNT(*) FROM ar_cc_error_mappings GROUP BY cc_trx_category;
• Change tracking: SELECT cc_error_code, receipt_method_id, last_update_date, last_updated_by FROM ar_cc_error_mappings WHERE last_update_date > :since_date;

Reporting scenarios include exception analysis of failed credit card receipts, documentation of automated retry intervals for audit or SOX control purposes, and impact assessment before adding or retiring a receipt method.

Related Objects

• AR_RECEIPT_METHODS — the parent table referenced by the RECEIPT_METHOD_ID foreign key (AR_CC_ERROR_MAPPINGS.RECEIPT_METHOD_ID → AR_RECEIPT_METHODS). It defines the payment methods, including credit card methods, to which the error mappings belong.
• AR_CC_ERROR_MAPPINGS_PK — the composite primary key constraint (CC_ERROR_CODE, RECEIPT_METHOD_ID) enforcing row uniqueness.
• AR_CC_ERROR_MAPPINGS_U1 — the unique index on CC_ERROR_CODE, CC_TRX_CATEGORY, and RECEIPT_METHOD_ID, the business-key candidate for category-specific mappings.
• AR_RECEIVABLE_APPLICATIONS / AR_CASH_RECEIPTS — receipt and application tables whose credit card processing flows consult the mappings when errors arise during receipt creation and settlement.
• Credit Card Processing (AR) program logic — the concurrent and online processing routines that read CC_ACTION_CODE, NO_DAYS, and SUBSEQUENT_ACTION_CODE to automate error remediation.
• AR_RECEIPT_METHODS_VL / AR_RECEIPT_METHODS_V — the translated views over the parent table commonly joined in reporting queries.