Search Results account_termination_date




Overview
Explore in AI Chat

Overview

APPS.ASO_PVT_CUST_ACCOUNTS_V is a reporting and validation view in the Oracle E-Business Suite Order Management and Customer Relationship Management schema. It exposes a filtered, point-in-time subset of customer accounts held in the Oracle Trading Community Architecture (TCA) model, and is owned by the APPS schema, making it accessible to any responsibility or concurrent program that runs with APPS-level privileges. The view is designed to answer a single business question: which customer accounts are currently active and eligible for transactional use today?

The view is relevant to the "account_activation_date" search term because that column is a core predicate of the view definition. Records are only returned when the account status is 'A' (active) and when the activation and termination date windows enclose the current system date. This makes ASO_PVT_CUST_ACCOUNTS_V a convenient, self-maintaining filter rather than a static snapshot.

Underlying Base Objects

The view is defined over a single base object, HZ_CUST_ACCOUNTS, resolved through a synonym. HZ_CUST_ACCOUNTS is the TCA table that stores customer account records, linking a customer account to a party (organization or person) and holding account numbers, account names, status, and the activation and termination date attributes. Because the view references only this table, it introduces no joins and therefore no fan-out or duplicate-row risk; each row in the view corresponds to exactly one row in HZ_CUST_ACCOUNTS.

The view is described in the ETRM metadata as a private (PVT) view, which typically indicates it is used internally by Oracle's Application Service/Order Capture logic rather than being a documented public interface. Customers and integrators should therefore treat it as a stable but unsupported dependency and validate its continued availability across patches.

Key Columns

  • CUST_ACCOUNT_ID — Primary key of the customer account. This is the value referenced by downstream transactional tables and is the join key for order, invoice, and agreement data.
  • PARTY_ID — Identifier of the owning party in HZ_PARTIES. Enables aggregation of multiple accounts under a single customer or organization.
  • ACCOUNT_NUMBER — The user-facing account number used in communications, statements, and searches.
  • ACCOUNT_NAME — The descriptive account name, commonly used in reports and pick lists.
  • ACCOUNT_ACTIVATION_DATE — Part of the base table but not projected by the view; it is consumed only inside the WHERE clause. Records with a null activation date are treated as active from the beginning of time via NVL(account_activation_date, sysdate).
  • ACCOUNT_TERMINATION_DATE — Similarly used only as a predicate, ensuring accounts whose termination date has passed are excluded.

Note that only four columns are projected. The date columns that drive the filter are not exposed, so consumers seeking activation or termination dates must query HZ_CUST_ACCOUNTS directly.

Common Use Cases and Queries

Typical uses include populating customer account list-of-values, restricting order entry to currently valid accounts, and producing active-account counts for reporting.

  • Listing all currently active customer accounts: SELECT cust_account_id, party_id, account_number, account_name FROM apps.aso_pvt_cust_accounts_v;
  • Counting active accounts per party: SELECT party_id, COUNT(*) FROM apps.aso_pvt_cust_accounts_v GROUP BY party_id;
  • Joining to orders for transactional reporting: SELECT v.account_number, o.order_number FROM apps.aso_pvt_cust_accounts_v v, oe_order_headers_all o WHERE v.cust_account_id = o.sold_to_org_id;
  • Validating a specific account before use: SELECT account_name FROM apps.aso_pvt_cust_accounts_v WHERE account_number = :p_number;

Because the date comparison is evaluated at query time with TRUNC(SYSDATE), the result set changes daily without any data modification, which is precisely the behavior expected of an activation-date-driven account filter.