Search Results name_suffix

Overview

AST_L_PARTY_PEOPLE_V is a TeleSales (AST) module view in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a unified listing of trading parties and their related persons or organizations, drawn from the Oracle TCA (Trading Community Architecture) model. Its practical role is to resolve the "related_party_id" reference into a usable identity — exposing party identifiers, party names, person name components, and relationship types in a single flattened structure. TeleSales and downstream reporting or integration logic can therefore join to a party without navigating the relationship tables directly.

Per the ETRM metadata, the view is not implemented in the database as delivered. Its text is documented for reference, which means EBS customers or implementers may create it in custom schemas when TeleSales relationship reporting is required. This distinction is important: the view is not a supported, seeded database object in a standard 12.1.1 or 12.2.2 instance.

Underlying Base Objects

The view is built entirely from TCA tables. The documented base objects are:

• HZ_PARTY_RELATIONSHIPS (alias REL) — the relationship repository linking a party to a subject or object party.
• HZ_PARTIES (aliases PTY, PER, ORG) — the master party table, used three times to resolve the owning party, the related person, and the related organization.

The definition is a UNION of two branches. The first branch joins REL to HZ_PARTIES for the relationship owner (PTY), the related person (PER), and the related organization (ORG), returning relationship-derived rows. The second branch selects from HZ_PARTIES directly for parties that have no relationship record as an object, providing standalone parties with a NULL relationship type. This UNION gives a complete universe of parties, whether or not a relationship exists.

Key Columns

• PARTY_ID — the identifier of the owning party. In the second UNION branch this is set to PARTY.PARTY_ID directly.
• PARTY_TYPE — 'ORGANIZATION' or 'PERSON', driving the DECODE logic that determines the returned identifier.
• PARTY_NAME — the formatted name of the organization or party.
• RELATED_PARTY_ID — the resolved related party. This is the column matching the search term "related_party_id". It is populated by the DECODE: for organizations it returns REL.OBJECT_ID, and for persons it returns REL.SUBJECT_ID (falling back to REL.OBJECT_ID). This column is what consumers use to look up the counterparty of a relationship.
• FIRST_NAME, LAST_NAME, MIDDLE_NAME, NAME_SUFFIX — person name attributes from HZ_PARTIES; NULL for the standalone branch and for organization rows.
• RELATIONSHIP_TYPE — the REL.PARTY_RELATIONSHIP_TYPE value; NULL for parties with no relationship.

Common Use Cases and Queries

Typical scenarios include identifying all persons associated with an organization, resolving a related party for a TeleSales call list, and validating that a party has relationship coverage. A representative query filtering on the searched column:

• SELECT party_id, party_type, party_name, related_party_id, relationship_type FROM ast_l_party_people_v WHERE related_party_id = :p_party_id;
• SELECT party_name, first_name, last_name FROM ast_l_party_people_v WHERE party_type = 'PERSON' AND relationship_type IS NOT NULL;
• SELECT DISTINCT party_id, party_name FROM ast_l_party_people_v; — enumerate the full party universe, including those without relationships.

Because the view is not seeded, confirm its existence before use and treat any local creation as a custom extension subject to upgrade review.