Results for “confirmed_flag”

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

Overview

ICX_AS_EVENT_ENROLLMENTS_V is a reporting view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 associated with the ICX (Oracle iProcurement) product family, though its underlying data originates from the Oracle Advanced Scheduler / Oracle Marketing event enrollment schema. ETRM documents it as the "Enrolled Attendees View." Its purpose is to present a denormalized, human-readable picture of event enrollment records by joining enrollment facts to customer, contact, phone, and lookup information in a single queryable object.

The view exposes enrollment-level attributes alongside descriptive customer and contact data, making it well-suited for both reporting and lightweight integration scenarios where consumers need attendee detail without navigating the full relational model. Notably, the ETRM metadata records the object as "Not implemented in this database" and lists no documented referenced base objects, which indicates the view is optional, context-dependent, and may be absent or superseded in a given EBS instance. Confirmation against the live data dictionary (for example, via ALL_VIEWS and ALL_DEPENDENCIES) is therefore recommended before relying on it.

Underlying Base Objects

The view text identifies five objects, of which one is the driving base table and four are joined sources:

• AS_EVENT_ENROLLMENTS (EVNTENR) — the primary enrollment fact table supplying the core columns, including enrollment identifiers, status, payment, and attendance counts. The view's FROM clause begins here and the other objects are outer/inner dependent joins.
• AS_LOOKUPS (ASLKP1) — decoded for enrollment status, constrained to LOOKUP_TYPE = 'EVENT_ENROLLMENT_STATUS' and joined on STATUS_CODE.
• RA_CUSTOMERS (CUST) — inner-joined on CUSTOMER_ID to provide CUSTOMER_NAME.
• RA_CONTACTS (CONT) — inner-joined on CONTACT_ID to provide LAST_NAME, FIRST_NAME, and JOB_TITLE.
• RA_PHONES (PHON) — outer-joined (indicated by the (+) operator) on CONTACT_ID, restricted to the primary (PRIMARY_FLAG = 'Y') and active (STATUS = 'A') phone, supplying phone number, area code, and extension.

Because CUSTOMER_ID and CONTACT_ID are mandatory joins, enrollment rows lacking a matching customer or contact are excluded from the view's result set.

Key Columns

The view returns the full enrollment column set plus descriptive joins. Principal columns include:

• EVENT_ENROLLMENT_ID — unique identifier of the enrollment record.
• EVENT_ID — the scheduled event to which the attendee is enrolled.
• CUSTOMER_ID / CONTACT_ID / ADDRESS_ID — party linkage keys.
• CUSTOMER_NAME — from RA_CUSTOMERS; the enrolling party.
• FIRST_NAME, LAST_NAME, JOB_TITLE — from RA_CONTACTS, giving the attendee identity and their professional title (the column surfaced by the user's search for "contact_job_title").
• STATUS_CODE / MEANING — the coded status and its decoded lookup meaning.
• NUM_ENROLLED, NUM_ATTENDED, CONFIRMED_FLAG, STATUS_CHANGE_FLAG — enrollment counts and workflow indicators.
• PAYMENT_AMOUNT — fees associated with the enrollment.
• PHONE_NUMBER, AREA_CODE, EXTENSION — primary contact telephone data.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the standard EBS descriptive flexfield columns retained from the base table.
• WHO/audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and the concurrent program columns.

Common Use Cases and Queries

Typical uses include attendee rosters, event participation summaries, contact-review reports, and feeder queries for downstream attendee or marketing integrations. A representative query joining the view to the event header and filtering on job title is shown below:

• Attendee roster with contact title: SELECT event_id, last_name, first_name, job_title, meaning AS status FROM icx_as_event_enrollments_v WHERE event_id = :p_event_id ORDER BY last_name, first_name;
• Confirmed and paid attendees: SELECT customer_name, first_name, last_name, job_title, payment_amount FROM icx_as_event_enrollments_v WHERE confirmed_flag = 'Y' AND payment_amount > 0;
• Count by status: SELECT meaning, COUNT(*) FROM icx_as_event_enrollments_v GROUP BY meaning;
• Contact contactability check: SELECT last_name, first_name, phone_number, area_code, extension FROM icx_as_event_enrollments_v WHERE phone_number IS NOT NULL;

Consumers should note the mandatory customer/contact joins and the outer phone join, and should verify view availability in each environment given the ETRM "Not implemented" annotation.