Search Results as_fund_contacts_v




Overview
Explore in AI Chat

Overview

The view APPS.AS_FUND_CONTACTS_V belongs to the Oracle Sales Foundation (AS) product family and is documented with the description "View to show fund contact details." It presents a consolidated, reporting-oriented projection that joins fund master data with the contact parties associated with each fund. In Oracle EBS 12.1.1 and 12.2.2, this view is defined as a VALID object in the APPS schema and is intended for inquiry, reporting, and integration scenarios where fund-level and contact-level attributes must be retrieved together without requiring the caller to reconstruct the underlying joins.

Because the view resolves the translated fund name from the language-enabled table using the session language, it returns descriptive fund data in the user's active language. This makes it suitable for both operational reporting and interface extraction where human-readable fund names are required alongside key identifiers.

Underlying Base Objects

The view is defined over four documented base objects, each referenced through a synonym in the APPS schema:

  • AS_FUNDS_B — the fund base table, supplying the fund identifier, strategy, target capital, management assets, and issue-related identifiers.
  • AS_FUNDS_TL — the translated fund table, supplying the language-sensitive FUND_NAME.
  • AS_FUND_CONTACTS — the fund contact association table, supplying contact role, party linkage, and audit columns.
  • HZ_PARTIES — the Trading Community Architecture (TCA) party table, supplying contact party name and party type.

The join predicates are explicit: HZ.PARTY_ID = FCNT.PARTY_ID, FB.FUND_ID = FTL.FUND_ID, FB.FUND_ID = FCNT.FUND_ID, and the language restriction FTL.LANGUAGE = USERENV('LANG'). This guarantees one row per contact per fund, resolved in the session language.

Key Columns

Common Use Cases and Queries

The view is commonly used to list all contacts for a given fund, to locate funds by name, and to feed downstream interfaces requiring fund-to-contact mappings. A typical query by fund name is:

  • SELECT fund_id, fund_name, contact_party_name, contact_role_code FROM apps.as_fund_contacts_v WHERE fund_name = :p_fund_name;
  • SELECT fund_id, strategy, target_cap, contact_party_name FROM apps.as_fund_contacts_v WHERE fund_id = :p_fund_id;
  • SELECT fund_name, contact_party_name, contact_party_type FROM apps.as_fund_contacts_v WHERE contact_party_id = :p_party_id;

Because the view encapsulates the language join, queries automatically return fund names in the session language, and callers need not reference AS_FUNDS_TL directly.