Results for “as_event_fac_rooms_u2”

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

Overview

OSM.AS_EVENT_FAC_ROOMS is a transactional master table in the Oracle E-Business Suite Event Management module (application short name AS). It stores the individual rooms or sub-spaces that belong to a bookable event facility, such as a hotel ballroom, conference center, or training venue. Each row represents one physical room, including its scheduling identity, physical characteristics, and pricing attributes. The table resides in the OSM schema and is exposed in EBS through the APPS synonym AS_EVENT_FAC_ROOMS, with FND design data registered as AS.AS_EVENT_FAC_ROOMS. Its status is VALID in both EBS 12.1.1 and 12.2.2.

The metadata classifies this object heuristically as standalone within a Data Vault model. Because the table carries its own descriptive attributes (capacity, area, cost, currency), it is best viewed as a satellite-style entity that hangs off the AS_EVENT_FACILITIES_ALL parent rather than a pure hub. Its single foreign key to AS_EVENT_FACILITIES_ALL establishes the parent-child relationship, while the presence of change-tracking columns confirms it is a fully audited transactional table.

Key Information Stored

The surrogate primary key is EVENT_FAC_ROOM_ID, a NUMBER column that uniquely identifies each room and underpins the AS_EVENT_FAC_ROOMS_PK constraint. Two unique indexes are defined: AS_EVENT_FAC_ROOMS_U1 on EVENT_FAC_ROOM_ID (the technical key) and AS_EVENT_FAC_ROOMS_U2 on (NAME, EVENT_FACILITY_ID), which is the real business-key candidate — room names need only be unique within their parent facility.

The most operationally significant columns are:

• EVENT_FAC_ROOM_ID — surrogate primary key and foreign-key target for downstream tables.
• EVENT_FACILITY_ID — FK to AS_EVENT_FACILITIES_ALL; ties the room to its parent facility.
• NAME — VARCHAR2(60) descriptive room name; half of the composite unique key.
• CAPACITY — maximum occupancy in persons, used for scheduling and room selection.
• AREA and CEILING_HEIGHT — physical dimensions of the space.
• COST_PER_DAY and CURRENCY_CODE — pricing basis for the room.
• DIRECT_PHONE_LINE_FLAG — whether the room has its own dedicated line.
• COMMENTS — VARCHAR2(240) free-text notes.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the standard EBS descriptive flexfield (DFF) columns.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — WHO-column audit trail.

Common Use Cases and Queries

The table is most often joined to its parent facility and to promotions when building event scheduling or cost-estimation reports. A typical query lists rooms with their facility context:

• SELECT r.EVENT_FAC_ROOM_ID, r.NAME, r.CAPACITY, r.COST_PER_DAY, f.FACILITY_NAME FROM AS_EVENT_FAC_ROOMS r, AS_EVENT_FACILITIES_ALL f WHERE r.EVENT_FACILITY_ID = f.EVENT_FACILITY_ID;
• Capacity-based filtering: WHERE CAPACITY >= :required_attendees.
• Pricing lookups by currency: WHERE CURRENCY_CODE = :currency.
• DFF extraction via ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 for custom reporting.

Common scenarios include room utilization analysis, event cost roll-ups, capacity planning for training or conference programs, and data migration or interface loads into Event Management.

Related Objects

• AS_EVENT_FACILITIES_ALL — parent table; joined on EVENT_FACILITY_ID = EVENT_FACILITY_ID.
• AS_PROMOTIONS_ALL — references this table via EVENT_FAC_ROOM_ID; used to associate promotions with specific rooms.
• APPS.AS_EVENT_FAC_ROOMS — the APPS synonym exposing the OSM table to application queries.
• AS_EVENT_FAC_ROOMS_U1 / U2 — unique indexes enforcing the PK and business key.
• FND Design Data: AS.AS_EVENT_FAC_ROOMS — registration entry for flexfield and AOL integration.