Search Results party_relations_type




Overview
Explore in AI Chat

Overview

ASF_PERSON_RELAT_LOV_V is an APPS-owned database view in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It is a reporting and list-of-values (LOV) object, not a transactional entity. The view presents person-to-person relationships recorded in the Oracle Trading Community Architecture (TCA) model, resolving raw relationship codes into their user-facing meanings and filtering the result to active or inactive parties and relationships. It exists to support the Agent/Sales Force (ASF) product family, where an LOV is required to select a related person — for example a contact, an employee, or a referral party — by name rather than by internal identifier.

Because the view joins HZ_RELATIONSHIPS to HZ_PARTIES, it exposes both the subject side and the object side of a relationship in a single row, which makes it convenient for both UI selection and ad-hoc reporting. The user search term "party_relations_type" maps directly to the lookup type dereferenced in the view, AR.LOOKUP_TYPE = 'PARTY_RELATIONS_TYPE', confirming the view's purpose of surfacing the resolved relationship type.

Underlying Base Objects

The documented referenced base objects are:

  • AR_LOOKUPS (VIEW) — supplies the lookup meaning for the relationship type via LOOKUP_TYPE = 'PARTY_RELATIONS_TYPE' and LOOKUP_CODE = REL.RELATIONSHIP_CODE.
  • HZ_PARTIES (SYNONYM) — the TCA party master, joined on REL.OBJECT_ID = PAR.PARTY_ID, providing the related party's name and identifiers.
  • HZ_RELATIONSHIPS (SYNONYM) — the TCA relationship fact table, providing the relationship code, status, and the subject/object party pair. Subject and object table names are constrained to 'HZ_PARTIES', so only party-to-party relationships are returned.

Key Columns

  • PARTY_NAME — the full name of the related (object) party from HZ_PARTIES.
  • PERSON_LAST_NAME — last name of the person party, useful for alphabetical LOV sorting and display.
  • PARTY_ID — the object party identifier from HZ_PARTIES. Note that HZ_RELATIONSHIPS also exposes a PARTY_ID column; the two should be distinguished by alias in custom SQL.
  • PARTY_TYPE — the party classification (for example PERSON or ORGANIZATION) of the related party.
  • STATUS — the relationship status from HZ_RELATIONSHIPS, restricted to 'A' (active) or 'I' (inactive).
  • SUBJECT_ID / OBJECT_ID — the source and target party identifiers of the relationship; the object-side value drives the HZ_PARTIES join.
  • MEANING — the resolved, translatable lookup meaning for the relationship type (for example the descriptive name of a party relations type).

Common Use Cases and Queries

Typical uses include populating LOVs for related-person selection, validating that a candidate relationship exists before creating a new one, and reporting the related persons tied to a given party.

A simple LOV query lists related persons by name:

SELECT party_id, party_name, meaning
FROM   apps.asf_person_relat_lov_v
WHERE  status = 'A'
ORDER  BY person_last_name, party_name;

A targeted lookup for a specific subject party and relationship type:

SELECT v.party_id, v.party_name, v.meaning
FROM   apps.asf_person_relat_lov_v v
WHERE  v.subject_id = :p_party_id
AND    v.meaning   = :p_relations_type;

Because the view is defined over TCA and AR objects without an org or operating-unit filter, custom queries should add the appropriate join to asg_person or per_business_group filters when restricting results is required. Performance relies on indexed access to HZ_RELATIONSHIPS by object_id and subject_id.