Results for “csc_prof_checks_vl”

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

Overview

CSC_PROF_CHECKS_VL is a Multi-Lingual Support (MLS) view owned by the APPS schema and shipped as part of the CSC – Customer Care product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the profile checks that are configured against a customer profile in the Customer Profile Setup form, specifically the records surfaced on the Profile Checks tab. A profile check represents a validation or scoring rule applied to customer data, such as a credit-grade threshold, rating threshold, or colour-code threshold, together with the input format expected from the user.

Because the object is a VL (view for language) rather than a physical table, it carries no independent data of its own. Instead, it presents translatable descriptive text from the translation table joined to non-translatable attributes held in the base table, filtered to the language of the current session. This makes the view the recommended access point for reporting, form personalisation, and integration code, since it automatically honours the runtime language environment and shields callers from having to write the MLS join predicate themselves.

The ETRM record lists the object with a status of VALID, confirming that the view is present and compiled in the shipped 12.2.2 file system. The view is date-effective and therefore also of interest to audit and configuration-review queries that need to reconstruct the historical state of profile check configuration.

Underlying Base Objects

The view is defined over two APPS synonyms, both ultimately resolving to tables in the CSC schema:

• CSC_PROF_CHECKS_B — the base table holding the non-translatable, or language-independent, attributes of each profile check, including identifiers, flags, thresholds, and WHO columns.
• CSC_PROF_CHECKS_TL — the translation table holding the language-dependent text for each check, principally CHECK_NAME and DESCRIPTION.

The two are joined on CHECK_ID, and the translation side is restricted by the predicate T.LANGUAGE = USERENV('LANG'). USERENV('LANG') returns the language code of the current session, so a user running with an English session sees English names and descriptions, while a user running with a French session sees French text where a translation exists. Because the join is an equi-join and not an outer join, a profile check whose translation row for the current language is missing will not appear in query results.

Key Columns

• ROW_ID — the ROWID of the base-table row, useful for direct row addressing and updatable-view handling.
• CHECK_ID — primary identifier of the profile check; the join key between the base and translation tables.
• CHECK_NAME and DESCRIPTION — the translated, user-facing name and description of the check.
• CHECK_NAME_CODE — the language-independent code for the check, stable across languages.
• START_DATE_ACTIVE and END_DATE_ACTIVE — the effective date range; a null end date indicates the check is currently active.
• SEEDED_FLAG — indicates whether the check was shipped by Oracle (seeded) or created by the customer.
• SELECT_TYPE and SELECT_BLOCK_ID — describe the selection mechanism, and for block-based selection the block from which values are chosen.
• DATA_TYPE and FORMAT_MASK — the expected data type and the display/validation mask applied to the value.
• THRESHOLD_GRADE, THRESHOLD_RATING_CODE, THRESHOLD_COLOR_CODE — threshold values that drive grading, rating, and colour-code evaluation.
• CHECK_UPPER_LOWER_FLAG — controls case sensitivity of the comparison.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the originating form.
• APPLICATION_ID — the owning application identifier.
• CHECK_LEVEL — the level at which the check applies, distinguishing profile-level from more granular scopes.
• WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical scenarios include extracting the configured checks for a specific profile, auditing changes to thresholds over time, comparing seeded versus customer-defined checks, and feeding check metadata into downstream validation or integration routines.

To list all currently active, seeded profile checks in the session language:

• SELECT check_id, check_name, check_name_code, data_type, format_mask, threshold_grade, threshold_rating_code, threshold_color_code FROM csc_prof_checks_vl WHERE seeded_flag = 'Y' AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE + 1);

To retrieve a single check by its stable code:

• SELECT check_id, check_name, description, select_type, select_block_id FROM csc_prof_checks_vl WHERE check_name_code = :p_code;

To inventory customer-defined checks by data type:

• SELECT data_type, COUNT(*) FROM csc_prof_checks_vl WHERE seeded_flag = 'N' GROUP BY data_type;

To perform a full extract for integration or audit purposes, join the view to the base table on CHECK_ID so that WHO and version columns are available even when a translation row is absent for the session language:

• SELECT b.check_id, v.check_name, b.check_name_code, b.application_id, b.object_version_number, b.last_updated_by, b.last_update_date FROM csc_prof_checks_b b, csc_prof_checks_vl v WHERE b.check_id = v.check_id(+);

Because the view is MLS-filtered, queries intended for multi-language reporting should either rely on the session language or join directly to CSC_PROF_CHECKS_TL and filter explicitly on LANGUAGE.