Results for “inbound_script_name”

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

Overview

AMS_P_CAMPAIGNS_V is a public view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the AMS (Marketing) product family. It returns all marketing campaigns along with related descriptive, financial, channel, and execution information, and functions as the primary read-only access point for campaign data in custom reports, concurrent programs, and integration interfaces.

The view is defined over AMS_CAMPAIGNS_VL, the multi-language base view for the AMS_CAMPAIGNS table, and applies a fixed set of filter predicates. Only campaigns where ROLLUP_TYPE is not 'RCAM', PRIVATE_FLAG equals 'N', TEMPLATE_FLAG equals 'N', ACTIVE_FLAG equals 'Y', and SHOW_CAMPAIGN_FLAG equals 'Y' are returned. Campaigns hidden as private, templates, inactive, or suppressed through the display flag are therefore excluded. Because the view references the VL layer, the language-dependent campaign name and description are automatically resolved to the session language.

Underlying Base Objects

The documented base object for AMS_P_CAMPAIGNS_V is AMS_CAMPAIGNS_VL (VIEW). The base view in turn reads from the AMS_CAMPAIGNS table, which stores campaigns in a single row per campaign, with translated attributes such as CAMPAIGN_NAME and DESCRIPTION resolved by the VL layer according to the AMS language setup. The public view exposes the CAM.CAMPAIGN_ID and CAM.CAMPAIGN_NAME columns directly from the VL layer, and passes through numerous operational attributes defined in the campaign entity, including funding, channel, fulfillment, and call center attributes. Several columns tied to media and channel dimension tables are represented by literal NULL values in the view definition, reflecting the pure marketing attributes delivered by the base view rather than denormalized dimension lookups.

Key Columns

• CAMPAIGN_ID / CAMPAIGN_NAME / DESCRIPTION — Primary campaign identifier and, from the VL layer, the language-specific name and description.
• CAMPAIGN_PURPOSE — Alias for CAMPAIGN_TYPE, indicating the campaign's functional classification.
• ROLLUP_TYPE — Campaign rollup classification; 'RCAM' rows are excluded by the view filter.
• STATUS_CODE / STATUS_DATE — Current campaign lifecycle status and the date it was set.
• SOURCE_CODE / OWNER_USER_ID — Origin of the campaign and the user who owns it.
• PARENT_CAMPAIGN_ID / PRIORITY — Parent campaign reference and priority ranking in the campaign hierarchy.
• PARENT_CAMPAIGN_ID / PARTNER_FLAG — Indicates whether the campaign involves partner participation.
• FUND_SOURCE_TYPE / FUND_SOURCE_ID — Funding source classification and identifier.
• ACTUAL_EXEC_START_DATE / ACTUAL_EXEC_END_DATE — Actual execution start and end dates of the campaign.
• MEDIA_ID / MEDIA_NAME / MEDIA_TYPE_CODE / MEDIA_TYPE_NAME — Media association; the name and type columns are returned as NULL in the view text.
• CHANNEL_ID / CHANNEL_NAME / CHANNEL_TYPE / CHANNEL_SOURCE — Channel association; CHANNEL_SOURCE is mapped from ARC_CHANNEL_FROM, and CHANNEL_NAME and CHANNEL_TYPE are NULL literals.
• INBOUND_URL / INBOUND_EMAIL_ID / INBOUND_PHONE_NO — Inbound response contact points for the campaign.
• FF_PRIORITY / FF_OVERRIDE_COVER_LETTER / FF_SHIPPING_METHOD — Fulfillment attributes controlling shipping and cover letter behavior.
• CC_CALL_STRATEGY / CC_MANAGER_USER_ID — Call center strategy and campaign manager assignment.
• START_PERIOD_NAME / END_PERIOD_NAME / CAMPAIGN_CALENDAR — Accounting or calendar period and calendar context for the campaign.
• CITY_ID — The city identifier associated with the campaign; this is the column most frequently used to drive geographic filtering and city-level campaign reporting.
• GLOBAL_FLAG / CUSTOM_SETUP_ID / BUSINESS_UNIT_ID — Multi-org and setup-related flags; BUSINESS_UNIT_ID supports operating unit context.
• RELATED_EVENT_FROM / RELATED_EVENT_ID — Reference to a related event where campaign execution is event-driven.
• VERSION_NO / CONTENT_SOURCE / APPLICATION_ID — Versioning, content origin, and owning application identifiers.

Common Use Cases and Queries

Typical reporting scenarios include listing all active marketing campaigns for a business unit, reporting campaign execution dates, and filtering campaigns by city. Because the view already restricts to active, non-private, non-template campaigns, most reporting queries only add business or geographic predicates.

Filtering by city, the column targeted by the search query:

• SELECT campaign_id, campaign_name, city_id, status_code FROM apps.ams_p_campaigns_v WHERE city_id = :p_city_id;

Listing campaigns with execution dates and funding source:

• SELECT campaign_id, campaign_name, actual_exec_start_date, actual_exec_end_date, fund_source_type, fund_source_id FROM apps.ams_p_campaigns_v ORDER BY actual_exec_start_date DESC;

Reporting active campaigns by call center strategy or channel:

• SELECT campaign_id, campaign_name, cc_call_strategy, channel_source, channel_id FROM apps.ams_p_campaigns_v WHERE cc_call_strategy IS NOT NULL;

Restricting to a business unit and city combination for multi-org reporting:

• SELECT campaign_id, campaign_name, business_unit_id, city_id FROM apps.ams_p_campaigns_v WHERE business_unit_id = :p_org_id AND city_id = :p_city_id;

Because media and channel name columns return NULL, queries requiring those descriptive values must join to the corresponding media and channel tables using MEDIA_ID and CHANNEL_ID respectively. The view should be treated as read-only; campaign creation and updates must occur through the AMS marketing application APIs and forms.