Search Results credit_analyst_id

Overview

The APPS.CSC_CUST_PROFILE_CREDIT_V view is a Customer Care (CSC) reporting object that consolidates customer credit profile and credit account attributes into a single, denormalized projection. Its primary role is to support credit management inquiries, customer care dashboards, and integration extract routines where a flattened view of credit risk, terms, collector, and analyst assignments is required for a given customer account. Because it joins the customer profile, the customer account header, standard terms, payment terms, and the collector master, it eliminates the need for reporting tools and downstream integrations to reconstruct these relationships individually.

The view is especially relevant to questions concerning credit_analyst_id, which is exposed directly as a column. Analysts searching for this attribute can obtain the credit analyst assignment for a customer profile without traversing the base profile table directly, alongside the associated collector, risk code, credit rating, and hold status for contextual interpretation.

Underlying Base Objects

The view text identifies five documented base objects, all owned under the APPS synonyms or views as listed in the ETRM 12.2.2 metadata:

• HZ_CUSTOMER_PROFILES (aliased CUST_PROFILE) — the driving table supplying credit profile attributes such as RISK_CODE, CREDIT_RATING, TOLERANCE, CLEARING_DAYS, NEXT_CREDIT_REVIEW_DATE, CREDIT_HOLD, and CREDIT_ANALYST_ID.
• HZ_CUST_ACCOUNTS (aliased CUST_ACCT) — provides account-level attributes including PAYMENT_TERM_ID, DEPOSIT_REFUND_METHOD, CREDIT_CLASSIFICATION_CODE, and the write-off amounts.
• RA_TERMS (aliased STD_TERMS) — the standard terms referenced by the profile, joined with an outer join (+) and constrained by active date ranges.
• AR_COLLECTORS (aliased C) — supplies the collector name associated with CUST_PROFILE.COLLECTOR_ID.
• RA_TERMS_VL (aliased PAY_TERMS) — the payment terms lookup used for the account's payment term name.

The join between HZ_CUSTOMER_PROFILES and HZ_CUST_ACCOUNTS is on CUST_ACCOUNT_ID. Standard terms are outer-joined, while the RA_TERMS_VL join is referenced in the projection.

Key Columns

• CREDIT_ANALYST_ID — identifier of the assigned credit analyst for the customer profile; the attribute most frequently queried from this view.
• COLLECTOR_ID / C.NAME — the collector identifier and collector name.
• RISK_CODE, CREDIT_RATING, PROFILE_CLASS_ID — credit risk classification attributes.
• RESTRICTION_LIMIT_AMOUNT, TOLERANCE — credit limit and tolerance thresholds.
• CLEARING_DAYS, INTEREST_PERIOD_DAYS, PAYMENT_GRACE_DAYS, DISCOUNT_GRACE_DAYS — credit control timing attributes.
• NEXT_CREDIT_REVIEW_DATE — scheduled credit review date.
• CREDIT_HOLD, STATUS — current hold and profile status flags.
• STANDARD_TERMS / STD_TERMS.NAME and PAYMENT_TERM_ID / PAY_TERMS.NAME — standard and payment terms references.
• OVERRIDE_TERMS, DISCOUNT_TERMS, INTEREST_CHARGES, CREDIT_CHECKING — Y/N flags decoded to YES/NO.
• WRITE_OFF_PAYMENT_AMOUNT, WRITE_OFF_AMOUNT, CREDIT_CLASSIFICATION_CODE, DEPOSIT_REFUND_METHOD — account-level credit attributes.
• ATTRIBUTE1–15, ATTRIBUTE_CATEGORY — descriptive flexfield context and segments on the profile.

Common Use Cases and Queries

Typical use cases include credit review reporting, collector and analyst workload analysis, and integration extracts feeding external credit systems. A common query retrieves the credit analyst and collector for a specific account:

• SELECT cust_account_profile_id, cust_account_id, credit_analyst_id, collector_id, c.name AS collector_name, risk_code, credit_rating, next_credit_review_date FROM apps.csc_cust_profile_credit_v WHERE cust_account_id = :cust_account_id;
• SELECT credit_analyst_id, COUNT(*) FROM apps.csc_cust_profile_credit_v GROUP BY credit_analyst_id; — analyst workload distribution.
• SELECT cust_account_id, risk_code, restriction_limit_amount, credit_hold FROM apps.csc_cust_profile_credit_v WHERE credit_hold = 'Y'; — accounts currently on credit hold.

Because the view embeds a filter on standard terms active dates, queries that are sensitive to date-effective terms should account for this constraint.