Search Results authorization_limit

Overview

GL_AUTHORIZATION_LIMITS_V is a General Ledger (GL) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the journal authorization limits configured for individual employees, resolving the surrogate identifiers held in the underlying authorization limits table into human-readable ledger and employee names. The view joins authorization limit records to the ledger definition and to the current employee record, so that consumers receive a denormalized result set combining the limit amount, its ledger context, and the person to whom the limit applies.

Its primary role is to support inquiry, reporting, and integration scenarios where the numeric ledger and employee identifiers alone would be insufficient. Because OBJECT_NAME is GL_AUTHORIZATION_LIMITS_V and OBJECT_TYPE is VIEW with STATUS VALID, it is a read-only reporting construct rather than a transactional entity; no DML should be issued against it.

Underlying Base Objects

The view is defined over three referenced objects: the synonym GL_AUTHORIZATION_LIMITS, which supplies the limit rows and the descriptive flexfield columns; the view GL_HR_EMPLOYEES_CURRENT_V, which supplies the current employee name; and the synonym GL_LEDGERS, which supplies the ledger name and currency code. Three HR packages — HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY — are also referenced, reflecting the name-formatting and security logic applied through the employee view.

The join conditions are equality on AL.EMPLOYEE_ID = HE.EMPLOYEE_ID and on LED.LEDGER_ID = AL.LEDGER_ID. Consequently, a limit row appears in the result set only when both a matching current employee record and a matching ledger definition exist. The view is therefore a projection and enrichment of GL_AUTHORIZATION_LIMITS, not an independent repository of data.

Key Columns

• ROW_ID — the ROWID of the underlying GL_AUTHORIZATION_LIMITS row, useful for uniquely identifying a limit record.
• LEDGER_ID / LEDGER_NAME / LEDGER_CURRENCY — the ledger identifier, its descriptive name, and the ledger currency code; the currency qualifies the monetary authorization limit.
• EMPLOYEE_ID / EMPLOYEE_NAME — the employee identifier and the resolved employee name obtained through the HR name and security logic.
• AUTHORIZATION_LIMIT — the monetary threshold an employee may approve or post within the associated ledger.
• CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — the descriptive flexfield segments and their context, enabling site-specific extensions.
• LAST_UPDATE_LOGIN, LAST_UPDATED_BY, LAST_UPDATE_DATE, CREATION_DATE, CREATED_BY — standard WHO audit columns describing the last modification and the original creation of the record.

Common Use Cases and Queries

Typical usage includes reviewing which employees hold authorization limits in a given ledger, determining the limit applicable to a specific employee, and extracting limits for audit or reconciliation against the base table. Because the view already joins ledger and employee information, it reduces the need for additional lookups in integration extracts.

To list all limits for a ledger, filtering on the ledger name:

• SELECT employee_id, employee_name, authorization_limit, ledger_currency FROM apps.gl_authorization_limits_v WHERE ledger_id = :p_ledger_id ORDER BY employee_name;

To retrieve the limit for one employee:

• SELECT ledger_name, ledger_currency, authorization_limit FROM apps.gl_authorization_limits_v WHERE employee_id = :p_employee_id;

To report limits by currency across ledgers:

• SELECT ledger_currency, ledger_name, employee_name, authorization_limit FROM apps.gl_authorization_limits_v ORDER BY ledger_currency, ledger_name, employee_name;

Queries should always prefix the view with the APPS schema. Note that employee visibility may be restricted by the security rules applied through the referenced HR objects, so results can vary by the responsibility or security profile under which the query is executed.