Results for “end_customer_contact_id”

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

Overview

OE_AK_END_CUS_CONT_V is a read-only view owned by the APPS schema in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It belongs to the ONT (Order Management) product family and is classified as a VALID database object in the ETRM repository. Its documented purpose is the defaulting of the End Customer Contact on order management transactions — that is, supplying the identifier of the contact associated with an end customer when Order Management needs to populate that value on an order, line, or related entity.

In the Oracle Order Management data model, the "end customer" differs from the sold-to or bill-to party. The end customer is the ultimate consumer or recipient of the goods, and the associated contact is often required for downstream processing, fulfillment, or reporting. Rather than storing this information directly, the view derives the appropriate contact role identifier from the Trading Community Architecture (TCA) tables. This makes OE_AK_END_CUS_CONT_V a lightweight, query-driven component used by the Order Management defaulting framework or by custom reporting and integration logic that must resolve an end customer contact ID.

Underlying Base Objects

The ETRM metadata documents that the view is defined over the following base objects, accessed through public synonyms in the APPS schema:

• HZ_CUST_ACCOUNTS — the TCA customer account header, representing the customer account entity.
• HZ_CUST_ACCOUNT_ROLES — the roles (such as CONTACT) assigned to a customer account.
• HZ_PARTIES — the master party records, both for the account holder and for the related party.
• HZ_RELATIONSHIPS — the TCA relationship records that link parties to one another.

The view text joins these objects to return the customer account role identifier of the contact party. The join path links a customer account role to a relationship where both the subject and object tables are HZ_PARTIES, aligns the subject party with the account's party, restricts the role type to 'CONTACT', and matches the object party to the customer account. In effect, the view returns only those contact roles that are valid end customer contacts within the TCA relationship framework.

Key Columns

The documented column list contains a single exposed column:

• END_CUSTOMER_CONTACT_ID — the identifier returned by the view, sourced from ACCT_ROLE.CUST_ACCOUNT_ROLE_ID. Despite its descriptive alias, the value is technically the HZ_CUST_ACCOUNT_ROLES primary key for the matched contact role. Consumers should treat it as the contact role ID used for defaulting the end customer contact.

Because the view projects only this column, it functions as a lookup or filter view rather than a general-purpose reporting source. Any additional contact attributes (name, email, phone) must be obtained by joining the returned ID back to HZ_CUST_ACCOUNT_ROLES and the associated HZ_PARTIES or contact point tables.

Common Use Cases and Queries

The primary use case is defaulting the end customer contact during order entry or order import. Application logic calls the view with the relevant customer account context and receives the contact role ID to populate the order attribute. A typical query selects the identifier for a given account:

• SELECT end_customer_contact_id FROM oe_ak_end_cus_cont_v;
• SELECT end_customer_contact_id FROM oe_ak_end_cus_cont_v WHERE end_customer_contact_id IN (SELECT cust_account_role_id FROM hz_cust_account_roles WHERE cust_account_id = :p_account_id);

Integration and reporting scenarios use the view to validate that a contact role is legitimately linked to an end customer through TCA relationships before assigning it to an order. When diagnosing defaulting failures, developers frequently query the view to confirm whether a qualifying contact role exists for the customer account in question. Because the view returns only IDs, troubleshooting usually extends to joining the result back to HZ_PARTIES for contact names and to HZ_CUST_ACCOUNT_ROLES for role status. Note that the view is informational and read-only; end customer contact defaulting rules should be configured through supported Order Management setup rather than by modifying the view.