Results for “ast_rs_campaigns”

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

Overview

The AST_RS_CAMPAIGNS table is a TeleSales (AST) module object in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to assign marketing campaigns to resources, establishing which telesales agents, sales representatives, or other resources are associated with a given campaign. The table resides in the AST schema and holds a VALID status in the ETRM repository.

Structurally, the object is a junction or association table. Its heuristic Data Vault classification, mined from the foreign-key structure, is link. In practice, this object should be modeled as a link table sitting between the AMS campaign hub and the JTF resource hub, resolving the many-to-many relationship between campaigns and the resources assigned to work them. Each row represents a single campaign-to-resource assignment, qualified by an effective date range and an enablement status.

The primary key is defined by the constraint AST_RS_CAMPAIGNS_PK on the surrogate column RS_CAMPAIGN_ID. A unique index, AST_RCA_CAMPAIGN_RESOURCEID_U1, provides the business-key candidate. The documented physical schema contains 13 columns.

Key Information Stored

• RS_CAMPAIGN_ID — the surrogate primary key that uniquely identifies each assignment record; it is the column enforced by AST_RS_CAMPAIGNS_PK and the business-key unique index.
• CAMPAIGN_ID — foreign key to AMS_CAMPAIGNS_ALL_B; identifies the campaign being assigned.
• RESOURCE_ID — foreign key to JTF_RS_RESOURCE_EXTNS; identifies the resource to which the campaign is assigned.
• START_DATE and END_DATE — the effective window during which the assignment is active.
• STATUS — the assignment state used to track workflow or lifecycle position.
• ENABLED_FLAG — a Y/N style flag controlling whether the assignment is currently enabled.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-org/multi-security-group data segregation.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns recording creation and last modification.

The distinction between the surrogate key (RS_CAMPAIGN_ID) and the business candidate key (the campaign/resource pairing reinforced by the unique index) is central to correct de-duplication and integration logic.

Common Use Cases and Queries

Typical scenarios include identifying all resources assigned to a campaign, retrieving the active campaign for a given resource, and driving telesales work lists and dashboards. A representative query joining assignments to resources follows:

• List active assignments: SELECT rs_campaign_id, campaign_id, resource_id FROM ast_rs_campaigns WHERE enabled_flag = 'Y' AND SYSDATE BETWEEN start_date AND end_date;
• Campaigns for a resource: filter on RESOURCE_ID and join to JTF_RS_RESOURCE_EXTNS for resource detail.
• Resource coverage per campaign: group by CAMPAIGN_ID and count DISTINCT RESOURCE_ID.

Reporting uses include workload balancing, campaign coverage analysis, and audit of assignment changes via the WHO columns.

Related Objects

• AMS_CAMPAIGNS_ALL_B — joined via CAMPAIGN_ID; provides campaign definitions.
• JTF_RS_RESOURCE_EXTNS — joined via RESOURCE_ID; provides assignable resource details.
• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID; governs data access.
• AST_RS_CAMPAIGNS_PK and AST_RCA_CAMPAIGN_RESOURCEID_U1 — the PK constraint and unique index enforcing row integrity.
• Other AST module tables and TeleSales concurrent programs that consume campaign-resource assignments.

Together these relationships position AST_RS_CAMPAIGNS as the linking mechanism for campaign-to-resource assignment within the TeleSales application.