Results for “cc_call_strategy”

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

Overview

ASO_I_CAMPAIGNS_V is a read-only view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It is delivered as part of the ASO (Order Capture) product family and exposes campaign information that originates from the Oracle Marketing (AMS) data model. The view is registered in the E-Business Suite Tables and Views Repository (ETRM) with a status of VALID and is described simply as a "View based on Campaigns."

Its principal role is to provide the Order Capture and iStore application layer with a stable, denormalized access point to campaign header data—including campaign identity, status, ownership, funding, media, and channel attributes—without requiring the calling module to join directly against the normalized AMS campaign tables. The "I" prefix denotes an internal/integration-facing view used by Oracle's own forms, concurrent programs, and public APIs rather than a customer-facing reporting object, although it is frequently queried in custom reporting and extensions because of the breadth of campaign attributes it surfaces.

Because the view is a thin projection over an existing AMS view, it carries no independent storage, no indexes, and no triggers. Performance is therefore inherited entirely from the underlying AMS objects, and administrators should expect AMS-level tuning (indexes on CAMPAIGN_ID, STATUS_CODE, and related keys) to determine query behavior.

Underlying Base Objects

The ETRM metadata documents a single referenced base object for this view: AMS_P_CAMPAIGNS_V, itself a view in the AMS (Marketing) schema. The definition of ASO_I_CAMPAIGNS_V is a direct column-by-column SELECT from that AMS view:

• Source object: AMS_P_CAMPAIGNS_V (VIEW)
• Join logic: None — a straight projection of 37 columns
• Filtering: None applied at the ASO layer
• Dependencies: All transitive dependencies (underlying AMS tables such as AMS_CAMPAIGNS_B/_TL and related channel/media entities) are resolved inside AMS_P_CAMPAIGNS_V

The implication is that any column added to or removed from AMS_P_CAMPAIGNS_V will propagate directly to ASO_I_CAMPAIGNS_V, and that row-level security or transitive filters implemented inside the AMS view will be honored automatically. Since there is no ASO-specific WHERE clause, all campaigns visible through AMS_P_CAMPAIGNS_V are visible through this view, subject to the querying user's privileges on the AMS and ASO schemas.

Key Columns

The view exposes 37 columns. The most significant for typical integrations include:

• CAMPAIGN_ID — Primary identifier for the campaign; the join key to most other campaign-related objects.
• CAMPAIGN_NAME, DESCRIPTION, CAMPAIGN_PURPOSE — Descriptive attributes of the campaign header.
• STATUS_CODE, STATUS_DATE — Current lifecycle state of the campaign and the date the status was set.
• OWNER_USER_ID — The application user who owns the campaign.
• PARENT_CAMPAIGN_ID, ROLLUP_TYPE — Support hierarchical/rollup campaign structures.
• CHANNEL_ID, CHANNEL_NAME, CHANNEL_TYPE, CHANNEL_SOURCE — The channel through which the campaign executes; CHANNEL_TYPE is the attribute most commonly queried when filtering campaigns by execution medium (for example, email, telemarketing, or direct mail).
• CHANNEL_INBOUND_FLAG, CHANNEL_OUTBOUND_FLAG — Flag the directional nature of the channel.
• MEDIA_ID, MEDIA_NAME, MEDIA_TYPE_CODE, MEDIA_TYPE_NAME — The specific media placement associated with the campaign.
• FUND_SOURCE_TYPE, FUND_SOURCE_ID — Budget or funding source attribution.
• ACTUAL_EXEC_START_DATE, ACTUAL_EXEC_END_DATE — Actual execution window, distinct from planned dates held elsewhere.
• PARTNER_FLAG, CASCADE_SOURCE_CODE_FLAG, PRIORITY, SOURCE_CODE — Governance and prioritization attributes.
• INBOUND_URL, INBOUND_EMAIL_ID, INBOUND_PHONE_NO, INBOUND_SCRIPT_NAME — Inbound response-handling configuration.
• FF_PRIORITY, FF_OVERRIDE_COVER_LETTER, FF_SHIPPING_METHOD — Fulfillment preferences for campaigns that trigger order capture flows.
• CONTENT_SOURCE, CC_CALL_STRATEGY, CC_MANAGER_USER_ID — Content and call-center coordination attributes.

Common Use Cases and Queries

The view is most often used by Order Capture and iStore components to validate and enrich order context with campaign metadata at the point of order entry. Common scenarios include looking up the channel type for a campaign to drive routing decisions, identifying the owner for notification, and retrieving funding and fulfillment preferences when an order is attributed to a campaign.

A representative query filtering by the frequently searched attribute is:

• SELECT campaign_id, campaign_name, channel_type, status_code FROM apps.aso_i_campaigns_v WHERE channel_type = 'EMAIL' AND status_code = 'ACTIVE';
• SELECT campaign_id, campaign_name, actual_exec_start_date, actual_exec_end_date FROM apps.aso_i_campaigns_v WHERE actual_exec_start_date >= SYSDATE - 30 ORDER BY actual_exec_start_date DESC;
• SELECT c.campaign_id, c.campaign_name, c.channel_name, c.owner_user_id FROM apps.aso_i_campaigns_v c WHERE c.partner_flag = 'Y' AND c.status_code = 'ACTIVE';

Because access is governed by ASO and AMS privileges, custom code should grant EXECUTE or SELECT on the view appropriately rather than on the underlying AMS view, ensuring the supported interface is used.