Search Results ar_gta_system_parameters_all




Overview
Explore in AI Chat

Overview

AR_GTA_SYSTEM_PARAMETERS_ALL is a Receivables (AR) module table that stores the system-level configuration parameters governing Global Tax Application (GTA) processing within Oracle E-Business Suite. GTA refers to the tax determination and calculation framework used by Receivables for tax calculation of transactions, and this table holds the control settings that drive that behavior at the operating unit level. The table is owned by the AR schema and resides in the APPS database tier, exposed through multi-org views. In ETRM 12.2.2 the object is documented as VALID, with 22 physical columns and a single unique business-key index, AR_GTA_SYSTEM_PARAMETERS_U1, defined on ORG_ID.

From a data warehousing and integration perspective, the heuristic Data Vault classification mined from the foreign-key structure is satellite-leaning. This suggests that, when modeled dimensionally or in a Data Vault, the table is best treated as a satellite holding descriptive configuration attributes keyed by an operating-unit business key rather than as a pure hub or link. The physical table is keyed by AR_GTA_SYSTEM_PARAMETERS_PK on ORG_ID, which functions as both the primary key and the unique business key.

Key Information Stored

The table stores one parameter row per operating unit, identified by ORG_ID. The surrogate primary key AR_GTA_SYSTEM_PARAMETERS_PK and the unique index AR_GTA_SYSTEM_PARAMETERS_U1 both resolve to ORG_ID, meaning ORG_ID is simultaneously the physical identifier and the business-key candidate. The most significant attributes include:

Common Use Cases and Queries

The primary use case is resolving configuration for GTA tax calculation at a specific operating unit. A typical query retrieves all parameters for an operating unit:

  • SELECT * FROM ar.ar_gta_system_parameters_all WHERE org_id = :p_org_id;
  • Reporting on batch numbering setup: SELECT org_id, auto_batch_numbering_flag, next_batch_number FROM ar_gta_system_parameters_all;
  • Joining to currencies to validate the GTA currency: SELECT p.org_id, p.gt_currency_code, c.name FROM ar_gta_system_parameters_all p, fnd_currencies c WHERE p.gt_currency_code = c.currency_code;
  • Auditing configuration changes: SELECT org_id, last_update_date, last_updated_by FROM ar_gta_system_parameters_all ORDER BY last_update_date DESC;
  • Extract for upstream tax engines or data warehouses keyed on ORG_ID.

Because the unique index is on ORG_ID, lookups by operating unit are the most efficient access path.

Related Objects

The documented foreign key links GT_CURRENCY_CODE to FND_CURRENCIES. Significant related objects include:

  • FND_CURRENCIES – Joined on AR_GTA_SYSTEM_PARAMETERS_ALL.GT_CURRENCY_CODE = FND_CURRENCIES.CURRENCY_CODE.
  • AR_GTA_SYSTEM_PARAMETERS_ALL (multi-org view / synonyms) – ORG_ID-driven access through MOAC.
  • AR_GTA_* tax and GTA processing tables – Depend on these parameters during tax determination.
  • FND_FLEX_VALUES / FND_DESCR_FLEX_COL_USAGE – Contextual flexfield metadata referenced by the RA_ and INV_ attribute context columns.
  • HR_OPERATING_UNITS – Resolves ORG_ID to an operating-unit name.