Search Results rule_line_id

Overview

The JMF_GTA_RULE_TRX_TYPES_ALL table is a core data object within the Oracle E-Business Suite (EBS) module JMF - Supply Chain Localizations. Specifically, it functions as a junction or detail table within the framework for managing Global Trade Automation (GTA) rules. Its primary role is to establish the linkage between a defined GTA rule and the specific transaction types to which that rule applies. By storing these associations, the table enables the system to automatically apply the correct trade compliance logic—such as license determination or restricted party screening—to relevant business transactions like sales orders or invoices based on their transaction type classification.

Key Information Stored

The table's structure is designed to maintain the relationship between a rule and applicable transaction types. The primary key, RULE_LINE_ID, uniquely identifies each association record. Two critical foreign key columns form the core of this relationship: RULE_HEADER_ID, which references the parent rule definition in the JMF_GTA_RULE_HEADERS_ALL table, and CUST_TRX_TYPE_ID, which references a specific transaction type defined in the RA_CUST_TRX_TYPES_ALL table (commonly used for invoices, debit memos, etc.). This design allows a single GTA rule to be associated with multiple transaction types, providing flexibility in rule configuration.

Common Use Cases and Queries

A primary use case is validating or reporting on the transaction types governed by a specific GTA rule, which is essential for compliance audits and rule maintenance. System processes query this table to determine if an incoming transaction's type is subject to automated trade checks. Common SQL patterns include joining to the related header and transaction type tables to retrieve descriptive information. For example, to list all rules and their associated transaction types, a query would join JMF_GTA_RULE_TRX_TYPES_ALL to JMF_GTA_RULE_HEADERS_ALL on RULE_HEADER_ID and to RA_CUST_TRX_TYPES_ALL on CUST_TRX_TYPE_ID. Conversely, to find which rule applies to a specific transaction type, a query would filter on the CUST_TRX_TYPE_ID.

Related Objects

This table is centrally connected to two key EBS tables via documented foreign key relationships:

• JMF_GTA_RULE_HEADERS_ALL: This is the parent table containing the master definition of the GTA rule. The relationship is maintained through the column JMF_GTA_RULE_TRX_TYPES_ALL.RULE_HEADER_ID, which references JMF_GTA_RULE_HEADERS_ALL.
• RA_CUST_TRX_TYPES_ALL: This Oracle Receivables table defines all customer transaction types (e.g., Invoice, Debit Memo, Credit Memo). The relationship is maintained through the column JMF_GTA_RULE_TRX_TYPES_ALL.CUST_TRX_TYPE_ID, which references RA_CUST_TRX_TYPES_ALL.

These relationships are critical for ensuring data integrity and for enabling joins that provide complete business context for any GTA rule configuration.