Search Results ams_campaign_schedules_tl




Overview
Explore in AI Chat

Overview

The AMS_CAMPAIGN_SCHEDULES_TL table is a core translation table within the Oracle E-Business Suite Marketing (AMS) module for versions 12.1.1 and 12.2.2. It is designed to store multilingual translations for the descriptive attributes of campaign schedules. Its primary role is to support the global deployment of Oracle EBS by enabling the storage of schedule information, such as names or descriptions, in multiple languages. This table works in tandem with its base table, AMS_CAMPAIGN_SCHEDULES_B, which holds the non-translatable, language-independent data. The existence of this TL (Translation) table is a standard Oracle EBS architectural pattern, ensuring that user-facing text can be presented in the language specified by a user's session.

Key Information Stored

The table stores translated text for schedule attributes linked to a specific language code. The primary key structure, consisting of SCHEDULE_ID and LANGUAGE, enforces a unique translation entry per schedule per language. While the provided metadata does not list all columns, standard translation table patterns in Oracle EBS dictate that it typically includes columns such as:

  • SCHEDULE_ID: The foreign key identifier linking to the base schedule record in AMS_CAMPAIGN_SCHEDULES_B.
  • LANGUAGE: The standard Oracle language code (e.g., 'US' for American English, 'KO' for Korean) for the translation.
  • SOURCE_LANG: A column indicating the original language of the source data, usually the language in which the data was initially entered.
  • Translatable Attribute Columns: Columns such as SCHEDULE_NAME, DESCRIPTION, or other user-defined descriptive flexfield attributes that require translation.

Common Use Cases and Queries

The primary use case is retrieving schedule information in a user's preferred language for UI display, reports, and integrations. Applications automatically query this table based on the session's NLS_LANGUAGE setting. A common reporting query involves joining the translation table with its base table and filtering by language. For example, to retrieve the English names for all schedules:

SELECT b.SCHEDULE_ID, tl.SCHEDULE_NAME, b.START_DATE_TIME
FROM AMS_CAMPAIGN_SCHEDULES_B b,
     AMS_CAMPAIGN_SCHEDULES_TL tl
WHERE b.SCHEDULE_ID = tl.SCHEDULE_ID
AND tl.LANGUAGE = 'US'
AND tl.SOURCE_LANG = tl.LANGUAGE;

Data maintenance use cases include seeding initial translations via FNDLOAD or directly through the application's translation forms, and updating translated text during localization projects.

Related Objects

The table has a direct and critical relationship with its base table, as defined by the documented foreign key. The primary related objects are:

  • AMS_CAMPAIGN_SCHEDULES_B (Base Table): This is the primary parent table. The foreign key constraint enforces that every SCHEDULE_ID in the TL table must exist in the B table (AMS_CAMPAIGN_SCHEDULES_TL.SCHEDULE_ID -> AMS_CAMPAIGN_SCHEDULES_B). All transactional logic and non-translatable data are stored in the base table.
  • FND_LANGUAGES (Reference View): While not explicitly listed in the metadata, the LANGUAGE column in AMS_CAMPAIGN_SCHEDULES_TL typically corresponds to valid language codes defined in this application-wide view.
  • Campaign Schedule APIs and UI Forms: All programmatic and form-based access to translated schedule data will inherently reference this table through the standard Oracle translation architecture.