Results for “title_description”

50+ results




Overview
Explore in AI Chat

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

Overview

XTR_DEAL_CONTACTS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, belonging to the XTR (Treasury) product family. Its status is VALID in both Oracle EBS 12.1.1 and 12.2.2. The view exposes contact information associated with treasury deals, presenting a denormalized, read-oriented projection of deal-party contact records. Rather than requiring report developers, integration teams, and business users to resolve deal context through multiple joins, the view surfaces party identifiers, deal classification attributes, and communication channel details in a single flattened result set. This makes it particularly suitable for operational reporting, contact-directory extracts, and outbound integration payloads where a recipient's fax number, phone number, email address, or telex number must be resolved against a specific treasury deal.

Underlying Base Objects

According to the documented ETRM metadata, XTR_DEAL_CONTACTS_V is defined over a single base object: the synonym XTR_DEAL_CONTACTS. The view text is a direct projection with no joins, aggregations, filters, or calculated columns:

Because the view is a straight pass-through, its data integrity and record population are entirely governed by the underlying XTR_DEAL_CONTACTS object. Any insert, update, or delete performed against the base table is immediately reflected in the view. No WHERE clause or security predicate is applied at the view layer, so the view returns all rows present in the base object. Consumers requiring filtering by deal, party, or currency must apply those predicates explicitly in their queries.

Key Columns

The view exposes eleven columns, each carrying a specific business meaning:

  • PARTY_CODE — Identifier for the party (counterparty, contact organization, or internal entity) associated with the contact record.
  • CONTACT_NAME — The name of the individual contact.
  • CURRENCY — Currency context under which the deal and its contact are recorded.
  • DEAL_TYPE — High-level treasury deal classification.
  • DEAL_SUBTYPE — Further refinement of the deal type.
  • PRODUCT_TYPE — Treasury product category associated with the deal.
  • TITLE_DESCRIPTION — Job title or salutation description for the contact.
  • PHONE_NUMBER — Voice telephone number.
  • FAX_NUMBER — Facsimile number, the column most commonly targeted when users search for "fax_number" in this view.
  • EMAIL_ADDRESS — Electronic mail address for the contact.
  • TELEX_NUMBER — Telex identifier, retained for legacy financial messaging scenarios.

Common Use Cases and Queries

The view is typically used for contact lookups, confirmation delivery, and reporting extracts. A common requirement is retrieving fax numbers for deal confirmations:

  • SELECT party_code, contact_name, fax_number FROM xtr_deal_contacts_v WHERE fax_number IS NOT NULL;
  • SELECT contact_name, phone_number, fax_number, email_address FROM xtr_deal_contacts_v WHERE deal_type = :p_deal_type AND currency = :p_currency;
  • SELECT party_code, contact_name, title_description, fax_number FROM xtr_deal_contacts_v WHERE party_code = :p_party_code ORDER BY contact_name;

Typical applications include generating counterparty contact directories, populating confirmation and advice templates, feeding downstream notification systems, and producing audit extracts for treasury operations. Because the view performs no filtering, reports should always include appropriate WHERE predicates on deal_type, party_code, currency, or the communication columns to avoid returning the full contact population.