Search Results status_dsp




Overview
Explore in AI Chat

Overview

AR_RGW_RECEIPT_HISTORY_V is a view owned by the APPS schema in Oracle E-Business Suite, classified under the Receivables (AR) product family. The ETRM metadata annotates it as "Release 10SC Only," indicating that its original design intent traces to the Receipt Gateway (RGW) functionality of very early Receivables releases. In practice the view remains VALID and available in 12.1.1 and 12.2.2 and continues to be used by the Receipt Gateway's Receipt History window for presenting the chronological status trail of a cash receipt.

The view's stated purpose, embedded in the view text comment, is to support the Receipt History window of the Receipt Gateway. It exposes the lifecycle of a receipt — creation, remittance, clearing, reversal, and related status transitions — by combining the raw status codes stored in AR_CASH_RECEIPT_HISTORY with their user-facing descriptions. Its principal reporting value is the STATUS_DSP column, which decodes the internal status code into a translatable lookup meaning, sparing report authors and integration developers from hard-coding lookup joins.

Underlying Base Objects

The view is defined over two documented base objects:

  • AR_CASH_RECEIPT_HISTORY (referenced through a synonym) — the transactional history table that records each state change applied to a cash receipt, including the transaction date, GL date, amount, exchange rate, and accounting amount at the time of the event.
  • AR_LOOKUPS (referenced as a view) — the Receivables lookup repository, seeded with lookup type RECEIPT_CREATION_STATUS, which supplies the meaning text for each status code.

The join is an equijoin on L.LOOKUP_TYPE = 'RECEIPT_CREATION_STATUS' AND L.LOOKUP_CODE = CRH.STATUS. Because AR_LOOKUPS is language-sensitive (it exposes MEANING, which resolves against the session's language), rows are only returned when a matching enabled lookup code exists for the given status. ROW_ID is drawn from CRH.ROWID and is retained for row-level identification purposes typical of older Oracle Forms-based views.

Key Columns

  • ROW_ID — Row identifier derived from AR_CASH_RECEIPT_HISTORY.ROWID.
  • CASH_RECEIPT_ID — Foreign key to the cash receipt whose history is being reported; the primary join key to AR_CASH_RECEIPTS.
  • CASH_RECEIPT_HISTORY_ID — Unique identifier of the individual history (status transition) record.
  • STATUS — The internal status code from AR_CASH_RECEIPT_HISTORY, matching LOOKUP_CODE in the RECEIPT_CREATION_STATUS lookup type.
  • STATUS_DSP — The decoded, display-ready status meaning from AR_LOOKUPS.MEANING. This is the column most commonly searched for as status_dsp.
  • TRX_DATE — Transaction date on which the status transition occurred.
  • GL_DATE — Accounting date associated with the history record.
  • AMOUNT — Entered (transaction currency) amount at the time of the event.
  • EXCHANGE_RATE — Rate applied between transaction and ledger currency.
  • ACCTD_AMOUNT — Amount converted to the functional/ledger currency.

Common Use Cases and Queries

The view is typically queried to reconstruct the audit trail of a receipt, to report on receipts by lifecycle stage using readable status text, or to feed downstream reconciliation extracts. A basic query listing the history of a single receipt follows:

SELECT status_dsp, trx_date, gl_date, amount, acctd_amount
FROM apps.ar_rgw_receipt_history_v
WHERE cash_receipt_id = :p_receipt_id
ORDER BY trx_date, cash_receipt_history_id;

A summary of receipts grouped by displayed status is equally common:

SELECT status_dsp, COUNT(*) status_count, SUM(acctd_amount) total_acctd
FROM apps.ar_rgw_receipt_history_v
WHERE trx_date BETWEEN :p_from AND :p_to
GROUP BY status_dsp;

Because the view restricts to codes present in RECEIPT_CREATION_STATUS, it is unsuitable for reporting on receipt states that fall outside that lookup type; in such cases AR_CASH_RECEIPT_HISTORY should be queried directly with an outer join to AR_LOOKUPS. All queries should be issued against the APPS synonym, respecting the standard EBS security and MOAC context for Receivables.