Results for “ar_gta_tax_limits_all”

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

Overview

AR_GTA_TAX_LIMITS_ALL is a Receivables (AR) module table that stores limited control information governing Global Tax Application (GTA) invoice processing. Its documented description—"Limited information for GTA invoice"—indicates that it functions as a constraint or threshold table that defines the boundaries within which GTA invoices may be generated or validated for a given tax registration and organization. In Oracle EBS 12.1.1 and 12.2.2, this table sits within the tax-determination and invoice-generation flow, enforcing ceilings on invoice amounts and line counts before a transaction can be processed under a specific fiscal registration. The table resides in the AR schema and is marked VALID in the ETRM 12.2.2 catalog.

From a data modeling perspective, the heuristic Data Vault classification supplied in the metadata is standalone. This suggests the table is best modeled as its own hub-like or reference entity rather than as a dependent satellite of a parent transaction, since it anchors business keys for tax registration and invoice type independently of any single invoice record.

Key Information Stored

The table contains eleven documented columns. The surrogate primary key is LIMITATION_ID, enforced by the AR_GTA_TAX_LIMITS_PK constraint and reinforced by the unique index AR_GTA_TAX_LIMITS_U1. The business-key candidate is a composite unique index, AR_GTA_TAX_LIMITS_U2, defined across ORG_ID, FP_TAX_REGISTRATION_NUMBER, and INVOICE_TYPE—meaning that at most one limitation row exists per organization, per fiscal tax registration, and per invoice type.

• LIMITATION_ID — surrogate primary key uniquely identifying each limitation record.
• ORG_ID — operating unit that owns the limitation; drives multi-org security and partitioning of tax rules.
• FP_TAX_REGISTRATION_NUMBER — the fiscal registration (taxpayer) number to which the limitation applies.
• INVOICE_TYPE — the invoice classification constrained by the row; this is the column most frequently searched by users.
• MAX_AMOUNT — the maximum monetary threshold permitted for qualifying GTA invoices.
• MAX_NUM_OF_LINE — the maximum number of invoice lines permitted.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns recording creation and modification metadata.

Common Use Cases and Queries

Typical use cases include validating whether an invoice falls within permitted tax thresholds, reporting on configured limitations per registration, and supporting reconciliation between tax setups and actual invoiced amounts. A common query retrieves the limitation applicable to a given operating unit, registration, and invoice type:

• SELECT limitation_id, org_id, fp_tax_registration_number, invoice_type, max_amount, max_num_of_line FROM ar.ar_gta_tax_limits_all WHERE org_id = :p_org_id AND fp_tax_registration_number = :p_reg AND invoice_type = :p_inv_type;
• Reporting queries often join to AR_GTA_TYPE_MAPPINGS to expand invoice-type mappings associated with each limitation.
• Audit queries use the WHO columns to trace configuration changes over time.
• The INVOICE_TYPE column is a frequent filter subject, since analysts commonly search for it to understand which invoice categories carry limits.

Related Objects

The most significant dependent object documented is AR_GTA_TYPE_MAPPINGS, which references this table through the LIMITATION_ID column (AR_GTA_TYPE_MAPPINGS.LIMITATION_ID → AR_GTA_TAX_LIMITS_ALL). This mapping table associates each limitation with related tax-type definitions, making it the primary join target for functional reporting.

• AR_GTA_TYPE_MAPPINGS — joins on LIMITATION_ID; expands invoice-type and tax-type mappings.
• AR_GTA_TAX_LIMITS_PK / AR_GTA_TAX_LIMITS_U1 / AR_GTA_TAX_LIMITS_U2 — supporting constraints and unique indexes.
• Organization and registration reference data (via ORG_ID and FP_TAX_REGISTRATION_NUMBER) — used to resolve operating unit and fiscal registration context.
• Receivables invoice and tax-processing objects that consume these limits during GTA invoice generation.