Results for “arbv_debits”

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

Overview

The ARBV_DEBITS view is an Oracle Receivables (AR) database object owned by the APPS schema. It presents information about debit items — receivables transactions that increase a customer's outstanding receivable balance. Such debit items remain open until the balance due is reduced to zero through receipts, credit memos, adjustments, or other settlement activity.

In Oracle EBS 12.1.1 and 12.2.2, ARBV_DEBITS functions as a read-only reporting and integration view. It exposes customer transaction header information in a denormalized, consumer-friendly form, making it suitable for custom reports, extracts, and downstream interfaces that need a consolidated view of debit-generating transactions without joining the underlying transaction tables directly. The view is defined WITH READ ONLY, ensuring that consumers cannot perform DML against it.

Underlying Base Objects

ARBV_DEBITS is defined over two documented base objects:

• RA_CUSTOMER_TRX (accessed via synonym) — the core Receivables table storing customer transaction headers, aliased as CT.
• RA_CUST_TRX_TYPES (accessed via synonym) — the transaction type definition table, aliased as CTT.

The join is performed on CUST_TRX_TYPE_ID, with an ORG_ID safety condition using NVL(CT.ORG_ID, -12345) = NVL(CTT.ORG_ID, -12345) to handle multi-org records where the transaction type may or may not carry an ORG_ID. The view is further filtered so that only transaction types with TYPE IN ('INV', 'DEP', 'DM', 'CB') are returned — that is, Invoices, Deposits, Debit Memos, and Chargebacks.

Key Columns

The view exposes the transaction identifier, transaction number, document sequence value, transaction date, and exchange rate information (rate, rate type, and exchange date). Descriptive attributes such as purchase order details, customer reference, finance charges flag, term due date, tax exemption flag, ship via, ship date, waybill number, FOB point, EDI processed flag, and printing attributes (original date, last printed, pending flag, count) are also included. Several columns are presented through lookups — for example, complete flag, transaction status, finance charges, tax exemption, FOB point, EDI processed, and printing pending — resolved against AR_LOOKUPS using their respective lookup types.

Identity columns include the batch ID, term ID, contact IDs (bill-to, ship-to, sold-to), customer IDs (bill-to, ship-to, sold-to, paying), transaction type ID, primary salesrep ID, site use IDs, remit-to address ID, customer bank account ID, receipt method ID, and ORG_ID. The WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, and CREATED_BY — are carried forward for auditing and incremental extraction.

Common Use Cases and Queries

Typical scenarios include aging and open-item reporting, customer balance analysis, receipt application reconciliations, and extract programs feeding data warehouses or external systems. A basic query returns all debit items for a given organization:

• SELECT transaction_number, tra, customer_trx_id, exchange_rate FROM apps.arbv_debits WHERE org_id = :p_org_id;
• Filtering by transaction date to isolate period activity for reconciliation.
• Joining to receipt and adjustment views to compute the remaining open balance on each debit item.
• Using the WHO columns to drive incremental or delta extracts in interface programs.

Because the view is read-only and pre-filtered to debit-generating transaction types, it simplifies reporting logic and reduces the risk of inadvertently including non-debit transaction classes.