Search Results override_terms

Overview

JTF_CUSTOMER_PROFILES_V is a CRM Foundation (JTF) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents credit profile information associated with customer accounts and customer account sites, and is documented as retrieving credit information for customer accounts and their associated account sites. The view functions as a reporting and integration layer over the customer profile data that supports credit management activities within the Receivables and Order Management flows, most notably credit checking, credit holds, dunning, statements, and collections.

Because it exposes a single flat row per customer account profile (and, where applicable, per site use), the view is convenient for ad-hoc queries, custom reports, and interface extracts without requiring the caller to join multiple Receivables and CRM tables. It is registered as a VALID object in the APPS schema and appears with the standard EBS audit and descriptive flexfield columns.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, the only documented referenced base object is the synonym HZ_CUSTOMER_PROFILES. The view text selects a substantial column list — including ROWID — directly from that customer profile source, meaning JTF_CUSTOMER_PROFILES_V is effectively a pass-through projection over the customer profiles data rather than a multi-table join. The profile records are keyed by CUST_ACCOUNT_PROFILE_ID, with foreign key relationships carried through CUST_ACCOUNT_ID and SITE_USE_ID, allowing each row to be resolved to either a customer account or a specific account site.

Key Columns

• CUST_ACCOUNT_PROFILE_ID — primary key of the customer profile record.
• CUST_ACCOUNT_ID — the customer account to which the profile belongs.
• SITE_USE_ID — the account site use, when the profile is defined at site level.
• CREDIT_RATING — the credit rating assigned to the customer account or site; this is the column most relevant to the search term "credit_rating".
• RISK_CODE — risk classification associated with the profile.
• CREDIT_CHECKING — flag indicating whether credit checking is enabled.
• CREDIT_HOLD — indicates whether the account is currently on credit hold.
• STATUS / ACCOUNT_STATUS — status of the profile and of the underlying account.
• COLLECTOR_ID / CREDIT_ANALYST_ID — collector and credit analyst responsible for the profile.
• TOLERANCE, PERCENT_COLLECTABLE, NEXT_CREDIT_REVIEW_DATE — credit limit tolerance, collectability percentage, and next scheduled review.
• STANDARD_TERMS / OVERRIDE_TERMS / DISCOUNT_TERMS — payment terms applied to the profile.
• DUNNING_LETTERS, DUNNING_LETTER_SET_ID, SEND_STATEMENTS, CREDIT_BALANCE_STATEMENTS — dunning and statement preferences.
• INTEREST_CHARGES, INTEREST_PERIOD_DAYS, PAYMENT_GRACE_DAYS, DISCOUNT_GRACE_DAYS, CLEARING_DAYS — finance charge and grace period controls.
• STALLMENT_CYCLE_ID (STATEMENT_CYCLE_ID), PROFILE_CLASS_ID, GROUPING_RULE_ID — statement cycle, profile class, and grouping rule references.
• ATTRIBUTE1–15, GLOBAL_ATTRIBUTE1–18, JGZZ_ATTRIBUTE1–15 — descriptive and global flexfield columns.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN and concurrent program columns (PROGRAM_APPLICATION_ID, PROGRAM_ID, REQUEST_ID, WH_UPDATE_DATE).

Common Use Cases and Queries

Typical uses include credit exposure reporting, identifying accounts on credit hold, and auditing credit ratings and risk codes across accounts or sites. A simple lookup by credit rating is shown below.

• List accounts with a given credit rating:

  SELECT cust_account_id, site_use_id, credit_rating, risk_code, credit_hold
  FROM   apps.jtf_customer_profiles_v
  WHERE  credit_rating = :credit_rating;

• Identify accounts currently on credit hold:

  SELECT cust_account_id, profile_class_id, credit_hold, account_status
  FROM   apps.jtf_customer_profiles_v
  WHERE  credit_hold = 'Y';

• Join to customer account details for reporting:

  SELECT p.cust_account_id, p.credit_rating, p.risk_code, hcp.customer_name
  FROM   apps.jtf_customer_profiles_v p,
         apps.hz_cust_accounts hca,
         apps.hz_parties hcp
  WHERE  p.cust_account_id = hca.cust_account_id
  AND    hca.party_id = hcp.party_id;

Because the view preserves flexfield attributes and site-level key columns, it is well suited to custom extracts and to integration endpoints that require a consolidated view of a customer's credit profile.