Search Results subcategory_code

Overview

CSC_ACCOUNT_OVERVIEW_V is an APPS-owned database view in the Customer Care (CSC) product family of Oracle E-Business Suite, available in both the 12.1.1 and 12.2.2 releases. The view retrieves an overview of a customer account, presenting a single denormalized row that consolidates account-level attributes from the Oracle Receivables customer model together with descriptive lookup values. It is a reporting and integration convenience object rather than a transactional entity; no data is stored at the view level, and all values are derived at query time from the underlying base objects. The view is defined in the APPS schema and is documented with a VALID status in the ETRM repository.

Its principal advantage is that it eliminates the need for downstream reports, custom pages, and integration extracts to re-implement the joins and the multi-org security predicate that govern customer account access. Because it exposes both the raw code and the decoded meaning for several attributes, it is well suited to dashboards, extracts, and inquiry screens where readable output is required.

Underlying Base Objects

The documented base objects referenced by the view are AR_LOOKUPS (a view), HZ_CUST_ACCOUNTS (a synonym), and RA_TERMS_TL (a synonym). HZ_CUST_ACCOUNTS is the driving source of the account data, supplying identifiers, balances, dates, and the descriptive flexfield columns ATTRIBUTE1 through ATTRIBUTE20. AR_LOOKUPS is joined on the account STATUS column, restricted to LOOKUP_TYPE = 'CODE_STATUS', to obtain a decoded account status description via AR.DESCRIPTION. RA_TERMS_TL supplies the payment term name, joined on PAYMENT_TERM_ID = TERM_ID using an outer join and filtered by the session language through PAY_TERMS.LANGUAGE = USERENV('LANG'). The view also applies a multi-organization security predicate comparing ACCT.ORG_ID to the organization identifier derived from USERENV('CLIENT_INFO'), so that only accounts in the current operating unit context are returned.

Key Columns

The view exposes a broad set of account attributes. Identification columns include ROW_ID, CUST_ACCOUNT_ID, ORG_ID, PARTY_ID, ACCOUNT_NUMBER, and ORIG_SYSTEM_REFERENCE. Status and classification columns include STATUS, ACCOUNT_STATUS_DESC (the decoded status from AR_LOOKUPS), CUSTOMER_TYPE, and CUSTOMER_CLASS_CODE. The column SUBCATEGORY_CODE, the search term of interest, is surfaced directly from HZ_CUST_ACCOUNTS and carries the customer subcategory classification used for segmentation and reporting.

Financial and lifecycle columns include CURRENT_BALANCE, TAX_CODE, PAYMENT_TERM_ID, the derived payment term NAME, TAX_ROUNDING_RULE, DEPOSIT_REFUND_METHOD, and the WRITE_OFF_ADJUSTMENT_AMOUNT, WRITE_OFF_PAYMENT_AMOUNT, and WRITE_OFF_AMOUNT measures. Date and audit columns include ACCOUNT_ESTABLISHED_DATE, ACCOUNT_ACTIVATION_DATE, ACCOUNT_TERMINATION_DATE, SUSPENSION_DATE, and the standard CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN fields.

Common Use Cases and Queries

Typical scenarios include customer account inquiry, status and balance reporting, subcategory-driven segmentation, and extraction of account data into external systems.

• List accounts by subcategory: SELECT cust_account_id, account_number, account_name, subcategory_code, account_status_desc FROM csc_account_overview_v WHERE subcategory_code = :p_subcategory;
• Review account balances and payment terms: SELECT account_number, current_balance, name, tax_code FROM csc_account_overview_v WHERE current_balance > 0;
• Track account lifecycle dates: SELECT account_number, account_established_date, account_termination_date FROM csc_account_overview_v WHERE account_termination_date IS NOT NULL;

Because the view enforces the ORG_ID security predicate automatically, queries return only accounts visible in the current organization context. Note that the view exposes only the subset of columns documented above; additional account attributes require querying HZ_CUST_ACCOUNTS directly.