Results for “aso_i_org_contacts_v”

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

Overview

The ASO_I_ORG_CONTACTS_V view is an Oracle Applications (APPS) database object owned by the APPS schema and registered as a VALID view within Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the ASO – Order Capture product family, which underpins Oracle's quoting, order capture, and sales contract functionality. Despite the ASO naming convention, the view's content is fundamentally sourced from Oracle's Trading Community Architecture (TCA/AR) party model, aggregated from HZ_ORG_CONTACTS, HZ_PARTIES, HZ_PARTY_RELATIONSHIPS, AR_LOOKUPS, and HZ_ORG_CONTACT_ROLES.

The documented description states that the view "gives the information about Party Name, Party Type etc." Its primary purpose is to expose organization contacts — the individuals attached to a customer or prospect organization — together with their party identification, name components, title, status, and contact-role information. Because it joins the party relationship model to organization contact records, it is a convenient reporting and integration source wherever order capture or sales activities must identify a contact person at a customer organization.

Underlying Base Objects

The view is defined over five documented base objects: AR_LOOKUPS (a VIEW), HZ_ORG_CONTACTS, HZ_ORG_CONTACT_ROLES, HZ_PARTIES, and HZ_RELATIONSHIPS (all SYNONYMs in the documented metadata). The join structure is as follows:

• HZ_ORG_CONTACTS (alias OC) is the driving table, supplying ORG_CONTACT_ID, job title, status, contact number, and the PARTY_RELATIONSHIP_ID foreign key linking the contact to the party relationship.
• HZ_PARTY_RELATIONSHIPS (alias PR) is joined on OC.PARTY_RELATIONSHIP_ID = PR.PARTY_RELATIONSHIP_ID, providing OBJECT_ID, SUBJECT_ID, and PARTY_ID.
• HZ_PARTIES (alias P) is joined on PR.SUBJECT_ID = P.PARTY_ID, supplying the party name, party number, party type, and person name components.
• AR_LOOKUPS (alias LK) is an outer-joined lookup on LOOKUP_TYPE = 'CONTACT_TITLE' to decode the title code.
• HZ_ORG_CONTACT_ROLES (alias ROLE) is outer-joined on OC.ORG_CONTACT_ID = ROLE.ORG_CONTACT_ID, providing the contact role type.

The presence of HZ_RELATIONSHIPS in the documented object list reflects the underlying TCA relationship framework that the party relationship records reference.

Key Columns

• ORG_CONTACT_ID — Primary identifier of the organization contact record.
• CUSTOMER_NAME, CUSTOMER_NUMBER, CUSTOMER_TYPE — The party name, party number, and party type sourced from HZ_PARTIES (P.PARTY_NAME, P.PARTY_NUMBER, P.PARTY_TYPE).
• FIRST_NAME, MIDDLE_NAME, LAST_NAME — Person name components from HZ_PARTIES.
• TITLE — Decoded contact title from AR_LOOKUPS (LK.MEANING, lookup type CONTACT_TITLE).
• JOB_TITLE, STATUS, CONTACT_NUMBER — Attributes of the organization contact.
• ORG_PARTY_ID — Party identifier of the organization (PR.OBJECT_ID).
• CONTACT_PARTY_ID — Party identifier of the contact person (PR.SUBJECT_ID).
• CONTACT_ROLE_TYPE — Role assigned to the contact (ROLE.ROLE_TYPE).
• RELATIONSHIP_PARTY_ID — Party relationship identifier (PR.PARTY_ID).

Common Use Cases and Queries

The view is typically used to enumerate contacts associated with customer organizations for quoting, order capture, or CRM-style reporting. A typical query retrieves active contacts for a given organization party:

SELECT org_party_id, customer_name, first_name, last_name, job_title, contact_role_type
  FROM apps.aso_i_org_contacts_v
  WHERE org_party_id = :p_org_party_id
    AND status = 'A';

Because it flattens the TCA relationship hierarchy into a single row per contact, it is also useful for integration interfaces that must resolve a party relationship ID to its associated party name and role. Users searching under the related term hz_party_relationships will find this view to be one of the most direct, ASO-facing projections of that underlying relationship data, exposing RELATIONSHIP_PARTY_ID, CONTACT_PARTY_ID, and ORG_PARTY_ID simultaneously for cross-referencing against the HZ schema.