Results for “use_matching_date”

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

Overview

AR_CASH_AUTOMATCHES is a Receivables (AR) module table in the Oracle E-Business Suite database schema. As its ETRM description states, it "stores Automatch Cash Rule Details (BETA)." Functionally, the table serves as the master definition repository for Automatic Cash Application rules — the configuration records that govern how Oracle Receivables automatically matches receipts to open transactions based on user-defined criteria. Each row represents a rule header that drives the automatic matching engine, controlling tolerances, matching logic, and the effective date range during which a rule applies.

Based on the FK-structure mining documented in the ETRM metadata, this object carries a heuristic Data Vault classification of standalone. In Data Vault modeling terms, this suggests treating AR_CASH_AUTOMATCHES as a self-contained structure rather than a conventional hub with dependent links and satellites. Practitioners should note the classification is heuristic and mined from FK relationships, so it is best regarded as a modeling suggestion rather than a definitive architectural fact.

Key Information Stored

The table is documented with 15 columns in the 12.2.2 physical schema. The surrogate primary key is AUTOMATCH_ID, constrained by two documented primary key declarations (AR_CASH_AUTOMATCHES_PK and AR_CASH_AUTOMATCHES_PK1), both keyed on AUTOMATCH_ID. This identifier is the join anchor used by all dependent child tables and should be treated as the sole documented unique key; the metadata does not document an alternate business-key unique index.

• AUTOMATCH_ID — surrogate primary key; the foreign key target referenced by all dependent tables.
• MATCHING_OPTION — the core rule attribute defining which matching behavior the Automatch process applies.
• AUTO_MATCH_THRESHOLD — tolerance governing fully automatic matches.
• SUGG_MATCH_THRESHOLD — tolerance governing suggested (non-automatic) matches.
• START_DATE / END_DATE — effective dating that determines the rule's active window.
• ACTIVE_FLAG — enables or disables the rule.
• MATCH_DATE_BY — controls which date is used during the match evaluation.
• USE_MATCHING_DATE / USE_MATCHING_AMOUNT — flags enabling date-based and amount-based matching logic respectively.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS WHO columns providing audit and concurrency tracking.

Common Use Cases and Queries

Typical reporting and support scenarios include auditing which Automatch rules are currently active, verifying tolerance configuration before running AutoCash, and tracing unmatched or mis-matched receipts back to the governing rule. A representative query lists active rules within their effective window:

• SELECT automatch_id, matching_option, auto_match_threshold, sugg_match_threshold, start_date, end_date FROM ar_cash_automatches WHERE active_flag = 'Y' AND SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE + 1);
• Joining to child details/rule mappings to reconstruct a complete rule definition for each AUTOMATCH_ID.
• Reconciling AutoCash behavior by joining AR_CASH_RECOS_ALL on AUTOMATCH_ID to determine which rule produced a given reconciliation outcome.
• Change-audit reporting using the LAST_UPDATED_BY and LAST_UPDATE_DATE columns.

Related Objects

The documented foreign key relationships identify the tables that reference AR_CASH_AUTOMATCHES through the AUTOMATCH_ID column. These are the most significant dependents for query and integration purposes:

• AR_CASH_AUTOMATCH_DTLS — child detail lines; joined via AUTOMATCH_ID.
• AR_CASH_RECOS_ALL — reconciliation records referencing the originating rule; joined via AUTOMATCH_ID.
• AR_CASH_AUTOMATCH_RULE_MAP — mapping table linking rules to their components; joined via AUTOMATCH_ID.

Because the object is classified as standalone with no outgoing foreign keys, it acts as a parent/master table for these dependents rather than as a child of other entities.