Results for “as_events_v”

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

Overview

AS_EVENTS_V is a reporting view within the AS (Sales Foundation) product of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. It presents event-related promotion data, exposing the attributes that describe marketing events, seminars, trade shows, and similar activities managed through the Sales Foundation promotion infrastructure. The view's primary purpose is to denormalize the promotion record into a single, query-friendly result set that joins lookup meanings, party names, facility addresses, and territory identifiers, allowing report writers and integration developers to retrieve fully described event records without reconstructing the join logic themselves.

The view is documented by ETRM as "Events view," and the metadata explicitly notes that it is not implemented in the reference database, meaning the view must be created in a target environment before it can be queried. Because the metadata records no documented referenced base objects, the SELECT text itself serves as the authoritative source for identifying the underlying tables.

Underlying Base Objects

Analysis of the view text shows that the driving table is the promotion table, aliased as PROM; the ROWID of the promotion row is carried forward as the first selected column. Supporting joins supply descriptive and lookup information:

• Promotion base table (PROM) — supplies promotion identity, code, status, type, currency, cost, response, and event scheduling columns.
• Lookup tables (ASLKP1, ASLKP2) — contribute translated MEANING values, correlating to the lookup codes held on the promotion record (for example, type and status).
• Person tables (OWNER_PER, COORD_PER) — provide FIRST_NAME and LAST_NAME for the promotion owner and the event coordinator.
• Event facility table (EVNTFAC) — provides facility code, name, address lines, city, state, province, county, postal code, country, phone, and directions.
• Territory table (FNDTERR) — supplies TERRITORY_SHORT_NAME for the facility's territory.
• Event name table (EVNTNAM) — supplies the event NAME and DESCRIPTION.

The view therefore functions as a convenience layer over the promotion and event facility model, joining each event promotion to its naming, ownership, coordination, and location context.

Key Columns

Several columns are particularly significant for reporting and for searches referencing event status. Because the view exposes PROM.STATUS directly, a query searching on "event_status" would typically filter or display this column, optionally alongside the lookup MEANING column that resolves the status code into a user-facing value. Other notable columns include PROM.PROMOTION_ID, PROM.CODE, PROM.TYPE, PROM.ENABLED_FLAG, and PROM.CURRENCY_CODE. Financial and capacity measures are represented by EXPECTED_PROMOTION_COST, ACTUAL_PROMOTION_COST, EXPECTED_NUM_OF_RESPONSES, EVENT_ENROLLMENT_FEE, EVENT_MAX_ATTENDEES, EVENT_OVERBOOK_PERCENT, and EVENT_NUM_REGISTERED. Scheduling is captured by EVENT_START_DATE, EVENT_END_DATE, EVENT_START_TIME, EVENT_END_TIME, and EVENT_REG_TIME. Facility staff details are held in EVENT_FAC_STAFF_LAST, EVENT_FAC_STAFF_FIRST, and related contact columns, while the fifteen ATTRIBUTE columns and ATTRIBUTE_CATEGORY provide the standard EBS descriptive flexfield extension points.

Common Use Cases and Queries

Typical uses include event calendars, enrollment reporting, cost-versus-expected-response analysis, and integration extracts that publish event data to external marketing or CRM systems. A representative query filtering on event status is shown below.

• Listing active events with resolved status meaning.
• Reporting enrollment against maximum attendees.
• Extracting facility contact and address information for event logistics.

SELECT promotion_id, code, name, status, event_start_date, event_end_date, event_num_registered FROM as_events_v WHERE status = 'ACTIVE';

Because the view is not implemented in the reference database, deployments must verify its existence before use and should confirm column availability against the site-specific view definition, since the SELECT text in the documentation is complete only for the reproduction excerpt provided.