Search Results cb_number




Overview
Explore in AI Chat

Overview

AR_CHARGEBACKS_V is an APPS-owned reporting view in the Oracle Receivables (AR) module. Its status is documented as VALID, and its original definition carries the annotation "(Release 10SC Only)," indicating that the view was introduced in an early release of the Receivables application and has been preserved across subsequent upgrade paths into Oracle EBS 12.1.1 and 12.2.2. The view exposes chargeback transactions — customer transactions created when a customer disputes all or part of an invoice and the disputed amount is transferred to a new transaction type — in a denormalized form suitable for reporting, extraction, and integration.

The view is particularly relevant to users searching on cb_number, the chargeback number column exposed by the view. In the view text, CB_NUMBER is sourced from RA_CUSTOMER_TRX.TRX_NUMBER, meaning the chargeback transaction's document number is surfaced under a chargeback-specific alias. This allows report authors and interface developers to reference cb_number directly rather than joining to RA_CUSTOMER_TRX and filtering by transaction type.

Underlying Base Objects

The documented base objects referenced by AR_CHARGEBACKS_V are:

  • RA_CUSTOMER_TRX (SYNONYM) — the primary transaction header table, aliased CT, supplying transaction number, dates, attributes, document sequencing, term, reason code, and audit columns.
  • AR_PAYMENT_SCHEDULES (SYNONYM) — aliased PS, supplying amount due original, exchange rate, and due date information used to compute the accounted amount due original.
  • AR_CUST_TRX_LINE_GL_DIST (SYNONYM) — aliased CTLGD, supplying GL posting date, GL date, and code combination ID from the distribution records.
  • RA_CUST_TRX_TYPES (SYNONYM) — aliased CTT, supplying transaction type name, creation sign, overapplication flag, and natural application flag.
  • AR_LOOKUPS (VIEW) — aliased REASON, supplying the meaning and description for the chargeback reason code.
  • AR_ADJUSTMENTS (SYNONYM) — documented as a referenced object, associated with the adjustment activity generated during chargeback processing.

The view is therefore a multi-table join anchored on the transaction header, enriched with payment schedule amounts, distribution GL information, transaction type attributes, and lookup descriptions.

Key Columns

Common Use Cases and Queries

Typical uses include chargeback aging reports, dispute analysis by reason code, reconciliation of chargebacks to GL distributions, and extraction feeds for downstream systems that key on cb_number. A representative query follows:

  • List chargebacks with outstanding balances by reason:

SELECT cb_number, trx_date, transaction_type, reason_meaning,
  amount_due_original, acctd_amount_due_original, due_date
FROM ar_chargebacks_v
WHERE set_of_books_id = :ledger_id
  AND amount_due_original > 0
ORDER BY trx_date, cb_number;

  • Retrieve a single chargeback by its number for integration or inquiry:

SELECT cb_number, customer_trx_id, trx_date, reason_code, cb_comments
FROM ar_chargebacks_v
WHERE cb_number = :cb_number;

  • Analyze chargebacks by transaction type and GL posting status:

SELECT transaction_type, COUNT(*) cb_count, SUM(amount_due_original) total_due
FROM ar_chargebacks_v
WHERE gl_posted_date IS NULL
GROUP BY transaction_type;

Because the view joins several base objects, queries should filter on indexed columns such as CUSTOMER_TRX_ID, CB_NUMBER, or SET_OF_BOOKS_ID where possible to avoid full scans of the underlying transaction and payment schedule tables.