Results for “room_name”

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

Overview

AMS_VENUES_V is a marketing venue inquiry view owned by the APPS schema in Oracle E-Business Suite, delivered with the Oracle Marketing (AMS) product family. It exposes consolidated venue information — both descriptive and physical — for use in reporting, concurrent programs, and integration interfaces across release 12.1.1 and 12.2.2. The view is documented as VALID and retrieves venue records by joining the venue base view to Oracle Trading Community Architecture (TCA) party and party site data, so that each venue row also carries its address and owning party. Because AMS_VENUES_V is defined over AMS_VENUES_VL rather than over a physical table, it inherits multi-language support (TL) semantics from the underlying VL object, though the view itself exposes a single translated row per venue.

Underlying Base Objects

The ETRM metadata documents three referenced base objects:

• AMS_VENUES_VL (VIEW) — the primary venue source, aliased as B, supplying all venue attribute columns including AREA_SIZE and AREA_SIZE_UOM_CODE, venue type, capacity, ratings, costing, and the DFF attribute columns.
• HZ_PARTIES (SYNONYM) — aliased as L, supplying the party name (PARTY_NAME) and address attributes such as CITY, STATE, COUNTRY, POSTAL_CODE, and ADDRESS1 through ADDRESS4.
• HZ_PARTY_SITES (SYNONYM) — aliased as P, supplying LOCATION_ID and the identifying-address relationship; the view filters to the identifying, active site via IDENTIFYING_ADDRESS_FLAG = 'Y' and STATUS = 'A'.

The join is an outer join on PARTY_ID across all three objects, so venues without an associated party or site remain visible with null address attributes.

Key Columns

From AMS_VENUES_VL the view selects ROW_ID and VENUE_ID (primary identifiers), ENABLED_FLAG, INTERNAL_FLAG, DIRECT_PHONE_FLAG and OBJECT_VERSION_NUMBER (state and concurrency control), RATING_CODE, VENUE_TYPE_CODE, VENUE_NAME, ROOM_NAME, DESCRIPTION, VENUE_CODE, CAPACITY, DIRECTIONS, and PARENT_VENUE_ID for hierarchical venues. Physical and cost measurements include AREA_SIZE with AREA_SIZE_UOM_CODE, CEILING_HEIGHT with CEILING_HEIGHT_UOM_CODE, and USAGE_COST with USAGE_COST_UOM_CODE and USAGE_COST_CURRENCY_CODE. Twenty attribute columns (ATTRIBUTE_CATEGORY plus ATTRIBUTE1–ATTRIBUTE15) support descriptive flexfield data. The view also exposes CUSTOM_SETUP_ID, PARTY_ID, TELECOM_CODE, and OBJECT_TYPE, plus LOCATION_ID, PARTY_NAME and the TCA address columns contributed by the join.

Common Use Cases and Queries

Typical usage includes venue capacity and space reporting (with AREA_SIZE and AREA_SIZE_UOM_CODE used to compare rooms by physical footprint), marketing event venue lookup by city or party, and interfaces that resolve a venue to its identifying TCA location. A representative query returning venue space details is:

• SELECT venue_id, venue_name, room_name, capacity, area_size, area_size_uom_code, usage_cost, usage_cost_currency_code FROM apps.ams_venues_v WHERE enabled_flag = 'Y' AND area_size IS NOT NULL ORDER BY area_size DESC;
• SELECT venue_name, party_name, city, state, country, location_id FROM apps.ams_venues_v WHERE UPPER(city) = 'LONDON';
• SELECT venue_id, venue_name, venue_type_code, rating_code FROM apps.ams_venues_v WHERE parent_venue_id IS NOT NULL;

Because address attributes originate from the outer join, queries filtering on city, state or country effectively exclude venues lacking a valid identifying site. Direct queries should be read-only; venue maintenance belongs to the Marketing venue setup forms.