Results for “person_title”

50+ results




Overview
Explore in AI Chat

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

Overview

ASF_CNT_PERSON_LOV_V is a validated view owned by the APPS schema in Oracle E-Business Suite (available in both 12.1.1 and 12.2.2). It belongs to the ASF - Sales Online product family, historically associated with Oracle Sales and TeleSales contact management functionality. The view is purpose-built to serve as a List of Values (LOV) source for person contacts and their relationships. It presents a denormalized, joined result set combining person party records, relationship definitions, and descriptive lookup meanings, so that forms, concurrent programs, and reporting layers can present a flat, human-readable list of contact persons together with the parties they relate to.

Because the view is keyed on the relationship between a subject party and an object party, it exposes both sides of the association. This makes it valuable wherever an application needs to resolve "who is related to whom" without issuing multiple correlated lookups against the underlying relationship and party tables. For integration and reporting, it provides a stable, read-only access point into contact-relationship data with descriptive text already resolved from the lookup tables.

Underlying Base Objects

The view is defined over three documented base objects:

  • HZ_PARTIES (referenced twice as synonyms A and HZ) — the Trading Community Architecture registry of person and organization parties. Alias A supplies the subject person and address attributes; alias HZ supplies the object party name.
  • HZ_RELATIONSHIPS (synonym B) — the TCA relationship registry linking a subject party to an object party, with relationship code, status, and effective dates.
  • AR_LOOKUPS (view C) — the Receivables lookup view supplying the descriptive relationship meaning.

The joins link A.PARTY_ID to B.SUBJECT_ID and B.OBJECT_ID to HZ.PARTY_ID. Filtering restricts results to person parties (A.PARTY_TYPE = 'PERSON'), active or inactive status ('A','I'), active relationships (B.STATUS = 'A'), and the current effective date window via SYSDATE BETWEEN B.START_DATE AND NVL(B.END_DATE, SYSDATE). The lookup join requires C.LOOKUP_TYPE = 'PARTY_RELATIONS_TYPE'. The SELECT DISTINCT clause deduplicates rows.

Key Columns

Common Use Cases and Queries

Typical uses include LOV population, contact-relationship reporting, and data extraction for integrations. A simple listing of a person's relationships:

  • SELECT party_name, relationship, object_party_name FROM apps.asf_cnt_person_lov_v WHERE party_id = :p_party_id;

Resolving a person by name for an LOV:

  • SELECT party_id, party_name, object_party_name FROM apps.asf_cnt_person_lov_v WHERE UPPER(party_name) LIKE UPPER(:search||'%');

Reporting relationships by type:

  • SELECT relationship, COUNT(*) FROM apps.asf_cnt_person_lov_v GROUP BY relationship ORDER BY 2 DESC;