Search Results error_notes

Overview

The AR_CC_ERROR_MAPPINGS_V view is an Oracle E-Business Suite Receivables (AR) database object owned by the APPS schema. It serves as the base table view supporting the Credit Card Error Mappings window in the Receivables module. The view exposes configuration data that governs how the Receivables application responds when payment processor errors are returned during credit card receipt processing, including the immediate action taken and any subsequent action that should follow. Because it is a view rather than a table, it presents a normalized, presentation-ready form of the underlying configuration data, resolving internal action codes into user-readable descriptions through an embedded lookup call. This makes it suitable for reporting, integration, and diagnostic purposes where administrators and technical users need to understand or extract credit card error handling rules without directly querying the underlying base table.

Underlying Base Objects

According to the documented ETRM 12.2.2 metadata, the view is defined over two referenced objects. The first is the synonym AR_CC_ERROR_MAPPINGS, which resolves to the physical base table holding the error mapping configuration records. The second referenced object is the package ARPT_SQL_FUNC_UTIL, whose function GET_LOOKUP_MEANING is invoked to translate the stored action codes into their display meanings. The view text selects from AR_CC_ERROR_MAPPINGS CC_ERROR and applies ARPT_SQL_FUNC_UTIL.GET_LOOKUP_MEANING('AR_CC_ACTION_CODES', ...) against both the CC_ACTION_CODE and SUBSEQUENT_ACTION_CODE columns. The view therefore does not store data independently; it derives its content entirely from the base table, joined conceptually with lookup values maintained under the AR_CC_ACTION_CODES lookup type.

Key Columns

• ROW_ID — The row identifier sourced from the base table ROWID.
• CC_ERROR_CODE — The processor error code being mapped.
• CC_ERROR_TEXT — Descriptive text associated with the error code.
• RECEIPT_METHOD_ID — The receipt method to which the error mapping applies.
• CC_TRX_CATEGORY — The credit card transaction category context for the mapping.
• CC_ACTION_CODE — The immediate action code applied when the error occurs.
• CC_ACTION_DSP — The lookup meaning of the immediate action code, resolved via GET_LOOKUP_MEANING.
• NO_DAYS — The number of days associated with the action or retry interval.
• SUBSEQUENT_ACTION_CODE — The action code applied after the initial action.
• SUBSEQUENT_ACTION_DSP — The lookup meaning of the subsequent action code.
• ERROR_NOTES — Free-form notes describing the mapping.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY, and OBJECT_VERSION_NUMBER.

Common Use Cases and Queries

Typical usage includes reviewing configured error handling behavior, auditing changes to credit card error mappings, and extracting rules for integration or reconciliation. Because the search term is subsequent_action_code, a common query filters on that column:

SELECT CC_ERROR_CODE, CC_ERROR_TEXT, CC_ACTION_CODE, CC_ACTION_DSP, SUBSEQUENT_ACTION_CODE, SUBSEQUENT_ACTION_DSP, NO_DAYS FROM APPS.AR_CC_ERROR_MAPPINGS_V WHERE SUBSEQUENT_ACTION_CODE IS NOT NULL;

Administrators may also list all mappings for a specific receipt method:

SELECT CC_ERROR_CODE, CC_ACTION_DSP, SUBSEQUENT_ACTION_DSP FROM APPS.AR_CC_ERROR_MAPPINGS_V WHERE RECEIPT_METHOD_ID = :p_method_id;

The view is read-only in practice and should be queried rather than modified, as configuration changes are made through the Credit Card Error Mappings window.