Results for “timezone_name”

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

Overview

The AST_LM_EVENTS_V view is an Oracle E-Business Suite 12.1.1 / 12.2.2 reporting object owned by the APPS schema and registered under the AST – TeleSales product family. It exposes event offer information created and maintained through the Oracle Marketing (AMS) event management engine as surfaced to TeleSales users. The view consolidates event header, offer, venue, location, language, timezone, user status, coordinator, and campaign source metadata into a single, denormalized result set, which allows TeleSales agents and reporting tools to query active event offers without manually joining the underlying transactional and reference tables. It is defined as a view (status VALID) and is therefore read-only with respect to the base transaction tables. The name prefix AST_LM denotes the TeleSales (AST) logical model objects, and the suffix _V denotes the deployed view artifact.

Underlying Base Objects

The documented view definition references the following objects, per ETRM 12.2.2 metadata: AMS_EVENT_HEADERS_VL, AMS_EVENT_OFFERS_VL, AMS_EVENT_REGISTRATIONS (SYNONYM), AMS_LOOKUPS, AMS_P_SOURCE_CODES_V, AMS_USER_STATUSES_VL, AMS_VENUES_V, FND_LANGUAGES_VL, FND_TIMEZONES_VL, HR_GENERAL (PACKAGE), HR_PERSON_NAME (PACKAGE), HR_SECURITY (PACKAGE), HZ_LOCATIONS (SYNONYM), HZ_PARTIES (SYNONYM), and JTF_RS_RES_EMP_VL. The view joins the header and offer _VL (base-plus-translation) views to retrieve language-aware names, then outer-joins headers, lookups, user statuses, languages, timezones, venues, locations, parties, source codes, and the JTF resource employee view. HR package references (HR_GENERAL, HR_PERSON_NAME, HR_SECURITY) are pulled in transitively via JTF_RS_RES_EMP_VL, and they enforce Oracle HRMS security at query time. The primary filter in the view restricts results to events where EVENT_LEVEL = 'MAIN'.

Key Columns

The projection exposes a broad set of descriptive and financial columns. Event identifiers include EVENT_OFFER_ID, EVENT_OFFER_NAME, EVENT_HEADER_ID, and EVENT_HEADER_NAME. Capacity management exposes REG_EFFECTIVE_CAPACITY and a derived REG_NUMBER_AVAILABLE, computed as effective capacity minus the count of registrations in the AMS_EVENT_REGISTRATIONS table where SYSTEM_STATUS_CODE = 'REGISTERED'. Registration behavior is controlled by REG_INVITED_ONLY_FLAG and REG_REQUIRED_FLAG. Financial metrics include FORECASTED_REVENUE, FORECASTED_COST, ACTUAL_REVENUE, and ACTUAL_COST. Scheduling columns include EVENT_START_DATE, EVENT_START_DATE_TIME, EVENT_END_DATE, EVENT_END_DATE_TIME, TIMEZONE_ID, and TIMEZONE_NAME. Descriptive fields include EVENT_LOCATION (concatenation of city, state, and country), CITY, STATE, PROVINCE, COUNTRY, EVENT_TYPE_CODE and its lookup meaning EVENT_TYPE, and USER_STATUS. The COORDINATOR_ID maps to OWNER_USER_ID, with COORDINATOR_NAME and COORDINATOR_PHONE drawn from JTF_RS_RES_EMP_VL. Campaign linkage is provided via CAMPAIGN_ID, CAMPAIGN_NAME, and CAMPAIGN_SOURCE_CODE. The standard ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 descriptive flexfield columns are also exposed. Language filtering uses EVENT_LANGUAGE_CODE and EVENT_LANGUAGE (translated via FND_LANGUAGES_VL).

Common Use Cases and Queries

Typical usage retrieves the available seats, coordinator identity, and campaign context for upcoming event offers. A representative query follows:

• SELECT EVENT_OFFER_NAME, EVENT_START_DATE, EVENT_VENUE_NAME, COORDINATOR_NAME, REG_NUMBER_AVAILABLE FROM APPS.AST_LM_EVENTS_V WHERE EVENT_START_DATE >= SYSDATE AND ACTIVE_FLAG = 'Y' ORDER BY EVENT_START_DATE;
• Capacity reporting: select offers where REG_NUMBER_AVAILABLE is low or negative, using the derived expression against AMS_EVENT_REGISTRATIONS.
• Coordinator workload: group by COORDINATOR_ID and COORDINATOR_NAME (from JTF_RS_RES_EMP_VL) to count active events per coordinator.
• Campaign attribution: join or filter on CAMPAIGN_ID / CAMPAIGN_SOURCE_CODE to reconcile event performance with AMS source code records.
• Localization: filter on EVENT_LANGUAGE_CODE to return offers in a specific language.

Because the view queries HR security packages through JTF_RS_RES_EMP_VL, results are subject to the querying user's HR security profile, which is important when building concurrent programs or integrations that run under a service account.