Search Results venue_code

Overview

AMS_VENUES_VL is a multilingual (VL) view owned by the APPS schema in Oracle E-Business Suite, released under the AMS – Marketing product family. Its documented purpose is to return information on venues. Because it is a VL view, it presents a translated, language-aware projection of the underlying venue entity: the untranslated attributes are drawn from the base table AMS_VENUES_B, while the descriptive, user-facing attributes are resolved from the translation table AMS_VENUES_TL filtered by the session language. The view is defined with a status of VALID and carries an Oracle Proprietary, Confidential Information classification.

Within EBS reporting and integration, the view functions as the standard read interface for venue data. Rather than requiring report authors and integration developers to join the base and translation tables manually, AMS_VENUES_VL performs that join and returns the current session's language translations automatically. This makes it the preferred access path for concurrent programs, Oracle Reports, BI Publisher data templates, OAF pages, and inbound or outbound interfaces that must consume or publish venue master data.

Underlying Base Objects

The view is defined over two documented base objects, both exposed as synonyms in the ETRM metadata:

• AMS_VENUES_B – the base table holding all non-translated venue attributes, including IDs, flags, financial and physical measurements, descriptive flexfield columns, and relationship columns.
• AMS_VENUES_TL – the translation table holding language-specific values for VENUE_NAME and DESCRIPTION.

The join condition is B.VENUE_ID = T.VENUE_ID AND T.LANGUAGE = USERENV('LANG'). Venue IDs are the shared key, and USERENV('LANG') restricts the result set to the language of the current application session, which is why each venue appears once per query rather than once per installed language. The view also surfaces B.ROWID as ROW_ID for row identification.

Key Columns

In response to the search for parent_venue_id, the view exposes PARENT_VENUE_ID sourced from AMS_VENUES_B. This column establishes the self-referencing hierarchy among venues, allowing a venue to be modeled as a child of another venue — for example, a hall within a convention centre, or a room within a hall. Because the reference is to VENUE_ID in the same base table, hierarchical reporting requires a self-join or a CONNECT BY query against the view.

Other significant columns include:

• VENUE_ID – the primary identifier for the venue; VENUE_CODE and VENUE_NAME provide the business key and translated name.
• LOCATION_ID, DIRECTIONS, TELECOM_CODE – physical location and contact details.
• CAPACITY, AREA_SIZE, AREA_SIZE_UOM_CODE, CEILING_HEIGHT, CEILING_HEIGHT_UOM_CODE – physical characteristics used in event planning.
• USAGE_COST, USAGE_COST_UOM_CODE, USAGE_COST_CURRENCY_CODE – cost basis and currency for the venue.
• RATING_CODE, VENUE_TYPE_CODE, INTERNAL_FLAG, ENABLED_FLAG, DIRECT_PHONE_FLAG – classification and status controls.
• PARTY_ID, OBJECT_TYPE, CUSTOM_SETUP_ID, OBJECT_VERSION_NUMBER – integration and concurrency control columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 – the descriptive flexfield segments.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – standard WHO audit columns.

Common Use Cases and Queries

Typical uses include validating venue setup, populating event scheduling interfaces, and reporting on venue hierarchies. A simple listing of enabled venues follows:

• SELECT venue_id, venue_code, venue_name, parent_venue_id FROM ams_venues_vl WHERE enabled_flag = 'Y' ORDER BY venue_name;

To walk the parent-child hierarchy defined by PARENT_VENUE_ID, a CONNECT BY query can be issued directly against the view:

• SELECT venue_id, venue_name, parent_venue_id, LEVEL FROM ams_venues_vl START WITH parent_venue_id IS NULL CONNECT BY PRIOR venue_id = parent_venue_id;

Because the view resolves translations through USERENV('LANG'), callers need not filter on language; results are returned in the language of the session, which is appropriate for locale-specific reporting.