Search Results related_party_id

Overview

ASF_PERSON_RELATIONSHIPS_V is a reporting view in the ASF – Sales Online module of Oracle E-Business Suite (available in 12.1.1 and 12.2.2). Its documented purpose is to present contact person information, joining party, person, relationship, phone, and address data into a single denormalized result set. The view consolidates attributes that would otherwise require multiple joins across the TCA (Trading Community Architecture) and relationship model, making it convenient for reporting and integration layers that surface contact details associated with a related party.

The search term "related_party_id" reflects the typical access pattern: consumers of this view resolve the related party of a contact, since the view exposes several PARTY_ID columns (including the related party's identifier) alongside the relationship code and relationship ID. ETRM metadata notes the view is "Not implemented in this database," meaning it is documented at the design level but may not exist in every environment — a critical consideration for developers referencing it.

Underlying Base Objects

The ETRM-provided metadata documents no owner and no referenced base objects. The view text, however, clearly references the following aliased sources:

• PRSN — the person/party record (aliased from a person party source such as HZ_PARTIES / PER_PERSONS), supplying PARTY_ID, PARTY_NAME, PERSON_LAST_NAME, PERSON_FIRST_NAME, PERSON_MIDDLE_NAME, KNOWN_AS, LAST_ORDERED_DATE, and the ATTRIBUTE1–18 flex columns plus audit columns (CREATION_DATE, LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY).
• PR — a relationship record supplying PARTY_ID, STATUS, OBJECT_ID, RELATIONSHIP_ID, and RELATIONSHIP_CODE.
• PARTY — a related party supplying PARTY_ID, PARTY_TYPE, and PARTY_NAME.
• AL1 — a lookup supplying MEANING (the decoded relationship code description).
• CPPH — a contact phone source supplying PHONE_COUNTRY_CODE, PHONE_AREA_CODE, PHONE_NUMBER, PHONE_EXTENSION, and PHONE_LINE_TYPE.
• RELPARTY — an address/email source supplying EMAIL_ADDRESS and ADDRESS1–ADDRESS4, STATE, CITY, PROVINCE, COUNTY, POSTAL_CODE, and COUNTRY.

The naming conventions (HZ-style relationship and party structures, FND lookup decode) confirm the view is built over TCA relationship tables rather than a dedicated ASF table.

Key Columns

• PARTY_ID (multiple) — three distinct PARTY_ID columns appear, corresponding to the person, the relationship, and the related party. Selecting the correct one is essential when resolving related_party_id.
• PARTY_NAME, PARTY_TYPE — name and classification of the related party.
• PERSON_LAST_NAME, PERSON_FIRST_NAME, PERSON_MIDDLE_NAME, KNOWN_AS — person naming attributes.
• RELATIONSHIP_ID, RELATIONSHIP_CODE — the relationship identifier and its code; MEANING provides the decoded description.
• STATUS, OBJECT_ID, LAST_ORDERED_DATE — relationship status and object linkage context.
• Phone and address composites — a formatted phone string and formatted address string, plus their individual components (EMAIL_ADDRESS, ADDRESS1–4, CITY, STATE, PROVINCE, COUNTY, POSTAL_CODE, COUNTRY).

Common Use Cases and Queries

A typical use is retrieving the related party for a given relationship and displaying contact information. Because multiple PARTY_ID columns exist, an alias is required:

• SELECT PARTY_NAME, RELATIONSHIP_CODE, MEANING, EMAIL_ADDRESS FROM ASF_PERSON_RELATIONSHIPS_V WHERE RELATIONSHIP_CODE = :code;
• SELECT PERSON_FIRST_NAME, PERSON_LAST_NAME, MEANING, EMAIL_ADDRESS FROM ASF_PERSON_RELATIONSHIPS_V WHERE RELATIONSHIP_ID = :relationship_id;

Integration scenarios use the formatted address and phone columns for display-ready output. Developers should confirm view existence per environment, since the metadata states it is not implemented in this database.