Search Results gl_tax_options




Overview
Explore in AI Chat

Overview

GL_TAX_OPTIONS is a General Ledger setup table owned by the GL schema in Oracle E-Business Suite. It stores the tax configuration options that govern how tax is calculated, rounded, and applied for a given ledger and operating unit combination. Because taxation rules differ by legal entity, jurisdiction, and currency, Oracle EBS externalizes these settings into a dedicated setup table rather than hard-coding them. Each row in GL_TAX_OPTIONS represents the effective tax preferences for one ledger within one operating unit, making the table a foundational reference during journal entry validation, tax calculation, and downstream reporting.

In Oracle EBS 12.1.1 and 12.2.2, GL_TAX_OPTIONS sits behind the Tax Options setup screen in the General Ledger responsibility. Its configuration determines whether amounts entered in journals are treated as tax-inclusive or tax-exclusive, which default tax codes apply to input and output transactions, and how monetary amounts are rounded. Applying a Data Vault modeling heuristic to the documented foreign key structure, the table is best classified as a link: it connects a ledger to a tax currency and carries the descriptive attributes that qualify that relationship. It does not operate as a standalone hub, because its identity depends on the ledger and operating unit it joins.

Key Information Stored

The physical schema documents 34 columns. The most operationally significant are the following.

The surrogate primary key is GL_TAX_OPTIONS_PK, defined on (LEDGER_ID, ORG_ID). The unique index GL_TAX_OPTIONS_U1 covers the same two columns and serves as the business-key candidate, confirming that at most one tax options record may exist per ledger and operating unit.

Common Use Cases and Queries

The most frequent requirement is retrieving the tax configuration for a specific ledger and operating unit so that rounding and default tax codes can be applied consistently.

SELECT ledger_id, org_id, tax_currency_code, tax_precision,
       input_rounding_rule_code, output_rounding_rule_code
FROM   gl.gl_tax_options
WHERE  ledger_id = :ledger_id
AND    org_id    = :org_id;

Auditors and implementers frequently inventory all configured tax options across ledgers to confirm currency alignment:

SELECT t.ledger_id, t.org_id, t.tax_currency_code
FROM   gl.gl_tax_options t
ORDER  BY t.ledger_id, t.org_id;

Reporting queries typically join GL_TAX_OPTIONS to GL_SETS_OF_BOOKS_11I to resolve the ledger name and to FND_CURRENCIES to obtain currency descriptions. Setup validation scripts also check that TAX_PRECISION and TAX_MAU are consistent with the precision of the assigned TAX_CURRENCY_CODE.

Related Objects

The table participates in a small but stable set of relationships, and the following objects are the most significant for both querying and integration.

  • GL_SETS_OF_BOOKS_11I — Joined on GL_TAX_OPTIONS.LEDGER_ID = GL_SETS_OF_BOOKS_11I.LEDGER_ID. Provides ledger name, chart of accounts, and functional currency context.
  • FND_CURRENCIES — Joined on GL_TAX_OPTIONS.TAX_CURRENCY_CODE = FND_CURRENCIES.CURRENCY_CODE. Supplies currency name and precision attributes used to validate TAX_PRECISION and TAX_MAU.
  • GL_TAX_OPTIONS_PK / GL_TAX_OPTIONS_U1 — The primary key constraint and unique index that enforce one row per ledger and operating unit.
  • HR_OPERATING_UNITS — Resolves ORG_ID to an operating unit name in multi-organization reporting.
  • GL_JE_HEADERS and GL_JE_LINES — Journal entry facts that consume the tax codes and rounding rules defined here during entry validation.
  • GL_TAX_CODES — Holds the tax code definitions referenced by INPUT_TAX_CODE and OUTPUT_TAX_CODE.

Because GL_TAX_OPTIONS controls rounding and default tax behavior, any change to its rows should be managed through the standard Tax Options setup form rather than by direct DML, ensuring that dependent journal entry processes receive consistent configuration.