Search Results xtr_user_access




Overview
Explore in AI Chat

Overview

XTR_USER_ACCESS is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM metadata as an "OTHER" API type. It is a supporting utility package within the Treasury (XTR) product family that governs user-level access to dealer and counterparty records. Its central role is to resolve and enforce the authorization logic that determines which dealer codes a given application user is permitted to view or transact upon.

Although the package exposes only one documented program unit, its influence is disproportionately broad. The ETRM dependency metadata records that XTR_USER_ACCESS is referenced by 119 other database objects, comprising almost entirely the secured views of the Treasury, Receivables, Payables, and Cash Management modules. Because Oracle EBS implements row-level security in these products through secured views rather than through direct grants, XTR_USER_ACCESS functions as a low-level access-control dependency rather than a user-facing API. In EBS 12.1.1 and 12.2.2 the package status is VALID, confirming that it compiles cleanly against the 11g or 12c database tier underlying each release.

Key Procedures and Functions

  • DEALER_CODE — The single documented program unit in the package. It encapsulates the logic for determining the dealer code context applicable to the current session or to a supplied user, and is the mechanism by which the secured views obtain the dealer-scope filter applied to their underlying queries. Detailed parameter signatures are not enumerated in the ETRM excerpt and should be confirmed by inspecting the package specification in the target instance.

Tables Accessed

  • XTR_DEALER_CODES (accessed through the APPS synonym) — The dealer master reference table. XTR_USER_ACCESS reads this table to resolve the set of dealer codes available for access validation, matching them against the user's assigned security profile. This is the only documented table dependency; no writes to application data tables are recorded in the metadata.

Usage Notes

XTR_USER_ACCESS is not normally invoked directly by end users. It is called indirectly from the WHERE clauses of secured views, which is why the dependency list is dominated by objects such as AR_AEL_GL_CB_REC_V, CE_BANK_ACCOUNTS_V, CE_FC_XTR_DISC_V, IBY_PAYMENTS_SEC_V, and related reconciliation and cash-management views spanning the AR, CE, IBY, and XLA schemas. The user's original search term, ar_ael_gl_cb_rec_v, is one of these dependent views; it inherits dealer-level row filtering from this package.

Because the package sits beneath so many secured views, any change to it carries a wide blast radius across the AR, CE, IBY, AP, and XLA reporting surfaces in both 12.1.1 and 12.2.2. The 12.2 upgrade retains the same object identity and dependencies, so remediation or patching activity that touches XTR_USER_ACCESS must be regression-tested against the full set of dependent views. When diagnosing "no rows returned" or missing-transaction symptoms in Treasury or Receivables secured views, verifying the dealer-code assignments queried through this package is an appropriate first step.