Results for “ar_cash_automatch_rule_map”

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

Overview

AR_CASH_AUTOMATCH_RULE_MAP is a Receivables (AR) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the association between individual AutoMatch rules and the rule sets to which they belong. It functions as the mapping or junction structure enabling a single AutoMatch rule set to be composed of one or more AutoMatch rules, and conversely allowing rules to be organized into sets used during the automatic cash application process. The object is documented as BETA in the ETRM metadata, meaning its use should be validated against the specific patch level and implementation before being relied upon for production reporting.

The table resides in the AR schema with a documented physical column count of 9. The heuristic Data Vault classification mined from its foreign key structure is standalone, which suggests modeling it as an independent hub-like entity rather than a pure link, though its two foreign key relationships to AR_CASH_AUTO_RULE_SETS and AR_CASH_AUTOMATCHES give it a clear associative character typical of a link table in a Data Vault model. Consumers should treat this classification as a modeling suggestion only.

Key Information Stored

The table captures the membership of AutoMatch rules within rule sets, together with audit and ordering information. The most significant columns are:

• AUTOMATCH_RULE_SET_MAP_ID — Surrogate primary key defined by the AR_CASH_AUTOMATCH_RULE_MAP_PK1 constraint. Uniquely identifies each rule-to-set mapping row.
• AUTOMATCH_SET_ID — Foreign key to AR_CASH_AUTO_RULE_SETS. Identifies the rule set to which the rule is attached.
• AUTOMATCH_ID — Foreign key to AR_CASH_AUTOMATCHES. Identifies the individual AutoMatch rule assigned to the set.
• PRIORITY — Determines the sequence or precedence in which member rules are evaluated within a rule set during automatic matching.
• CREATED_BY, CREATION_DATE — Standard WHO audit columns recording the creating user and timestamp.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns tracking the most recent modification user, timestamp, and login session.

Two unique indexes are documented: AR_CASH_AUTOMATCH_RULE_MAP_UK1 (AUTOMATCH_SET_ID, AUTOMATCH_ID) and AR_CASH_AUTO_RULE_MAP_UK1 (AUTOMATCH_ID, AUTOMATCH_SET_ID). These define the business-key candidates that prevent duplicate assignment of the same rule to the same set. The alternate primary key constraints AR_CASH_AUTO_RULE_MAP_PK and AR_CASH_AUTO_RULE_MAP_UK1 reflect the same underlying relationships.

Common Use Cases and Queries

Typical usage revolves around reconciling which rules belong to which set and in what priority order, and around ensuring that no duplicate mappings exist. A representative query lists the composition of a rule set:

• SELECT m.automatch_rule_set_map_id, m.automatch_set_id, m.automatch_id, m.priority FROM ar.ar_cash_automatch_rule_map m WHERE m.automatch_set_id = :set_id ORDER BY m.priority;
• Joining to AR_CASH_AUTOMATCHES to retrieve rule names and to AR_CASH_AUTO_RULE_SETS to retrieve set descriptions for reporting.
• Detecting duplicate or orphaned mappings by grouping on AUTOMATCH_SET_ID and AUTOMATCH_ID, or by outer-joining to the parent tables.
• Auditing rule set changes over a period using CREATION_DATE and LAST_UPDATE_DATE, for example to identify rules added or reassigned during a given month.

These queries support configuration review, migration validation between environments, and troubleshooting when automatic cash application fails to apply receipts as expected.

Related Objects

The documented foreign key relationships and the surrounding Receivables AutoMatch configuration objects are the most relevant dependencies:

• AR_CASH_AUTO_RULE_SETS — Parent table referenced by AUTOMATCH_SET_ID; defines the rule sets that these mappings populate.
• AR_CASH_AUTOMATCHES — Parent table referenced by AUTOMATCH_ID; defines the individual AutoMatch rules assigned to sets.
• AR_CASH_AUTOMATCH_RULE_MAP_PK1 / AR_CASH_AUTOMATCH_RULE_MAP_UK1 / AR_CASH_AUTO_RULE_MAP_PK / AR_CASH_AUTO_RULE_MAP_UK1 — Constraint objects enforcing uniqueness on the mapping.
• AutoMatch configuration and cash application views and concurrent programs within the AR module that consume the composed rule sets.
• Receivables AutoLockbox and cash application processes that evaluate AutoMatch rules during receipt application.

Because the object is flagged as BETA, integrators should confirm its population and behavior in the target environment before building dependent interfaces or reports.