Search Results receipt_payment_schedule_id

Overview

AR_DED_CHARGEBACKS_V is a Receivables (AR) reporting view owned by the APPS schema. It exposes deduction and chargeback transactions generated in Oracle EBS Receivables, presenting each chargeback as a customer transaction (invoice-type record) along with its original amount, account-rate-adjusted equivalent amount, general ledger distribution context, and the associated receipt and payment schedule identifiers. The view consolidates attributes of the chargeback transaction, its transaction type, its reason code, its GL distribution, and the originating payment schedule, so that reported deductions can be traced from the receipt to the resulting chargeback.

Because the view is defined in the APPS schema and is treated as a reportable interface object, it is used for operational reporting, reconciliation, and integration extracts where chargeback activity must be analyzed. The column CHARGEBACK_AMOUNT, one of the primary search terms associated with this object, maps to the original amount due on the deduction's payment schedule and represents the nominal value of the deduction itself.

Underlying Base Objects

Per the documented metadata, the view is defined over the following base objects:

• RA_CUSTOMER_TRX — source of the chargeback transaction header (alias CT).
• RA_CUST_TRX_TYPES — provides the transaction type name.
• RA_CUST_TRX_LINE_GL_DIST — supplies GL posted date, code combination, and GL date.
• AR_PAYMENT_SCHEDULES — supplies the original amount due, exchange rate, and due date.
• AR_RECEIVABLE_APPLICATIONS — links the chargeback to the cash receipt and associated payment schedule.
• AR_LOOKUPS — resolves the reason code into a meaning and description.
• HZ_CUST_SITE_USES / location data — supplies the location value.

The join structure centers on the chargeback transaction (RA_CUSTOMER_TRX), joined to its payment schedule (AR_PAYMENT_SCHEDULES), its application to a receipt (AR_RECEIVABLE_APPLICATIONS), its GL distribution (RA_CUST_TRX_LINE_GL_DIST), and lookup/type/location descriptive tables. Implementation objects appear as synonyms in the APPS schema.

Key Columns

• CB_NUMBER — the transaction number of the chargeback.
• CUSTOMER_TRX_ID / CUST_TRX_TYPE_ID / SET_OF_BOOKS_ID — identifying keys for the transaction, its type, and ledger.
• TRX_DATE — transaction date of the chargeback.
• TRANSACTION_TYPE — the name of the chargeback transaction type.
• CHARGEBACK_AMOUNT — the original amount due on the payment schedule; the primary deduction value.
• ACCTD_CHARGEBACK_AMOUNT — the chargeback amount converted to ledger currency using NVL(exchange rate, 1).
• DUE_DATE — due date of the chargeback.
• ASSOCIATED_CASH_RECEIPT_ID and RECEIPT_PAYMENT_SCHEDULE_ID — the receipt and receipt payment schedule associated with the chargeback.
• REASON_CODE, REASON_MEANING, REASON_DESCRIPTION — deduction reason details.
• GL_POSTED_DATE, GL_DATE, CODE_COMBINATION_ID — accounting distribution context.
• LOCATION — customer site location.
• DDF/audit columns — ATTRIBUTE1–15, CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, REQUEST_ID, PROGRAM_ID, DOC_SEQUENCE_ID, DOC_SEQUENCE_VALUE.

Common Use Cases and Queries

Typical scenarios include reconciling deductions against receipts, analyzing chargeback amounts by customer or reason, and feeding downstream reporting or integration extracts.

Sample query returning chargebacks by amount and receipt:

SELECT cb_number, customer_trx_id, trx_date, transaction_type,
       chargeback_amount, acctd_chargeback_amount,
       associated_cash_receipt_id, reason_meaning
FROM   apps.ar_ded_chargebacks_v
WHERE  chargeback_amount > 0
ORDER BY trx_date;

Sample aggregation of chargebacks by reason:

SELECT reason_meaning, SUM(chargeback_amount) total_cb
FROM   apps.ar_ded_chargebacks_v
GROUP BY reason_meaning;

The view is read-only and derives all values from its base objects; consequently it reflects current transactional state rather than a historical snapshot, and it should be queried within the APPS schema context or through a synonym with appropriate grants.