Search Results cust_acct

Overview

APPS.QA_CUSTOMERS_LOV_V is a database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is designed to serve as a List of Values (LOV) source for customer accounts, presenting a consolidated, name-resolved list of customers drawn from the Oracle Trading Community Architecture (TCA) model. The view answers the common search term cust_acct by surfacing the CUST_ACCOUNT_ID and providing a human-readable party name and account number for each record.

Unlike transactional customer tables, this view is intentionally read-only and denormalized for presentation purposes. It joins the base customer account record with its owning party record so that both the account-level identifier and the party-level descriptive name are available in a single query. Because it carries a literal discriminator value ('CUSTOMER'), the view is suitable for use in selection dialogs and pickers where a consistent label must accompany each returned identifier.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over two referenced base objects, both exposed through APPS synonyms:

• HZ_CUST_ACCOUNTS (SYNONYM) — aliased as cust_acct; supplies the account-level attributes.
• HZ_PARTIES (SYNONYM) — aliased as party; supplies the party-level descriptive attributes.

The join condition is cust_acct.party_id = party.party_id, an inner equijoin on the party identifier. Because only records with a matching party row are returned, orphaned or unlinked customer accounts are excluded. The view inherits the security and access characteristics of the underlying synonyms rather than maintaining any storage of its own.

Key Columns

• CUST_ACCOUNT_ID — Primary identifier of the customer account (from HZ_CUST_ACCOUNTS); the value typically returned to a calling form or interface.
• PARTY_ID — Identifier of the associated party (from HZ_PARTIES); useful when the transaction must operate at party level rather than account level.
• PARTY_NAME — The display name of the party, providing the readable label used in LOV presentation.
• ACCOUNT_NUMBER — The customer account number, a common business key used for reconciliation and reference.
• STATUS — The account status flag from HZ_CUST_ACCOUNTS; used by LOV consumers to filter active versus inactive accounts.
• 'CUSTOMER' — A literal discriminator column producing the constant string 'CUSTOMER' for every row, enabling uniform labeling in LOV contexts.

Common Use Cases and Queries

The view is most frequently consumed in custom forms, concurrent programs, and reporting queries that require a customer-account selection list. A typical projection is shown below.

• LOV population: SELECT cust_account_id, party_name, account_number FROM apps.qa_customers_lov_v WHERE status = 'A' ORDER BY party_name;
• Name lookup by account number: SELECT party_name, party_id FROM apps.qa_customers_lov_v WHERE account_number = :account_number;
• Party resolution for an account: SELECT party_id FROM apps.qa_customers_lov_v WHERE cust_account_id = :cust_account_id;

Because the view abstracts the TCA join, report developers avoid re-encoding the party/account relationship. Care should be taken to filter on STATUS where only active customers are relevant, and to treat the returned identifier as the account key rather than the party key unless PARTY_ID is explicitly required.