Search Results actual_start_date_time




Overview
Explore in AI Chat

Overview

The AMS.AMS_CAMPAIGN_SCHEDULES table resides in the AMS (Marketing) schema of Oracle E-Business Suite and, according to the ETRM documentation for releases 12.1.1 and 12.2.2, is flagged as obsoleted and no longer in use. Historically it formed part of the Oracle Marketing campaign execution model, holding the scheduled occurrences — forecasted and actual — that connected a parent campaign to the offers, deliverables, statuses, and channels used to execute it. Although the table remains physically present in many environments (status VALID, 50 documented columns, primary key AMS_CAMPAIGN_SCHEDULES_PK), Oracle no longer supports or populates it, so it should be treated as legacy schema rather than a functional integration point.

From a modeling perspective, the mined foreign-key structure classifies this object as satellite-leaning. This is a heuristic suggestion only: the table carries descriptive, time-stamped attributes about a scheduled campaign activity (dates, status, source codes, delivery metadata) keyed back to hub-like parents such as AMS_CAMPAIGNS_ALL_B and AMS_ACT_OFFERS. A Data Vault design would typically recast it as a satellite hanging off a campaign/activity hub, or as a link if the schedule is treated as an association between campaign, offer, and deliverable.

Key Information Stored

The most significant columns, as documented in the physical schema, are:

Common Use Cases and Queries

Because the table is obsoleted, its practical value is limited to legacy data extraction, archival, and historical reconciliation. Common patterns include:

  • Resolving the schedule's parent chain for historical reporting: join AMS_CAMPAIGN_SCHEDULES to AMS_CAMPAIGNS_ALL_B on CAMPAIGN_ID = CAMPAIGN_ID.
  • Reconstructing planned versus actual execution timelines using the forecasted and actual start/end date columns.
  • Auditing which offers and deliverables were attached to a schedule via ACTIVITY_OFFER_ID and DELIVERABLE_ID.

A representative legacy query:

SELECT cs.campaign_schedule_id, cs.campaign_id, cs.status_code, cs.forecasted_start_date_time, cs.actual_start_date_time
FROM ams.ams_campaign_schedules cs
WHERE cs.active_flag = 'Y' AND cs.campaign_id = :campaign_id;

Analysts migrating to a supported release should expect no inserts or updates against this table and should source equivalent scheduling data from current Marketing tables.

Related Objects