Search Results related_party_id

Overview

OKL_CS_PERSON_PARTIES_UV is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKL – Leasing and Finance Management product family. Its documented status is VALID in both EBS 12.1.1 and 12.2.2. The view presents a consolidated, denormalized list of parties and their related persons, drawing together party identity, party type, related party linkage, and the individual name attributes for persons. Because it flattens data originating from the Oracle Trading Community Architecture (TCA) into a single relational result set, it is well suited for reporting, inquiry screens, concurrent program extracts, and integration views within the leasing and finance domain that need party and person name information without navigating multiple TCA entities directly.

The view exposes person-level name components including PERSON_FIRST_NAME, PERSON_LAST_NAME, PERSON_MIDDLE_NAME, and PERSON_NAME_SUFFIX, which is the attribute most commonly sought by developers searching for a person middle name within the OKL module.

Underlying Base Objects

The ETRM 12.2.2 metadata records two referenced base objects, both accessed through synonyms: HZ_PARTIES and HZ_RELATIONSHIPS. HZ_PARTIES is the TCA master table that stores the identifying and naming attributes for every party, including both organizations and persons. HZ_RELATIONSHIPS stores the associations between parties, such as a person related to an organization via a given relationship code.

The view is defined as a UNION of two queries. The first query joins HZ_RELATIONSHIPS to HZ_PARTIES three times: as PTY (the primary party), ORG (the object side of the relationship), and PER (the subject side, holding the person name columns). The DECODE on PTY.PARTY_TYPE returns REL.OBJECT_ID for organizations and REL.SUBJECT_ID for persons as the PARTY_ID. The second query selects parties that have no HZ_RELATIONSHIPS record where the party appears on the OBJECT_ID side and is of type PERSON, and assigns a NULL RELATIONSHIP_TYPE. This union ensures every qualifying party is represented, whether or not a relationship association exists.

Key Columns

• PARTY_ID – The resolved identifier of the party. Via DECODE, it equals REL.OBJECT_ID for organizations and REL.SUBJECT_ID for persons; in the second union branch it is the party's own PARTY_ID.
• PARTY_TYPE – Indicates whether the row represents a PERSON or ORGANIZATION.
• PARTY_NAME – The formatted party name sourced from the ORG alias (HZ_PARTIES.PARTY_NAME).
• RELATED_PARTY_ID – The counterparty identifier: REL.SUBJECT_ID in the joined branch, or the party's own PARTY_ID in the standalone branch.
• PERSON_FIRST_NAME, PERSON_LAST_NAME, PERSON_MIDDLE_NAME, PERSON_NAME_SUFFIX – The individual name components taken from the PER alias (HZ_PARTIES). PERSON_MIDDLE_NAME specifically carries the middle name of the person party.
• RELATIONSHIP_TYPE – The relationship code from HZ_RELATIONSHIPS, or NULL when no relationship applies.

Common Use Cases and Queries

The view is typically queried to retrieve person names alongside their associated party context, for example in leasing customer or contact reporting where a middle name is required.

To locate a person by middle name:

SELECT party_id, party_name, person_first_name,
       person_middle_name, person_last_name, person_name_suffix
FROM   okl_cs_person_parties_uv
WHERE  party_type = 'PERSON'
AND    person_middle_name IS NOT NULL;

To list person parties with their relationship association:

SELECT party_id, related_party_id, relationship_type,
       person_first_name, person_middle_name, person_last_name
FROM   okl_cs_person_parties_uv
WHERE  party_type = 'PERSON'
ORDER  BY person_last_name, person_first_name;

Because the view joins TCA tables directly, queries should filter on PARTY_TYPE and consider indexing or restricting results by party identifiers to avoid full scans against the underlying HZ_PARTIES and HZ_RELATIONSHIPS data volumes.