Results for “customer_reference”

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

Overview

AR_CASH_REMIT_REFS_ALL is a Receivables (AR) transaction table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores Cash Remittance Reference details. It carries remittance reference information used during automatic and manual cash application, associating remittance lines received from customers or banks with receipts, invoices, and the rules used to resolve matching. The ETRM metadata marks the object as BETA, indicating the feature set around it is comparatively recent or of limited production exposure and should be treated with corresponding caution during upgrades or custom development.

The table is owned by the AR schema and is documented at 41 columns in the 12.2.2 physical schema. From a heuristic Data Vault perspective, the standalone FK classification suggests modeling this object as a hub for the remittance reference identifier, with dependent descriptive attributes best represented in a satellite; the absence of upstream hub-style parents in the mined metadata further supports treating it as a standalone reference construct rather than a pure link table.

Key Information Stored

The table is anchored by the surrogate primary key REMIT_REFERENCE_ID, enforced through the AR_CASH_REMIT_REFS_ALL_PK constraint (a second documented PK variant, AR_CASH_REMIT_REFS_ALL_PK1, references the same column). No separate unique business-key index is documented in the metadata, so business identifiers such as CUSTOMER_REFERENCE, INVOICE_REFERENCE, and INSTALLMENT_REFERENCE function as candidate natural keys rather than enforced unique keys.

• REMIT_REFERENCE_ID — surrogate primary key for each remittance reference row.
• AUTOMATCH_SET_ID — foreign key to AR_CASH_AUTO_RULE_SETS, identifying the auto-application rule set applied.
• TRANSMISSION_ID — foreign key to AP_TRANSMISSIONS_SETUP, linking the remittance to its transmission/batch setup.
• CASH_RECEIPT_ID — the receipt against which the remittance reference is resolved.
• CUSTOMER_ID, CUSTOMER_NUMBER, CUSTOMER_REFERENCE — customer identification and the customer-supplied reference.
• INVOICE_REFERENCE, INVOICE_CURRENCY_CODE, INVOICE_STATUS — invoice-facing attributes used for matching.
• RESOLVED_MATCHING_NUMBER, RESOLVED_MATCHING_INSTALLMENT, RESOLVED_MATCHING_DATE, MATCH_RESOLVED_USING, MATCH_SCORE_VALUE — the outcome of the matching process.
• AMOUNT_APPLIED, AMOUNT_APPLIED_FROM, TRANS_TO_RECEIPT_RATE — applied amounts and currency conversion rate.
• AUTO_APPLIED, MANUALLY_APPLIED, RECEIPT_REFERENCE_STATUS — processing state flags.
• BANK_ACCOUNT_NUMBER, TRANSIT_ROUTING_NUMBER — remitting bank details.
• ORG_ID — multi-org operating unit context.

Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and concurrent request columns (PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID) are also present for audit and traceability.

Common Use Cases and Queries

Typical usage centers on diagnosing why a remittance line auto-applied, partially matched, or failed to match. A common pattern joins the reference row to its rule set and transmission configuration:

SELECT r.remit_reference_id, r.customer_reference, r.invoice_reference,
  r.amount_applied, r.match_resolved_using, r.match_score_value,
  s.name auto_rule_set, r.receipt_reference_status
FROM ar_cash_remit_refs_all r, ar_cash_auto_rule_sets s
WHERE r.automatch_set_id = s.rule_set_id
AND r.org_id = :p_org_id;

Reporting scenarios include auto-application success rates (comparing AUTO_APPLIED to MANUALLY_APPLIED), unapplied or unresolved remittance lines (RECEIPT_REFERENCE_STATUS not resolved), and throughput by transmission batch using TRANSMISSION_ID or BATCH_ID. Reconciliation reports often aggregate AMOUNT_APPLIED by INVOICE_CURRENCY_CODE, applying TRANS_TO_RECEIPT_RATE where the invoice currency differs from the receipt currency.

Related Objects

• AR_CASH_AUTO_RULE_SETS — joined on AUTOMATCH_SET_ID to identify the auto-application rule set.
• AP_TRANSMISSIONS_SETUP — joined on TRANSMISSION_ID for the remittance transmission configuration.
• AR_CASH_RECEIPTS_ALL — related through CASH_RECEIPT_ID for receipt header attributes.
• AR_CASH_RECEIPT_HISTORY_ALL — receipt activity history for the applied receipt.
• AR_PAYMENT_SCHEDULES_ALL — joined via PAYMENT_SCHEDULE_ID and INSTALLMENT_NUMBER for the matched installment.
• RA_CUSTOMER_TRX_ALL — joined on CUSTOMER_TRX_ID for invoice-level detail.
• HZ_CUST_ACCOUNTS / HZ_CUSTOMERS — customer context for CUSTOMER_ID and CUSTOMER_NUMBER.
• AR_RECEIVABLE_APPLICATIONS_ALL — the applications created once a remittance reference is resolved and applied.

Because the object is flagged BETA, implementations should confirm supported use in the target patch level before building dependent extensions or custom reports.