Search Results ar_approval_user_limits




Overview
Explore in AI Chat

Overview

AR_APPROVAL_USER_LIMITS is an Oracle Receivables (AR) transactional configuration table that stores the adjustment approval limits assigned to individual users. Each row defines the monetary range within which a specific user is authorized to approve manual adjustments, optionally scoped by document type, currency, and adjustment reason code. The table is owned by the AR schema and is classified as VALID in both Oracle EBS 12.1.1 and 12.2.2. Its role is central to the Receivables adjustment approval workflow: the AutoAccounting and approval engine consults these rows to determine whether a given approver may authorize an adjustment without escalation.

From a dimensional modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification. The table does not act as an independent hub; instead, it extends FND_USER with descriptive approval-limit attributes keyed by USER_ID, making it a natural satellite of the user hub, with additional business qualifiers (document type, currency, reason code) that behave like link dimensions. This classification is offered heuristically based on the FK topology and should be validated against actual reporting requirements before being adopted as a formal Data Vault design.

Key Information Stored

The table is defined with 28 documented columns. The most significant are:

  • USER_ID — The surrogate primary key component and foreign key to FND_USER, identifying the approver to whom the limit applies.
  • AMOUNT_FROM and AMOUNT_TO — The lower and upper bounds of the approval range. Together they define the monetary band a user may approve.
  • CURRENCY_CODE — The currency in which the limit is denominated, allowing per-currency thresholds.
  • DOCUMENT_TYPE — Restricts the limit to a specific adjustment document type.
  • REASON_CODE — Narrows the limit to a particular adjustment reason.
  • PRIMARY_FLAG — Indicates whether the row is the primary/most relevant limit for the user.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns tracking who created and last modified each limit record.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The standard EBS Flexfield-style descriptive columns available for customer extensions.

The primary key is AR_APPROVAL_USER_LIMITS_PK on USER_ID. The documented unique index AR_APPROVAL_USER_LIMITS_U1 spans (USER_ID, DOCUMENT_TYPE, CURRENCY_CODE, REASON_CODE) and represents the business-key candidate: a user should hold only one limit row per document type, currency, and reason combination.

Common Use Cases and Queries

Typical scenarios include determining whether a user may approve an adjustment of a given amount, auditing configured approval thresholds, and reporting on approval authority by currency or reason. A representative query to retrieve a user's limits is:

  • SELECT user_id, document_type, currency_code, reason_code, amount_from, amount_to, primary_flag FROM ar.ar_approval_user_limits WHERE user_id = :p_user_id;
  • Joining to FND_USER to resolve the approver name: SELECT u.user_name, l.amount_to FROM ar.ar_approval_user_limits l, fnd_user u WHERE l.user_id = u.user_id;
  • Checking which adjustments were approved beyond or within a user's band by joining AR_ADJUSTMENTS_ALL.APPROVED_BY back to this table's USER_ID.

Related Objects

The most significant related objects, per documented foreign keys, are:

  • FND_USER — Referenced by AR_APPROVAL_USER_LIMITS.USER_ID; supplies the approver identity.
  • AR_ADJUSTMENTS_ALL — Its APPROVED_BY column references this table, linking approved adjustments to the limits that governed them.
  • AR_APPROVAL_USER_LIMITS_PK — The primary key constraint enforcing unique USER_ID.
  • AR_APPROVAL_USER_LIMITS_U1 — The unique business-key index (USER_ID, DOCUMENT_TYPE, CURRENCY_CODE, REASON_CODE).