Results for “ar_cc_errors_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AR_CC_ERRORS_V is a read-only view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2, delivered as part of the Oracle Receivables (AR) product family. Its stated purpose in the ETRM documentation is to support the credit error card correction Oracle Application (OA) page — the framework page through which Receivables users identify, review, and remediate credit card transactions that failed during authorization, settlement, or related payment processing steps. Rather than representing a physical table, the view consolidates error records drawn from credit card receipts and credit card transactions into a single, presentation-ready result set with friendly error codes, error descriptions, category lookups, and customer context.

The view is therefore best understood as an integration and reporting surface rather than a transactional object. It is not designed for DML and should never be used as a target for inserts or updates. Its principal consumers are the OA-based correction UI and, at the reporting layer, custom queries, Oracle Reports, OAF-based extensions, and BI Publisher data templates that need to enumerate credit card failures for a given operating unit, period, or customer.

Underlying Base Objects

AR_CC_ERRORS_V is defined as a UNION ALL of two branches. The first branch selects from AR_CASH_RECEIPTS (credit card receipts), joined to AR_CASH_RECEIPT_HISTORY, AR_RECEIPT_METHODS, AR_PAYMENT_SCHEDULES, HZ_PARTIES, HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES, and IBY_TRXN_EXTENSIONS_V. The second branch draws from RA_CUSTOMER_TRX and RA_CUST_TRX_TYPES for transaction-level errors. Supporting packages include ARPT_SQL_FUNC_UTIL (for the GET_LOOKUP_MEANING call against the CC_TRX_CATEGORY lookup type) and ARP_STANDARD (for the FND_MESSAGE calls that supply fallback error text such as AR_CC_UNKNOWN_ERROR_CODE and AR_CC_UNKNOWN_ERROR_TEXT). The documented 12.2.2 metadata lists the synonym-level base objects as AR_CASH_RECEIPTS, AR_CASH_RECEIPT_HISTORY, AR_PAYMENT_SCHEDULES, AR_RECEIPT_METHODS, HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES, HZ_PARTIES, IBY_CREDITCARD, IBY_FNDCPT_TX_EXTENSIONS, IBY_PMT_INSTR_USES_ALL, RA_CUSTOMER_TRX, and RA_CUST_TRX_TYPES.

The receipt branch is restricted to receipts whose receipt method carries PAYMENT_CHANNEL_CODE = 'CREDIT_CARD', whose CC_ERROR_FLAG is 'Y', and whose SELECTED_REMITTANCE_BATCH_ID is null — that is, credit card receipts that failed and have not yet been batched for remittance.

Key Columns

• ERROR_CODE / ERROR_DESC — the credit card error code and its descriptive text, defaulted to FND messages when null.
• CATEGORY / CATEGORY_DSP — the internal error category type and its CC_TRX_CATEGORY lookup meaning.
• TRX_ID / TRX_NUMBER / TRX_DATE — the cash receipt or customer transaction identifier, number, and date.
• PARTY_ID, CUSTOMER_NAME, CUST_ACCOUNT_ID, CUSTOMER_NUMBER, SITE_USE_ID, CUSTOMER_LOCATION — customer and site context.
• CUSTOMER_BANK_ACCOUNT_ID — exposed as a null placeholder in the receipt branch; users searching for this column should note it is not populated from a base table in the documented view text.
• CC_NUMBER, EXPIRATION_DATE, PAYMENT_SERVER_ID, APPROVAL_CODE — credit card and payment processor details.
• OBJECT_VERSION_NUMBER — row version for OA framework concurrency control.

Common Use Cases and Queries

Typical uses include diagnosing failed credit card receipts, driving the correction OA page, and feeding reconciliation reports. A representative query:

SELECT error_code, error_desc, category_dsp, trx_number, trx_date, customer_name, cc_number FROM apps.ar_cc_errors_v WHERE cust_account_id = :cust_account_id AND trx_date BETWEEN :start_date AND :end_date ORDER BY trx_date DESC;

Because CUSTOMER_BANK_ACCOUNT_ID is a null placeholder, join to IBY_PMT_INSTR_USES_ALL or IBY_CREDITCARD directly when bank account or instrument detail is required for the correction workflow.