Search Results document_currency_code




Overview
Explore in AI Chat

Overview

The APPS.ARBR_DOCS_RECEIVABLES_V view is a Receivables (AR) reporting and integration object that exposes receivables transaction data in a flattened, settlement-oriented format. Although its internal object name contains the AR prefix, the view functions within the Oracle Payments settlement framework, marshalling receivable invoice and credit memo information so that downstream payment settlement processes can consume a consistent row set for each eligible transaction. The view is marked VALID and is owned by the APPS schema, which means it is a standard seeded database object delivered with Oracle E-Business Suite 12.1.1 and 12.2.2.

The view selects from RA_CUSTOMER_TRX, RA_CUSTOMER_TRX_LINES, RA_CUST_TRX_TYPES_ALL, AR_TRANSACTION_HISTORY, and IBY_TRXN_EXTENSIONS_V, applying a set of join and filter conditions that restrict output to transactions carrying a populated BR_AMOUNT and a valid payment transaction extension. Because the BR_AMOUNT column is a Receivables-specific attribute used by certain localization and payment integration flows, the view serves as a bridge between core AR transaction data and the IBY payments schema.

Underlying Base Objects

The documented base objects referenced by ARBR_DOCS_RECEIVABLES_V are:

  • RA_CUSTOMER_TRX (synonym) – the header table for customer transactions, used both as the primary transaction (TRXBR) and the referenced transaction (TRX).
  • RA_CUSTOMER_TRX_LINES (synonym) – transaction lines, supplying BR_REF_CUSTOMER_TRX_ID and the settlement amount.
  • RA_CUST_TRX_TYPES_ALL (synonym) – transaction type definition, providing the transaction class name and drawee/signed flags.
  • AR_TRANSACTION_HISTORY (synonym) – supplies the current record flag and the protested status used to derive a document flag.
  • IBY_TRXN_EXTENSIONS_V (view) – the Payments transaction extension view, joined on PAYMENT_TRXN_EXTENSION_ID to obtain the payment system order number.
  • FND_GLOBAL (package), IBY_FNDCPT_TRXN_PUB (package) – supporting PL/SQL packages referenced by the view's dependency chain.

The joins require that the header and line share a CUSTOMER_TRX_ID, that a valid transaction type exists, that the history record is current (NVL(CURRENT_RECORD_FLAG,'Y') = 'Y'), and that the referenced transaction resolves through BR_REF_CUSTOMER_TRX_ID.

Key Columns

The view projects a fixed set of aliased columns in a specific positional order. Numeric placeholders (NULL, 1) fill positions where no source column is mapped, preserving a stable interface for downstream consumers.

Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) are also exposed, along with ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15.

Common Use Cases and Queries

The view is typically queried during payment settlement processing, when reconciling receivable documents against IBY payment transaction extensions. Because DUTY_AMOUNT is returned as NULL, queries that inspect the column for duty or customs charges will always yield no value; it exists to satisfy the fixed column contract of the settlement interface rather than to carry data.

A representative query is:

  • SELECT ORDER_EXT_ID, CALLING_APP_DOC_REF_NUMBER, DOCUMENT_DATE, DOCUMENT_CURRENCY_CODE, DOCUMENT_AMOUNT, SETTLEMENT_AMOUNT, DUTY_AMOUNT FROM APPS.ARBR_DOCS_RECEIVABLES_V WHERE ORDER_EXT_ID = :p_extension_id;
  • SELECT PAYMENT_TRXN_EXTENSION_ID, DOCUMENT_TYPE, DOCUMENT_AMOUNT, LEGAL_ENTITY_ID FROM APPS.ARBR_DOCS_RECEIVABLES_V WHERE TRUNC(DOCUMENT_DATE) BETWEEN :p_from AND :p_to;
  • SELECT ORDER_TANGIBLE_ID, DOCUMENT_AMOUNT, SETTLEMENT_AMOUNT, DUTY_AMOUNT FROM APPS.ARBR_DOCS_RECEIVABLES_V ORDER BY DOCUMENT_DATE DESC;

Because the view is APPS-owned and marked VALID, it should be treated as read-only in custom code. Any query joining to it should use the exposed extension identifiers to correlate with IBY tables rather than assuming DUTY_AMOUNT carries settlement data.