Search Results ceiling_height_uom_code




Overview

AMS_VENUES_B is the base table of the Oracle Marketing (AMS) venue entity, residing in the AMS schema. It stores the places that can be used to hold an event, such as hotels, conference centers, internal meeting rooms, and other physical or logical facilities. In Oracle EBS 12.1.1 and 12.2.2, this table acts as the master definition of venues that are subsequently referenced by event agendas (rooms), event offers, and venue rate schedules.

The table follows the standard Oracle EBS multilanguage design: AMS_VENUES_B holds language-independent attributes (capacity, area, parent venue, location, party), while a companion table, AMS_VENUES_TL, stores translatable descriptive columns. Only the "_B" base table is documented here, and it contains 45 physical columns in the 12.2.2 ETRM schema.

From a heuristic Data Vault classification, the FK structure suggests a hub-leaning model. The table has a single-column surrogate primary key, AMS_VENUES_B_PK (VENUE_ID), which is also enforced by the unique index AMS_VENUES_B_U1. The self-referencing PARENT_VENUE_ID supports a hierarchical venue structure (for example, a hotel as a parent venue with individual meeting rooms as children), which is characteristic of a hub with a recursive relationship rather than a pure transactional satellite.

Key Information Stored

The most significant columns in AMS_VENUES_B include:

Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — are present as expected in EBS tables.

Common Use Cases and Queries

Typical use cases include venue selection during event setup, capacity-based filtering, hierarchical reporting of parent/child venues, and cost analysis for venue usage. A common query pattern joining the base table to its translations and location is:

  • Active venue lookup: SELECT venue_id, venue_code, capacity FROM ams_venues_b WHERE enabled_flag = 'Y';
  • Venue with address: join AMS_VENUES_B.LOCATION_ID to HZ_LOCATIONS to retrieve formatted addresses.
  • Hierarchical venue listing: self-join on PARENT_VENUE_ID to display parent venues and their child rooms.
  • Venue rate reporting: join AMS_VENUE_RATES_B on VENUE_ID to compare negotiated rates.
  • Upcoming events by venue: join AMS_EVENT_OFFERS_ALL_B.EVENT_VENUE_ID to AMS_VENUES_B.VENUE_ID.
  • Room usage within agendas: join AMS_AGENDAS_B.ROOM_ID to AMS_VENUES_B.VENUE_ID.

Reporting typically combines AMS_VENUES_B with AMS_VENUES_TL to obtain the translated venue name and description, since the base table stores non-translatable attributes only.

Related Objects

The following objects have the most significant documented relationships with AMS_VENUES_B:

  • AMS_VENUES_TL — translation table; joins on VENUE_ID to provide language-specific name and description text.
  • AMS_VENUES_B (self) — PARENT_VENUE_ID references VENUE_ID, defining parent/child venue hierarchies.
  • HZ_LOCATIONS — joined via LOCATION_ID to resolve the venue's address and geography.
  • HZ_PARTIES — joined via PARTY_ID to associate the venue with a party record.
  • AMS_VENUE_RATES_B — references AMS_VENUES_B.VENUE_ID; stores rate schedules per venue.
  • AMS_AGENDAS_B — references AMS_VENUES_B through ROOM_ID; identifies the room used for an agenda item.
  • AMS_EVENT_OFFERS_ALL_B — references AMS_VENUES_B via EVENT_VENUE_ID; ties venues to event offers.
  • AMS_CUSTOM_SETUPS_B — referenced by CUSTOM_SETUP_ID; provides extensible setup metadata.
  • FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID; governs row-level security visibility.

These relationships make AMS_VENUES_B a central reference table in the Marketing event lifecycle, feeding agenda scheduling, offer management, and rate planning across the AMS module.

  • Table: AMS_VENUES_B 12.1.1

    owner:AMS,  object_type:TABLE,  fnd_design_data:AMS.AMS_VENUES_B,  object_name:AMS_VENUES_B,  status:VALID,  product: AMS - Marketingdescription: Stores places that can be used to hold an event at. ,  implementation_dba_data: AMS.AMS_VENUES_B

  • Table: AMS_VENUES_B 12.2.2

    owner:AMS,  object_type:TABLE,  fnd_design_data:AMS.AMS_VENUES_B,  object_name:AMS_VENUES_B,  status:VALID,  product: AMS - Marketingdescription: Stores places that can be used to hold an event at. ,  implementation_dba_data: AMS.AMS_VENUES_B

  • View: AMS_VENUES_V 12.1.1

    owner:APPS,  object_type:VIEW,  fnd_design_data:AMS.AMS_VENUES_V,  object_name:AMS_VENUES_V,  status:VALID,  product: AMS - Marketingdescription: This view retrives venue information ,  implementation_dba_data: APPS.AMS_VENUES_V

  • View: AMS_VENUES_VL 12.2.2

    owner:APPS,  object_type:VIEW,  fnd_design_data:AMS.AMS_VENUES_VL,  object_name:AMS_VENUES_VL,  status:VALID,  product: AMS - Marketingdescription: This view returns information on Venues ,  implementation_dba_data: APPS.AMS_VENUES_VL

  • View: AMS_VENUES_V 12.2.2

    owner:APPS,  object_type:VIEW,  fnd_design_data:AMS.AMS_VENUES_V,  object_name:AMS_VENUES_V,  status:VALID,  product: AMS - Marketingdescription: This view retrives venue information ,  implementation_dba_data: APPS.AMS_VENUES_V

  • View: AMS_VENUES_VL 12.1.1

    owner:APPS,  object_type:VIEW,  fnd_design_data:AMS.AMS_VENUES_VL,  object_name:AMS_VENUES_VL,  status:VALID,  product: AMS - Marketingdescription: This view returns information on Venues ,  implementation_dba_data: APPS.AMS_VENUES_VL