Search Results ams_campaign_schedules




Overview
Explore in AI Chat

Overview

The AMS_CAMPAIGN_SCHEDULES table is a historical data object within the Oracle E-Business Suite (EBS) Marketing (AMS) module. According to the official ETRM documentation for versions 12.1.1 and 12.2.2, this table is explicitly marked as obsoleted and no longer in use. It was originally designed to manage scheduling information for marketing campaigns, acting as a central junction table that linked campaigns to their associated activities, deliverables, and statuses. Its role was to facilitate the planning and execution timeline of marketing initiatives. However, its functionality has been superseded by other application features or tables in later releases, rendering it a legacy artifact within the database schema.

Key Information Stored

While the table is obsolete, its structure reveals the type of scheduling data it was intended to manage. The primary key, CAMPAIGN_SCHEDULE_ID, uniquely identified each schedule record. Critical foreign key columns linked the schedule to core marketing entities: CAMPAIGN_ID (to AMS_CAMPAIGNS_ALL_B), ACTIVITY_OFFER_ID (to AMS_ACT_OFFERS), DELIVERABLE_ID (to AMS_DELIVERABLES_ALL_B), and USER_STATUS_ID (to AMS_USER_STATUSES_B). These columns indicate the table stored references to the specific campaign, its associated offer activity, the deliverable (e.g., an email or advertisement), and the current workflow status of the schedule.

Common Use Cases and Queries

As a deprecated table, there are no current operational use cases for AMS_CAMPAIGN_SCHEDULES in a standard Oracle EBS implementation. Direct interaction with this table for reporting or data manipulation is strongly discouraged, as the application logic no longer maintains it. Any historical data present would be for archival purposes only. Sample queries are provided strictly for understanding its past structure, such as identifying legacy schedule records for a specific campaign: SELECT * FROM AMS.AMS_CAMPAIGN_SCHEDULES WHERE CAMPAIGN_ID = <campaign_id>;. For any active scheduling requirements, consultants must refer to the current, supported tables and APIs within the Oracle Marketing module.

Related Objects

The foreign key relationships documented in the ETRM metadata illustrate the table's former integration points within the Marketing schema. Key related objects include:

These relationships show the table was once a hub connecting campaigns to metrics, scripts, postings, and target lists.