Search Results qrm_deals_analyses

Overview

The XTR_PARTY_INFO table is a core master data table within the Oracle E-Business Suite Treasury (XTR) module. It serves as the primary repository for legal entities or "parties" that are defined and managed for treasury operations. These parties typically represent the treasury's own companies (legal entities within the corporate group) as well as external counterparties such as banks, brokers, and other financial institutions with which the treasury transacts. Its creation from the entity XTR_PARTY indicates its foundational role in modeling the participants in the treasury ecosystem. The table's integrity is enforced by the primary key XTR_PARTY_INFO_PK on PARTY_CODE, making this identifier unique for every entity recorded.

Key Information Stored

While the provided metadata does not list specific column details beyond key relationships, the table's structure can be inferred from its foreign key constraints and its central role. The primary identifier is the PARTY_CODE. The table stores critical categorization and default parameters for each party, as evidenced by its foreign key relationships to several category tables. These include a BROKERAGE_CATEGORY (linking to XTR_BROKERAGE_CATEGORIES), a TAX_CATEGORY (linking to XTR_TAX_CATEGORIES), a SETTLEMENT_DEFAULT_CATEGORY (linking to XTR_SETTLEMENT_CATEGORIES), and a CONVERSION_TYPE (linking to GL_DAILY_CONVERSION_TYPES). This design allows for standardized configuration and rule application across all treasury transactions associated with a given party.

Common Use Cases and Queries

This table is essential for any process requiring party identification, validation, or parameter retrieval. Common use cases include the setup and maintenance of treasury legal entities, the enrichment of deal and transaction data with party-specific attributes, and regulatory or internal reporting that segments data by company or counterparty. A fundamental query retrieves a party's details using its unique code, often joining to the related category tables for descriptive information. For reporting, a typical pattern involves joining XTR_PARTY_INFO to transactional tables like XTR_DEALS using PARTY_CODE to analyze exposure or activity by entity.

• Sample Query: SELECT p.party_code, p.name, b.name brokerage_category, t.name tax_category FROM xtr_party_info p, xtr_brokerage_categories b, xtr_tax_categories t WHERE p.brokerage_category = b.brokerage_category(+) AND p.tax_category = t.tax_category(+);

Related Objects

The XTR_PARTY_INFO table has extensive relationships throughout the Treasury schema, underscoring its centrality. It is referenced as a foreign key by numerous other tables. As a COMPANY_CODE, it links to configuration and transactional tables such as XTR_COMPANY_PARAMETERS, XTR_BATCHES, XTR_HEDGE_ATTRIBUTES, and XTR_GAIN_LOSS_DNM. As a general PARTY_CODE, it links to objects like XTR_BANK_ACCOUNTS and XTR_COMPANY_AUTHORITIES. Furthermore, it maintains referential integrity with master category tables for brokerage, tax, settlement, and GL conversion types. Its relationship with the QRM_DEALS_ANALYSES table also indicates integration with the Oracle Risk Management module for advanced deal analytics.