Search Results group_enabled_flag

Overview

The view APPS.AST_GRP_CAMPAIGN_SCHEDS_V is a TeleSales (AST) reporting object that consolidates group-level campaign schedule assignments into a single queryable structure. It is defined in the APPS schema with a VALID status and is used primarily to drive group campaign scheduling, enrollment, and outreach processes within the Oracle E-Business Suite TeleSales module. The view joins group definitions, campaign schedules, and group-to-campaign assignment records, then applies effective-dating and status filters so that only currently active combinations are surfaced.

The view is significant for the keyword group_enabled_flag, which it exposes from the underlying AST_GRP_CAMPAIGNS assignment record. This flag allows consumers to distinguish enabled group campaign assignments from disabled ones directly at the view level, without needing to join back to the base table. Because the view also filters on schedule activity and active flags, it behaves as a ready-to-use source for runtime campaign processing rather than a raw data extract.

Underlying Base Objects

The documented base objects referenced by this view are:

• AST_GRP_CAMPAIGNS (SYNONYM) — the group campaign assignment table, aliased ASSG, supplying GROUP_CAMPAIGN_ID, GROUP_ID, date ranges, ENABLED_FLAG, and the campaign linkage via CAMPAIGN_ID.
• AMS_CAMPAIGN_SCHEDULES_VL (VIEW) — aliased SCH, supplying schedule identifiers, names, status and source codes, activity linkage, and start/end date-time filters.
• JTF_RS_GROUPS_VL (VIEW) — aliased GRP, supplying group number, name, and effective start/end dates.

The joins link GRP.GROUP_ID = ASSG.GROUP_ID and ASSG.CAMPAIGN_ID = SCH.SCHEDULE_ID. Effective-dating predicates ensure that the truncated system date falls within the group's active range and the schedule's start/end range, using NVL fallbacks to the current date. The view further restricts records to ACTIVITY_ID = 460 and ACTIVE_FLAG = 'Y'.

Key Columns

• GROUP_CAMPAIGN_ID — primary identifier of the group campaign assignment.
• SCHEDULE_ID / SCHEDULE_NAME — the campaign schedule linked to the assignment.
• GROUP_ID — identifier of the resource group associated with the campaign.
• GROUP_START_DATE / GROUP_END_DATE — the effective range of the group campaign assignment.
• GROUP_ENABLED_FLAG — the enabled indicator sourced from ASSG.ENABLED_FLAG, the column most relevant to the user's search. A value of Y indicates the group campaign assignment is enabled.
• GROUP_STATUS — exposed as NULL in the view text, providing no status value.
• SCHEDULE_STATUS_CODE / SCHEDULE_SOURCE_CODE — status and origin of the underlying campaign schedule.
• GROUP_NUMBER / GROUP_FULL_NAME — human-readable group identifiers.
• GROUP_EFFECTIVE_START_DATE / GROUP_EFFECTIVE_END_DATE — the group's active date range.

Common Use Cases and Queries

Typical scenarios include identifying which enabled group campaigns are active today, validating group membership before campaign execution, and feeding TeleSales outreach or analytics. Because the view already restricts to active schedules with ACTIVITY_ID = 460, queries generally only add further narrowing. A representative query is:

SELECT group_campaign_id, group_id, group_number, schedule_id, schedule_name, group_enabled_flag FROM apps.ast_grp_campaign_scheds_v WHERE group_enabled_flag = 'Y' ORDER BY group_number;

Consumers may also join the view to group membership tables using GROUP_ID, or aggregate counts by SCHEDULE_ID to measure how many groups are assigned to each campaign schedule. The group_enabled_flag column is especially useful as a filter or reporting dimension where only enabled assignments should be actioned.