Search Results ar_gta_rule_trx_types_pk

Overview

The AR_GTA_RULE_TRX_TYPES_ALL table is a core data object within Oracle E-Business Suite (EBS) Receivables (AR) module, specifically for versions 12.1.1 and 12.2.2. It serves as a junction table that defines the association between Global Transfer Accounting (GTA) rules and specific transaction types. Its primary role is to store the transactional scope for a given GTA rule, ensuring that automated accounting entries are generated correctly for designated customer transactions. This table is fundamental for the GTA functionality, which automates the transfer of receivable balances between different legal entities or balancing segments based on pre-defined business logic.

Key Information Stored

The table stores the linkage between a GTA rule header and the transaction types to which it applies. Key columns include RULE_LINE_ID, which serves as the primary unique identifier for each record. The RULE_HEADER_ID is a foreign key that links to the AR_GTA_RULE_HEADERS_ALL table, identifying the parent rule. The CUST_TRX_TYPE_ID is a critical foreign key that links to the RA_CUST_TRX_TYPES_ALL table, specifying the exact transaction type (e.g., Invoice, Debit Memo, Credit Memo) governed by the rule. The table supports multi-organization architecture, as indicated by the "_ALL" suffix, meaning it stores data for all operating units accessible to a responsibility.

Common Use Cases and Queries

This table is central to configuring and auditing GTA setups. A common use case is verifying which transaction types are assigned to a specific GTA rule for troubleshooting or compliance purposes. System administrators and functional consultants frequently query this table to validate setup integrity before migration or during period-end close. A typical diagnostic query would join to related setup tables:

• Identifying all rules for a transaction type: SELECT rule_header_id, cust_trx_type_id FROM ar_gta_rule_trx_types_all WHERE cust_trx_type_id = <TYPE_ID>;
• Listing all transaction types for a rule: SELECT rtt.cust_trx_type_id, rctt.name FROM ar_gta_rule_trx_types_all rtt, ra_cust_trx_types_all rctt WHERE rtt.cust_trx_type_id = rctt.cust_trx_type_id AND rtt.rule_header_id = <HEADER_ID>;

Reporting use cases often involve generating a master list of all GTA rule assignments across the enterprise.

Related Objects

AR_GTA_RULE_TRX_TYPES_ALL has defined relationships with several key Receivables tables, as per the provided metadata. It is a child table of AR_GTA_RULE_HEADERS_ALL via the RULE_HEADER_ID foreign key, which stores the rule's master definition and parameters. It references RA_CUST_TRX_TYPES_ALL via the CUST_TRX_TYPE_ID foreign key to obtain the valid transaction type codes and names. The table is protected by two primary key constraints: AR_GTA_RULE_TRX_TYPES_PK (on RULE_LINE_ID) and AR_GTA_RULE_TRX_TYPES_U2 (on the combination of RULE_HEADER_ID and CUST_TRX_TYPE_ID), ensuring data integrity by preventing duplicate rule-to-transaction-type assignments.