Search Results gl_authorization_limits




Overview
Explore in AI Chat

Overview

GL_AUTHORIZATION_LIMITS is a General Ledger (GL) application table that stores journal approval authorization limits for employees within Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the GL schema and is classified as VALID in the ETRM repository. The table defines the maximum journal amount that a given employee is permitted to approve for a specific ledger, thereby supporting the Journal Approval workflow and the enforcement of approval hierarchies during journal entry and posting cycles.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure is that of a link. GL_AUTHORIZATION_LIMITS resolves the many-to-many relationship between ledgers and employees by carrying the foreign keys LEDGER_ID and EMPLOYEE_ID, which makes it a natural candidate for a link entity in a dimensional or Data Vault design. Each row therefore represents the association of one authorization limit value with a particular employee-ledger pair.

Key Information Stored

The table contains 24 documented columns, though only a subset is significant for functional and reporting purposes. The most important columns are:

  • LEDGER_ID — Identifies the ledger (set of books) to which the limit applies. Part of the primary key.
  • EMPLOYEE_ID — Identifies the employee granted the approval authorization. Part of the primary key.
  • AUTHORIZATION_LIMIT — The monetary threshold up to which the employee may approve journals for the specified ledger.
  • SET_OF_BOOKS_ID — Legacy reference to GL_SETS_OF_BOOKS, retained for backward compatibility with earlier releases.
  • CREATION_DATE, CREATED_BY — Standard WHO columns capturing when and by whom the record was created.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns recording the most recent modification and session information.
  • CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — The DFF (Descriptive Flexfield) columns used to extend the record with client-specific attributes.

The surrogate primary key is GL_AUTHORIZATION_LIMITS_PK, defined on (LEDGER_ID, EMPLOYEE_ID). The unique index GL_AUTHORIZATION_LIMITS_U1 mirrors the same column pair (LEDGER_ID, EMPLOYEE_ID), confirming that the combination of ledger and employee is the natural business key. Foreign keys are documented from LEDGER_ID to GL_SETS_OF_BOOKS_11I and from SET_OF_BOOKS_ID to GL_SETS_OF_BOOKS.

Common Use Cases and Queries

The primary practical application of this table is determining whether a given approver is authorized to approve a journal of a particular amount for a specified ledger. Approvers with limits below the journal amount are routed out of the approval chain, while those exceeding the threshold are eligible. Typical reporting scenarios include auditing approval authority, identifying approvers with unusually high limits, and reconciling limits against HR records.

A representative query to retrieve all limits for a specific ledger follows:

  • SELECT employee_id, authorization_limit FROM gl_authorization_limits WHERE ledger_id = :ledger_id ORDER BY authorization_limit DESC;

A join against the ledger table to enrich the output is also common:

  • SELECT gal.employee_id, gal.authorization_limit, gsob.name AS ledger_name FROM gl_authorization_limits gal JOIN gl_sets_of_books gsob ON gal.set_of_books_id = gsob.set_of_books_id;

Reconciliation queries comparing approval limits to actual approved journals frequently use this table as the starting point when generating "approval authority" audit reports.

Related Objects

The following objects are the most significant in relation to GL_AUTHORIZATION_LIMITS:

  • GL_SETS_OF_BOOKS — Referenced through SET_OF_BOOKS_ID; provides ledger name and currency context.
  • GL_SETS_OF_BOOKS_11I — Referenced through LEDGER_ID; the 11i-compatible view of the ledger definition.
  • GL_JE_HEADERS — Journal entries whose approval routing depends on the limits defined here.
  • GL_JE_BATCHES — Journal batches subject to approval authorization checks.
  • PER_ALL_PEOPLE_F — Employee master record joined via EMPLOYEE_ID to resolve approver names.
  • GL_JE_SOURCES — Journal sources that can be configured to require approval and hence consume these limits.
  • FND_USER — Application user records linked to employees for workflow notification purposes.

Together these objects form the approval authority framework that governs journal approval in Oracle General Ledger.