Results for “event_required_flag”

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

Overview

AMS_EVENT_OFFERS_AGENDA_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the AMS (Marketing) product family. Its documented purpose is to return general information about a marketing event offering agenda. As a view rather than a base table, it exposes a denormalized, query-ready projection of event offering data without requiring consumers to join the underlying transactional tables themselves.

The defining characteristic of this view is its restriction to sub-level event offerings. The view text applies the predicate EVO.EVENT_LEVEL='SUB', meaning only offerings whose event level is SUB are returned. Parent event offerings are therefore excluded from the result set, except where referenced through the self-join for parent event offer names. This makes the view suitable for agenda-oriented reporting, where the grain of interest is the individual sub-event rather than the top-level event offer.

In Oracle EBS 12.1.1 and 12.2.2, the view serves as a reporting and integration surface for the AMS Marketing module. It is not a table of record; all data originates from the joining views and tables listed in its definition, and it inherits the security and validation semantics of those objects.

Underlying Base Objects

The view is defined over the following documented objects:

• AMS_EVENT_OFFERS_VL (VIEW) — referenced twice, once as the primary alias EVO and once as PEVO for the parent offering self-join.
• AMS_EVENT_HEADERS_VL (VIEW) — outer-joined source of the event header name.
• AMS_USER_STATUSES_VL (VIEW) — source of the user-defined status name.
• FND_LANGUAGES_VL (VIEW) — outer-joined source of the NLS language description.
• AMS_ACT_DELIVERY_METHODS_V (VIEW) — outer-joined source of the delivery media name.
• AMS_VENUES_VL (VIEW) — outer-joined source of the venue name.
• HZ_TIMEZONES_VL (VIEW) — outer-joined source of the timezone name.
• HZ_LOCATIONS (SYNONYM) — outer-joined source of location, city, state, province and country attributes.

Join conditions link EVENT_OFFER_ID-based foreign keys from the primary offer record to each lookup object. The parent join is outer (+), the header, language, venue, timezone, delivery method and location joins are outer, while the user status join to AMS_USER_STATUSES_VL is mandatory. The view therefore returns a row for every SUB-level event offer, regardless of whether optional descriptive attributes exist.

Key Columns

The column set includes identifiers, descriptive attributes and audit fields. EVENT_OFFER_ID is the primary identifier, and PARENT_EVENT_OFFER_ID links each sub-level offer to its parent. EVENT_HEADER_ID ties the offer to its event header.

The column most relevant to the search term event_required_flag is EVENT_REQUIRED_FLAG, which is exposed directly from AMS_EVENT_OFFERS_VL and indicates whether the event offering is designated as required. Related status and control flags include ACTIVE_FLAG, PRIVATE_FLAG, PARTNER_FLAG, EVENT_STANDALONE_FLAG and SYSTEM_STATUS_CODE. Scheduling attributes include EVENT_START_DATE, EVENT_START_DATE_TIME, EVENT_END_DATE, EVENT_END_DATE_TIME and LAST_STATUS_DATE.

Descriptive columns include EVENT_OFFER_NAME, EVENT_HEADER_NAME, DELIVERY_MEDIA_NAME, VENUE_NAME, the concatenated location string, TIMEZONE_ID and its name, plus URL, PHONE and EMAIL. Audit columns ROW_ID, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER and APPLICATION_ID are also present.

Common Use Cases and Queries

Typical uses include agenda reports for a marketing event, population of downstream campaign calendars, and integration extracts feeding external registration or scheduling systems. A common query filters on the required flag and active status for a given event header:

• SELECT event_offer_id, event_offer_name, event_required_flag, event_start_date_time, event_end_date_time FROM apps.ams_event_offers_agenda_v WHERE event_header_id = :header_id AND active_flag = 'Y';
• SELECT event_offer_name, parent_event_offer_id, venue_name, city, state FROM apps.ams_event_offers_agenda_v WHERE event_required_flag = 'Y';
• SELECT event_offer_name, delivery_media_name, nls_language, name FROM apps.ams_event_offers_agenda_v WHERE sysdate BETWEEN event_start_date AND event_end_date;

Because the view is confined to EVENT_LEVEL='SUB', queries seeking parent-level offerings must be redirected to AMS_EVENT_OFFERS_VL or a related view. All access should be granted through the APPS schema or a custom synonym to preserve the intended security model.