Search Results crh_status




Overview
Explore in AI Chat

Overview

AR_RECEIPT_HISTORY_H_V is a reporting view owned by the APPS schema in Oracle E-Business Suite Receivables (AR). As documented in ETRM, its description is "cash receipt history header extract," and its purpose is to expose the header-level (level flag 'H') Cash Receipt History records that participate in Subledger Accounting (SLA) extract processing. The view is defined over AR_XLA_LINES_EXTRACT, AR_CASH_RECEIPT_HISTORY_ALL, and AR_RECEIVABLE_APPLICATIONS_ALL, and it is heavily used by the Create Accounting and Receivables SLA extract programs to join accounting event data back to the underlying receipt history rows.

The view is available in both 12.1.1 and 12.2.2 with the same logical content. The view text carries a hint, /*+INDEX(HE AR_XLA_LINES_EXTRACT_N1) */, indicating the optimizer is directed to drive processing through the extract table by event, which is consistent with its role in accounting extract flows. The reason users frequently search for the term crh_status is that the column is aliased from the base table as CRH_STATUS, and it forms the core status filter driving receipt accounting.

Underlying Base Objects

ETRM documents three referenced base objects:

  • AR_XLA_LINES_EXTRACT — the Subledger Accounting extract table. The view restricts to HE.LEVEL_FLAG = 'H' and HE.CRH_STATUS IS NOT NULL, and joins it to the receipt history by EVENT_ID.
  • AR_CASH_RECEIPT_HISTORY_ALL — the core receipt history table, aliased as CRH (the primary row) and again as CRH1 (the reversal row, joined via REVERSAL_CASH_RECEIPT_HIST_ID with an outer join).
  • AR_RECEIVABLE_APPLICATIONS_ALL — the applications/application history table that supplies transaction application linkage for the header extract.

Because the view is defined as a UNION ALL, it produces one row set for current receipt history rows and a second row set associated with reversal activity, effectively pairing each status change with the corresponding reversal status and reversal GL date.

Key Columns

Common Use Cases and Queries

Typical use cases include troubleshooting receipt accounting entries, reconciling receipt status transitions to GL dates, and extracting header-level receipt history for downstream reporting. A common query filters on the aliased status column:

  • Receipt status snapshot: SELECT crh_cash_receipt_history_id, crh_status, crh_gl_date FROM ar_receipt_history_h_v WHERE crh_status = 'CLEARED';
  • Reversal reconciliation: SELECT crh_cash_receipt_history_id, crh_status, crh_reversal_status, crh_reversal_gl_date FROM ar_receipt_history_h_v WHERE crh_reversal_id IS NOT NULL;
  • Event linkage: SELECT event_id, crh_status, crh_trx_date FROM ar_receipt_history_h_v WHERE event_id = :event_id;
  • Attribute reporting: SELECT crh_attribute_category, crh_attribute1, crh_status FROM ar_receipt_history_h_v WHERE crh_attribute_category = 'MISC';

Because the view is defined with an outer join to the reversal row and a UNION ALL, queries should account for duplicate logical receipts across the two branches. Performance is best when predicates include EVENT_ID or CASH_RECEIPT_HISTORY_ID so that the AR_XLA_LINES_EXTRACT_N1 index and receipt history primary keys are used. The view is not designed for direct DML and is supplied strictly for read access within the APPS schema.