Search Results object_party_id




Overview
Explore in AI Chat

Overview

The view BIC_CONTACTS_DETAIL_V belongs to the BIC — Customer Intelligence module of Oracle E-Business Suite. Customer Intelligence was an early analytical and reporting layer delivered alongside Oracle CRM in releases spanning 11i through the early 12.x family. In Oracle EBS 12.1.1 and 12.2.2, the module is documented as obsolete and the view itself is listed in ETRM metadata with the note "Not implemented in this database." Accordingly, the object should be treated as a legacy or dormant artifact rather than a supported reporting interface in current installations.

The view presents a denormalized, contact-centric projection of trading community data. It joins parties, party relationships, organization contacts, party sites, addresses, and contact points to expose one row per contact associated with a given party. The searched term object_party_id corresponds to the OBJECT_PARTY_ID column, which carries the party identifier of the owning (object) party — that is, the organization or person to whom the contact is related — while PARTY_ID carries the contact's own party identifier.

Underlying Base Objects

The view text references the following base tables and supporting views:

  • HZ_PARTIES A — the owning party, aliased as the relationship object.
  • HZ_PARTIES C — the contact party, the relationship subject.
  • HZ_PARTY_RELATIONSHIPS R — supplies the CONTACT_OF relationship linking object and subject.
  • HZ_ORG_CONTACTS CON — organization contact attributes such as department, title, job title, and rank.
  • HZ_PARTY_SITES ST — the contact's party site, joined with active-date validation using NVL on the start and end dates.
  • BIC_ADDRESS_V L — a BIC address view supplying the formatted ADDRESS.
  • BIC_CONTACT_POINTS_V P — a BIC contact points view supplying contact type, contact identifier, and primary flag.

ETRM documentation records no referenced base objects for this view in 12.2.2 metadata, so the join logic above is drawn from the stored view definition. All outer joins use the Oracle (+) syntax, and the view is declared WITH READ ONLY.

Key Columns

  • CUST_ACCOUNT_ID and ORG_ID — both projected as literal NULL, retained for interface compatibility.
  • OBJECT_PARTY_ID — the party identifier of the organization or person that owns the contact relationship.
  • PARTY_ID — the contact person's party identifier.
  • CONTACT_NAME — the contact's party name.
  • DEPARTMENT, TITLE, JOB_TITLE, RANK — organizational contact attributes from HZ_ORG_CONTACTS.
  • ADDRESS — formatted address from BIC_ADDRESS_V.
  • CONTACT_TYPE, CONTACT_ID, PRIMARY_FLAG — contact point details, restricted to primary entries where the owner is a party.

Common Use Cases and Queries

Because the view is obsolete and unimplemented, queries are primarily diagnostic or migration-oriented. A typical lookup retrieves all contacts for a given owning party:

SELECT contact_name, department, title, address, contact_id FROM bic_contacts_detail_v WHERE object_party_id = :party_id;

Analysts migrating to supported interfaces would instead use HZ_PARTIES joined to HZ_PARTY_RELATIONSHIPS and HZ_ORG_CONTACTS directly, or the current HZ_ contact views, which are maintained in 12.1.1 and 12.2.2. Any dependency on BIC_CONTACTS_DETAIL_V should be reviewed and replaced before upgrade or patching.