Search Results event_num_registered

Overview

ICX_AS_EVENTS_V is a reporting view in the Oracle iProcurement (ICX) module of Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented description is "Events View." The name and column structure indicate that it exposes iProcurement promotional and event records—seminars, training sessions, vendor events, and similar catalog activities managed through the promotions framework—denormalized into a single, query-friendly row per event. The ETRM record notes that the view is "Not implemented in this database," meaning it is a shipped definition that is not compiled into every instance (for example, when iProcurement's promotions or events functionality is not licensed or enabled). Its primary role is to serve as the read-only source for event listings, registration summaries, and integration extracts, sparing report authors and interface developers the effort of reimplementing the joins across promotions, lookup, person, facility, and territory tables.

Underlying Base Objects

The view is defined over the promotions table, aliased PROM (identifiable as ICX_PROMOTIONS or its synonym), which supplies an explicit ROWID and all primary event attributes: PROMOTION_ID, CODE, NAME, TYPE, STATUS, and the audit columns CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. Around this base, the definition joins several supporting objects: two lookup aliases, ASLKP1 and ASLKP2, each contributing a MEANING column that translates coded values (typically TYPE and STATUS) into display text; OWNER_PER and COORD_PER, person joins on OWNER_PERSON_ID and EVENT_COORDIN_PERSON_ID that return first and last names for the event owner and the event coordinator; EVNTFAC, the event facility, contributing CODE, NAME and the full address block (CITY, STATE, ADDRESS1–4, POSTAL_CODE, PROVINCE, COUNTY, COUNTRY_CODE, AREA_CODE); and FNDTERR, the territory/geography table, supplying TERRITORY_SHORT_NAME. The ETRM metadata lists no formally documented base objects, but the view text itself establishes these relationships unambiguously.

Key Columns

• PROMOTION_ID / CODE / NAME / TYPE / STATUS — the event's primary identifier and descriptive attributes; TYPE and STATUS meanings are resolved through ASLKP1 and ASLKP2.
• EVENT_ENROLLMENT_FEE — the per-attendee fee for the event. This is the column most commonly searched for by name and is central to registration-cost reporting.
• Event scheduling — EVENT_START_DATE, EVENT_END_DATE, EVENT_START_TIME, EVENT_END_TIME, and EVENT_REG_TIME.
• Registration control — EVENT_MAX_ATTENDEES, EVENT_OVERBOOK_PERCENT, EVENT_NUM_REGISTERED, and EVENT_ENROLLMENT_FROZEN_FLAG, which indicates that enrollment is closed.
• Financial tracking — CURRENCY_CODE, EXPECTED_PROMOTION_COST, ACTUAL_PROMOTION_COST, and EXPECTED_NUM_OF_RESPONSES.
• Personnel — OWNER_PERSON_ID, EVENT_COORDIN_PERSON_ID, and the EVENT_FAC_STAFF_* columns (name, area code, phone, extension).
• Additional attributes — LONG_DESCRIPTION, COMMENTS, the ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 flexfield columns, and EVENT_FOOD_AVAILABLE_FLAG.

Common Use Cases and Queries

A frequent requirement is simply listing events with their enrollment fees and currency. Because the fee is stored as a number, the view applies FND_CURRENCY.SAFE_GET_FORMAT_MASK to produce a display-ready figure, so a query may select both the raw and formatted values. Typical uses include catalog/calendar listings, reconciliation of registered attendees against maximum capacity, budget-versus-actual cost analysis, and extracts feeding external registration systems.

SELECT promotion_id, name, event_start_date, event_end_date,
       event_enrollment_fee, currency_code, event_num_registered
FROM   apps.icx_as_events_v
WHERE  status = 'ACTIVE'
AND    event_start_date >= SYSDATE
ORDER  BY event_start_date;

Because the promotion record is singular, the view does not itself expose individual registrations or billing transactions. Analysts needing attendee-level detail must join outward to the underlying enrollment and order tables using PROMOTION_ID as the linking key, while this view continues to supply the event header, facility address, and coordinator information.