Search Results greeting_text




Overview

The AMS.AMS_CAMPAIGN_SCHEDULES_TL table is a translation ("TL") table within the Oracle Marketing (AMS) module of Oracle E-Business Suite, applicable to releases 12.1.1 and 12.2.2. Its documented purpose is to store the schedule attributes that require translation support, meaning it holds the language-dependent descriptive text associated with campaign schedules defined in the base table. In the standard Oracle multi-language schema pattern, the _TL table operates alongside a corresponding base table (AMS_CAMPAIGN_SCHEDULES_B), where the base table stores language-independent data and the translation table stores one row per installed language for translatable attributes.

Based on the foreign key and primary key structure mined from the metadata, the heuristic Data Vault classification for this table is satellite-leaning. This reflects its role as a dependent, descriptive store keyed by the parent schedule identifier and language, rather than as a hub or link. This classification should be treated as a modeling suggestion derived from the FK topology, not an authoritative architectural designation.

Key Information Stored

The table contains 14 documented columns. The most significant are described below.

  • SCHEDULE_ID — The identifier linking the translation row to its parent schedule in AMS_CAMPAIGN_SCHEDULES_B. It forms part of the composite primary key.
  • LANGUAGE — The language code identifying which installed language the translated text applies to. Together with SCHEDULE_ID, it constitutes the primary key AMS_CAMPAIGN_SCHEDULES_TL_PK.
  • SOURCE_LANG — Indicates the source language of the row, used by the translation framework to determine whether text requires re-translation.
  • SCHEDULE_NAME — The translated, user-facing name of the campaign schedule.
  • DESCRIPTION — The translated long description of the schedule.
  • GREETING_TEXT — Translatable greeting content associated with the schedule.
  • FOOTER_TEXT — Translatable footer content associated with the schedule.
  • CAMPAIGN_ID — References the campaign with which the schedule is associated, supporting reporting joins to campaign data.
  • SECURITY_GROUP_ID — The security group identifier, referenced against FND_SECURITY_GROUPS, controlling multi-organization and security access.
  • Audit columnsLAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN track row-level change history consistent with the EBS Who columns convention.

The surrogate-level primary key is the composite (SCHEDULE_ID, LANGUAGE). The unique index AMS_CAMPAIGN_SCHEDULES_TL_U1 overlaps this composite key and serves as the business-key candidate enforcing one translation row per schedule per language.

Common Use Cases and Queries

The principal use case is retrieving language-specific schedule text for display or reporting. A typical pattern joins the translation table to the base table, filtering by the session or reporting language.

  • Retrieve translated schedule names and descriptions in a target language for a given campaign.
  • Audit translation coverage, identifying schedules that lack a row for a particular installed language.
  • Report on translation freshness using SOURCE_LANG and LAST_UPDATE_DATE to detect stale translations.

A representative query pattern:

SELECT b.schedule_id, t.schedule_name, t.description
FROM   ams.ams_campaign_schedules_b b,
       ams.ams_campaign_schedules_tl t
WHERE  b.schedule_id = t.schedule_id
AND    t.language = USERENV('LANG');

Coverage analysis can be performed by comparing distinct SCHEDULE_ID values between the base and translation tables. Because the table is security-group enabled, queries executed under multi-org responsibility should also respect SECURITY_GROUP_ID filtering as imposed by the standard EBS security framework.

Related Objects

The following objects are most significant to the operation and querying of this table.

  • AMS_CAMPAIGN_SCHEDULES_B — The base table; joined on SCHEDULE_ID. The documented foreign key from this translation table references AMS_CAMPAIGN_SCHEDULES_TL.SCHEDULE_ID to AMS_CAMPAIGN_SCHEDULES_B.
  • FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID, providing the security group definition governing access to schedule translation rows.
  • Campaign tables (campaign header entities) — Linked via CAMPAIGN_ID to associate schedules with their parent campaigns.
  • AMS_CAMPAIGN_SCHEDULES_TL_PK / _U1 indexes — The primary key and unique index support efficient lookup by schedule and language.

Together these objects form the schedule translation cluster within the AMS Marketing schema, with the translation table acting as the language-dependent satellite of the base schedule entity.