Search Results ams_event_offers_all_b

Overview

The AMS_EVENT_OFFERS_ALL_B table is a core data object within the Oracle E-Business Suite (EBS) Marketing (AMS) module. It serves as the primary repository for information pertaining to Event Offerings, which represent specific, schedulable instances of a marketing event. An event offering defines the logistical and commercial details for a single occurrence, such as a particular date, time, venue, and pricing. Crucially, the table also stores data for all Agenda Items associated with those offerings, linking the event schedule to its master definition. Its role is central to the management, tracking, and execution of marketing events across operating units, as indicated by the '_ALL_' suffix in its name.

Key Information Stored

The table's structure is defined by its primary and foreign keys, which highlight the critical data points it manages. The primary identifier is the EVENT_OFFER_ID. The table maintains a relationship to its parent event definition via EVENT_HEADER_ID, linking to AMS_EVENT_HEADERS_ALL_B. Key logistical attributes include EVENT_VENUE_ID (linked to AMS_VENUES_B), EVENT_LOCATION_ID (linked to HZ_LOCATIONS), and TIMEZONE_ID. Commercial details are captured through links to pricing lists (PRICELIST_HEADER_ID, PRICELIST_LINE_ID). Operational data includes the event's USER_STATUS_ID, COORDINATOR_ID, OWNER_USER_ID, and funding source (FUND_SOURCE_ID). The PARENT_EVENT_OFFER_ID column supports hierarchical relationships between offerings.

Common Use Cases and Queries

This table is fundamental for operational reporting and process integration in marketing campaigns. Common use cases include generating event schedules, analyzing offering performance, managing resource allocation for coordinators, and integrating event data with financial systems for fund tracking. A typical query might join to related tables to create a comprehensive event offering report:

• Listing all offerings for a specific event header with venue and status details.
• Identifying offerings managed by a specific coordinator within a date range.
• Reporting on offerings linked to a particular price list for revenue analysis.
• Querying agenda items (stored within this table) for a specific EVENT_OFFER_ID to build session schedules.

A sample SQL pattern to retrieve basic offering information would involve joins to AMS_EVENT_HEADERS_ALL_B for the event name and AMS_USER_STATUSES_B for the status meaning.

Related Objects

The table has extensive relationships with other EBS objects, as documented by its foreign keys. Key dependencies include:

• AMS_EVENT_HEADERS_ALL_B: Via EVENT_HEADER_ID (master event definition) and FUND_SOURCE_ID.
• AMS_VENUES_B: Via EVENT_VENUE_ID.
• HZ_LOCATIONS & HZ_TIMEZONES: For physical and temporal location data.
• QP_LIST_HEADERS_B & QP_LIST_LINES: For pricing information (PRICELIST_HEADER_ID, PRICELIST_LINE_ID).
• JTF_RS_RESOURCE_EXTNS: For COORDINATOR_ID and OWNER_USER_ID (resource management).
• AMS_USER_STATUSES_B: For USER_STATUS_ID (lifecycle status).
• OZF_FUNDS_ALL_B & AMS_CAMPAIGNS_ALL_B: Alternative sources for FUND_SOURCE_ID.
• AMS_EVENT_OFFERS_ALL_B (self-referencing): Via PARENT_EVENT_OFFER_ID for hierarchical offerings.
• AMS_ACT_DELIVERY_METHODS: Via EVENT_DELIVERY_METHOD_ID.