Results for “resolved_trx_amount_rem”

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

Overview

AR_CASH_RECOS_ALL is a Receivables (AR) module table owned by the AR schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. As described in the ETRM metadata, the table stores recommendation details generated against document number references supplied to the cash reconciliation process. The object is flagged as BETA in the source documentation, which indicates that its structure and behavior are subject to change and that it should be treated with caution in production reporting or custom development.

The table is populated by the automatic cash application and matching engine, which evaluates incoming receipts against open transactions and produces a scored, ranked set of candidate matches. Each row captures both the matched transaction candidate and the reasoning behind the recommendation, including the matching score, the reason code, and the mechanism used to resolve the match. The table is therefore best understood as an audit and diagnostics surface for cash application recommendations rather than a transactional system of record.

Applying a heuristic Data Vault classification, AR_CASH_RECOS_ALL most closely resembles a satellite. It holds descriptive, non-key attributes attached to a recommendation identifier and is keyed on a single surrogate column, with no evidence of hub-like business key enforcement or of a multi-source link structure. It does, however, carry a foreign key reference to AR_CASH_AUTOMATCHES via AUTOMATCH_ID, which provides lineage back to the automatch run that produced the recommendation.

Key Information Stored

The table is documented with 31 columns. The most significant are summarized below.

• RECOMMENDATION_ID — The surrogate primary key, enforced by AR_CASH_RECOS_ALL_PK and also referenced in the secondary index AR_CASH_RECOS_ALL_PK1. This is the only documented unique identifier; no separate business-key unique index is recorded in the metadata.
• AUTOMATCH_ID — Foreign key to AR_CASH_AUTOMATCHES, linking the recommendation to the automatch batch or run that generated it.
• REMIT_REFERENCE_ID — Reference to the remittance or document number context supplied to the reconciliation engine.
• PAY_FROM_CUSTOMER — The paying customer associated with the receipt or remittance being evaluated.
• RESOLVED_MATCHING_NUMBER, RESOLVED_MATCHING_DATE, RESOLVED_MATCHING_CLASS — The transaction number, date, and class of the recommended match candidate.
• RESOLVED_MATCH_CURRENCY, RESOLVED_TRX_AMOUNT, RESOLVED_TRX_AMOUNT_REM — Currency and amount of the resolved transaction, including the amount remaining after prior application.
• MATCH_RESOLVED_USING, MATCH_SCORE_VALUE, MATCH_REASON_CODE — The matching mechanism applied, the confidence score, and the coded rationale for the recommendation.
• RECOMMENDATION_STATUS, RECOMMENDATION_REASON, RECOMMENDATION_SOURCE, RECOMMENDATION_TYPE — The state, explanation, origin, and category of the recommendation.
• PRIORITY and AUTOAPPLY_STATUS — Ranking of the recommendation and its disposition in the autoapply process.
• CUSTOMER_SITE_USE_ID and CONS_INV_ID — Site-use and consolidated invoice context for the recommendation.
• ORG_ID — Multi-org operating unit identifier.
• Standard audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, and REQUEST_ID.

Common Use Cases and Queries

The primary use case is diagnostic analysis of automatic cash application: identifying why a receipt was matched to a particular transaction, how confident the engine was, and whether the recommendation was accepted. Reconciliation analysts and AR support teams use these rows to tune matching rules and to investigate unmatched or misapplied cash.

A typical query joins recommendations to their parent automatch run and filters on confidence or status:

• Select RECOMMENDATION_ID, RESOLVED_MATCHING_NUMBER, MATCH_SCORE_VALUE, MATCH_REASON_CODE, RECOMMENDATION_STATUS from AR_CASH_RECOS_ALL where ORG_ID = :org_id and MATCH_SCORE_VALUE < :threshold order by MATCH_SCORE_VALUE.
• Aggregate recommendation volume and acceptance rates by MATCH_RESOLVED_USING or RECOMMENDATION_SOURCE to measure engine effectiveness over a period.
• Join to AR_CASH_AUTOMATCHES on AUTOMATCH_ID to attribute recommendations to a specific run or batch.
• Report low-scoring or rejected recommendations for manual review by prioritizing on PRIORITY and filtering AUTOAPPLY_STATUS.

Because audit columns are present, change tracking and request-level tracing are possible through REQUEST_ID and PROGRAM_ID.

Related Objects

• AR_CASH_AUTOMATCHES — Parent automatch run referenced by AUTOMATCH_ID; the only documented foreign key relationship.
• AR_CASH_RECEIPTS_ALL — Receipt header data context for the remittance being evaluated.
• AR_CASH_RECEIPT_HISTORY_ALL — Application history used to confirm whether a recommendation was ultimately posted.
• AR_PAYMENT_SCHEDULES_ALL — Transaction schedule rows that supply RESOLVED_MATCHING_NUMBER, date, class, and amount values.
• HZ_CUST_ACCOUNTS and HZ_CUST_SITE_USES_ALL — Customer and site-use context behind PAY_FROM_CUSTOMER and CUSTOMER_SITE_USE_ID.
• AR_RECEIVABLE_APPLICATIONS_ALL — The downstream application table populated when a recommendation is accepted.
• AR_AUTOAPPLY_RULES — Rule configuration driving MATCH_RESOLVED_USING and MATCH_REASON_CODE outcomes.

Given the BETA designation in the ETRM documentation, integrators should validate column availability and behavior against the specific patch level of the 12.1.1 or 12.2.2 instance before relying on these columns in custom code.