Search Results subsequent_action_dsp

Overview

APPS.AR_CC_ERROR_MAPPINGS_V is a reporting and integration view in the Oracle E-Business Suite Receivables (AR) module, owned by the APPS schema. It is documented in ETRM for both release 12.1.1 and 12.2.2. The view exposes the configuration data held in the AR_CC_ERROR_MAPPINGS table, which drives how Oracle Receivables responds when a payment instrument, typically a credit card, is declined or otherwise returns an error during a receipt or automatic receipt process. The view presents the mapping between an incoming error condition and the corrective action Receivables should take, optionally after a defined interval and with a defined follow-up action.

The object is a simple projection view defined with a single SELECT statement. Because it has no aggregation, joins, or complex logic beyond two lookup-derivation calls, it behaves as a read-only window onto the base table and is therefore suitable for concurrent-program extracts, custom reports, Oracle Discoverer or BI Publisher data models, and e-commerce or payment gateway integration code that needs to resolve a processor error code into a Receivables action.

Underlying Base Objects

The view is defined over a single base object, AR_CC_ERROR_MAPPINGS, accessed through the public synonym of the same name. ETRM lists the referenced base objects as ARPT_SQL_FUNC_UTIL (PACKAGE) and AR_CC_ERROR_MAPPINGS (SYNONYM). CARPT_SQL_FUNC_UTIL is a shared Receivables utility package that supplies the GET_LOOKUP_MEANING function, used twice in the view to translate internal action codes into their user-facing lookup meanings.

Because the view is defined on the synonym rather than a fully qualified table, it resolves to the APPS-owned AR_CC_ERROR_MAPPINGS table at runtime. The view retains the ROWID of the underlying row as its first selected column, which allows callers to identify the physical row without exposing primary key values. All filter, update-date, and audit columns are passed through unchanged.

Key Columns

• ROWID – the physical row identifier of the underlying AR_CC_ERROR_MAPPINGS record.
• CC_ERROR_CODE – the error code returned by the credit card processor or payment instrument.
• CC_ERROR_TEXT – the descriptive text of the error condition.
• RECEIPT_METHOD_ID – the receipt method against which the mapping applies.
• CC_TRX_CATEGORY – the transaction category associated with the error mapping.
• CC_ACTION_CODE – the action Receivables takes when the error occurs.
• The first derived lookup column – GET_LOOKUP_MEANING('AR_CC_ACTION_CODES', CC_ACTION_CODE), the display meaning of the current action.
• NO_DAYS – the number of days before the action, typically a retry or reversal, is executed.
• SUBSEQUENT_ACTION_CODE – the follow-up action applied if the initial action does not resolve the error.
• The second derived lookup column – GET_LOOKUP_MEANING('AR_CC_ACTION_CODES', SUBSEQUENT_ACTION_CODE), the display meaning of the subsequent action.
• ERROR_NOTES – free-form notes describing the error or its handling.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY – standard EBS audit columns.
• OBJECT_VERSION_NUMBER – the optimistic locking version counter.

Common Use Cases and Queries

Typical usage includes diagnosing why a specific processor error produced a particular Receivables outcome, reviewing the action codes configured for a receipt method, and extracting the mapping grid for audit or migration purposes. A representative query filters by error code:

SELECT cc_error_code,
       cc_error_text,
       receipt_method_id,
       cc_action_code,
       no_days,
       subsequent_action_code,
       error_notes
FROM   apps.ar_cc_error_mappings_v
WHERE  cc_error_code = :error_code;

To review all mappings tied to a receipt method, filtering on RECEIPT_METHOD_ID isolates the relevant configuration rows. Because the view exposes GET_LOOKUP_MEANING values, reports can display readable action descriptions without joining FND_LOOKUPS directly. Ordering by CC_ERROR_CODE or RECEIPT_METHOD_ID produces the familiar setup listing used in implementation documentation and troubleshooting of declined-card behavior.