Results for “as_event_facilities_v”

4 results




Overview
Explore in AI Chat

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

Overview

AS_EVENT_FACILITIES_V is a reporting and integration view in the Oracle E-Business Suite Sales Foundation (AS) module. It presents enriched event facility information by joining the base event facility entity with lookup descriptions and territory translations, exposing both the raw code values and their user-facing meanings in a single queryable object. The object is documented under the ETRM metadata for Oracle EBS 12.2.2 and applies equally to 12.1.1 deployments in which the AS schema objects are present.

Event facilities represent physical locations used in trade management and sales event activities — venues, conference centers, exhibition halls, and similar sites at which promotional or sales events are conducted. The view consolidates address, contact, classification, and descriptive information for these facilities, making it suitable for operational reporting, custom concurrent programs, and inbound/outbound integration where a flattened facility record is required. Because the join conditions use outer joins, the view retains facility rows even when a matching lookup or territory translation is absent, returning a null meaning or territory name in those cases.

Underlying Base Objects

The view is defined over four base objects:

All three lookup and territory joins are outer joins, designated by the (+) operator. Note that the ETRM metadata records "Referenced base objects: none documented" and "Not implemented in this database" for the source environment; the base objects listed above are recovered from the view text itself, which remains authoritative.

Key Columns

  • EVENT_FACILITY_ID / CODE / NAME — primary key, short code, and descriptive name of the facility.
  • RANK_CODE and its meaning — classification of the facility's rank or priority; the resolved meaning is returned from AS_LOOKUPS.
  • TYPE_CODE and its meaning — the facility type (for example hotel, convention center); the resolved meaning is returned from AS_LOOKUPS.
  • ENABLED_FLAG — indicates whether the facility is active for selection.
  • ADDRESS1–ADDRESS4, CITY, STATE, PROVINCE, POSTAL_CODE, COUNTY, COUNTRY_CODE — the complete postal address; COUNTRY_CODE is joined to FND_TERRITORIES_TL for the translated territory short name.
  • AREA_CODE, PHONE_NUMBER, EXTENSION — contact telephone details.
  • COMMENTS, DIRECTIONS — free-text notes and driving/directional instructions.
  • ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield segments supporting client-specific extensions.
  • Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include facility listing reports, event planning lookups, and integrations that require human-readable type and rank descriptions. Facilities should be filtered on ENABLED_FLAG = 'Y' for active-site reporting.

  • Active facility listing: SELECT event_facility_id, code, name, type_code, rank_code, city, state, country_code FROM as_event_facilities_v WHERE enabled_flag = 'Y' ORDER BY name;
  • Facilities by type: SELECT code, name, type_code, city, country_code FROM as_event_facilities_v WHERE type_code = :p_type;
  • Address/contact extract: SELECT name, address1, city, postal_code, area_code, phone_number FROM as_event_facilities_v;
  • Joining to event data: link EVENT_FACILITY_ID to the event scheduling tables (for example AS_EVENT_SCHEDULES) to report which facility hosts each event.

Because ROW_ID is exposed, the view is also usable with Oracle Forms-based or OAF-based update mechanisms where a row identifier is required.