Results for “ar_app_rule_sets”

50+ results




Overview
Explore in AI Chat

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

Overview

AR_APP_RULE_SETS is a Receivables (AR) module table that stores Application Rule Sets — reusable configuration records that govern how cash receipts are automatically applied to open debit items such as invoices, debit memos, chargebacks, and on-account credits. In Oracle EBS 12.1.1 and 12.2.2, rule sets act as the central definition object referenced by AutoAccounting and AutoCash processing: each rule set groups one or more application rules and is assigned to a receipt class, remittance bank, or customer, driving the order in which Receivables attempts to match receipts to transactions. The table therefore sits at the heart of the receipt application and cash management configuration layer, well upstream of transactional activity.

From a Data Vault modeling perspective, the ETRM metadata classifies this object heuristically as standalone. In practice, this makes AR_APP_RULE_SETS a natural hub candidate keyed on RULE_SET_ID, with descriptive and audit attributes (name, description, flags, and the ATTRIBUTE1–15 flexfield columns) behaving as satellite payload. Because no foreign keys depend on it beyond the inbound reference from AR_RECEIVABLE_APPLICATIONS_ALL, the table is self-contained and does not require link-table decomposition.

Key Information Stored

The table contains 27 documented columns. The most significant are:

  • RULE_SET_ID — the surrogate primary key, enforced by AR_APP_RULE_SETS_PK, uniquely identifying each rule set.
  • RULE_SET_NAME — the user-facing identifier for the rule set, used throughout Receivables setup and assignment screens.
  • DESCRIPTION — free-text explanation of the rule set's purpose or application order.
  • FREEZE_FLAG — indicates whether the rule set is locked against modification, typically once it has been used in live application processing.
  • RULE_SOURCE — identifies the origin or category of the rule set (for example, seeded versus user-defined), which affects maintenance and upgrade behavior.
  • ZD_EDITION_NAME — a multi-tenant / editioning column; combined with RULE_SET_ID it forms the unique business-key candidate AR_APP_RULE_SETS_U1 (RULE_SET_ID, ZD_EDITION_NAME), supporting edition-based redefinition in 12.2.x.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle DFF (descriptive flexfield) columns, available for customer-specific extensions without schema change.
  • Creation/audit set — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide WHO-column audit traceability.

No other unique index is documented except a system-managed LOB/index entry (SYS_IL0000029448C00026$$), reinforcing RULE_SET_ID as the sole true business identifier.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include listing all active rule sets, identifying frozen (in-use) configurations, and tracing which receipts were applied under each rule set.

  • Inventory of rule sets: SELECT rule_set_id, rule_set_name, description, freeze_flag, rule_source FROM ar.ar_app_rule_sets ORDER BY rule_set_name;
  • Find frozen rule sets before a configuration change: SELECT rule_set_name FROM ar.ar_app_rule_sets WHERE freeze_flag = 'Y';
  • Usage audit — join to receipts to see application volume per rule set: SELECT s.rule_set_name, COUNT(*) FROM ar.ar_app_rule_sets s, ar.ar_receivable_applications_all a WHERE s.rule_set_id = a.rule_set_id GROUP BY s.rule_set_name;
  • DFF extraction — query ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 for custom reporting or migration mapping.
  • Audit trail — filter on LAST_UPDATE_DATE and LAST_UPDATED_BY to review recent configuration changes.

Related Objects

  • AR_RECEIVABLE_APPLICATIONS_ALL — holds the transactional applications; its RULE_SET_ID column is the documented foreign key back to AR_APP_RULE_SETS. This is the primary join path for usage analysis.
  • AR_APP_RULE_SET_LINES / application rules — child rule lines that define the individual matching rules within a set (logical parent-child relationship).
  • AR_RECEIPT_CLASSES — receipt classes reference rule sets for automatic application during receipt creation.
  • AR_AUTO_CASH_RULES and AutoCash configuration — consume rule sets to determine cash application order.
  • AR_CUSTOMERS — customer-level payment or AutoCash preferences can point to specific rule sets.
  • AR_RECEIPTS_ALL / AR_CASH_RECEIPTS_ALL — transactional tables whose application behavior is governed by the assigned rule set.