Results for “schedule_desc”

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

Overview

CAC_SR_SCHEDULES_TL is a translation table owned by the JTF schema within the CRM Foundation module (JTF) of Oracle E-Business Suite. It stores the language-dependent descriptive attributes — name and description — for service request schedules defined in the base table CAC_SR_SCHEDULES_B. The "_TL" suffix follows the standard Oracle Applications multilingual convention: the "_B" table holds language-independent columns and one row per entity, while the "_TL" table holds one row per entity per installed language, joined on the shared primary key columns LANGUAGE and SCHEDULE_ID.

Schedule records in this family are used by CRM service request functionality and the field service / telephony scheduling components built on the CRM Foundation. From a Data Vault modeling perspective, the ETRM metadata classifies this object as satellite-leaning: it carries descriptive, non-key attributes keyed by a parent business key (SCHEDULE_ID) plus a language discriminator (LANGUAGE), and it references the parent hub-like structure in CAC_SR_SCHEDULES_B. This classification is a heuristic derived from the foreign-key structure rather than an Oracle-published designation.

Key Information Stored

The table contains 10 documented columns. The most significant are:

• SCHEDULE_ID — Surrogate identifier for the schedule. It is part of the composite primary key and is a foreign key to CAC_SR_SCHEDULES_B.SCHEDULE_ID, establishing the link to the base entity.
• LANGUAGE — The language code of the translation row. Together with SCHEDULE_ID it forms the primary key CAC_SR_SCHEDULES_TL_PK.
• SOURCE_LANG — The language in which the source text was originally entered; used by the translation framework to indicate the origin language of the name and description.
• SCHEDULE_NAME — The translated display name of the schedule, presented to users in the selected session language.
• SCHEDULE_DESC — The translated long description of the schedule.
• CREATED_BY, CREATION_DATE — Standard WHO audit columns recording the user and timestamp of row creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns capturing the most recent modification user, timestamp, and login.

The composite primary key CAC_SR_SCHEDULES_TL_PK (LANGUAGE, SCHEDULE_ID) is the surrogate key for a translation row. The unique index CAC_SR_SCHEDULES_TL_U1 (SCHEDULE_ID, LANGUAGE) enforces that only one translation exists per schedule per language and represents the business-key candidate for the entity.

Common Use Cases and Queries

Translation tables are queried in two primary ways: to resolve the display name of a schedule in a specific language, and to join translated descriptions onto the base entity for reporting. A typical lookup restricts on the session language and falls back to SOURCE_LANG when no row exists for the requested language.

• Language-specific schedule listing: join CAC_SR_SCHEDULES_TL to CAC_SR_SCHEDULES_B on SCHEDULE_ID with a WHERE LANGUAGE = :p_lang predicate to render names in the user's language.
• Translation completeness audit: compare counts in CAC_SR_SCHEDULES_B against rows in CAC_SR_SCHEDULES_TL grouped by LANGUAGE to identify missing or stale translations.
• Change tracking: filter on LAST_UPDATE_DATE and LAST_UPDATED_BY to report recently modified schedule descriptions.
• Search: apply UPPER(SCHEDULE_NAME) LIKE predicates against the translated name for interactive LOV queries on the schedule form.

Related Objects

• CAC_SR_SCHEDULES_B — The base, language-independent schedule table. Joined via CAC_SR_SCHEDULES_TL.SCHEDULE_ID = CAC_SR_SCHEDULES_B.SCHEDULE_ID; the sole documented foreign-key reference.
• CAC_SR_SCHEDULES_TL_PK — Primary-key constraint (LANGUAGE, SCHEDULE_ID) enforcing uniqueness of the translation row.
• CAC_SR_SCHEDULES_TL_U1 — Unique index on (SCHEDULE_ID, LANGUAGE), the business-key candidate.
• CAC_SR_SCHEDULE_ASSIGNMENTS and other CRM scheduling child objects — populate SCHEDULE_ID values whose names are resolved through this translation table.
• FND_LANGUAGES — The reference table validating LANGUAGE and SOURCE_LANG codes used when joining for language-appropriate display.