Search Results ar_cmgt_auto_rules




Overview
Explore in AI Chat

Overview

AR_CMGT_AUTO_RULES is a Receivables (AR) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the configuration rules governing whether a credit review and the resulting credit decision can be completed automatically, without user intervention. The table belongs to the Credit Management (CMGT) feature set, which automates customer credit scoring, credit review, and credit limit assignment using score models defined elsewhere in the AR schema. Each row represents a rule set that an organization defines to determine the conditions under which the credit engine can proceed autonomously rather than routing the case to a credit analyst for manual disposition.

From a data-modeling perspective, the metadata classifies this object heuristically as a standalone structure within a Data Vault framework. This classification is a modeling suggestion rather than an enforced constraint; in practice the table functions as a reference or configuration entity that anchors child detail rows and points to a score model. Its grain is one row per automatic rule definition, identified by the surrogate primary key AUTO_RULES_ID.

Key Information Stored

The table contains 10 documented columns. The most significant are summarized below.

  • AUTO_RULES_ID — The surrogate primary key, enforced by constraint AR_CMGT_AUTO_RULES_PK and backed by unique index AR_CMGT_AUTO_RULES_U1. This column uniquely identifies each automatic rule record and is the column referenced by dependent child tables.
  • SCORE_MODEL_ID — A foreign key to AR_CMGT_SCORES. It links each auto-rule to the credit score model used to evaluate the customer, thereby binding the automation logic to a specific scoring definition.
  • START_DATE and END_DATE — The effective date range during which the rule is active. These columns support date-effective rule selection, allowing multiple rule versions to coexist over time.
  • SUBMIT_FLAG — A control flag indicating whether the rule participates in automated submission of the credit review/decision process without user intervention.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide the standard WHO-column audit trail for row-level lineage and change tracking.

The surrogate key AUTO_RULES_ID should be distinguished from business-key candidates; the documented unique index AR_CMGT_AUTO_RULES_U1 covers AUTO_RULES_ID itself, confirming it as the sole documented uniqueness constraint.

Common Use Cases and Queries

Typical scenarios include identifying which score models drive fully automated credit decisions, auditing active versus expired rules, and reporting on rule coverage across the credit portfolio. A representative query joining the auto-rule to its score model is:

  • SELECT a.AUTO_RULES_ID, a.SCORE_MODEL_ID, a.START_DATE, a.END_DATE, a.SUBMIT_FLAG FROM AR.AR_CMGT_AUTO_RULES a WHERE TRUNC(SYSDATE) BETWEEN a.START_DATE AND NVL(a.END_DATE, TRUNC(SYSDATE)); — retrieves currently effective automatic rules.
  • Joining to AR_CMGT_SCORES on SCORE_MODEL_ID to resolve which score model each rule references.
  • Joining to AR_CMGT_AUTO_RULE_DTLS on AUTO_RULES_ID to enumerate the detailed conditions attached to each rule.
  • Auditing recent configuration changes using LAST_UPDATE_DATE and LAST_UPDATED_BY.

Related Objects

The following objects are most significant to AR_CMGT_AUTO_RULES, based on the documented foreign-key relationships:

  • AR_CMGT_SCORES — Referenced by AR_CMGT_AUTO_RULES.SCORE_MODEL_ID; supplies the scoring model used by each rule.
  • AR_CMGT_AUTO_RULE_DTLS — References AR_CMGT_AUTO_RULES.AUTO_RULES_ID; stores the detailed rule lines and conditions belonging to each parent rule.
  • AR_CMGT_AUTO_RULES_PK / AR_CMGT_AUTO_RULES_U1 — The primary-key constraint and unique index enforcing AUTO_RULES_ID uniqueness.
  • Other Credit Management configuration tables within the AR schema, such as credit profile and score definition objects, which participate in the same automated credit decision workflow.

Together these objects form the configuration backbone of the Credit Management automation engine in Oracle Receivables.