Search Results as_fund_contacts_pk




Overview
Explore in AI Chat

Overview

The AS_FUND_CONTACTS table resides in the OSM schema and belongs to the AS – Sales Foundation product family within Oracle E-Business Suite (validated under 12.1.1 and 12.2.2). It stores the association between funds and the parties who serve as contacts for those funds. In practice, this table functions as an intersection entity that links a fund record to a party record, carrying a role qualifier and the standard Oracle EBS who-columns and descriptive flexfield attributes.

The ETRM metadata applies a heuristic Data Vault classification of standalone. Interpreted as a modeling suggestion, this indicates the table is best treated as a link-style relationship object rather than a hub or a satellite: it does not own the business identity of either the fund or the party, but instead records the fact that a contact relationship exists. The relationship is anchored by a composite primary key over PARTY_ID and FUND_ID, with a secondary unique index reversing the column order.

Key Information Stored

The documented schema contains 26 columns. The columns that carry the substantive business meaning are:

  • PARTY_ID – identifies the contact party (person or organization) associated with the fund; part of the composite primary key.
  • FUND_ID – identifies the fund to which the contact is attached; the other half of the primary key.
  • CONTACT_ROLE_CODE – the lookup code describing the contact's function on the fund (for example, a fund manager, administrator, or trustee role).
  • SECURITY_GROUP_ID – the multi-org/security grouping used to partition visibility of the row; a foreign key to FND_SECURITY_GROUPS.
  • OBJECT_VERSION_NUMBER – the optimistic locking column used by the OAF/BC4J framework to detect concurrent updates.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – the standard Oracle EBS audit (who-column) set.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 – the descriptive flexfield (DFF) segment set for customer-specific extension.

Regarding keys: the surrogate-style composite primary key is defined by the constraint AS_FUND_CONTACTS_PK over (PARTY_ID, FUND_ID). The business-key candidate is expressed by the unique index AS_FUND_CONTACTS_U1 over (FUND_ID, PARTY_ID), confirming that a given party may appear only once per fund. CONTACT_ROLE_CODE is not part of either unique definition, so a party's role is a descriptive attribute rather than a key discriminator.

Common Use Cases and Queries

The table is typically queried when resolving which parties are associated with a fund, or when building contact rosters for fund-related reporting. A basic join pattern returning all contacts for a given fund is:

  • SELECT fc.party_id, fc.contact_role_code FROM as_fund_contacts fc WHERE fc.fund_id = :p_fund_id;
  • Joining to AS_FUNDS and the party tables (via PARTY_ID) to produce a fund-to-contact directory with names and addresses.
  • Filtering on CONTACT_ROLE_CODE to isolate a specific role, such as the primary fund administrator.
  • Security-filtered extracts constrained by SECURITY_GROUP_ID for multi-org or restricted reporting.
  • Audit queries using LAST_UPDATE_DATE and LAST_UPDATED_BY to detect recent contact maintenance.

Because ATTRIBUTE_CATEGORY and the fifteen attribute columns are present, reporting may also surface flexfield values that clients populate for fund-specific contact metadata.

Related Objects

Based on the documented foreign key and key structure, the most significant related objects are:

  • FND_SECURITY_GROUPS – referenced through AS_FUND_CONTACTS.SECURITY_GROUP_ID; governs row-level security partitioning.
  • AS_FUNDS – the fund master; joined on FUND_ID to resolve the fund context for each contact.
  • HZ_PARTIES – the trading community party registry; joined on PARTY_ID to obtain the contact's name and classification.
  • HZ_PERSON_PROFILES / HZ_ORGANIZATION_PROFILES – supply person- or organization-level detail for the linked party.
  • FND_LOOKUP_VALUES – resolves CONTACT_ROLE_CODE to its displayed meaning.
  • AS_FUND_CONTACTS_PK / AS_FUND_CONTACTS_U1 – the constraints enforcing identity and uniqueness on the table.

These relationships make AS_FUND_CONTACTS a small but central link object for fund contact management within the AS Sales Foundation schema.