Results for “address_6”

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

Overview

XTR_SETTLEMENT_CONTACTS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the XTR – Treasury product family. The view exposes settlement contact information captured for treasury counterparties and parties, presenting one row per settlement contact record together with its associated currency, account, and address attributes. In Oracle EBS 12.1.1 and 12.2.2 the object carries a VALID status, confirming that it compiles against the referenced base objects and can be relied upon by concurrent programs, Oracle Reports, BI Publisher data templates, and inbound or outbound interface routines that need counterparty settlement details.

Because the view is a thin projection over a single underlying object rather than a join across multiple tables, it performs an essentially row-for-row pass-through of the source data. Its principal value lies in the stable, descriptively named column list it publishes — particularly the ADDRESS_1 through ADDRESS_6 line items and the communication fields — which allows reporting layers to retrieve formatted settlement contact information without querying the base object directly. This decoupling means the view can be referenced in custom reports and integrations with the assurance that the APPS-owned interface remains consistent across 12.1.1 and 12.2.2 releases.

Underlying Base Objects

The documented referenced base object is XTR_SETTLEMENT_CONTACTS, accessed through a SYNONYM in the APPS schema. The view text confirms the relationship directly: every column in the view is sourced from XTR_SETTLEMENT_CONTACTS with no derivations, expressions, or additional joins. There is no DISTINCT clause, aggregation, or filter predicate in the documented view text, so the view returns exactly the rows present in the base table, subject only to standard security applied elsewhere in the application. Implementers performing impact analysis should therefore treat XTR_SETTLEMENT_CONTACTS as the authoritative data source and recognize that any change to the base table's columns or data model propagates directly to this view and to every dependent report or interface.

Key Columns

The view exposes the following columns, each corresponding to a settlement contact attribute:

• PARTY_CODE – Identifier of the party (counterparty or internal entity) to which the settlement contact belongs; the primary grouping key for reporting.
• CONTACT_NAME – Name of the individual contact at the party.
• CURRENCY – Currency associated with the settlement contact record, used when contacts are maintained per currency.
• ACCOUNT_NUMBER – Settlement bank account number applicable to the contact.
• TITLE_DESCRIPTION – Job title or role description of the contact.
• ADDRESS_1 … ADDRESS_6 – Six free-form address lines. ADDRESS_1 is the first line of the contact's address and is the column most commonly used in queries and printed correspondence.
• PHONE_NUMBER, FAX_NUMBER, EMAIL_ADDRESS, TELEX_NUMBER – Communication details for the contact, including the legacy TELEX_NUMBER field retained for backward compatibility.

Common Use Cases and Queries

Typical scenarios include settlement instruction reports, counterparty contact listings, mail-merge or notification extracts, and integration feeds that pass payment or confirmation details to external systems. Address output frequently begins at ADDRESS_1, so filtering or ordering on that column is common. The following queries illustrate standard usage:

• SELECT party_code, contact_name, address_1, currency FROM xtr_settlement_contacts_v ORDER BY party_code, contact_name;
• SELECT * FROM xtr_settlement_contacts_v WHERE currency = 'USD';
• SELECT contact_name, address_1, address_2, phone_number, email_address FROM xtr_settlement_contacts_v WHERE party_code = :party_code;

Because no WHERE clause is embedded in the view, these queries return all qualifying rows in the base object; applications must apply party, currency, or organizational filters explicitly. All access should be granted through the APPS schema or a custom synonym to preserve supportability.