Search Results next_credit_review_date




Overview

AST_CUST_PROFILE_CREDIT_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined under the AST (TeleSales) product. It consolidates customer credit profile information held against customer accounts in Oracle Receivables with related setup data such as payment terms, collectors, and lookup meanings. The view is read-only and is intended for query and reporting purposes, exposing a denormalized, human-readable projection of credit attributes rather than maintaining data of its own. In EBS 12.1.1 and 12.2.2 it sits on the Trading Community Architecture (TCA) model, drawing from HZ_CUSTOMER_PROFILES and HZ_CUST_ACCOUNTS, and is typically consumed by TeleSales credit dashboards, collections inquiries, and custom reports that need credit rating, credit limits, and customer profile detail in a single result set.

Underlying Base Objects

The view is defined over several documented base objects: HZ_CUSTOMER_PROFILES (SYNONYM), HZ_CUST_ACCOUNTS (SYNONYM), RA_TERMS (SYNONYM), RA_TERMS_VL (VIEW), AR_COLLECTORS (SYNONYM), and FND_LOOKUPS (VIEW). The FND_GLOBAL package is also referenced in the metadata, consistent with a profile-driven view that resolves session context. HZ_CUSTOMER_PROFILES supplies the credit profile segment, including CREDIT_RATING, RISK_CODE, PROFILE_CLASS_ID, restriction and tolerance values, clearing days, and the flexible ATTRIBUTE1 through ATTRIBUTE15 columns. HZ_CUST_ACCOUNTS provides account-level credit attributes such as CREDIT_CLASSIFICATION_CODE, WRITE_OFF_AMOUNT, WRITE_OFF_PAYMENT_AMOUNT, DEPOSIT_REFUND_METHOD, and PAYMENT_TERM_ID. RA_TERMS joins as the standard terms source, while RA_TERMS_VL supplies the translated payment term name. AR_COLLECTORS provides the collector name, and FND_LOOKUPS is joined multiple times (alias LK1–LK4) to translate coded values into descriptive meanings.

Key Columns

Joined lookups require accurate FND_LOOKUPS setup; missing or inactive lookup values will cause the corresponding MEANING column to return null.

Common Use Cases and Queries

Typical scenarios include retrieving the credit rating and credit limit for a customer account, listing accounts by collector or credit analyst, identifying profiles with an overdue NEXT_CREDIT_REVIEW_DATE, and feeding credit data into TeleSales or collections reporting. A sample query retrieving credit rating by account:

SELECT cust_account_id, credit_rating, restriction_limit_amount, risk_code, next_credit_review_date FROM apps.ast_cust_profile_credit_v WHERE cust_account_id = :p_account_id;

A second query lists accounts by collector with their active credit classification:

SELECT c.name collector, v.credit_rating, v.credit_classification_code, v.risk_code FROM apps.ast_cust_profile_credit_v v, apps.ar_collectors c WHERE v.collector_id = c.collector_id AND v.status = 'A' ORDER BY c.name;

Because the view embeds SYSDATE comparisons and NVL logic against RA_TERMS start and end dates, results are current as of query execution and best suited to point-in-time or scheduled reporting rather than historical trend analysis.