Search Results ar_autocash_rules




Overview
Explore in AI Chat

Overview

The AR_AUTOCASH_RULES table is a core configuration table within the Oracle E-Business Suite Receivables (AR) module. It defines the specific application methods that constitute an AutoCash Rule Set. An AutoCash Rule Set is a business rule engine that automates the application of customer payments (cash) to outstanding debit items (invoices, debit memos) according to a pre-defined hierarchy and logic. This table stores the individual, sequenced steps within a rule set, enabling automated, consistent, and efficient cash application, which is a critical accounts receivable operation.

Key Information Stored

The table's structure centers on linking a rule to its parent rule set and defining its execution order and logic. The primary identifier is AUTOCASH_RULE_ID. The most critical columns for functional configuration are AUTOCASH_HIERARCHY_ID, which foreign-key links to the parent rule set defined in AR_AUTOCASH_HIERARCHIES, and RULE_SEQUENCE, which dictates the order in which the application method is executed within the set. The combination of these two columns forms a unique key (AR_AUTOCASH_RULES_UK1). Other essential columns specify the application method itself, such as the matching priority (e.g., by invoice number, transaction number, due date, amount), aging periods, and whether to apply to specific transaction types like invoices, debit memos, or chargebacks.

Common Use Cases and Queries

The primary use case is the review and maintenance of AutoCash Rule Sets to optimize the automatic cash application process. Administrators may query this table to audit or document existing rules. A common reporting query lists all rules within a specific hierarchy in execution sequence:

  • SELECT rule_sequence, application_method, aging_period FROM ar_autocash_rules WHERE autocash_hierarchy_id = <ID> ORDER BY rule_sequence;

Another frequent scenario involves troubleshooting cash application results. Analysts might join this table with application history tables to understand which rule was responsible for applying a specific payment. During implementations or upgrades, SQL scripts may reference this table to migrate or validate custom rule sets between environments.

Related Objects

The most direct relationship, as defined by the foreign key, is with the AR_AUTOCASH_HIERARCHIES table, which stores the header definition of the rule set (name, description, active date range). The rules defined in AR_AUTOCASH_RULES are executed by the core AutoCash program and its underlying PL/SQL logic. The operational results of these rules are reflected in application data stored in tables such as AR_RECEIVABLE_APPLICATIONS and AR_PAYMENT_SCHEDULES. Key views like AR_AUTOCASH_RULES_V may provide a more accessible layer for reporting on this configuration data.