Results for “xtr_party_info”

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

Overview

XTR_PARTY_INFO is a Treasury (XTR) module table in the Oracle E-Business Suite, owned by the XTR schema. It was created from entity XTR PARTY by Oracle on 06-MAY-93 and is documented as VALID in ETRM 12.2.2. The table stores the master record for a Treasury party (also referred to as a "company" or counterparty in Treasury terminology), holding identity, classification, address, contact, settlement, tax, brokerage, and default accounting attributes. It functions as the central reference for counterparties, brokers, banks, and internal entities used across Treasury deal capture, hedging, cash pooling, and interest tolerance processing.

Based on the documented foreign-key pattern — the table is referenced by many downstream tables (bank accounts, batches, cashpool attributes, company authorities, parameters, hedge attributes, gain/loss DNM, and interest tolerances) while it references only a small set of lookup objects — the heuristic Data Vault classification is hub-leaning. In Data Vault modeling terms, XTR_PARTY_INFO most closely resembles a hub, with PARTY_CODE serving as the business key and numerous satellites in the surrounding XTR schema holding descriptive and transactional detail. This classification should be treated as a modeling suggestion only.

Key Information Stored

The table contains 69 documented columns in ETRM 12.2.2. The primary key is XTR_PARTY_INFO_PK, defined on the column PARTY_CODE. A unique index, XTR_PARTY_INFO_U1, is also defined on PARTY_CODE, making PARTY_CODE both the surrogate primary key and the business-key candidate in the documented schema. The most significant columns include:

• PARTY_CODE — Primary key and business key; the unique identifier for each Treasury party.
• FULL_NAME — The party's full legal or trading name, used in reports and deal confirmations.
• SHORT_NAME — Abbreviated name used in screens and reconciliations.
• PARTY_TYPE and PARTY_CATEGORY — Classifiers distinguishing client, broker, bank, or internal entity roles.
• PARTY_GROUP and CLIENT_GROUPING — Grouping attributes for portfolio and reporting rollups.
• CLIENT_YN, BROKER, ADVISOR_YN, VALUER_YN, INTERNAL_PTY, RISK_PARTY — Boolean-style flags indicating functional roles assigned to the party.
• ADDRESS_1 through ADDRESS_6, CONTACT_NAME, PHONE_NUMBER, FAX_NUMBER, EMAIL_ADDRESS, SWIFT_ID, COUNTRY_CODE, STATE_CODE — Contact and communication details.
• SETTLEMENT_DEFAULT_CATEGORY, CONVERSION_TYPE, TAX_CATEGORY, BROKERAGE_CATEGORY — Defaults referenced by foreign keys to XTR_SETTLEMENT_CATEGORIES, GL_DAILY_CONVERSION_TYPES, XTR_TAX_CATEGORIES, and XTR_BROKERAGE_CATEGORIES.
• LEGAL_ENTITY_ID — Foreign key to FV_LEGAL_ENTITIES linking the Treasury party to its legal entity.
• CHART_OF_ACCOUNTS_ID and SET_OF_BOOKS_ID — Accounting context for the party.
• AUTHORISED, ACCOUNT_STATUS, AUDIT_INDICATOR — Control and status flags governing usage.
• CREATED_BY, CREATED_ON, UPDATED_BY, UPDATED_ON — Standard audit columns.

The remaining columns cover complementary details such as account manager, cross-references, default address details, tax number, and counterparty flags for FX, MM, and EM instruments.

Common Use Cases and Queries

The table is queried whenever Treasury users need to identify, validate, or report on a counterparty. Typical scenarios include retrieving a party's address and contact details for confirmations, joining to bank accounts to determine remittance instructions, and checking role flags to filter the deal-processing parties. A representative query is:

• Lookup by business key: SELECT PARTY_CODE, FULL_NAME, PARTY_TYPE, PARTY_CATEGORY FROM XTR_PARTY_INFO WHERE PARTY_CODE = :p_party_code;
• Settlement defaults: SELECT p.PARTY_CODE, p.FULL_NAME, s.DESCRIPTION FROM XTR_PARTY_INFO p JOIN XTR_SETTLEMENT_CATEGORIES s ON p.SETTLEMENT_DEFAULT_CATEGORY = s.SETTLEMENT_CATEGORY;
• Counterparty roles: SELECT PARTY_CODE, FULL_NAME, CLIENT_YN, BROKER, RISK_PARTY FROM XTR_PARTY_INFO WHERE CLIENT_YN = 'Y' ORDER BY FULL_NAME;
• Bank account relationships: SELECT b.BANK_ACCOUNT_NAME, p.FULL_NAME FROM XTR_BANK_ACCOUNTS b JOIN XTR_PARTY_INFO p ON b.PARTY_CODE = p.PARTY_CODE;
• Legal-entity reconciliation: SELECT p.PARTY_CODE, p.FULL_NAME, l.NAME FROM XTR_PARTY_INFO p JOIN FV_LEGAL_ENTITIES l ON p.LEGAL_ENTITY_ID = l.LEGAL_ENTITY_ID;
• Hedging exposure: SELECT h.COMPANY_CODE, p.FULL_NAME FROM XTR_HEDGE_ATTRIBUTES h JOIN XTR_PARTY_INFO p ON h.COMPANY_CODE = p.PARTY_CODE;

These patterns support operational screens, settlement validation, and management reporting on counterparty exposure and Treasury deal activity.

Related Objects

XTR_PARTY_INFO is referenced by numerous XTR and QRM objects through foreign keys on COMPANY_CODE or PARTY_CODE, and it references several lookup tables. The most significant related objects are:

• XTR_BANK_ACCOUNTS — joins on XTR_BANK_ACCOUNTS.PARTY_CODE = XTR_PARTY_INFO.PARTY_CODE.
• XTR_BATCHES — joins on XTR_BATCHES.COMPANY_CODE = XTR_PARTY_INFO.PARTY_CODE.
• XTR_CASHPOOL_ATTRIBUTES — joins on PARTY_CODE.
• XTR_COMPANY_AUTHORITIES — joins on PARTY_CODE.
• XTR_COMPANY_PARAMETERS — joins on COMPANY_CODE.
• XTR_HEDGE_ATTRIBUTES and XTR_HEDGE_RETRO_TESTS — join on COMPANY_CODE.
• XTR_INTEREST_TOLERANCES — joins on both COMPANY_CODE and CPARTY_CODE.
• QRM_DEALS_ANALYSES — joins on COMPANY_CODE.
• GL_DAILY_CONVERSION_TYPES — referenced via CONVERSION_TYPE.
• XTR_SETTLEMENT_CATEGORIES, XTR_TAX_CATEGORIES, XTR_BROKERAGE_CATEGORIES — default category lookups.
• FV_LEGAL_ENTITIES — referenced via LEGAL_ENTITY_ID.

Collectively, these relationships establish XTR_PARTY_INFO as a central reference hub for Treasury party and counterparty processing.