Results for “as_event_facilities_u1”

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

Overview

OSM.AS_EVENT_FACILITIES_ALL is a foundation table within the Oracle E-Business Suite (EBS) Event and Trade Management (ETRM) module, registered under the OSM schema and mapped to FND Design Data object AS.AS_EVENT_FACILITIES_ALL. The table stores definitions of event facilities — physical venues such as hotels, conference centers, or exhibition halls — that are referenced by promotions, event room allocations, and event staffing records. In release 12.1.1 and 12.2.2 it is validated and resides in the APPS_TS_ARCHIVE tablespace with a PCTFREE of 10.

The "_ALL" suffix denotes a multi-organization (multi-tenant) structure: the table carries an ORG_ID column so that facility definitions can be partitioned by operating unit or organization. A designated AS_EVENT_FACILITIES_U2 unique index spans CODE, NAME, and ORG_ID, enforcing uniqueness of the facility business key within each organization. This is the object the user searched for when looking up "as_event_facilities_u2".

From a Data Vault modeling perspective, this table is heuristically classified as hub-leaning. It holds a stable, unique business object (the event facility) identified by a surrogate key, with descriptive attributes attached. It could be modeled as a hub keyed on EVENT_FACILITY_ID or CODE/NAME, with dependent satellites carrying the descriptive and address attributes.

Key Information Stored

The table contains 43 documented columns. The most significant are:

• EVENT_FACILITY_ID (NUMBER) — the surrogate primary key, enforced by AS_EVENT_FACILITIES_PK and the unique index AS_EVENT_FACILITIES_U1.
• CODE (VARCHAR2 15) and NAME (VARCHAR2 60) — the human-readable business identifiers; together with ORG_ID they form the business-key candidate enforced by AS_EVENT_FACILITIES_U2.
• ORG_ID (NUMBER) — the multi-org partitioning column that scopes the U2 uniqueness rule.
• ENABLED_FLAG — controls whether the facility is active and selectable.
• TYPE_CODE (VARCHAR2 30) and RANK_CODE (VARCHAR2 30) — classification and ranking attributes used to categorize and prioritize facilities.
• Address columns — ADDRESS1 through ADDRESS4, CITY, STATE, PROVINCE, POSTAL_CODE, COUNTY, and COUNTRY_CODE — defining the physical location of the venue.
• Contact columns — AREA_CODE (10), PHONE_NUMBER (25), and EXTENSION (20).
• DIRECTIONS (VARCHAR2 2000) and COMMENTS (VARCHAR2 240) — free-text guidance for event staff and planners.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 (each VARCHAR2 150) — the standard EBS flexfield descriptive columns for extensibility.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The table is queried to populate facility picklists in promotion setup, to retrieve venue addresses for event documentation, and to validate facility references during data loads. A typical lookup by business key is:

SELECT event_facility_id, code, name, city, country_code FROM osm.as_event_facilities_all WHERE code = :code AND org_id = :org_id AND enabled_flag = 'Y';

A reporting pattern joins facilities to promotions to measure activity per venue:

SELECT f.name, COUNT(p.promotion_id) FROM osm.as_event_facilities_all f, osm.as_promotions_all p WHERE f.event_facility_id = p.event_facility_id GROUP BY f.name;

Because the table is "_ALL", every query should include ORG_ID to respect multi-org security, particularly in customized reports and interfaces.

Related Objects

Three documented foreign-key children reference this table, confirming its hub-like role:

• AS_PROMOTIONS_ALL — links via EVENT_FACILITY_ID; identifies the venue associated with each promotion.
• AS_EVENT_FAC_ROOMS — links via EVENT_FACILITY_ID; defines rooms or spaces within a facility.
• AS_EVENT_FAC_STAFF — links via EVENT_FACILITY_ID; assigns staff to a facility.

The primary-key constraint AS_EVENT_FACILITIES_PK anchors the table, while the unique indexes AS_EVENT_FACILITIES_U1 and AS_EVENT_FACILITIES_U2 define the surrogate and business-key access paths that most queries and interfaces depend on.