Results for “xtr_a_party_info”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

XTR_A_PARTY_INFO is the master party information table within the Oracle Treasury (XTR) module of Oracle E-Business Suite. It stores the complete profile of every counterparty, broker, client, and internal party with which the treasury organization transacts. Created on 06-MAY-93 and owned by the XTR schema, the table carries 68 documented columns and remains VALID in release 12.1.1 and 12.2.2. Every treasury instrument — foreign exchange deals, money market placements, and confirmation processing — references a party record held in this table, making it one of the foundational reference-data objects in the Treasury subledger.

From a data-vault modeling perspective, the heuristic classification for this object is standalone. Because the referenced tables (FV_LEGAL_ENTITIES and GL_MGT_SEG_UPGRADE_H) are dependencies rather than identifying parents, the table is best treated as an independent hub of party identity with embedded descriptive attributes, rather than as a pure satellite attached to a larger hub. Analysts designing downstream warehouses should therefore model it as a party hub plus an associated descriptive satellite keyed on the party identifier.

Key Information Stored

Party identity and classification data dominate the table. The most significant columns include:

• PARTY_CODE and FULL_NAME/SHORT_NAME — the principal business-key candidates and the display names used throughout treasury screens.
• PARTY_TYPE, PARTY_CATEGORY, PARTY_GROUP, and CLIENT_GROUPING — control how the party is classified for deal entry, reporting, and counterparty limits.
• LEGAL_ENTITY_ID — foreign key to FV_LEGAL_ENTITIES, linking the party to the owning legal entity.
• SET_OF_BOOKS_ID and CHART_OF_ACCOUNTS_ID — accounting context; CHART_OF_ACCOUNTS_ID references GL_MGT_SEG_UPGRADE_H. SUSPENSE_CCID defines the clearing account used when settlement details are incomplete.
• ADDRESS_1 through ADDRESS_6, CONTACT_NAME, PHONE_NUMBER, FAX_NUMBER, EMAIL_ADDRESS, and SWIFT_ID — communication and settlement routing data.
• Relationship flag columns — CLIENT_YN, BROKER, RISK_PARTY, MM_CPARTY, FX_CPARTY, FX_CPARTY, and INTERNAL_PTY — determine the roles the party may assume in money market and FX transactions.
• AUTHORISED, ACCOUNT_STATUS, and ACCOUNT_MANAGER — approval and servicing metadata.
• Audit columns CREATED_BY, CREATED_ON, UPDATED_BY, and UPDATED_ON.

A dedicated surrogate primary key column is not exposed in the documented metadata; the party code acts as the practical unique business key, and joins to dependent deal tables are customarily performed on the party identifier.

Common Use Cases and Queries

Typical reporting includes counterparty exposure summaries, active-party listings, and role-based extracts. A representative query filtering active FX counterparties follows:

• SELECT party_code, full_name, party_type, party_category FROM xtr_a_party_info WHERE fx_cparty = 'Y' AND authorised = 'Y' ORDER BY full_name;
• Joining to the legal entity for ownership reporting: SELECT p.party_code, p.full_name, le.legal_entity_name FROM xtr_a_party_info p, fv_legal_entities le WHERE p.legal_entity_id = le.legal_entity_id;
• Identifying settlement gaps: SELECT party_code, full_name, suspense_ccid FROM xtr_a_party_info WHERE suspense_ccid IS NULL;
• Audit and reconciliation extracts driven by the UPDATED_ON timestamp for incremental loads.

Integration and data-conversion projects also use the table as the target for legacy party migration, with validation scripts checking SWIFT_ID uniqueness and required address fields.

Related Objects

• FV_LEGAL_ENTITIES — referenced via LEGAL_ENTITY_ID; identifies the legal entity owning the party.
• GL_MGT_SEG_UPGRADE_H — referenced via CHART_OF_ACCOUNTS_ID for accounting flexfield context.
• GL_CODE_COMBINATIONS — implied parent of SUSPENSE_CCID for the suspense account.
• Treasury deal tables (FX and MM) that consume PARTY_CODE as the counterparty reference.
• Treasury confirmation and settlement tables that inherit the communication and SWIFT attributes stored here.
• The XTR party maintenance API and concurrent programs that create and update rows in this table.