Results for “num_enrolled”

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

Overview

BIM_EVENT_RESP_SUMM is a summarized response table within the BIM (Marketing Intelligence) product family of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It stores aggregated event-response metrics calculated over user-defined periods rather than transactional-level detail. Rows are not created by online form activity; they are populated exclusively by the BIM_EVENT_RESP_SUMM_PKG concurrent program, which rolls up the underlying response data into period buckets identified by PERIOD_NAME, PERIOD_START_DATE, and PERIOD_END_DATE.

Because the table is a periodic snapshot of an event and event-offering combination, its natural modeling role is that of a satellite, holding measures and audit attributes keyed by an event context and a time period. The documented Data Vault classification (heuristic, mined from the foreign-key structure) is standalone, indicating that no downstream tables reference it and that its relationships are expressed toward shared reference data rather than through an internal hub-and-link lattice. This classification is a modeling suggestion derived from FK topology, not a physical constraint of the schema.

Key Information Stored

The table contains 21 documented columns. Three groups are relevant to consumers:

• Business key: The unique index BIM_EVENT_RESP_SUMM_U1 spans PERIOD_NAME, PERIOD_START_DATE, PERIOD_END_DATE, EVENT_ID, and EVENT_OFFERING_ID. Together these five columns identify a single summarized row — one period per event offering. Note that no dedicated single-column surrogate primary key is documented; the unique index is the de facto row identifier.
• Period and context: PERIOD_NAME carries the user-defined period label, while PERIOD_START_DATE and PERIOD_END_DATE bound the reporting window. EVENT_ID and EVENT_OFFERING_ID tie the row to a specific event and the offering scheduled within it.
• Response measures: Six cumulative counters quantify the funnel — NUM_AVAILABLE, NUM_TARGETED, NUM_RESPONDED, NUM_ENROLLED, NUM_ATTENDED, and NUM_CANCELLED. Read in sequence, they describe progression from audience availability through targeting, response, enrollment, attendance, and cancellation.
• Audit and security: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, plus the concurrent request stamp REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE record how and when the summary was generated. SECURITY_GROUP_ID references FND_SECURITY_GROUPS and enforces multi-org style access partitioning.

Common Use Cases and Queries

The primary use case is period-over-period event response reporting without scanning transactional response tables. Typical queries aggregate the counters by event or by period.

• Funnel analysis for one event offering: select the period columns and the six counters filtered on EVENT_ID and EVENT_OFFERING_ID, ordered by PERIOD_START_DATE, to plot targeting versus attendance trends.
• Conversion reporting: derive ratios such as NUM_RESPONDED / NUM_TARGETED and NUM_ATTENDED / NUM_ENROLLED in the select list, grouped by PERIOD_NAME.
• Refresh auditing: join REQUEST_ID to the concurrent request tables to confirm which run produced a given period's figures and when it last refreshed.
• Security-scoped extracts: always constrain by SECURITY_GROUP_ID in multi-group environments before feeding downstream reporting.

Related Objects

• BIM_EVENT_RESP_SUMM_PKG — the concurrent program package that populates and refreshes this table; the authoritative source of derivation logic for the counter columns.
• FND_SECURITY_GROUPS — referenced by BIM_EVENT_RESP_SUMM.SECURITY_GROUP_ID; the only documented foreign key and the join path for security context.
• FND_CONCURRENT_REQUESTS — joined on REQUEST_ID to trace the program run that generated or updated summary rows.
• FND_APPLICATION and FND_CONCURRENT_PROGRAMS — joined on PROGRAM_APPLICATION_ID and PROGRAM_ID to resolve the owning application and program definition.
• The BIM event and event-offering base tables implied by EVENT_ID and EVENT_OFFERING_ID — the descriptive parents supplying event and offering names for reports.