Results for “csc_prof_checks_tl”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
CSC_PROF_CHECKS_TL is a translation table owned by the CSC (Customer Care) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the language-specific, translated columns of profile checks. The base or non-translated attributes for each profile check are held in CSC_PROF_CHECKS_B, while CSC_PROF_CHECKS_TL supplies the translatable text (such as the check name and description) for each installed language. This _TL / _B pairing is the standard Oracle EBS multilanguage design pattern, allowing a single profile check definition to expose localized display text without duplicating its functional definition.
The table is marked VALID and carries 12 documented columns. Under a heuristic Data Vault classification mined from the foreign-key structure, this table is satellite-leaning: it hangs off the base table CSC_PROF_CHECKS_B as a dependent, keyed by the same identity column plus LANGUAGE, and holds descriptive/attribute payload rather than representing an independent business entity or a many-to-many relationship.
Key Information Stored
The table is keyed by the composite primary key CSC_PROF_CHECKS_TL_PK (CHECK_ID, LANGUAGE). CHECK_ID is the surrogate key inherited from the base table and also the foreign key to CSC_PROF_CHECKS_B; LANGUAGE identifies which installed language the row's translated text applies to. Together they are the identity of a translated row.
- CHECK_ID — Surrogate identifier of the profile check; FK to
CSC_PROF_CHECKS_B.CHECK_ID. - LANGUAGE — Language code of the translated content; part of the primary key.
- SOURCE_LANG — Language from which the translation was derived, used by the translation tooling.
- CHECK_NAME — Localized display name of the profile check; a business-key candidate via
CSC_PROF_CHECKS_TL_U2 (CHECK_NAME, LANGUAGE, ZD_EDITION_NAME). - DESCRIPTION — Localized descriptive text for the check.
- SECURITY_GROUP_ID — FK to
FND_SECURITY_GROUPS, enforcing EBS security-group (operating unit) partitioning. - ZD_EDITION_NAME — Edition/version discriminator used in the unique indexes
CSC_PROF_CHECKS_TL_U1andU2. - Audit columns —
CREATED_BY,CREATION_DATE,LAST_UPDATED_BY,LAST_UPDATE_DATE, andLAST_UPDATE_LOGINcapture standard Oracle EBS who/when auditing.
The two unique indexes are the documented business-key candidates: CSC_PROF_CHECKS_TL_U1 (CHECK_ID, LANGUAGE, ZD_EDITION_NAME) and CSC_PROF_CHECKS_TL_U2 (CHECK_NAME, LANGUAGE, ZD_EDITION_NAME). Note that CHECK_ID is the surrogate and CHECK_NAME the natural business key.
Common Use Cases and Queries
The predominant use is joining translations to base definitions for a specific language, typically filtered to the session or reporting language. A representative query returning localized names and descriptions is:
SELECT b.check_id, t.check_name, t.description FROM csc_prof_checks_b b, csc_prof_checks_tl t WHERE b.check_id = t.check_id AND t.language = :lang;- Reporting on all translations of a single check:
SELECT language, check_name, description FROM csc_prof_checks_tl WHERE check_id = :check_id; - Leveraging the business-key index for lookup by name:
... WHERE check_name = :name AND language = :lang;
Typical scenarios include rendering profile-check pick lists and validation messages in a user's preferred language, auditing translation completeness across multiple languages, verifying that SOURCE_LANG is populated correctly after a translation load, and filtering translated rows by security group in multi-org or secured deployments.
Related Objects
- CSC_PROF_CHECKS_B — The base table holding the non-translated profile check definition; joined on
CHECK_ID. - FND_SECURITY_GROUPS — Referenced through
SECURITY_GROUP_IDfor security-group partitioning. - CSC_PROF_CHECKS_TL_PK — Primary key constraint on
(CHECK_ID, LANGUAGE). - CSC_PROF_CHECKS_TL_U1 / U2 — Unique indexes forming the documented business-key candidates.
- CSC_PROF_CHECKS_VL / _V — The conventional base-plus-translation views that expose localized profile checks to forms and reports (standard EBS naming pattern).
Because the table is translation-only, maintenance is normally performed through the profile-check setup UI or the Oracle translation (FND) utilities rather than through direct DML.
-
CSC_PROF_CHECKS_TL table stores the translated columns of profile checks stored in CSC_PROF_CHECKS_B table
-
CSC_PROF_CHECKS_TL table stores the translated columns of profile checks stored in CSC_PROF_CHECKS_B table
-
View: CSC_PROF_CHECKS_VL 12.2.2
This view is the MLSed view based on CSC_PROF_CHECKS_B and CSC_PROF_CHECKS_TL. This view is used in Customer Profile Setup form- Profile Checks tab.
APPS.CSC_PROF_CHECKS_VL·↳ CSC_PROF_CHECKS_B·↳ CSC_PROF_CHECKS_TL·Explore CSC module →
-
View: CSC_PROF_CHECKS_VL 12.1.1
This view is the MLSed view based on CSC_PROF_CHECKS_B and CSC_PROF_CHECKS_TL. This view is used in Customer Profile Setup form- Profile Checks tab.
APPS.CSC_PROF_CHECKS_VL·↳ CSC_PROF_CHECKS_B·↳ CSC_PROF_CHECKS_TL·Explore CSC module →
-
View of CSC_PROF_GROUP_CHECKS. This view is used in Customer Profile Setup form - Profile Groups tab and Dashboard Groups tab.
APPS.CSC_PROF_GROUP_CHECKS_V·↳ CSC_PROF_CHECKS_TL·↳ CSC_PROF_GROUP_CHECKS·Explore CSC module →
-
View of CSC_PROF_GROUP_CHECKS. This view is used in Customer Profile Setup form - Profile Groups tab and Dashboard Groups tab.
APPS.CSC_PROF_GROUP_CHECKS_V·↳ CSC_PROF_CHECKS_TL·↳ CSC_PROF_GROUP_CHECKS·Explore CSC module →
-
12.2.2 DBA Data 12.2.2
-
12.2.2 FND Design Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
eTRM - CSC Tables and Views 12.2.2
Translation table to Store Drilldown details for a profile variable. This stores the column and table names for the drilldown form. Also stores the object_code, which provides the form_function to drilldown
-
eTRM - CSC Tables and Views 12.1.1
Translation table to Store Drilldown details for a profile variable. This stores the column and table names for the drilldown form. Also stores the object_code, which provides the form_function to drilldown