Results for “ar_gta_type_mappings”

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

Overview

AR_GTA_TYPE_MAPPINGS is a Receivables (AR) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 whose documented purpose is to hold the mapping between transaction types and the combination of a Tax Registration Number and an Invoice Type. The prefix "GTA" associates the object with the Global Tax/Government Tax Authority reporting functionality used in jurisdictions that require transaction-level tax reporting, where the legal reporting category (Invoice Type) and the taxpayer registration affected by the transaction must be resolved from the receivables transaction type.

The table is stored in the AR schema and its status is documented as VALID. The ETRM metadata assigns it a heuristic Data Vault classification of "standalone," meaning no FK relationships to other hubs are mined from the constraint structure apart from the single documented reference below. In Data Vault modeling terms this suggests the object behaves most like a reference or link-style mapping table rather than a transactional hub or a slowly changing satellite; the classification is a modeling suggestion only and does not affect the physical definition.

Key Information Stored

The documented physical schema exposes eight columns. The most significant are:

• MAPPING_ID — surrogate primary key of the table, enforced by AR_GTA_TYPE_MAPPINGS_PK. It is also the single business-key candidate carried by unique index AR_GTA_TYPE_MAPPINGS_U1, so the key alone is sufficient to identify a mapping row.
• LIMITATION_ID — the only documented foreign key column. It references AR_GTA_TAX_LIMITS_ALL, tying the transaction type mapping to a specific tax limitation record.
• TRANSACTION_TYPE_ID — identifies the Receivables transaction type to which the tax registration number and invoice type mapping applies. This is the operative business attribute of the row.
• LAST_UPDATE_DATE and CREATION_DATE — standard EBS audit timestamps recording when the row was last changed and first inserted.
• LAST_UPDATED_BY and CREATED_BY — the application user identifiers associated with the last modification and the original creation.
• LAST_UPDATE_LOGIN — the login context under which the last update occurred, used for audit tracing.

No descriptive (non-key) foreign key columns beyond LIMITATION_ID are documented in this release, and the Data Vault classification confirms the table is standalone at the constraint level.

Common Use Cases and Queries

The table is primarily consumed during tax reporting and invoice generation, where the application must determine which reporting category and registration number apply to a receivables transaction. Typical queries join the mapping to the tax limits table and to the transaction type reference:

• Resolving the reporting mapping for a given transaction type: SELECT t.* FROM ar_gta_type_mappings t WHERE t.transaction_type_id = :transaction_type_id;
• Joining to the limitation definition: SELECT t.mapping_id, t.transaction_type_id, l.* FROM ar_gta_type_mappings t, ar_gta_tax_limits_all l WHERE t.limitation_id = l.limitation_id;
• Auditing changes by user or date: filter on LAST_UPDATED_BY or LAST_UPDATE_DATE to identify recently maintained mappings.
• Reporting setup completeness: list transaction types that have no mapping row, using an outer join against the transaction type reference table, to detect configuration gaps before filing.

Because the row count is typically small, these queries are cheap, but they are executed per transaction or per reporting run and should be indexed on TRANSACTION_TYPE_ID and LIMITATION_ID.

Related Objects

• AR_GTA_TAX_LIMITS_ALL — referenced through LIMITATION_ID. This is the only documented FK relationship and is the primary dependency for this table.
• AR_GTA_TYPE_MAPPINGS_PK and AR_GTA_TYPE_MAPPINGS_U1 — the primary key and unique index that enforce MAPPING_ID uniqueness.
• AR_GTA_TAX_LIMITS_ALL — again relevant as the parent, since its LIMITATION_ID key is the join column.
• RA_CUST_TRX_TYPES_ALL — the standard Receivables transaction type definition referenced conceptually via TRANSACTION_TYPE_ID.
• ZX/AR tax reporting APIs — the tax reporting and invoice generation programs that read the mapping at runtime.

As a standalone reference object, AR_GTA_TYPE_MAPPINGS depends on the tax limits table and on the transaction type definition rather than on any child tables of its own.