Results for “cust_acct_id”

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

Overview

The OKX_CUST_ROLE_RESP_V view is a reporting and integration object owned by the APPS schema within the OKX - Contracts Integration product module. It presents customer contact information in a denormalized form suitable for consumption by Oracle Contracts and related downstream applications. The view is documented as VALID in Oracle E-Business Suite 12.1.1 and 12.2.2.

The view's purpose, as stated in the ETRM metadata, is to expose customer contacts. It consolidates contact-level attributes from the Oracle Trading Community Architecture (TCA) model — specifically account roles, parties, relationships, and role responsibilities — into a single flattened row per contact role assignment. This flattening shields consuming modules from the normalization that TCA applies across HZ_CUST_ACCOUNT_ROLES, HZ_PARTIES, HZ_RELATIONSHIPS, and HZ_ROLE_RESPONSIBILITY.

The view is of particular interest to integrations that must resolve a customer account's contact roster along with each contact's assigned responsibility type, primary indicatory flag, and status. Because these represent the authoritative source of contact role data, the view is frequently referenced by contract authoring, order capture, and customer-facing interfaces that need a stable, read-only projection.

Underlying Base Objects

The view is defined over five synonym-referenced TCA base objects:

• HZ_CUST_ACCOUNT_ROLES — the driving table, supplying the customer account role record.
• HZ_PARTIES — provides party name and email address for the contact.
• HZ_RELATIONSHIPS — establishes the party-to-party relationship linking the account to the contact.
• HZ_ROLE_RESPONSIBILITY — supplies the responsibility type and primary flag for the contact role.
• HZ_CUST_ACCT_SITES — referenced via an EXISTS subquery to ensure the customer account has at least one account site.

The join predicates are tightly constrained. Only rows where CAR.ROLE_TYPE = 'CONTACT' are returned, restricting the view to contact-type roles rather than other account role types. The relationship must be CONTENT_SOURCE_TYPE = 'USER_ENTERED', and the account role must be joinable to HZ_ROLE_RESPONSIBILITY through CUST_ACCOUNT_ROLE_ID. The EXISTS clause against HZ_CUST_ACCT_SITES guarantees that only accounts possessing at least one site are surfaced, which is a meaningful filter for contract and order contexts where an account site is presumed.

Key Columns

• PARTY_ID / PARTY_ID2 — the relationship object identifier and a placeholder ('#') respectively; PARTY_ID identifies the party in the relationship.
• DESCRIPTION / NAME — both derived from P.PARTY_NAME, giving the contact's display name.
• EMAIL_ADDRESS — from HZ_PARTIES.EMAIL_ADDRESS.
• CUST_ACCT_ID — the customer account identifier from the role record.
• ROLE_TYPE — the account role classification; per the predicate, always 'CONTACT' in returned rows. This is the column most commonly searched for as "role_type".
• CUST_ACCT_SITE_ID — the account site associated with the role.
• RESPONSIBILITY_TYPE — the responsibility assigned to the contact role (for example, a functional or administrative designation).
• PRIMARY_FLAG — indicates whether the responsibility is the primary one for the contact.
• STATUS — the relationship status, derived from HZ_RELATIONSHIPS.STATUS.

Common Use Cases and Queries

Typical usage involves retrieving contact rosters for a given customer account, or locating contacts by responsibility. A representative query:

SELECT party_id, name, email_address, cust_acct_id, responsibility_type, primary_flag, status FROM okx_cust_role_resp_v WHERE cust_acct_id = :acct_id AND status = 'A';

To identify the primary contact for an account:

SELECT name, email_address, responsibility_type FROM okx_cust_role_resp_v WHERE cust_acct_id = :acct_id AND primary_flag = 'Y';

Because ROLE_TYPE is fixed to 'CONTACT' by the view definition, filtering on role_type is redundant but is sometimes retained in ad hoc SQL for readability. Integration developers should be aware that the view is read-only, constrained by the EXISTS clause on HZ_CUST_ACCT_SITES, and excludes relationship rows not marked USER_ENTERED — factors that can cause accounts visible elsewhere in TCA to be absent from this projection.