Search Results rel_party_id




Overview
Explore in AI Chat

Overview

The view ASF_PERSON_RELAT_LOV_V is an Oracle Applications (APPS) schema database view owned by the APPS user. It belongs to the ASF – Sales Online product family within Oracle E-Business Suite and is documented as VALID in both the 12.1.1 and 12.2.2 releases. The view is designed to support List of Values (LOV) functionality by presenting related person records that can be surfaced to end users during sales and order-entry flows.

Its structural role is to resolve relationship data between parties in the TCA (Trading Community Architecture) model into a flattened, human-readable form. Rather than requiring application code to join HZ_RELATIONSHIPS, HZ_PARTIES, and AR_LOOKUPS manually, the view delivers a single queryable surface containing both parties involved in a relationship: the subject party and the related (object) party. This makes it a convenient reporting and integration object for answering questions about who is related to whom.

The inclusion of the AR.MEANING column, decoded from the PARTY_RELATIONS_TYPE lookup, is a defining characteristic. Consumers receive the translated relationship description (for example, "Contact" or another seeded meaning) instead of a raw lookup code, which is essential for LOV display and user-facing reports.

Underlying Base Objects

The documented metadata identifies three referenced base objects, which form the view's SELECT statement:

The joins are constrained so that REL.OBJECT_ID = PAR.PARTY_ID, meaning the party row returned by this view is the object side of the relationship. Both the relationship status and the party status must be in ('A', 'I') — active or inactive. The relationship is further restricted to subjects and objects both stored in HZ_PARTIES, ensuring the relationship represents a party-to-party association rather than a link involving a different entity table.

Key Columns

  • PARTY_NAME — the formatted name of the party on the object side of the relationship.
  • NAME — the person last name (PERSON_LAST_NAME) exposed under the label NAME for LOV display convenience.
  • PARTY_ID — the object party identifier; the returned related person's primary key.
  • PARTY_TYPE — classification of the party (for example, PERSON or ORGANIZATION).
  • STATUS — the party status, restricted to active ('A') or inactive ('I').
  • REL_PARTY_ID — the relationship party identifier, representing the subject side of the relationship and commonly the value users search for when entering "rel_party_id."
  • SUBJECT_ID — the identifier of the subject party in the relationship.
  • OBJECT_ID — the identifier of the related (object) party.
  • RELATIONSHIP_TYPE — the decoded meaning of the relationship, sourced from AR_LOOKUPS.MEANING.

Common Use Cases and Queries

Typical usage centers on populating LOVs that let users pick a related contact or associated person from a known subject party, and on reporting relationships between parties.

  • Retrieving all parties related to a given subject party.
  • Filtering related persons by relationship meaning for display in an order-entry LOV.
  • Feeding integration extracts that map subject/object party relationships into external systems.

Sample query joining on the relationship subject:

SELECT party_name, rel_party_id, object_id, relationship_type FROM asf_person_relat_lov_v WHERE subject_id = :p_subject_id AND status = 'A';

Searching by related party identifier:

SELECT subject_id, object_id, relationship_type FROM asf_person_relat_lov_v WHERE rel_party_id = :p_rel_party_id;