Results for “ar_gta_gt_headers_v”

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

Overview

AR_GTA_GT_HEADERS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes header-level information for Global Tax and Accounting (GTA) invoices generated within the Oracle Receivables module. In regions where tax authorities mandate a distinct tax invoice document separate from the standard customer transaction, the GTA framework stores that document's identifying data — invoice number, invoice date, tax registration numbers, and monetary totals — in dedicated GTA tables. This view consolidates those header attributes into a single queryable object and joins them to the corresponding Receivables transaction for cross-reference.

The view supports tax reporting, reconciliation of GTA documents to Receivables transactions, and integration scenarios where downstream systems (data warehouses, tax filing engines, or customer-facing portals) require the invoice date and invoice number of a VAT/GTA invoice. Because the view filters on SOURCE = 'GT', it returns only records that originated as GTA-generated invoices.

Underlying Base Objects

The view is defined over two documented base objects:

• AR_GTA_TRX_HEADERS_ALL (referenced as synonym JGTH) — the primary source of GTA header data, including invoice numbers, invoice dates, amounts, and tax registration numbers.
• RA_CUSTOMER_TRX_ALL (referenced as RCT) — the standard Receivables transaction table, joined via RA_TRX_ID to CUSTOMER_TRX_ID using an outer join.

The outer join on RA_CUSTOMER_TRX_ALL means a GTA header record is returned even when no corresponding Receivables transaction exists, though such rows will show a null RA_TRX_NUM. The filter JGTH.SOURCE = 'GT' restricts output to GTA-sourced headers. The view also carries standard Who columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and concurrent program context columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) inherited from the GTA header table.

Key Columns

• VAT_INVOICE_DATE — the date of the VAT/GTA invoice. This is the column most relevant to users searching on "vat_invoice_date" and is the primary date attribute for tax-period reporting.
• VAT_INVOICE_NUMBER / GTA_INVOICE_NUMBER — the legally significant invoice identifier assigned to the GTA document.
• VAT_NET_AMOUNT / VAT_TAX_AMOUNT — the net and tax components of the invoice.
• TOTAL_VAT_INVOICE_AMOUNT — a derived column computed as GT_INVOICE_NET_AMOUNT + GT_INVOICE_TAX_AMOUNT, providing the gross invoice value.
• FP_TAX_REGISTRATION_NUMBER / TP_TAX_REGISTRATION_NUMBER — the first-party (issuer) and third-party (customer) tax registration numbers required on compliant tax invoices.
• CUSTOMER_NAME, CUSTOMER_ADDRESS_PHONE, BANK_ACCOUNT_NAME_NUMBER — billing and payment details printed on the invoice.
• ORG_ID — the operating unit, enabling multi-org security filtering.
• RA_TRX_ID / RA_TRX_NUM — the link to the underlying Receivables transaction and its transaction number.
• STATUS, DESCRIPTION, INVOICE_TYPE — document state and classification attributes.

Common Use Cases and Queries

A frequent requirement is retrieving VAT invoices issued within a given tax period, ordered by invoice date:

• SELECT vat_invoice_number, vat_invoice_date, customer_name, total_vat_invoice_amount FROM ar_gta_gt_headers_v WHERE vat_invoice_date BETWEEN :start_date AND :end_date AND org_id = :org_id ORDER BY vat_invoice_date;
• SELECT g.vat_invoice_number, g.vat_invoice_date, r.trx_number FROM ar_gta_gt_headers_v g WHERE g.ra_trx_id IS NOT NULL AND g.org_id = :org_id;
• SELECT org_id, COUNT(*), SUM(total_vat_invoice_amount), SUM(vat_tax_amount) FROM ar_gta_gt_headers_v WHERE vat_invoice_date >= :period_start GROUP BY org_id;

Because the view does not expose a single column literally named RA_TRX_NUM in some patches (the underlying select alias is RA_TRX_NUM), consumers should verify column names against the deployed ETRM version before embedding them in production SQL. The view is read-only and intended for query access; no DML should be performed against it.