Results for “account_name”

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

Overview

ASO_PVT_CUST_ACCOUNTS_V is a database view owned by the APPS schema in Oracle E-Business Suite, belonging to the ASO - Order Capture product family. It presents a filtered list of active customer accounts sourced from Oracle Receivables' customer master data, and its primary role is to expose only those accounts that are currently valid based on their activation and termination dates. The view is consumed internally by Order Capture logic, particularly the private (PVT) API layer, to validate whether a customer account may be referenced during order entry, order import, or related integration processing.

The name prefix "ASO_PVT" indicates that this is a private view, not exposed through a supported public API. Oracle documents such private views solely for DBA and technical reference; customers and integrators should treat the view as internal and use supported public APIs for customer validation wherever possible. Its value lies in providing a single, self-filtering data source that reflects the effective status of a customer account on the current system date.

Underlying Base Objects

According to the documented view text, ASO_PVT_CUST_ACCOUNTS_V is defined over the HZ_CUST_ACCOUNTS table, accessed in the APPS schema through the HZ_CUST_ACCOUNTS synonym. HZ_CUST_ACCOUNTS is the Trading Community Architecture (TCA) base table that stores customer account information, including account numbers, names, status, and lifecycle dates. The view does not join to any additional tables; it applies a row-level filter and projects a small subset of columns directly from that base table.

The filtering condition restricts the result set in three ways. First, only rows where STATUS equals 'A' (Active) are retained. Second, the effective activation date—calculated as NVL(ACCOUNT_ACTIVATION_DATE, SYSDATE)—must be less than or equal to the current date. Third, the effective termination date—calculated as NVL(ACCOUNT_TERMINATION_DATE, SYSDATE)—must be greater than or equal to the current date. The TRUNC function removes time components, so comparisons occur at day granularity. Because the filters reference SYSDATE, the view's content changes between invocations based on the database server date.

Key Columns

The view exposes four significant columns, all inherited from HZ_CUST_ACCOUNTS:

• CUST_ACCOUNT_ID — The unique identifier (primary key) of the customer account record. This value is the standard foreign key used throughout Order Management, Receivables, and TCA-related tables.
• PARTY_ID — The identifier of the party (person or organization) that owns the account, linking the account to the TCA party registry.
• ACCOUNT_NUMBER — The externally visible, user-defined account number associated with the customer account.
• ACCOUNT_NAME — The descriptive name of the account, typically used for display and search purposes in order entry screens.

Although ACCOUNT_ACTIVATION_DATE and ACCOUNT_TERMINATION_DATE drive the view's filtering logic, they are not projected as output columns; they are referenced only in the WHERE clause.

Common Use Cases and Queries

The view is commonly used whenever a business process requires confirmation that a customer account is eligible for transaction as of today. Typical scenarios include validating an account before attaching it to an order, resolving account identifiers during order import, and building diagnostic or reconciliation reports of active accounts.

A typical query retrieves the active accounts visible to the view:

• SELECT cust_account_id, party_id, account_number, account_name FROM aso_pvt_cust_accounts_v WHERE account_number = :p_account_number;
• SELECT cust_account_id, account_name FROM aso_pvt_cust_accounts_v ORDER BY account_name;

Because the view already enforces STATUS and date-range logic, callers do not need to repeat those predicates. When debugging why an expected account is missing, technicians should inspect the base HZ_CUST_ACCOUNTS record directly for its status, activation date, and termination date, since any of these three conditions can exclude the row. Given its private designation, the view should be referenced only for investigation and diagnostics; production integrations should use supported customer APIs such as the TCA or Order Capture public interfaces.