Search Results xtr_parties_v




Overview
Explore in AI Chat

Overview

XTR_PARTIES_V is a Treasury (XTR) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the general information of Treasury parties—counterparties, clients, brokers, and internal companies—while enforcing user access to company information through the Treasury dealer authority model. Unlike a simple denormalized listing of XTR_PARTY_INFO, the view deliberately filters results so that a user querying it only sees company-type parties for which an explicit input authorization exists in XTR_COMPANY_AUTHORITIES for that user's dealer code. Non-company party types (counterparties, brokers, clients) are passed through without that restriction. In practice this makes XTR_PARTIES_V a secured, reporting-friendly projection of party master data, suitable for use by concurrent programs, Oracle Reports, BI Publisher data models, OAF pages, and custom integrations that must respect Treasury security rules.

Because the view resolves the dealer code through the XTR_USER_ACCESS package at runtime, its result set is inherently session-dependent; two users with different Treasury responsibilities will receive different rows for the same query.

Underlying Base Objects

The view is defined over four documented objects:

  • XTR_PARTY_INFO (synonym to the APPS base table) — the primary source of all party attributes, aliased as XPI.
  • XTR_COMPANY_AUTHORITIES — supplies the authorization rows that restrict company-type parties to those the current dealer may input.
  • XTR_PRO_PARAM — a profile/parameter table joined on PARAM_NAME = 'SYSTEM_FUNCTIONAL_CCY' to retrieve the system functional currency.
  • GL_SETS_OF_BOOKS — an outer-joined source of the ledger currency code, matched on SET_OF_BOOKS_ID.
  • XTR_USER_ACCESS — a package (not a table) whose DEALER_CODE function is invoked in the WHERE clause to determine the current user's dealer identity.

The joins are non-enforcing except for the outer join to GL_SETS_OF_BOOKS, so a party will still be returned even when no set of books is linked.

Key Columns

Common Use Cases and Queries

Typical uses include Treasury party validation lists, counterparty exposure lookups, broker and client selection LOVs, and reconciliation reports that must honor dealer-level company authorization. A basic listing follows:

  • SELECT party_code, full_name, party_type, currency_code FROM apps.xtr_parties_v WHERE authorised = 'Y' ORDER BY full_name;
  • SELECT party_code, short_name, risk_party FROM apps.xtr_parties_v WHERE party_type = 'C' AND risk_party = 'Y';
  • SELECT party_code, swift_id, tax_category, settlement_default_category FROM apps.xtr_parties_v WHERE broker = 'Y';

Because authorization is resolved from the session, reports run as a generic application user may return the full set of company parties, whereas interactive queries reflect the logged-in dealer. When integrating externally, verify that the connected user has a valid Treasury dealer code; otherwise the company branch of the predicate evaluates to no rows while non-company parties remain visible.