Search Results campaign_source_code




Overview
Explore in AI Chat

Overview

AST_LS_EVENTS_V is a TeleSales (AST) module view that exposes event offer information for use within the Oracle E-Business Suite TeleSales and Advanced Marketing (AMS) product family. Its primary role is to present a consolidated, query-ready result set of active, main-level event offers together with their registration availability, location, language, user status, campaign association, and event type classification. The view is most commonly referenced when building prospect lists, campaign audiences, or registration workflows in TeleSales, where agents need to identify events that are currently open for registration.

The view name itself suggests a TeleSales listing ("LS") of events, and it is typically consumed by concurrent programs, forms, or custom reports that require a filtered, business-ready list rather than the raw event offer table. Because it embeds several filtering predicates directly in its definition, callers benefit from consistent eligibility rules across all consumers.

Underlying Base Objects

Although the ETRM metadata documentation notes "Referenced base objects: none documented," the view definition clearly incorporates the following AMS and shared tables:

The joins are largely outer joins for language, lookup, campaign, and location, ensuring that an active event offer still appears even when optional attributes are absent.

Key Columns

Common Use Cases and Queries

Typical uses include TeleSales agent event pick lists, campaign audience generation, and capacity monitoring. A simple query lists active events with available seats:

  • SELECT event_offer_id, event_offer_name, event_type, event_start_date, reg_number_available FROM ast_ls_events_v WHERE reg_number_available > 0;
  • SELECT event_offer_name, city, state, country, campaign_name FROM ast_ls_events_v WHERE event_type = 'Conference';
  • SELECT event_offer_name, reg_number_available FROM ast_ls_events_v ORDER BY reg_number_available DESC;

The view is documented as not implemented in the reference database, so availability should be confirmed in the target 12.1.1 or 12.2.2 instance before use in custom reports.