Results for “ibe_oe_contacts_v”

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

Overview

IBE_OE_CONTACTS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the IBE (iStore) product family. As documented in the ETRM repository for releases 12.1.1 and 12.2.2, its stated purpose is to retrieve the billing or shipping contact name associated with an order. In practice the view exposes the customer contact records maintained in Oracle's Trading Community Architecture (TCA) model, joined to the customer account and party relationship structures that iStore and Order Management rely on when resolving "who to contact" for a given account or account site.

Because it is a simple view rather than a table, it carries no storage of its own and always reflects the current state of the underlying TCA tables. It is typically referenced by iStore checkout, order confirmation, and account administration pages, and by custom reports or integrations that need a flattened, queryable representation of contact names. The view has a VALID status in the data dictionary and is not a public API; Oracle does not guarantee its signature across releases, so custom code should treat it as a reporting convenience rather than a stable interface.

Underlying Base Objects

The documented metadata lists five referenced base objects, each accessed through an APPS synonym:

• HZ_CUST_ACCOUNT_ROLES — the driving table, filtered to ROLE_TYPE = 'CONTACT'. Supplies the customer account role identifier, the linked party, the site, and the role status.
• HZ_CUST_ACCOUNTS — the customer account header, providing the account number and the account party identifier used in the relationship join.
• HZ_RELATIONSHIPS — the TCA relationship model that links a contact party to the account's owning party, constrained to subject and object table names of 'HZ_PARTIES'.
• HZ_PARTIES — appears twice logically: once as the contact person and once as the related party, supplying the first name, last name, and party identifiers.
• HZ_ORG_CONTACTS — joined through the party relationship identifier to supply the contact's job title.

The view therefore depends entirely on the TCA data model and inherits its behavior, including the requirement that contact roles and party relationships be correctly maintained for rows to be returned.

Key Columns

• CUST_ACCOUNT_ROLE_ID — primary identifier of the contact role record; the most selective column for lookups.
• CUST_ACCT_SITE_ID — the account site, aliased as ORG_ID in the view text; indicates the site context of the contact.
• CUST_ACCOUNT_ID / ACCOUNT_NUMBER — the customer account and its human-readable number.
• COMPANY_PARTY_ID / REL_PARTY_ID / PERSON_PARTY_ID — party identifiers for the account-owning organization, the related party, and the contact person respectively.
• PARTY_NAME — concatenation of first and last name, convenient for display.
• FIRST_NAME / LAST_NAME — individual name components, useful for sorting or formal correspondence.
• JOB_TITLE — the contact's title from HZ_ORG_CONTACTS.
• STATUS — the active/inactive status of the customer account role.

Common Use Cases and Queries

Typical uses include populating billing or shipping contact fields on order documents, validating that a contact exists for an account before order submission, and building extracts of contact details for downstream systems.

To list active contacts for a given account number:

• SELECT cust_account_role_id, party_name, first_name, last_name, job_title FROM ibe_oe_contacts_v WHERE account_number = '1234' AND status = 'A';

To find all contacts for a specific site:

• SELECT cust_acct_site_id, party_name, job_title FROM ibe_oe_contacts_v WHERE cust_acct_site_id = :p_site_id;

Because joins to TCA tables can be expensive on large volumes, always constrain by account, site, or role identifier, and avoid unbounded full scans in production queries.