Results for “reg_required_flag”

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

Overview

The AST_LM_EVENTS_SRC_V view is a TeleSales (AST) module object owned by the APPS schema. It exposes a consolidated, denormalized result set of event offer (event) records that are simultaneously active and published at the MAIN event level. The view joins the event offer header data to event headers, user-defined statuses, languages, locations, venues, source codes (campaigns), and resources, thereby returning a single flat row per qualifying event offer. Its principal function in Oracle EBS 12.1.1 and 12.2.2 is to serve as the source-of-truth selection for the TeleSales "Events" list, the Scripting/Lead Management (LM) subsystem, and downstream reporting or integration consumers that require event offer data together with its coordinator, venue, and campaign context. Because the view pre-filters on EVENT_LEVEL = 'MAIN', SYSTEM_STATUS_CODE = 'ACTIVE', and ACTIVE_FLAG = 'Y', consumers do not need to re-implement these eligibility rules. The view is read-only and carries no DML capability; it is a query surface only.

Underlying Base Objects

The view is defined over a set of AMS (Marketing) and shared EBS objects. Documented referenced objects include:

• AMS_EVENT_OFFERS_VL — the driving multi-language (VL) view of event offers; supplies most event attributes.
• AMS_EVENT_HEADERS_VL — the VL view of event headers; joined with an outer join on EVENT_HEADER_ID.
• AMS_EVENT_REGISTRATIONS — used in a correlated scalar subquery to compute the remaining registration capacity.
• AMS_USER_STATUSES_VL, AMS_LOOKUPS, AMS_VENUES_V, AMS_P_SOURCE_CODES_V — status, type meaning, venue, and campaign/source code lookups.
• FND_LANGUAGES_VL — resolves the event language code to a display language.
• HZ_LOCATIONS and HZ_PARTIES — Trading Community Architecture tables providing location and venue party names.
• JTF_RS_RES_EMP_VL — resource/employee VL view supplying coordinator attributes.
• HR_GENERAL, HR_PERSON_NAME, HR_SECURITY — HR packages leveraged (directly or indirectly through the resource view) for name formatting and security.

All joins are inner joins except the header join (outer), so an event offer must resolve its user status, language, venue party, resource, and source code to appear in the result set.

Key Columns

Notable columns include:

• EVENT_OFFER_ID / EVENT_OFFER_NAME — primary identifier and name of the event offer.
• EVENT_HEADER_ID / EVENT_HEADER_NAME — parent event header linkage.
• COORDINATOR_ID, COORDINATOR_NAME, COORDINATOR_PHONE — the coordinator is derived from EVT.OWNER_USER_ID mapped to the JTF resource view; COORDINATOR_NAME comes from RES.FULL_NAME. This is the column referenced by the search term coordinator_name.
• CAMPAIGN_ID, CAMPAIGN_NAME, CAMPAIGN_SOURCE_CODE — source code (campaign) context.
• EVENT_START_DATE, EVENT_END_DATE and their _TIME counterparts — scheduling.
• REG_EFFECTIVE_CAPACITY, REG_NUMBER_AVAILABLE — capacity and remaining seats (capacity minus registrations with SYSTEM_STATUS_CODE='REGISTERED').
• EVENT_VENUE_NAME, EVENT_LOCATION, CITY, STATE, COUNTRY — venue and location display attributes.
• FORECASTED_REVENUE, FORECASTED_COST, ACTUAL_REVENUE, ACTUAL_COST — financial measures.
• USER_STATUS, EVENT_TYPE, EVENT_LANGUAGE — decoded lookups.
• ATTRIBUTE1…ATTRIBUTE15, ATTRIBUTE_CATEGORY — DFF (descriptive flexfield) columns.

Common Use Cases and Queries

Typical usage is to list active events with coordinator and campaign detail for TeleSales users or downstream reports. For example, retrieving events and their coordinator:

• List all active MAIN-level events for a coordinator: SELECT event_offer_id, event_offer_name, coordinator_name, event_start_date FROM ast_lm_events_src_v WHERE coordinator_name = :p_coordinator;
• Capacity monitoring: SELECT event_offer_name, reg_effective_capacity, reg_number_available FROM ast_lm_events_src_v WHERE reg_number_available < :threshold;
• Campaign-joined reporting: SELECT campaign_name, COUNT(*) FROM ast_lm_events_src_v GROUP BY campaign_name;
• Association with LOVs that need coordinator selection, where the search term coordinator_name is typically matched via an LIKE or exact predicate.

Because the view applies eligibility filters internally and resolves all lookup meanings, it is preferable to querying the underlying AMS_EVENT_OFFERS_VL and joining lookup tables manually.