Results for “bim_event_resp_summ_u1”

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

Overview

BIM.BIM_EVENT_RESP_SUMM is a summary (aggregate) table in the Oracle EBS Event Management (BIM) schema. It stores pre-aggregated response and attendance metrics for events and event offerings, rolled up to a user-defined period. Rather than querying transactional registration, enrollment, and attendance records directly, reporting and analytical processes read from this table to obtain fast, period-based measures of event performance.

The table is populated by the concurrent program BIM_EVENT_RESP_SUMM_PKG, which the ETRM documentation identifies as the primary data loader. In EBS 12.1.1 and 12.2.2 the object resides in the APPS_TS_ARCHIVE tablespace with PCT FREE 10, reflecting its role as a retention/history-oriented aggregate rather than an actively mutated transactional table.

Under a heuristic Data Vault classification, the structure of BIM_EVENT_RESP_SUMM suggests a satellite pattern: the descriptive period and measure columns (capacity, targeted, responded, enrolled, attended, cancelled) are functionally dependent on the composite business key formed by the event, offering, and period, and are refreshed as a unit by the summarization program. It is not a hub or link, since it carries no independent business entity identity beyond the keys it references.

Key Information Stored

The table contains 21 documented columns. The most operationally significant are:

• EVENT_ID (VARCHAR2(80)) — identifier of the event; a sentinel value of -999 indicates an unknown event. Event details are resolved via the view BIM_DIMV_EVENT_HEADERS.
• EVENT_OFFERING_ID (VARCHAR2(80)) — identifier of the specific offering of the event; -999 signifies unknown. Offering details are resolved via BIM_DIMV_EVENT_OFFERS.
• PERIOD_NAME (VARCHAR2(25)) — the name of the period to which the data is summarized.
• PERIOD_START_DATE and PERIOD_END_DATE (DATE) — the boundaries of the summarizing period.
• NUM_AVAILABLE — event capacity available.
• NUM_TARGETED — number of invitees/persons targeted for the event.
• NUM_RESPONDED — number of persons who responded.
• NUM_ENROLLED — number enrolled.
• NUM_ATTENDED — number attended.
• NUM_CANCELLED — number cancelled.
• SECURITY_GROUP_ID — the security group under which the row is protected; the only documented foreign key, referencing FND_SECURITY_GROUPS.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program audit columns identifying the last summarization run that touched the row.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.

The business key is enforced by the unique index BIM_EVENT_RESP_SUMM_U1 on (PERIOD_NAME, PERIOD_START_DATE, PERIOD_END_DATE, EVENT_ID, EVENT_OFFERING_ID). This composite index — the subject of the original search — is the key to both uniqueness enforcement and efficient lookup by period and event.

Common Use Cases and Queries

Typical reporting scenarios include event performance dashboards (targeted vs. responded vs. enrolled vs. attended conversion), capacity utilization, cancellation analysis, and period-over-period trend reporting. A representative query joining the unique key columns to dimension views:

• SELECT s.period_name, h.event_name, o.offering_name, s.num_targeted, s.num_responded, s.num_enrolled, s.num_attended FROM bim_event_resp_summ s, bim_dimv_event_headers h, bim_dimv_event_offers o WHERE s.event_id = h.event_id AND s.event_offering_id = o.event_offering_id AND s.period_name = :period;
• Conversion/response-rate analysis: compute num_responded/num_targeted, num_enrolled/num_responded, and num_attended/num_enrolled per event and offering.
• Capacity utilization: NUM_AVAILABLE vs. NUM_ENROLLED by period.
• Incremental refresh auditing: filter by REQUEST_ID or PROGRAM_UPDATE_DATE to verify the latest BIM_EVENT_RESP_SUMM_PKG run completed.

Because the data is pre-summarized, queries should filter on the leading columns of BIM_EVENT_RESP_SUMM_U1 (PERIOD_NAME and the period dates) to leverage the index. Rows with EVENT_ID or EVENT_OFFERING_ID of -999 should be excluded or handled explicitly in dimensional reporting.

Related Objects

• BIM.BIM_EVENT_RESP_SUMM_PKG — the concurrent program/package that populates and refreshes this table.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID; enforces multi-org/security group isolation.
• BIM_DIMV_EVENT_HEADERS — dimension view used to resolve EVENT_ID to event attributes.
• BIM_DIMV_EVENT_OFFERS — dimension view used to resolve EVENT_OFFERING_ID to offering attributes.
• BIM.BIM_EVENT_RESP_SUMM_U1 — the unique index on the business key, used for lookups and uniqueness enforcement.
• APPS_TS_ARCHIVE tablespace — storage location shared with related historical summary objects.

In summary, BIM_EVENT_RESP_SUMM is a period-summarized satellite-style aggregate that supplies fast, secure, event- and offering-level response metrics for Oracle EBS Event Management reporting in both 12.1.1 and 12.2.2.