Results for “csc_hz_parties_self_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CSC_HZ_PARTIES_SELF_V is an APPS-owned database view in the Oracle E-Business Suite Customer Care (CSC) module. It is documented as a VALID object in both EBS 12.1.1 and 12.2.2, and its primary role is to expose party relationship information to the Contact Center form while simultaneously providing the "self" relationship record for each party. This self-inclusion is significant: rather than returning only the relationships a party holds with other parties, the view also returns the party's own row, enabling forms and reports to display a party alongside its relationship network in a single result set without a separate union query.

The view is defined over the Oracle Trading Community Architecture (TCA) registry tables HZ_PARTIES and HZ_PARTY_RELATIONSHIPS, and the documented metadata identifies the referenced base objects as HZ_PARTIES (SYNONYM) and HZ_RELATIONSHIPS (SYNONYM). Because it joins the party master to its relationship rows and additionally aliases the "object" and "subject" parties, it functions as a flattened, denormalized projection suitable for both UI data retrieval and ad hoc reporting against party hierarchies.

Underlying Base Objects

The view text references several aliases over the same TCA structures. PARTY represents the primary row from HZ_PARTIES, supplying the party's own number, type, name, and address attributes. PARTY_REL represents the relationship row from HZ_PARTY_RELATIONSHIPS, supplying PARTY_RELATIONSHIP_ID and PARTY_RELATIONSHIP_TYPE. SUB_PARTY and OBJ_PARTY are additional aliases that resolve the subject and object parties of the relationship, each contributing identifiers, numbers, names, and person-name components from HZ_PARTIES.

This join pattern is what allows a single query to return three logical perspectives at once: the base party, the related party on one side of the relationship, and the related party on the other. The documented dependency list (HZ_PARTIES and HZ_RELATIONSHIPS) reflects the TCA registry foundation, though the runtime definition also touches relationship-oriented columns. Any customization or extension of the view should therefore respect TCA data integrity and the party relationship model, since the Contact Center form depends directly on its output.

Key Columns

• PARTY.PARTY_ID, PARTY.PARTY_NUMBER, PARTY.PARTY_TYPE, PARTY.PARTY_NAME — identity and classification of the base party.
• PARTY_REL.PARTY_RELATIONSHIP_ID, PARTY_REL.PARTY_RELATIONSHIP_TYPE — the relationship record and its type classification.
• SUB_PARTY.PARTY_ID, SUB_PARTY.PARTY_NUMBER, SUB_PARTY.PARTY_NAME — the subject party of the relationship.
• OBJ_PARTY.PARTY_ID, OBJ_PARTY.PARTY_NUMBER, OBJ_PARTY.PARTY_NAME, OBJ_PARTY.PARTY_TYPE — the object party, including GROUP_TYPE and person-name attributes (PERSON_FIRST_NAME, PERSON_LAST_NAME, KNOWN_AS, SIC_CODE).
• Address columns — ADDRESS1 through CITY, STATE, PROVINCE, POSTAL_CODE, COUNTRY, with a concatenated ADDRESS built from ADDRESS1–ADDRESS4 using semicolon delimiters.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE19 — descriptive flexfield columns carried from the object party.

The user search term "obj_status" does not appear as a documented column in this view. In TCA, party status is typically derived from HZ_PARTIES.STATUS rather than a column named OBJ_STATUS; where a status-like value is required, it should be sourced from the underlying party record or its associated status table. Queries should not assume an OBJ_STATUS column exists on CSC_HZ_PARTIES_SELF_V.

Common Use Cases and Queries

Typical scenarios include populating the Contact Center party relationships region, resolving a party's related contacts, and building ad hoc reports that list a party beside its relationships without losing the self row.

• Retrieve all relationship rows for a specific party, including the self record.
• Report on relationship types across a customer base.
• Locate the object party of each relationship for name and address display.

SELECT party_id,
       party_number,
       party_name,
       party_relationship_id,
       party_relationship_type,
       obj_party_id,
       obj_party_name,
       obj_party_number
FROM   apps.csc_hz_parties_self_v
WHERE  party_id = :p_party_id;

SELECT party_id,
       obj_party_name,
       party_relationship_type
FROM   apps.csc_hz_parties_self_v
WHERE  party_relationship_type = 'CONTACT_OF'
ORDER  BY party_name;

Because the view is owned by APPS, direct queries should reference APPS.CSC_HZ_PARTIES_SELF_V or rely on the standard synonym resolution in the EBS environment. Joins back to HZ_PARTIES on OBJ_PARTY_ID are common when additional attribute-level detail is required.