Results for “ar_cash_auto_rule_sets”

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

Overview

The AR_CASH_AUTO_RULE_SETS table in the Oracle Receivables (AR) schema stores the definition of Automatch Rule Sets used by the AutoCash and automatic receipt matching engine. An Automatch Rule Set is a named configuration container that groups one or more matching rules (orderings, transaction types, date ranges, and tolerance criteria) applied against open receivable transactions when cash is received and automatically applied. The table is labelled BETA in the ETRM documentation, indicating that Oracle has positioned it as an evolving configuration object rather than a fully hardened transactional table.

The object is owned by the AR schema and is present as a valid table in both Oracle EBS 12.1.1 and 12.2.2. From a data-modelling perspective, the heuristic Data Vault classification mined from the foreign-key structure is standalone. This should be read as a modelling suggestion: although AR_CASH_AUTO_RULE_SETS is referenced by many dependent tables, it does not itself carry outbound foreign keys to other master data, so it behaves like a reference or hub-style object rather than a link or satellite.

Key Information Stored

The documented physical schema for 12.2.2 contains 10 columns. The most operationally significant are:

• AUTOMATCH_SET_ID — the surrogate primary key. Two primary key definitions are documented (AR_CASH_RULE_SETS_ALL_PK1 and AR_CASH_RULE_SETS_PK1), both keyed on AUTOMATCH_SET_ID. This value is the join key propagated to every dependent table that consumes an automatch rule set.
• START_DATE and END_DATE — the effective date window during which the rule set is valid. These bound rule evaluation and allow date-versioned rule sets to coexist.
• ACTIVE_FLAG — indicates whether the rule set is enabled for use.
• EXCEPTION_REASON — stores the reason code or descriptive text recorded when a rule set produces an unmatched or exception outcome.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS WHO columns providing audit lineage for the configuration record.

No business-key unique index is documented; AUTOMATCH_SET_ID is the sole primary key candidate and the de facto business identifier for downstream consumers.

Common Use Cases and Queries

The table is queried primarily to resolve which rule set is assigned to a receipt, a lockbox, a customer profile, or a system default. A representative resolution query joins the dependent table back to this table by AUTOMATCH_SET_ID:

• Identifying the active rule set for a lockbox: SELECT r.AUTOMATCH_SET_ID, r.START_DATE, r.END_DATE, r.ACTIVE_FLAG FROM AR_CASH_AUTO_RULE_SETS r, AR_LOCKBOXES_ALL l WHERE l.AUTOMATCH_SET_ID = r.AUTOMATCH_SET_ID.
• Reporting the system-level default rule set via AR_SYSTEM_PARAMETERS_ALL.
• Auditing configuration change history using CREATION_DATE, LAST_UPDATE_DATE, and the WHO user columns.
• Validating date-window coverage to ensure a receipt or lockbox date falls between START_DATE and END_DATE for the assigned set.

Related Objects

The following objects reference AR_CASH_AUTO_RULE_SETS through the AUTOMATCH_SET_ID column and are the most significant dependencies:

• AR_CASH_AUTOMATCH_RULE_MAP — maps individual automatch rules to a rule set; the most direct child of this table.
• AR_CASH_REMIT_REFS_ALL and AR_CASH_REMIT_REFS_INTERIM — link remittance references and interim remittance data to a rule set.
• AR_INTERIM_CASH_RECEIPTS_ALL and AR_CASH_RECEIPTS_ALL — carry the rule set applied to a receipt.
• AR_LOCKBOXES_ALL — assigns the default rule set for a lockbox.
• AR_SYSTEM_PARAMETERS_ALL — holds the system-level default rule set.
• HZ_CUSTOMER_PROFILES, HZ_CUSTOMER_PROFILES_M, and HZ_CUST_PROFILE_CLASSES — provide customer-level and profile-class-level rule set defaults.