Search Results ams_campaign_schedules_b

Overview

The AMS_CAMPAIGN_SCHEDULES_B table is a core data object within the Oracle E-Business Suite Marketing (AMS) module, specifically for versions 12.1.1 and 12.2.2. Its primary function is to store the master transactional data for all campaign schedules. A campaign schedule defines the execution plan for a marketing campaign, detailing when and how campaign activities are to be launched. This table serves as the central hub for linking a campaign's strategic definition to its operational execution, managing timelines, resource assignments, approval workflows, and status tracking. It is integral to the campaign management lifecycle, enabling the planning, scheduling, and monitoring of marketing initiatives.

Key Information Stored

The table's primary key is the SCHEDULE_ID, which uniquely identifies each schedule record. As indicated by its extensive foreign key relationships, the table stores critical foreign key references that contextualize the schedule within the broader application. Key columns include CAMPAIGN_ID, linking to the parent campaign in AMS_CAMPAIGNS_ALL_B, and ACTIVITY_ID, linking to the specific media or activity in AMS_MEDIA_B. It tracks workflow and ownership via OWNER_USER_ID, APPROVER_USER_ID, and NOTIFY_USER_ID, all referencing JTF_RS_RESOURCE_EXTNS. The table also holds the schedule's current state through USER_STATUS_ID (linked to AMS_USER_STATUSES_B) and may reference a TASK_ID (JTF_TASKS_B) for project management integration, a TRIGGER_ID (AMS_TRIGGERS) for event-driven execution, and a MARKETING_MEDIUM_ID (AMS_CHANNELS_B) for the delivery channel.

Common Use Cases and Queries

This table is central to reporting and operational queries within Marketing. Common use cases include generating campaign timelines, monitoring schedule statuses for operational dashboards, and auditing resource assignments. A typical query might join to the translated table (AMS_CAMPAIGN_SCHEDULES_TL) for descriptive information and to campaign tables to report on all schedules for a given campaign or status.

• Finding Schedules for a Campaign: SELECT * FROM AMS_CAMPAIGN_SCHEDULES_B WHERE CAMPAIGN_ID = <campaign_id>;
• Listing Schedules by Owner and Status: SELECT schedule_id, campaign_id, user_status_id FROM AMS_CAMPAIGN_SCHEDULES_B WHERE OWNER_USER_ID = <resource_id> ORDER BY creation_date;
• Integration with Campaign Performance: Data from this table is often joined with transactional output tables like AMS_TCOP_CONTACTS or AMS_TCOP_REQUESTS to analyze the execution results of a specific schedule.

Related Objects

The AMS_CAMPAIGN_SCHEDULES_B table has a dense network of relationships, acting as a parent to numerous transactional tables and a child to several master data tables. Key documented relationships include:

• Parent Tables (Foreign Key References): AMS_CAMPAIGNS_ALL_B (CAMPAIGN_ID), JTF_TASKS_B (TASK_ID), AMS_MEDIA_B (ACTIVITY_ID), AMS_TRIGGERS (TRIGGER_ID), AMS_CHANNELS_B (MARKETING_MEDIUM_ID), FND_LANGUAGES (LANGUAGE_CODE), AMS_USER_STATUSES_B (USER_STATUS_ID), JTF_RS_RESOURCE_EXTNS (OWNER_USER_ID, APPROVER_USER_ID, NOTIFY_USER_ID).
• Child Tables (Referenced by Foreign Key): AMS_CAMPAIGN_SCHEDULES_TL (SCHEDULE_ID) for translated descriptions, AMS_ACT_LISTS (LIST_USED_BY_ID) for associated target lists, AMS_DM_OPT_TGT_METRICS (SCHEDULE_ID) for optimization metrics, and a suite of campaign output tables including AMS_TCOP_CONTACTS, AMS_TCOP_REQUESTS, AMS_TCOP_CHANNEL_SUM_DTL, and AMS_TCOP_FATIGUED_BY, which store the detailed results and contact history generated by the schedule's execution.