Results for “ar_gta_trx_headers_v”

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

Overview

AR_GTA_TRX_HEADERS_V is an APPS-owned view in the Oracle E-Business Suite Receivables (AR) module that exposes header-level information for Global Tax and Accounting (GTA) invoices. GTA is the mechanism used in Latin American localizations—most notably Brazil—to generate fiscal documents such as Nota Fiscal and related tax reporting records. The view consolidates data spanning invoice header, customer, bank, currency, tax, batch, and Organization Unit information into a single denormalized structure, making it suitable for reporting, integration with external tax engines, and downstream extraction programs. The view carries a status of VALID and is available in both 12.1.1 and 12.2.2 releases. Because it maps directly onto underlying transactional base tables, it provides a stable read-only interface that shields report developers from the complexities of joining the GTA rule and transaction tables.

Underlying Base Objects

The view is defined over several physical objects and one PL/SQL package. The primary driver is AR_GTA_TRX_HEADERS_ALL, which stores the header records for every GTA transaction generated from a Receivables invoice. Supporting joins include:

• AR_GTA_RULE_HEADERS_ALL — provides rule header context and the RULE_NAME value.
• RA_CUSTOMER_TRX_ALL — sourced from Receivables for the transaction number (RA_TRX_NUMBER) and linkage to the source invoice.
• RA_BATCHES_ALL and RA_BATCH_SOURCES_ALL — supply batch names and source information.
• RA_CUST_TRX_TYPES_ALL — supplies the transaction type (RCTT.TYPE) and type name (RCTT.NAME).
• HR_ALL_ORGANIZATION_UNITS and HR_ALL_ORGANIZATION_UNITS_TL — resolve the operating unit / organization name (OTL.NAME).
• AR_GTA_TRX_UTIL — a PL/SQL utility package referenced for derived amount calculations.

The view columns are predominantly direct projections of columns on AR_GTA_TRX_HEADERS_ALL, meaning any DML executed against the base table is immediately visible through the view.

Key Columns

The view exposes a wide set of identifying, financial, and localization-specific columns:

• GTA_TRX_HEADER_ID, GTA_TRX_NUMBER, GROUP_NUMBER, VERSION, LATEST_VERSION_FLAG — uniquely identify the GTA header and its version lineage.
• RA_TRX_ID, RA_TRX_NUMBER — link back to the originating Receivables transaction.
• RA_CURRENCY_CODE, CONVERSION_TYPE, CONVERSION_DATE, CONVERSION_RATE — currency and exchange rate attributes; the searched term ra_currency_code corresponds directly to the RA_CURRENCY_CODE column.
• GT_INVOICE_NUMBER, GT_INVOICE_DATE, GT_INVOICE_NET_AMOUNT, GT_INVOICE_TAX_AMOUNT, GT_INVOICE_TYPE, GT_INVOICE_CLASS — the fiscal invoice identification and monetary values.
• DEFAULT_AMOUNT (computed as GT_INVOICE_NET_AMOUNT + GT_INVOICE_TAX_AMOUNT) — the total invoice amount.
• TAX_CODE, TAX_RATE, GT_TAX_MONTH — tax reporting elements.
• BILL_TO_CUSTOMER_ID, BILL_TO_CUSTOMER_NUMBER, BILL_TO_CUSTOMER_NAME, CUSTOMER_ADDRESS — bill-to party details.
• BANK_ACCOUNT_NAME, BANK_ACCOUNT_NUMBER — payment instrument details.
• STATUS, CANCEL_FLAG, GENERATOR_ID, EXPORT_REQUEST_ID — processing state and audit information.
• Standard audit and descriptive flexfield columns (ATTRIBUTE1 through ATTRIBUTE15, CREATED_BY, LAST_UPDATE_DATE, ORG_ID).

Common Use Cases and Queries

Report developers and integration engineers commonly query this view to reconcile GTA invoices, extract fiscal reporting data, and verify currency and conversion details. A typical query filtering on the currency column follows:

• SELECT gta_trx_number, ra_trx_number, gt_invoice_number, ra_currency_code, conversion_rate, gt_invoice_net_amount, gt_invoice_tax_amount FROM apps.ar_gta_trx_headers_v WHERE ra_currency_code = 'BRL' AND org_id = :p_org_id;
• To retrieve the latest version of each GTA invoice: SELECT * FROM apps.ar_gta_trx_headers_v WHERE latest_version_flag = 'Y';
• To link back to Receivables: SELECT h.gta_trx_number, t.trx_number FROM apps.ar_gta_trx_headers_v h, apps.ra_customer_trx_all t WHERE h.ra_trx_id = t.customer_trx_id;

Because the view is a thin projection over the base GTA table, queries should always restrict on ORG_ID in a multi-org environment to satisfy operating unit security. It is also advisable to filter on CANCEL_FLAG = 'N' when extracting active fiscal documents.