Results for “rs_campaign_id”

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

Overview

The AST_RS_CAMPAIGNS_V view is a reporting and integration object in the Oracle E-Business Suite TeleSales (AST) module. It exposes the assignment of marketing campaigns to individual resources (agents) together with descriptive campaign and resource attributes, allowing downstream reporting, dashboards, and integration processes to consume a single denormalized result set rather than joining multiple underlying objects manually.

The view is owned by the APPS schema and is documented as VALID in both EBS 12.1.1 and 12.2.2. Its stated purpose is "to show the assignment of campaigns to resources with additional information." Critically, the view is date-filtered at query time: the WHERE clause restricts rows to assignments whose START_DATE and END_DATE bracket the current system date, and it further restricts results to assignments where ENABLED_FLAG = 'Y'. This makes AST_RS_CAMPAIGNS_V an "active assignments as of today" view rather than a historical record of every assignment ever created. Users searching for assign_start_date should note that the assignment start date is surfaced through the ASSIGN_START_DATE column, which is the START_DATE of the underlying AST_RS_CAMPAIGNS assignment row.

Underlying Base Objects

The view text is defined over three referenced objects:

• AST_RS_CAMPAIGNS (referenced as a synonym in the ETRM metadata) — the assignment table joining resources to campaigns. It supplies the primary key ROWID, RS_CAMPAIGN_ID, RESOURCE_ID, CAMPAIGN_ID, START_DATE, END_DATE, STATUS, and ENABLED_FLAG.
• AMS_P_CAMPAIGNS_V (view) — the campaign master view supplying CAMPAIGN_NAME, DESCRIPTION, STATUS_CODE, SOURCE_CODE, INBOUND_SCRIPT_NAME, CHANNEL_OUTBOUND_FLAG, CHANNEL_INBOUND_FLAG, INBOUND_EMAIL_ID, and INBOUND_PHONE_NO.
• JTF_RS_EMP_DTLS_VL (view) — the resource (employee) details view supplying RESOURCE_NUMBER, SOURCE_ID, START_DATE_ACTIVE, END_DATE_ACTIVE, PRIMARY_LANGUAGE, SECONDARY_LANGUAGE, FIRST_NAME, LAST_NAME, MIDDLE_NAME, FULL_NAME, EFFECTIVE_START_DATE, and EFFECTIVE_END_DATE.

The join predicates are RS.RESOURCE_ID = ASSG.RESOURCE_ID and ASSG.CAMPAIGN_ID = CAMP.CAMPAIGN_ID, with the additional active-date and enabled-flag filters applied to the assignment.

Key Columns

• ROW_ID — the ROWID of the underlying AST_RS_CAMPAIGNS row, usable as a unique row identifier.
• RS_CAMPAIGN_ID — unique identifier of the resource-campaign assignment.
• RESOURCE_ID / RESOURCE_PERSON_ID — the resource (agent) identifier.
• CAMPAIGN_ID — identifier of the assigned campaign.
• ASSIGN_START_DATE / ASSIGN_END_DATE — the effective window of the assignment; ASSIGN_START_DATE corresponds to ASSG.START_DATE and is the column most relevant to searches for the assignment start date.
• ASSIGN_STATUS / ASSIGN_ENABLED_FLAG — status and enabled indicator of the assignment.
• CAMPAIGN_NAME, CAMPAIGN_DESCRIPTION, CAMPAIGN_STATUS_CODE, CAMPAIGN_SOURCE_CODE — descriptive attributes of the campaign.
• CAMPAIGN_INBOUND_SCRIPT, CAMPAIGN_OUTBOUND_FLAG, CAMPAIGN_INBOUND_FLAG, CAMPAIGN_INBOUND_EMAIL, CAMPAIGN_INBOUND_PHONE — channel and inbound-handling attributes.
• RESOURCE_NUMBER, RESOURCE_FULL_NAME, RESOURCE_FIRST_NAME, RESOURCE_LAST_NAME, RESOURCE_MIDDLE_NAME — resource identity information.
• RESOURCE_START_DATE_ACTIVE / RESOURCE_END_DATE_ACTIVE and RESOURCE_EFFECTIVE_START_DATE / RESOURCE_EFFECTIVE_END_DATE — resource lifecycle dates.

Common Use Cases and Queries

Typical uses include agent-facing worklists, campaign rosters, and telemarketing supervision reports that need currently valid assignments. A representative query listing active assignments with their start dates is:

• SELECT resource_full_name, campaign_name, assign_start_date, assign_end_date, assign_status FROM apps.ast_rs_campaigns_v ORDER BY campaign_name, resource_full_name;
• SELECT campaign_id, campaign_name, COUNT(*) FROM apps.ast_rs_campaigns_v GROUP BY campaign_id, campaign_name;

Because the view already enforces the enabled-flag and current-date predicates, no additional filtering is required for "active today" reporting. For historical analysis, users must query the base table AST_RS_CAMPAIGNS directly, since expired or disabled assignments are excluded from this view.