Results for “ar_customer_accounts_ce”

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

Overview

AR_CUSTOMER_ACCOUNTS_CE is an APPS-owned database view in the Oracle E-Business Suite Receivables (AR) module. Per the ETRM documentation, its definition is explicitly designated as Release 11.5 Only, yet the view remains present, VALID, and referenced in Release 12.1.1 and 12.2.2 environments, where it functions primarily as a legacy compatibility and reporting artifact. The "CE" suffix denotes a "Customer Entry" or "Customer Extract" style presentation designed to surface consolidated customer account information — balances, exposure, and credit metrics — in a single queryable structure.

The view presents one row per customer account combined with currency context, exposing computed collections metrics such as Days Sales Outstanding (DSO), past-due invoice counts, overall and order credit limits, and credit availability. In practice it supports receivables reporting, collections analysis, credit exposure monitoring, and downstream integration extracts where a denormalized customer-level snapshot is preferable to joining HZ_CUST_ACCOUNTS, HZ_CUSTOMER_PROFILES, and AR_PAYMENT_SCHEDULES manually.

Underlying Base Objects

The documented 12.2.2 metadata identifies the following referenced objects, resolved through APPS synonyms unless noted:

• HZ_CUST_ACCOUNTS — the primary customer account entity, supplying CUST_ACCOUNT_ID, ACCOUNT_NUMBER, and STATUS.
• HZ_PARTIES — supplies the party name (truncated to 50 bytes via SUBSTRB) as CUSTOMER_NAME.
• HZ_CUSTOMER_PROFILES — supplies the account status (CP.ACCOUNT_STATUS) and risk code.
• HZ_CUST_PROFILE_CLASSES — supplies the profile class name (CPC.NAME), which is the source of the PROFILE_CLASS column the user searched for.
• AR_COLLECTORS — supplies the collector name associated with the account.
• AR_PAYMENT_SCHEDULES — the transactional driver, providing amounts due, transaction dates, due dates, status, and class codes used in the DSO and balance aggregations.
• AR_SYSTEM_PARAMETERS — supplies system-level settings referenced in the DSO computation.
• HZP_CUST_PKG — a PL/SQL package invoked directly within the SELECT list to compute ARXVAMAI_OVERALL_CR_LIMIT and ARXVAMAI_ORDER_CR_LIMIT.

Key Columns

• CUSTOMER_ID / CUST_ACCOUNT_ID — the customer account identifier (CUST_ACCT.CUST_ACCOUNT_ID).
• CUSTOMER_NAME — the party name, truncated to 50 bytes.
• CUSTOMER_NUMBER — the account number.
• CUSTOMER_STATUS / ACCOUNT_STATUS — account status from the account and profile records respectively.
• PROFILE_CLASS — the profile class name derived from HZ_CUST_PROFILE_CLASSES via HZ_CUSTOMER_PROFILES; this is the column most relevant to the user's search on "profile_class".
• RISK_CODE — credit risk classification.
• COLLECTOR_NAME — assigned collector.
• DSO — computed Days Sales Outstanding, derived from outstanding amounts, credit terms days, and transaction/term dates.
• CURRENCY_CODE — invoice currency context (PS.INVOICE_CURRENCY_CODE).
• OVERALL_CREDIT_LIMIT / ORDER_CREDIT_LIMIT / CREDIT_AVAILABLE — credit exposure metrics; CREDIT_AVAILABLE is the overall limit less the sum of amount due remaining.
• PASTDUE_INVOICES — count of open items past their due date.
• BALANCE — aggregate of amount due remaining.

Common Use Cases and Queries

Because PROFILE_CLASS is exposed directly, the view is commonly used to segment customers by profile class for credit and collections reporting:

• Listing accounts by profile class: SELECT customer_number, customer_name, profile_class FROM ar_customer_accounts_ce WHERE profile_class = :p_class;
• Credit exposure review: SELECT customer_number, currency_code, overall_credit_limit, credit_available, balance FROM ar_customer_accounts_ce WHERE credit_available < 0;
• Collections prioritization: SELECT customer_number, collector_name, dso, pastdue_invoices FROM ar_customer_accounts_ce WHERE pastdue_invoices > 0 ORDER BY dso DESC;

Given the view's Release 11.5 designation and its reliance on HZP_CUST_PKG and heavy aggregation, it should be treated as read-only and performance-sensitive. Where possible, confirm against the R12 native credit and collections views before depending on it in new 12.1.1 / 12.2.2 customizations.