Search Results adj_activity

Overview

AR_TA_VRH_ADJ_V is a Receivables (AR) reporting view that consolidates adjustment activity processed through the Cash Engine into the receipts remittance history. It joins adjustment records to their originating receivables transaction type and to the remittance history table, exposing a denormalized, read-only result set suitable for reconciliation, audit, and reporting. The view is specifically scoped to remittance history rows of RECORD_TYPE = 9 that were created from the CASH_ENGINE source, and it only returns rows where a matching adjustment record exists.

The view behaves as a composite of adjustment, transaction-type, and remittance-history data. Its primary value is that it resolves the adjustment's descriptive activity (the receivables transaction NAME) and its amount and status without requiring the report author to join AR_ADJUSTMENTS, AR_RECEIVABLES_TRX, and AR_TA_REMIT_HIST manually. In Oracle EBS 12.1.1 and 12.2.2 the object is documentation-only in the ETRM metadata, and the supplied metadata states it is not implemented in the documented database. Therefore it should be treated as a reference definition; verify existence and column semantics against the target instance before depending on it in custom code or reports.

Underlying Base Objects

The view is defined over three base tables:

• AR_ADJUSTMENTS (ADJ) — the adjustment header/line records holding amount, status, type, and the receivables transaction reference.
• AR_RECEIVABLES_TRX (RTRX) — the receivables transaction definition, supplying the NAME used as the adjustment activity.
• AR_TA_REMIT_HIST (RH) — the remittance history table that tracks processing of receipts and adjustments through the Cash Engine, keyed by HISTORY_LINE_ID and PARENT_HISTORY_LINE_ID, and carrying batch and check identifiers.

The joins are: ADJ.RECEIVABLES_TRX_ID = RTRX.RECEIVABLES_TRX_ID; and RH.ADJUSTMENT_ID = ADJ.ADJUSTMENT_ID combined with RH.RECORD_TYPE = 9 and RH.CREATED_FROM = 'CASH_ENGINE'. No additional base objects are documented in the ETRM metadata.

Key Columns

• BATCH_NAME — remittance batch identifier from the history table.
• CHECK_NUMBER — the receipt/check number associated with the remittance history row.
• HISTORY_LINE_ID / PARENT_HISTORY_LINE_ID — the unique history line and its parent, useful for tracing hierarchical Cash Engine processing.
• ADJUSTMENT_ID / ADJUSTMENT_NUMBER — the AR adjustment identifier and its user-facing number.
• ADJ_AMOUNT — the adjustment amount (aliased from ADJ.AMOUNT).
• STATUS — the adjustment's approval/posting status.
• ADJ_TYPE — the adjustment classification.
• ADJ_ACTIVITY — the receivables transaction name describing the adjustment activity.

Common Use Cases and Queries

Typical uses include reconciling Cash Engine adjustments to receipt remittance batches and tracing activity by batch or check. A sample query:

• SELECT batch_name, check_number, adjustment_number, adj_activity, adj_amount, status, adj_type FROM ar_ta_vrh_adj_v WHERE batch_name = :p_batch ORDER BY history_line_id;
• Aggregate adjustment amounts by activity: SELECT adj_activity, SUM(adj_amount) FROM ar_ta_vrh_adj_v GROUP BY adj_activity;
• Join to AR_TA_REMIT_HIST or AR_ADJUSTMENTS by identifier for drill-down where additional columns are required.