Search Results subcategory_code

Overview

AST_CUST_ACCT_BALI_V is a TeleSales (AST) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes customer account records from the Receivables/HZ customer model in a form suited to TeleSales and Collections-style inquiries, presenting account identity, status, classification, balances, and a set of lifecycle dates on a single row per customer account. Because the view joins the customer account table to the AR_LOOKUPS status codes, the cryptic status code stored on the account is surfaced alongside its human-readable description, allowing reporting tools, concurrent programs, and custom extensions to display account standing without additional decoding. The view is documented as VALID and its column list, including ACCOUNT_ACTIVATION_DATE, is fixed at the object level; the view text selects a defined column sequence directly from the base tables rather than deriving values, so it behaves as a filtered, denormalized projection of HZ_CUST_ACCOUNTS.

Underlying Base Objects

The view is defined over two documented referenced objects:

• HZ_CUST_ACCOUNTS (SYNONYM) — the primary source of all account columns. The view aliases this object as CUST_ACCT and selects its ROWID and identifying, classification, balance, and date attributes.
• AR_LOOKUPS (VIEW) — joined to HZ_CUST_ACCOUNTS on STATUS = LOOKUP_CODE with LOOKUP_TYPE = 'CODE_STATUS', providing the ACCOUNT_STATUS_DESCRIPTION column via the lookup DESCRIPTION field.

The join is an inner equijoin on status code and lookup type, meaning an account is returned only when a matching CODE_STATUS lookup row exists. No ORG_ID-based multitenancy predicate is added by the view itself; the ORG_ID column is simply projected from HZ_CUST_ACCOUNTS. Several positions in the SELECT list are populated with literal NULL placeholders (including CATEGORY_CODE, THIRD_PARTY_FLAG, COMPETITOR_FLAG, and others in the excerpted text), so these columns exist in the view definition but carry no data.

Key Columns

• CUST_ACCOUNT_ID — primary identifier of the customer account; the join key to related AR and HZ objects.
• PARTY_ID / ACCOUNT_NUMBER / ORIG_SYSTEM_REFERENCE — party linkage, the account number, and the originating source system reference used in integrations.
• STATUS / ACCOUNT_STATUS_DESCRIPTION — the CODE_STATUS lookup code and its decoded description.
• CUSTOMER_TYPE / CUSTOMER_CLASS_CODE / SUBCATEGORY_CODE / TAX_CODE — classification and tax attributes of the account.
• CURRENT_BALANCE — the account's current balance, relevant to credit and collections review in TeleSales.
• ACCOUNT_ESTABLISHED_DATE / ACCOUNT_ACTIVATION_DATE / SUSPENSION_DATE / ACCOUNT_TERMINATION_DATE — the account lifecycle date set. ACCOUNT_ACTIVATION_DATE records when the account was activated and is the column matching the search term.
• HIGH_PRIORITY_INDICATOR / HIGH_PRIORITY_REMARKS — priority flagging used by agents.
• ATTRIBUTE1–ATTRIBUTE20 and ATTRIBUTE_CATEGORY — the standard EBS descriptive flexfield columns, available for site-specific extensions.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical scenarios include agent-facing account searches, activation-date reporting, and status-driven customer lists. A query targeting the search term takes the form:

• SELECT cust_account_id, account_number, account_name, account_activation_date, current_balance FROM apps.ast_cust_acct_bali_v WHERE account_activation_date >= :p_from_date AND account_activation_date < :p_to_date;
• SELECT account_number, account_status_description, current_balance FROM apps.ast_cust_acct_bali_v WHERE status = 'A' ORDER BY current_balance DESC;
• SELECT cust_account_id, party_id, account_established_date, account_activation_date FROM apps.ast_cust_acct_bali_v WHERE org_id = :p_org_id AND account_activation_date IS NULL;

Because the view performs no org-level filtering, queries should apply an explicit ORG_ID predicate under multitenant operating units, and should account for the NULL placeholder columns when mapping to downstream structures.