Results for “end_customer_id”

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

Overview

The view APPS.OE_AK_END_CUS_V is a lightweight Oracle E-Business Suite database object owned by the APPS schema and classified under the Order Management (ONT) product family. Its documented purpose is to support the defaulting of the End Customer attribute during order capture and related Order Management processing. In EBS releases 12.1.1 and 12.2.2, the End Customer field on an order or order line frequently requires a value derived from a valid customer account, and this view provides the lookup source that the Order Management defaulting framework (the "AK" / attribute defaulting infrastructure) consults when populating that attribute.

Rather than returning a full customer record, the view exposes a single column, END_CUSTOMER_ID, which is the identifier used throughout the Order Management data model to reference an end customer. This narrow projection makes the view inexpensive to query and ideal for validation and defaulting logic. A user searching on end_customer_id is typically attempting to trace which customer accounts are eligible to serve as an end customer, or to join order data back to HZ_CUST_ACCOUNTS for reporting.

Underlying Base Objects

The documented view text is straightforward:

SELECT CUST_ACCOUNT_ID
FROM HZ_CUST_ACCOUNTS
WHERE STATUS = 'A'

The single referenced base object is HZ_CUST_ACCOUNTS (accessed through an APPS synonym). HZ_CUST_ACCOUNTS is the core Trading Community Architecture (TCA) table that stores customer account records, keyed by CUST_ACCOUNT_ID. The view applies one filter, STATUS = 'A', restricting output to accounts whose status is Active. Inactive accounts are therefore excluded from defaulting and validation, which prevents users from assigning a dormant or closed customer account as an end customer.

Because the view is defined solely over HZ_CUST_ACCOUNTS, it does not itself store data; it is a runtime projection. Any change to the status of a customer account is immediately reflected in subsequent queries against the view without additional synchronization.

Key Columns

• END_CUSTOMER_ID — The only column exposed by the view. It is populated from HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID and represents the unique identifier of an active customer account eligible for use as an end customer. Consumers of this view treat END_CUSTOMER_ID as a foreign key into the TCA customer account model.

No descriptive attributes such as customer name, account number, or party name are projected. Callers requiring those values must join the view back to HZ_CUST_ACCOUNTS or to related TCA objects such as HZ_PARTIES.

Common Use Cases and Queries

Typical scenarios include defaulting the end customer on an order line, validating a user-supplied end customer value, and reporting on orders by end customer. A simple validation query confirms whether a given account is an eligible end customer:

SELECT end_customer_id
FROM   oe_ak_end_cus_v
WHERE  end_customer_id = :p_cust_account_id;

To enrich the identifier with descriptive information for reporting, join to the base table and party:

SELECT v.end_customer_id,
       ca.account_number,
       hp.party_name
FROM   oe_ak_end_cus_v v,
       hz_cust_accounts  ca,
       hz_parties        hp
WHERE  ca.cust_account_id = v.end_customer_id
AND    hp.party_id        = ca.party_id;

For LOV-style defaulting, the view can be combined with HZ_CUST_ACCOUNTS and HZ_CUST_ACCT_SITES_ALL to present active accounts as selectable end customers. Because the view embeds the active-status restriction, application logic that relies on it automatically enforces the same eligibility rule documented for Order Management end-customer defaulting.