Search Results ra_grouping_trx_types




Overview
Explore in AI Chat

Overview

The RA_GROUPING_TRX_TYPES table is a core data object within Oracle E-Business Suite Receivables (AR) module, specifically for versions 12.1.1 and 12.2.2. It functions as a junction table that defines the association between AutoInvoice grouping rules and the specific transaction types to which those rules apply. Its primary role is to support the AutoInvoice program's grouping logic, which determines how individual transaction lines from external systems are consolidated into invoices and invoice lines within Oracle Receivables. By linking grouping rules to transaction types, this table ensures that the appropriate consolidation criteria are applied based on the nature of the transaction being imported.

Key Information Stored

The table's structure is designed to manage the many-to-many relationship between grouping rules and transaction types. The key columns, as indicated by the provided metadata, include the primary key GROUPING_TRX_TYPE_ID, which uniquely identifies each association record. The critical foreign key column is GROUPING_RULE_ID, which links back to the parent rule defined in the RA_GROUPING_RULES table. While the specific column for the transaction type identifier (e.g., CUST_TRX_TYPE_ID) is not explicitly named in the excerpt, its presence is implied by the table's purpose. This column would store the internal ID of the transaction type (from RA_CUST_TRX_TYPES) that is subject to the linked grouping rule.

Common Use Cases and Queries

The primary use case is the configuration and analysis of AutoInvoice grouping behavior. Administrators query this table to audit which transaction types are governed by specific grouping rules, which is essential for troubleshooting invoice consolidation issues. A common reporting query would join this table to RA_GROUPING_RULES and RA_CUST_TRX_TYPES to produce a human-readable list of rules and their associated transaction types. For example, to identify all transaction types linked to a specific grouping rule named 'REVENUE_STANDARD', one might use a SQL pattern such as:

  • SELECT rgt.grouping_rule_id, rgr.name rule_name, rctt.name trx_type_name
  • FROM ra_grouping_trx_types rgt,
  • ra_grouping_rules rgr,
  • ra_cust_trx_types rctt
  • WHERE rgt.grouping_rule_id = rgr.grouping_rule_id
  • AND rgt.cust_trx_type_id = rctt.cust_trx_type_id
  • AND rgr.name = 'REVENUE_STANDARD';

Related Objects

As documented in the provided metadata, RA_GROUPING_TRX_TYPES has defined relationships with several key Receivables tables. It is a child table to RA_GROUPING_RULES via the foreign key on GROUPING_RULE_ID. This is the primary relationship, defining the parent grouping rule. Conversely, it acts as a parent table to RA_GROUP_BYS, which stores the specific attributes (like customer, bill-to site, or term) used for grouping. The foreign key in RA_GROUP_BYS on GROUPING_TRX_TYPE_ID links back to this table's primary key. While not listed in the excerpt, a foreign key relationship to RA_CUST_TRX_TYPES is a logical and functional necessity to identify the applicable transaction type.