Search Results job_title_type




Overview
Explore in AI Chat

Overview

APPS.AST_RELATIONSHIP_DETAILS_V is a supplementary view owned by the APPS schema and registered under FND Design Data as AST.AST_RELATIONSHIP_DETAILS_V. Its documented purpose is to simplify forms coding within Oracle EBS, consolidating party relationship data and its associated contact points into a single denormalized row per party. It is classified explicitly as a supplementary view, meaning Oracle does not recommend querying or altering data through it, and its definition may change dramatically in subsequent minor or major releases. Oracle further designates the object for internal use only: applications data should not be accessed through it except from standard Oracle Applications programs.

Because the view carries status VALID and is not referenced by any other database object, it behaves as a terminal presentation layer rather than a dependency for further database constructs. For the search term "primary_email," the view is relevant because it exposes a PRIMARY_EMAIL column of VARCHAR2(2000), allowing the primary electronic mail address of a party contact to be returned alongside name, role, address, and telephone attributes.

Underlying Base Objects

The view's dependencies comprise AR_LOOKUPS (VIEW) and the synonyms FND_TERRITORIES_TL, HZ_CONTACT_POINTS, HZ_ORG_CONTACTS, HZ_ORG_CONTACT_ROLES, HZ_PARTIES, and HZ_RELATIONSHIPS. These map to the TCA (Trading Community Architecture) registry: HZ_PARTIES supplies the party identity, HZ_RELATIONSHIPS links parties to one another, HZ_ORG_CONTACTS and HZ_ORG_CONTACT_ROLES establish organization contact records and their assigned roles, HZ_CONTACT_POINTS holds the actual phone, email, and address contact point rows, FND_TERRITORIES_TL resolves territory descriptions, and AR_LOOKUPS decodes lookup-coded values such as role or address types. The view therefore joins party, relationship, contact, and contact point data into one flattened result set.

Key Columns

Common Use Cases and Queries

Typical uses include contact-directory reporting, supplier or customer contact extraction, and integration feeds that require a primary email with its associated party, role, and telephone context. Because the view is documented as unsupported for direct access, such queries should be treated as read-only reporting and validated against the ETRM/source definition before production use.

SELECT party_id,
       relationship_name,
       primary_role,
       primary_email
FROM   apps.ast_relationship_details_v
WHERE  primary_email IS NOT NULL;

To retrieve a full contact block for a specific party:

SELECT party_id,
       relationship_name,
       primary_role,
       job_title,
       department,
       primary_address,
       primary_phone_country_code || ' ' ||
       primary_phone_area_code    || ' ' ||
       primary_phone_number       AS phone,
       primary_email
FROM   apps.ast_relationship_details_v
WHERE  party_id = :p_party_id;

Because the view is not referenced by any database object, it can be replaced or redefined by Oracle without downstream database impact, reinforcing the recommendation to rely on it only within standard Applications code paths.