Search Results ar_crh_gt

Overview

The AR_CRH_GT table is a global temporary table (indicated by the _GT suffix) residing in the AR (Receivables) schema of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It is associated with the Cash Receipt History (CRH) processing framework, functioning as a transient staging structure that the AutoAccounting and receipt posting engines populate during the generation of distribution lines. The table temporarily holds the accounting attributes — amounts, currency conversions, code combinations, and posting control references — that will ultimately drive the creation of subledger journal entries for cash receipts and their applied activities.

From a Data Vault modelling perspective, the mined FK structure classifies this object as standalone. This is a heuristic suggestion rather than a delivered characteristic: because the table is a temporary working set rather than a persistent entity, no hub, link, or satellite role applies. It behaves as a transient sateline/staging artifact whose rows are generated and consumed within a single session or transaction cycle.

Key Information Stored

The 23 documented columns capture the envelope of an accounting distribution candidate. The most significant columns include:

• CASH_RECEIPT_ID and CASH_RECEIPT_HISTORY_ID — identify the parent cash receipt and the specific history record being processed; these are the principal business-key candidates linking back to AR_CASH_RECEIPTS and AR_CASH_RECEIPT_HISTORY.
• CRH_LINE_ID — the line within the receipt history that this distribution pertains to.
• POSTING_CONTROL_ID — the documented foreign key; it references AR_POSTING_CONTROL, determining the posting rule applied.
• SOURCE_TYPE — indicates the origin of the receipt event (for example, manual, lockbox, or miscellaneous).
• AMOUNT and ACCTD_AMOUNT — the entered and accounted balances of the candidate distribution.
• RECP_AMOUNT and RECP_ACCTD_AMOUNT — the receipt-level amounts carried for allocation and rounding logic.
• CODE_COMBINATION_ID — the target accounting flexfield combination for the distribution.
• EXCHANGE_DATE, EXCHANGE_RATE, EXCHANGE_RATE_TYPE, and BASE_CURRENCY_CODE — the currency conversion attributes applied to reach the accounted amount.
• LEDGER_ID and ORG_ID — the ledger and operating unit context, essential for multi-org and multi-ledger environments.
• STATUS and DIST_LINE_STATUS — control flags governing whether the distribution row is eligible for posting or held back.

No surrogate primary key is documented on the temporary structure itself, consistent with its role as a session-scoped work area. Business-key identity is derived from the cash receipt, history, and line combination.

Common Use Cases and Queries

Because the table is transient, diagnostics are typically performed while a posting or AutoAccounting session is active, or by inspecting the persistent output in AR_DISTRIBUTIONS_ALL after the process commits. A typical diagnostic query joins the temporary rows back to their driving posting control and receipt identifiers:

• Trace a receipt's accounting: SELECT crh.cash_receipt_id, crh.posting_control_id, crh.amount, crh.acctd_amount, crh.code_combination_id FROM ar_crh_gt crh WHERE crh.cash_receipt_id = :receipt_id;
• Validate currency conversion: compare AMOUNT against ACCTD_AMOUNT using EXCHANGE_RATE, flagging rate-type mismatches.
• Audit posting eligibility: filter on STATUS and DIST_LINE_STATUS to identify rows excluded from journal creation.
• Reconcile ledger and operating unit: group totals by LEDGER_ID and ORG_ID to confirm distributions respect organisational boundaries.

Report developers should avoid treating AR_CRH_GT as a persistence layer; reporting should target the posted subledger tables instead.

Related Objects

The most significant related objects, grounded in the documented foreign key and receipt-processing context, are:

• AR_POSTING_CONTROL — joined via POSTING_CONTROL_ID; the only documented FK target.
• AR_CASH_RECEIPTS — joined via CASH_RECEIPT_ID.
• AR_CASH_RECEIPT_HISTORY — joined via CASH_RECEIPT_HISTORY_ID and CRH_LINE_ID.
• AR_DISTRIBUTIONS_ALL — the persistent destination for rows generated from this staging table.
• GL_CODE_COMBINATIONS — referenced through CODE_COMBINATION_ID.
• AR_RECEIVABLE_APPLICATIONS_ALL — the applied receipt activity that generates distributions.
• GL_JE_LINES and GL_JE_HEADERS — the eventual general ledger journal targets.

These relationships make AR_CRH_GT a pivotal, if temporary, junction in the Receivables-to-General-Ledger accounting flow.