Results for “xtr_settlement_contacts”

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

Overview

XTR_SETTLEMENT_CONTACTS is a Treasury (XTR) module table in the Oracle E-Business Suite, owned by the XTR schema and valid in both 12.1.1 and 12.2.2. The object was originally created on 28-MAR-96, making it one of the earliest structures in the Treasury settlement foundation. It stores the contact and correspondence details associated with a specific bank account use, allowing treasury users to record the personnel, address, and communication channels that settlement instructions and payment-related correspondence should reference.

The table functions as a child of CE_BANK_ACCT_USES_ALL, joined through the BANK_ACCT_USE_ID foreign key. Because the primary business context (the bank account use) is held in the parent table and this table carries descriptive attributes about contacts tied to that context, the heuristic Data Vault classification is satellite-leaning. In a dimensional or Data Vault model this object is best treated as a satellite attached to a bank-account-use hub or link, rather than as an independent hub or a pure link table.

The documented physical schema contains 16 columns. The table has no documented unique index beyond its relationship to CE_BANK_ACCT_USES_ALL, so BANK_ACCT_USE_ID should be treated as the effective business join key, with contact-level attributes acting as descriptive payload.

Key Information Stored

The most significant columns of XTR_SETTLEMENT_CONTACTS are:

• BANK_ACCT_USE_ID — foreign key to CE_BANK_ACCT_USES_ALL; the principal join column and the anchor of the parent-child relationship.
• CONTACT_NAME — the name of the settlement contact at the bank or counterparty.
• PARTY_CODE — the party identifier associated with the contact record.
• TITLE_DESCRIPTION — the job title or role description of the contact.
• ACCOUNT_NUMBER — the account number to which the contact is linked.
• CURRENCY — the currency context under which the contact applies.
• PHONE_NUMBER, FAX_NUMBER, TELEX_NUMBER, EMAIL_ADDRESS — the communication channels used to reach the settlement contact.
• ADDRESS_1 through ADDRESS_6 — the multi-line postal address of the contact, providing the correspondence address used for settlement-related notifications.

This set of columns supports identification (name, party, title), routing (phone, fax, telex, email), and location (address lines) of the settlement contact, anchored to a specific bank account use.

Common Use Cases and Queries

Typical uses include producing settlement instruction reports, validating that each active bank account use has a reachable contact, and exposing contact details for treasury payment processing. A standard query joins the child to its parent:

• SELECT c.contact_name, c.title_description, c.phone_number, c.email_address FROM xtr_settlement_contacts c, ce_bank_acct_uses_all b WHERE c.bank_acct_use_id = b.bank_acct_use_id;
• Filter by bank account use to retrieve all contacts for a given account: WHERE c.bank_acct_use_id = :p_use_id.
• Audit reporting on missing or obsolete contact information, using ACCOUNT_NUMBER and CURRENCY as grouping attributes.

These patterns are commonly embedded in custom Treasury reports and in interfaces that feed settlement instructions to payment systems.

Related Objects

The principal related object is CE_BANK_ACCT_USES_ALL, joined on BANK_ACCT_USE_ID, which supplies the bank account use context. Additional relevant objects in the settlement and cash management domain include CE_BANK_ACCOUNTS (the underlying bank account), CE_BANKS, and the Treasury settlement instruction tables (XTR_SETTLE_INSTRUCTIONS and its related structures). The parent account-use record itself references cash management and payment setup tables, so reporting on settlement contacts frequently cascades through CE_BANK_ACCT_USES_ALL to reach bank and account master data.