Search Results group_effective_start_date

Overview

APPS.AST_GRP_CAMPAIGN_SCHEDS_V is a supplementary database view in the Oracle E-Business Suite (EBS) Applications schema, classified under FND Design Data as AST.AST_GRP_CAMPAIGN_SCHEDS_V. In the Oracle EBS 12.1.1 and 12.2.2 releases, this view exists primarily to simplify forms coding within the Oracle Trade Management (AST) and Marketing (AMS) product family. It consolidates campaign schedule information associated with group campaigns, exposing a flattened result set that application forms can consume without issuing complex multi-table joins.

The view carries the standard Oracle designation of "Oracle Internal Use Only." Oracle Corporation explicitly does not support direct access to application data through this object except from standard Oracle Applications programs. The documentation further warns that the view is a supplementary construct and is not recommended for direct querying or data alteration, as its definition may change substantially in subsequent minor or major releases. The user's search term "group_status" maps directly to the GROUP_STATUS column exposed by this view, which reports the operational state of the group campaign.

Underlying Base Objects

The view is defined over three documented base objects:

• AMS_CAMPAIGN_SCHEDULES_VL (VIEW) — a marketing campaign schedules view supplying schedule identifiers, schedule names, status codes, and source codes.
• AST_GRP_CAMPAIGNS (SYNONYM) — the group campaign entity providing the primary group campaign identifier, group reference, and group-level attributes.
• JTF_RS_GROUPS_VL (VIEW) — the resource group view supplying group number, group full name, and group effective dating.

The view is not referenced by any other database object, confirming its role as a terminal presentation layer rather than an intermediate dependency. Its status is VALID, meaning it compiles cleanly against the referenced objects in the reported environment.

Key Columns

• GROUP_CAMPAIGN_ID (NUMBER) — the primary identifier linking the schedule to its parent group campaign.
• SCHEDULE_ID, SCHEDULE_NAME — identify and describe the underlying campaign schedule.
• GROUP_ID — the resource group associated with the campaign schedule.
• GROUP_START_DATE, GROUP_END_DATE — the active window for the group campaign.
• GROUP_STATUS (VARCHAR2) — the status of the group campaign, the column most relevant to the user's "group_status" search.
• GROUP_ENABLED_FLAG (VARCHAR2) — indicates whether the group campaign is enabled.
• SCHEDULE_STATUS_CODE, SCHEDULE_SOURCE_CODE (VARCHAR2(30)) — status and origin of the schedule.
• GROUP_NUMBER, GROUP_FULL_NAME — human-readable group identifiers.
• GROUP_EFFECTIVE_START_DATE, GROUP_EFFECTIVE_END_DATE — effective dating for the group record.

Common Use Cases and Queries

Typical scenarios include verifying active group campaigns for a given period and auditing schedule status by group. Because Oracle discourages direct access, queries should be limited to read-only diagnostics and used with the caveat that column definitions may change across releases.

A representative query filtered on the user's search term is:

• SELECT group_campaign_id, schedule_name, group_number, group_full_name, group_status, group_enabled_flag FROM apps.ast_grp_campaign_scheds_v WHERE group_status = 'ACTIVE';

Additional queries may join the view to unrelated reporting tables on GROUP_CAMPAIGN_ID or restrict results by GROUP_START_DATE and GROUP_END_DATE to isolate currently effective campaigns.