Results for “ams_event_offers_only_v”

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

Overview

AMS_EVENT_OFFERS_ONLY_V is a reporting and integration view owned by the APPS schema within the Oracle Marketing (AMS) module. As its name indicates, the view exposes marketing event offerings — the individual, independently schedulable sessions or occurrences that belong to a parent marketing event — while deliberately omitting the parent event header columns. The description states plainly that the view "returns the general information about marketing event offerings without event header information."

This design makes the view a lightweight projection suited to list-of-values populations, concurrent extracts, and interface programs that require session-level detail without the overhead of joining the full event header. The view is documented as VALID in EBS 12.1.1 and 12.2.2, and its structure is stable across both releases, which makes it a reliable dependency for custom reports and third-party marketing integrations.

Underlying Base Objects

The view draws on a mix of base views and synonyms. The primary driver is AMS_EVENT_OFFERS_VL, the translation-enabled base view for event offerings, which supplies all EVO-prefixed columns. Supporting lookups and descriptive attributes are resolved through joins to:

• AMS_LOOKUPS — provides decoded meanings such as LKUP4.MEANING for EVENT_TYPE.
• AMS_USER_STATUSES_VL — supplies the user-defined status name (AUS.NAME).
• AMS_ACT_DELIVERY_METHODS_V — resolves the delivery media type code for the event delivery method.
• AMS_VENUES_VL — supplies the venue name (AVN.VENUE_NAME).
• FND_LANGUAGES_VL — returns the NLS language description (LANG.NLS_LANGUAGE) for the event language code.
• HZ_LOCATIONS (synonym) — resolves the event location into city, state, province, and country, concatenated into a single display string.
• HZ_TIMEZONES_VL — referenced for time zone resolution on event scheduling columns.

Key Columns

Column families fall into several logical groups. Identifying and classification columns include ROW_ID, EVENT_OFFER_ID, EVENT_HEADER_ID (retained as a foreign key reference even though header detail is not projected), EVENT_TYPE_CODE and its decoded EVENT_TYPE, SOURCE_CODE, EVENT_LEVEL, and OBJECT_VERSION_NUMBER for optimistic locking.

Registration control is the richest area of the view. Columns include REG_REQUIRED_FLAG, REG_CHARGE_FLAG, REG_INVITED_ONLY_FLAG, REG_FROZEN_FLAG, REG_WAITLIST_ALLOWED_FLAG, REG_OVERBOOK_ALLOWED_FLAG, REG_MINIMUM_CAPACITY, REG_MAXIMUM_CAPACITY, REG_OVERBOOK_PCT, REG_WAITLIST_PCT, and REG_EFFECTIVE_CAPACITY. The AUTO_REGISTER_FLAG column is part of this family: it indicates whether registrants are automatically enrolled into the offering when eligibility conditions are met, rather than requiring an explicit registration action. Because the user searched for auto_register_flag, it is worth noting that the column is exposed directly from AMS_EVENT_OFFERS_VL with no decoding join, so values are returned as the raw stored flag ('Y'/'N').

Scheduling and logistics columns include EVENT_START_DATE, EVENT_START_DATE_TIME, EVENT_END_DATE, EVENT_END_DATE_TIME, EVENT_DURATION, EVENT_DURATION_UOM_CODE, REG_START_DATE/TIME, REG_END_DATE/TIME, and the venue and location columns. Financial and status columns include ACTUAL_REVENUE, FORECASTED_REVENUE, ACTUAL_COST, FORECASTED_COST, FUND_SOURCE_TYPE_CODE, FUND_AMOUNT_TC/FC, currency codes, SYSTEM_STATUS_CODE, USER_STATUS_ID, and LAST_STATUS_DATE.

Common Use Cases and Queries

The most frequent use is a filtered listing of offerings for a given status or date window, typically inside a custom report or an LOV query. A representative query retrieving active offerings that auto-register:

• SELECT event_offer_id, event_type, event_start_date, reg_start_date, auto_register_flag
• FROM apps.ams_event_offers_only_v
• WHERE active_flag = 'Y'
• AND auto_register_flag = 'Y'
• AND event_start_date >= SYSDATE
• ORDER BY event_start_date;

A second common pattern joins the view back to AMS_EVENT_HEADERS to reintroduce the omitted header context when full reporting is needed, filtering on organization_id and private_flag to respect multi-org and security rules. Because the view is not secured with row-level organization policy by default, integration code must apply the organization_id predicate explicitly to avoid cross-org leakage.