Results for “csc_prof_check_ratings_v”

16 results




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

Overview

CSC_PROF_CHECK_RATINGS_V is an Oracle E-Business Suite view owned by the APPS schema and registered as VALID in both 12.1.1 and 12.2.2. It belongs to the CSC – Customer Care product family and is a thin projection over the base table CSC_PROF_CHECK_RATINGS. As its name implies, it exposes check-rating definitions—the grading bands, rating codes, color codes, and numeric ranges used to score and classify customer profile check results.

The view is documented as the data source for the Profile Checks tab of the Customer Profile Setup form. In that capacity it supplies the lookup values displayed when a user defines scoring bands for a profile check. Because it is a view rather than a table, it carries no independent storage; it also carries no business logic in its own right, which makes it a stable, low-risk integration point for reporting and inbound/outbound interfaces.

Underlying Base Objects

The ETRM metadata documents a single referenced base object: CSC_PROF_CHECK_RATINGS, exposed through a synonym. The view definition is a straightforward SELECT of fourteen columns plus the ROWID pseudo-column, aliased as ROW_ID, and terminating with FROM CSC_PROF_CHECK_RATINGS. There are no joins, no aggregations, and no WHERE predicates. This matters for extension planning: any row present in the base table is visible through the view, and the view text contains no schema-qualification, so resolution depends on standard APPS synonym resolution.

For the column RANGE_HIGH_VALUE, the user's search term, the value is taken verbatim from the base table with no transformation. The same applies to RANGE_LOW_VALUE, so range logic stored on the table is preserved exactly as authored.

Key Columns

Because RANGE_HIGH_VALUE and RANGE_LOW_VALUE define band boundaries, the rows must be ordered and interpreted carefully so that scoring intervals remain contiguous and non-overlapping.

Common Use Cases and Queries

Typical uses include audit extracts of scoring bands, validation that no bands overlap, and diagnostic review of seeded versus customized ratings.

  • List all bands for a given check, ordered by range.
  • Identify multi-band checks where RANGE_HIGH_VALUE is populated.
  • Compare seeded and user-defined ratings across environments.

Sample SQL:

SELECT CHECK_RATING_ID, CHECK_ID, CHECK_RATING_GRADE, RATING_CODE, COLOR_CODE, RANGE_LOW_VALUE, RANGE_HIGH_VALUE, SEEDED_FLAG FROM APPS.CSC_PROF_CHECK_RATINGS_V WHERE CHECK_ID = :p_check_id ORDER BY RANGE_LOW_VALUE, RANGE_HIGH_VALUE;

Overlap detection:

SELECT a.CHECK_ID, a.CHECK_RATING_ID, a.RANGE_HIGH_VALUE AS A_HIGH, b.CHECK_RATING_ID AS B_ID, b.RANGE_LOW_VALUE AS B_LOW FROM APPS.CSC_PROF_CHECK_RATINGS_V a, APPS.CSC_PROF_CHECK_RATINGS_V b WHERE a.CHECK_ID = b.CHECK_ID AND a.CHECK_RATING_ID < b.CHECK_RATING_ID;

For high-volume extracts, select only the needed columns rather than SELECT *, since ROW_ID and audit columns add no analytical value.