Results for “ra_grouping_rules”

50+ results




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

Overview

RA_GROUPING_RULES is an Oracle Receivables (AR) AutoInvoice configuration table that stores grouping rules used to determine how transaction lines are consolidated into invoices during the AutoInvoice import process. AutoInvoice is the EBS engine that validates, defaults, and imports transaction data from external feeder systems into the AR interface tables, ultimately creating invoices, debit memos, credit memos, and on-account credits. Grouping rules control whether lines that share common attributes (such as the same customer, ship-to site, bill-to site, currency, or transaction type) are grouped onto a single invoice or split across multiple invoices.

The table is owned by the AR schema and resides in the same operational domain as the line ordering rules and transaction type groupings that govern AutoInvoice behavior. In Data Vault modeling terms, the documented foreign key structure suggests a hub-leaning classification: GROUPING_RULE_ID acts as the stable business key around which configuration and profile relationships are organized. This classification should be treated as a heuristic modeling suggestion rather than a declarative fact.

Key Information Stored

RA_GROUPING_RULES contains 28 documented columns. The most operationally significant include:

The combination of a surrogate key and a named business-key candidate means reporting can join on either the internal ID or the human-readable rule name.

Common Use Cases and Queries

Typical scenarios include auditing which grouping rules are currently active, identifying rules assigned to customer profiles or transaction types, and tracing the ordering rule paired with each grouping rule. A representative query retrieves active rules joined to their ordering rule:

  • SELECT g.grouping_rule_id, g.name, g.description, l.name ordering_rule FROM ra_grouping_rules g, ra_line_ordering_rules l WHERE g.ordering_rule_id = l.ordering_rule_id AND SYSDATE BETWEEN g.start_date AND NVL(g.end_date, SYSDATE + 1);
  • Joining to AR_CUSTOMER_PROFILES on GROUPING_RULE_ID to report which grouping rule applies to a given customer profile.
  • Joining to RA_GROUPING_TRX_TYPES on GROUPING_RULE_ID to see which transaction types a rule governs.
  • Querying the DFF columns (ATTRIBUTE1–ATTRIBUTE15) for site-specific configuration reporting.

Reporting use cases center on AutoInvoice governance: confirming that grouping rules are correctly assigned before running the AutoInvoice Master Program, and reconciling grouping behavior against expected invoice consolidation.

Related Objects

The documented foreign key relationships identify the following significant dependencies:

  • RA_LINE_ORDERING_RULES — referenced by RA_GROUPING_RULES.ORDERING_RULE_ID; defines line ordering behavior paired with each grouping rule.
  • AR_CUSTOMER_PROFILES — references RA_GROUPING_RULES.GROUPING_RULE_ID; assigns grouping rules at the customer profile level.
  • AR_CUSTOMER_PROFILE_CLASSES — references RA_GROUPING_RULES.GROUPING_RULE_ID; assigns grouping rules at the profile class level.
  • RA_GROUPING_TRX_TYPES — references RA_GROUPING_RULES.GROUPING_RULE_ID; maps grouping rules to transaction types.

These relationships position RA_GROUPING_RULES as a central configuration hub consulted by AutoInvoice, customer profile setup, and transaction type setup within Oracle Receivables 12.1.1 and 12.2.2.