Search Results jmf_gta_trx_lines_all

Overview

The JMF_GTA_TRX_LINES_ALL table is a core transactional data store within the Oracle E-Business Suite Supply Chain Localizations module (JMF). It is specifically designed to capture and manage line-level details for transactions governed by the Global Trade Agreement (GTA) framework. This table plays a critical role in localizations that require detailed tracking and compliance of trade-related financial transactions, such as those involving specific tax or regulatory reporting mandates. Each record in this table represents a single line item associated with a GTA transaction header, enabling granular financial and logistical tracking. Its ALL suffix indicates it is a multi-organization access enabled (MOAC) table, storing data partitioned by operating unit.

Key Information Stored

The table's structure is centered on linking trade agreement lines to their corresponding financial system entries. The primary key is the system-generated identifier, GTA_TRX_LINE_ID. The most significant columns, as indicated by its foreign key relationships, are GTA_TRX_HEADER_ID and AR_TRX_LINE_ID. The GTA_TRX_HEADER_ID column links the line to its parent transaction record in the JMF_GTA_TRX_HEADERS_ALL table, establishing the header-line relationship. The AR_TRX_LINE_ID column is crucial for integration with the Oracle Receivables module, as it provides a direct reference to the specific invoice line in RA_CUSTOMER_TRX_LINES_ALL. This link is essential for reconciling localized trade agreement data with the standard AR invoicing and revenue recognition processes.

Common Use Cases and Queries

This table is primarily accessed for generating compliance reports, auditing trade-related financial data, and troubleshooting integration issues between the GTA localization and Oracle Receivables. A common reporting use case involves joining to the Receivables tables to pull detailed invoice information for all GTA-tracked transactions within a specific period or operating unit. A typical query pattern would be:

• SELECT gtl.gta_trx_line_id, gtl.gta_trx_header_id, rctl.line_number, rctl.extended_amount FROM jmf_gta_trx_lines_all gtl, ra_customer_trx_lines_all rctl WHERE gtl.ar_trx_line_id = rctl.customer_trx_line_id AND gtl.gta_trx_header_id = :p_header_id;

Data validation and reconciliation scripts also frequently query this table to identify GTA lines that lack a corresponding AR line or vice versa, ensuring data integrity across modules.

Related Objects

The table maintains defined foreign key relationships with two primary tables, forming the backbone of its data model:

• JMF_GTA_TRX_HEADERS_ALL: The parent table. Joined via JMF_GTA_TRX_LINES_ALL.GTA_TRX_HEADER_ID = JMF_GTA_TRX_HEADERS_ALL.GTA_TRX_HEADER_ID. This relationship retrieves header-level information for the transaction.
• RA_CUSTOMER_TRX_LINES_ALL: The integrated Receivables table. Joined via JMF_GTA_TRX_LINES_ALL.AR_TRX_LINE_ID = RA_CUSTOMER_TRX_LINES_ALL.CUSTOMER_TRX_LINE_ID. This is the critical link for financial reporting and reconciliation.

As the source for line details, this table is also likely referenced by various localization-specific reports, interfaces, and potentially by public APIs within the JMF module for data extraction and processing.