Results for “actual_start_date_time”

40 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The AMS_P_CAMPAIGN_GEO_AREAS_V view is a public, APPS-owned database object in the Oracle E-Business Suite Marketing (AMS) module. It is registered as VALID in both Oracle EBS 12.1.1 and 12.2.2. The view exposes the relationship between Marketing campaigns and the geographic areas against which those campaigns are targeted or made available. It returns, in a single denormalized result set, campaign descriptive and status attributes alongside geographic area type, hierarchy, and name attributes.

Because the view is registered as a public object, it functions as a supported reporting and integration surface. External reports, custom concurrent programs, embedded analytics, and downstream integration extracts can query it without needing to understand the internal join geometry between the geographic area assignment table and the campaign master. The view applies an implicit filter, returning only assignments where the geographic area user type is CAMP, so consumers are automatically restricted to campaign-scoped geographic data rather than other area-user relationships. Campaign rows are further limited to active campaigns.

Underlying Base Objects

The view is defined over two documented base objects: AMS_ACT_GEO_AREAS_V and AMS_CAMPAIGNS_VL. The first is a view over the activity geographic area assignments and supplies the geographic columns: the area user identifier, geographic type code, geographic type name, hierarchy identifier, and area name. The second is the campaign master view, which is a translated (_VL) view and supplies campaign attributes including status, source, execution dates, name, media, and channel identifiers.

The two objects are joined on AGEO.ACT_GEO_AREA_USER_ID = CAMP.CAMPAIGN_ID, meaning the geographic assignment record must be linked to a campaign identifier. Three predicates constrain the result set: AGEO.ACT_GEO_AREA_USER = 'CAMP', CAMP.STATUS_CODE = 'ACTIVE', CAMP.ACTIVE_FLAG = 'Y', and CAMP.SHOW_CAMPAIGN_FLAG = 'Y'. The net effect is that only active, displayable campaigns with campaign-scoped geographic assignments appear.

Key Columns

Common Use Cases and Queries

Reporting requirements typically involve listing active campaigns by geography with their execution schedule. A representative query filters on the actual start date:

  • SELECT campaign_id, campaign_name, geo_area_name, actual_start_date_time, actual_end_date_time FROM ams_p_campaign_geo_areas_v WHERE actual_start_date_time >= :p_start_date;
  • SELECT geo_area_name, COUNT(*) FROM ams_p_campaign_geo_areas_v GROUP BY geo_area_name; — distribution of active campaigns across geographic areas.
  • SELECT campaign_name, geo_area_name, actual_start_date_time FROM ams_p_campaign_geo_areas_v WHERE channel_id = :p_channel_id; — campaign coverage by channel within a geography.

Because the view embeds active-status and show-flag predicates, consumers cannot use it to retrieve inactive, historical, or hidden campaigns; those require the base campaign objects directly.