Results for “ar_cc_unknown_error_code”

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

Overview

APPS.AR_CC_ERRORS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It exposes credit card processing exceptions raised during Oracle Receivables receipt and payment workflows. The view consolidates error and diagnostic information originating from the credit card authorization and settlement infrastructure, including the IBY (Oracle Payments) payment instrument layer and the Receivables cash receipt layer. Its FND Design Data identifier is AR.AR_CC_ERRORS_V, and the object is registered as VALID with an internal view type.

Oracle designates the view as Oracle Internal Use Only. Access to application data through this object is unsupported unless invoked from standard Oracle Applications programs. The view is not referenced by any other database object, indicating its role is primarily as a terminal reporting surface for diagnostics rather than as a dependency for further views or packages. The output includes the CATEGORY column, which classifies the nature of the failure, and the CATEGORY_DSP column, which provides the display-friendly (translated) form of that category for user-facing inquiry and reporting.

Underlying Base Objects

The view is defined over thirteen documented base objects. Functional groupings are as follows:

• Receivables transactions and receipts: AR_CASH_RECEIPTS, AR_CASH_RECEIPT_HISTORY, AR_PAYMENT_SCHEDULES, AR_RECEIPT_METHODS, RA_CUSTOMER_TRX, RA_CUST_TRX_TYPES.
• Customer and party data: HZ_PARTIES, HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES.
• Payments and instrument data: IBY_CREDITCARD, IBY_FNDCPT_TX_EXTENSIONS, IBY_PMT_INSTR_USES_ALL.
• PL/SQL helper packages: ARPT_SQL_FUNC_UTIL and ARP_STANDARD, which supply utility logic used in deriving columns such as category descriptions and formatted amounts.

The mix of Receivables, Trading Community (HZ), and Oracle Payments (IBY) sources positions the view as a cross-module exception report: it joins the receipt-to-transaction chain with the underlying payment instrument to surface the exact receipt, transaction, customer, and card context in which an error occurred.

Key Columns

• ERROR_CODE / ERROR_DESC: The machine-readable error identifier and the human-readable description of the failure.
• CATEGORY / CATEGORY_DSP: The internal error category and its translated, display-ready equivalent used in inquiries and reports.
• TRX_ID, TRX_NUMBER, TRX_DATE, TRX_CURRENCY_CODE, DAYS_LATE: Transaction identity, date, currency, and aging context.
• PARTY_ID, CUSTOMER_NAME, CUST_ACCOUNT_ID, CUSTOMER_NUMBER: The party and customer account associated with the failing receipt.
• SITE_USE_ID, CUSTOMER_LOCATION: The customer site and its descriptive location.
• CUSTOMER_BANK_ACCOUNT_ID, CC_NUMBER, EXPIRATION_DATE.
• PAYMENT_SERVER_ID, APPROVAL_CODE: The payment server reference and the authorization approval code returned by the processor.
• OBJECT_VERSION_NUMBER: The optimistic locking version, retained for consistency with underlying Applications tables.

Common Use Cases and Queries

The view is used to diagnose credit card receipt failures, reconcile authorization responses with Receivables receipts, and drive exception reporting for collections and cash management staff. A typical query filters by category and customer:

• By category: SELECT trx_number, error_code, error_desc, category_dsp FROM apps.ar_cc_errors_v WHERE category = 'DECLINE';
• By customer: SELECT trx_id, customer_name, trx_date, days_late, approval_code FROM apps.ar_cc_errors_v WHERE cust_account_id = :p_cust_account_id;

Because the view is designated internal and unsupported for direct access, these queries should be treated as diagnostic or ad hoc only. Production integrations should rely on supported Oracle Payments and Receivables APIs rather than querying AR_CC_ERRORS_V directly.