Results for “currency_exchange_rate”

50+ results




Overview
Explore in AI Chat

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

Overview

The APPS.ARBV_RECEIPT_HISTORIES view is a Receivables (AR) reporting and integration object that exposes the historical lifecycle of cash receipts recorded in Oracle E-Business Suite. It is a retrofitted, read-only view defined over AR_CASH_RECEIPT_HISTORY, providing a flattened, denormalized projection of receipt history records for use by Oracle's business intelligence, subledger accounting, and application integration layers. Because the view text is declared WITH READ ONLY, it is intended strictly for query and reporting consumption rather than transactional DML. Its role in EBS reporting is to surface the audit trail of every state change a receipt passes through — creation, application, confirmation, reversal, and factoring — along with the associated amount and exchange rate context. The view also carries lookups-based translation columns (for example receipt status, current record flag, factoring flag, and note status) that resolve underlying lookup codes to their meanings, which simplifies downstream reporting and eliminates the need for callers to join AR_LOOKUPS explicitly. In 12.1.1 and 12.2.2, the object retains the same functional contract, with the "_LA:"-prefixed columns reflecting the standard Subledger Accounting / lookups attribute convention used by retrofitted Receivables views.

Underlying Base Objects

The view is defined over a single documented base object, AR_CASH_RECEIPT_HISTORY (referenced via its APPS synonym), aliased as CRH in the view SQL. All exposed columns are derived from that table; the view performs no joins to other base tables, relying instead on inline lookup annotations embedded as column expressions (the "_LA:" entries) that map code values to descriptive meanings at runtime. The /* UNIQUE ATTRIBUTES */ and /* REGULAR ATTRIBUTES */ comments in the view text identify which columns serve as the unique identifier (CASH_RECEIPT_HISTORY_ID) versus the descriptive attributes. The view is not a materialized object and stores no data itself; every query reads live from AR_CASH_RECEIPT_HISTORY, so its results reflect the current committed state of the underlying history table.

Key Columns

Common Use Cases and Queries

Typical usage includes receipt lifecycle auditing, reconciliation between entered and functional amounts, and extracting history for subledger or data-warehouse feeds. A representative query for functional amount analysis by operating unit is:

SELECT cash_receipt_history_id, cash_receipt_id, batch_id, amount, functional_amount, currency_exchange_rate, org_id, creation_date FROM apps.arbv_receipt_histories WHERE org_id = :p_org_id AND creation_date >= :p_from_date ORDER BY creation_date;

To compare entered versus functional values and flag exchange differences:

SELECT cash_receipt_id, amount, functional_amount, (functional_amount - amount) AS fx_difference FROM apps.arbv_receipt_histories WHERE amount <> functional_amount;

To trace the current active record for a receipt:

SELECT cash_receipt_id, "_LA:RECEIPT_STATUS", functional_amount FROM apps.arbv_receipt_histories WHERE "_LA:CURRENT_RECORD_FLAG" = 'Yes';

Because the view is read-only and non-materialized, queries should be filtered by ORG_ID and date ranges where volumes are large, and callers should reference the quoted lookup-meaning columns exactly as named when writing custom SQL.