Results for “as_party_org_contacts_v”

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

Overview

The AS_PARTY_ORG_CONTACTS_V view is a Sales Foundation (AS) reporting and integration object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It consolidates organization contact records that exist at the party and party-site level, intentionally excluding role type information and person-profile related attributes. This design allows consumers to retrieve the core contact identity and assignment data without the overhead associated with role-specific or profile-specific denormalization.

The view is registered with a VALID status in the ETRM data dictionary and exposes data supporting downstream reporting, interfaces, and concurrent programs that need a flattened, join-ready representation of contacts attached to a party (organization) or a specific party site. Because it draws from the Trading Community Architecture (TCA) model, it is particularly relevant when resolving a contact to its owning party and to the related organization party through relationship records.

Underlying Base Objects

The view is defined over four documented base objects, all referenced through APPS synonyms:

• HZ_ORG_CONTACTS — the organization contact assignment table, contributing the primary key rowid and most contact-attribute columns.
• HZ_PARTIES — referenced twice (aliased PARTY and PARTY2), supplying the person party attributes and the related organization party attributes.
• HZ_RELATIONSHIPS — provides relationship status and relationship code linking the person contact to the organization.
• HZ_CONTACT_POINTS — supplies the contact point email address exposed by the view.

The join is anchored on ORG_CONT.PARTY_RELATIONSHIP_ID-style linkage across HZ_RELATIONSHIPS, with PARTY representing the person party and PARTY2 representing the organization party. Party and party-site identifiers are surfaced from ORG_CONT and the joined party rows, enabling both organization-level and site-level contact resolution.

Key Columns

• ORG_CONTACT_ID — unique identifier of the organization contact record.
• PARTY_ID / PARTY_NUMBER (PARTY) — the person party. The user search term cont_party_number maps conceptually to PARTY_NUMBER, which uniquely identifies the contact party across TCA.
• PARTY_ID / PARTY_NUMBER (PARTY2) — the organization party to which the contact is related.
• PARTY_SITE_ID — the party site at which the contact is registered, if site-specific.
• CONTACT_NUMBER — the business-facing contact identifier.
• PERSON_FIRST_NAME, PERSON_LAST_NAME, PERSON_NAME_SUFFIX, PERSON_PRE_NAME_ADJUNCT, PARTY_NAME — person and party names.
• EMAIL_ADDRESS — contact point email from HZ_CONTACT_POINTS.
• TITLE, JOB_TITLE, DEPARTMENT, DEPARTMENT_CODE, MAIL_STOP, RANK — assignment and organizational attributes.
• STATUS, RELATIONSHIP_CODE (REL) — relationship state and classification.
• DECISION_MAKER_FLAG, REFERENCE_USE_FLAG, MANAGED_BY — contact role indicators retained in the view.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE20 — descriptive flexfield context and values.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, LAST_UPDATED_BY, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

The view is typically used to list contacts for an organization or party site without invoking role-based filtering, and to resolve a contact's party number for integration payloads. A representative query retrieving contacts by party number is:

• SELECT org_contact_id, party_number, party2_party_number AS org_party_number, person_first_name, person_last_name, email_address, status FROM as_party_org_contacts_v WHERE party_number = :p_party_number;

A second pattern filters contacts by organization party and site:

• SELECT contact_number, title, job_title, department, relationship_code, decision_maker_flag FROM as_party_org_contacts_v WHERE party2_party_number = :p_org_number AND party_site_id = :p_site_id;

Because the view excludes role type and person profile data, it is preferable for straightforward contact extraction where those attributes are not required; consumers needing role-specific detail should join to the underlying TCA role tables instead.