Results for “ra_grouping_trx_types”

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

Overview

RA_GROUPING_TRX_TYPES is an Oracle Receivables (AR) transaction table that stores the transaction types associated with AutoInvoice grouping rules. Within the Oracle E-Business Suite 12.1.1 and 12.2.2 data model, it functions as a configuration and reference table that binds specific transaction types to grouping rules used during AutoInvoice import processing. AutoInvoice uses grouping rules to determine how interface lines are consolidated into transactions; RA_GROUPING_TRX_TYPES defines which transaction types these rules apply to, allowing grouping behavior to be scoped by transaction type.

The table resides in the AR schema and its metadata classifies it as VALID and actively used by the Receivables module. Based on the mined foreign key structure, the heuristic Data Vault classification for this object is satellite-leaning. In Data Vault modeling terms, this suggests the table behaves as a descriptive satellite attached to a parent hub or link represented by its foreign key relationships, rather than as an independent hub of business entities.

Key Information Stored

The table contains 25 documented columns. The most significant columns and their roles are:

• GROUPING_TRX_TYPE_ID — The surrogate primary key, uniquely identifying each grouping-rule-to-transaction-type association. It is the column used in RA_GROUPING_TRX_TYPES_PK.
• GROUPING_RULE_ID — Foreign key to RA_GROUPING_RULES, identifying the grouping rule to which the transaction type is attached.
• CLASS — Holds the transaction type classification used to scope grouping behavior.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — The standard Oracle EBS descriptive flexfield (DFF) context and segment columns, enabling customer-specific extensibility without schema changes.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard "Who" audit columns tracking record creation and modification.
• ZD_EDITION_NAME — The editioning column supporting Oracle EBS 12.2 online patching and edition-based redefinition.

The documented unique index RA_GROUPING_TRX_TYPES_U1 spans (GROUPING_TRX_TYPE_ID, ZD_EDITION_NAME), which reflects the edition-aware business key required for 12.2.2 operation. A second unique index, RA_GROUPING_TRX_TYPES_UK1, is documented over GROUPING_TRX_TYPE_ID.

Common Use Cases and Queries

Typical scenarios involve validating and reporting on AutoInvoice grouping configuration. Administrators and developers query this table to confirm which transaction types a given grouping rule governs, or to identify all rules assigned to a particular transaction type. Representative query patterns include:

• Joining RA_GROUPING_TRX_TYPES to RA_GROUPING_RULES on GROUPING_RULE_ID to list rule names alongside their associated transaction types.
• Filtering by CLASS to review configuration for a specific transaction class.
• Querying DFF attribute columns when customer-specific grouping logic has been configured.
• Auditing records using LAST_UPDATE_DATE and LAST_UPDATED_BY to identify recent configuration changes.

A basic join illustrates the relationship: SELECT gr.NAME, gtt.CLASS FROM RA_GROUPING_RULES gr, RA_GROUPING_TRX_TYPES gtt WHERE gtt.GROUPING_RULE_ID = gr.GROUPING_RULE_ID;

Related Objects

The following objects are most significant in relation to RA_GROUPING_TRX_TYPES, based on documented foreign key relationships:

• RA_GROUPING_RULES — Parent table referenced by GROUPING_RULE_ID; defines the grouping rules themselves.
• RA_GROUP_BYS — Child table referencing GROUPING_TRX_TYPE_ID via its GROUPING_TRX_TYPE_ID column; defines the grouping columns applied under each transaction type.
• RA_INTERFACE_LINES_ALL — AutoInvoice interface lines processed using these grouping rules.
• RA_CUSTOMER_TRX_ALL — Destination table for transactions created by AutoInvoice using the grouping configuration.
• RA_BATCH_SOURCES_ALL — Batch sources that reference grouping rules during AutoInvoice submission.

Understanding these relationships supports accurate tracing from grouping configuration through to the generated Receivables transactions.