Results for “venue_name”

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

Overview

AMS_VENUES_TL is the translation (TL) table for the Oracle Marketing (AMS) Venues entity in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores all language-dependent, translatable columns for venue records, most notably the display name and long description of a marketing venue. The table is owned by the AMS schema and holds one row per venue per installed language, allowing marketing users to maintain venue information in multiple languages while sharing a single language-independent record in the base table.

Following the documented Data Vault classification heuristic (derived from the foreign key structure), this table is best modeled as satellite-leaning. The surrogate key VENUE_ID plus LANGUAGE behaves as a dependent child of the base entity, and the table carries descriptive, versioned attributes rather than acting as a hub or a pure relationship link.

Key Information Stored

The table contains 11 documented columns. The most significant are listed below.

• VENUE_ID — Surrogate identifier tying each translation row to its parent venue in AMS_VENUES_B. Part of both the primary key and the parent foreign key.
• LANGUAGE — Language code for the translated content. Part of the composite primary key and business key.
• VENUE_NAME — The translated venue name. This is the business-key candidate column (together with LANGUAGE) referenced by unique index AMS_VENUES_TL_UK1.
• DESCRIPTION — The translated long description of the venue.
• SOURCE_LANG — The language in which the row was originally entered, used by the multi-language support (MLS) framework.
• SECURITY_GROUP_ID — Operating unit / security group reference, with a foreign key to FND_SECURITY_GROUPS.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns tracking who created and last modified each translation row.

The primary key is AMS_VENUES_TL_PK (VENUE_ID, LANGUAGE), which uniquely identifies each translated row. The unique index AMS_VENUES_TL_U1 (VENUE_ID, LANGUAGE) is the documented business-key candidate, and the unique index AMS_VENUES_TL_UK1 (VENUE_NAME, LANGUAGE) enforces uniqueness of the translated name within a language — the object referenced in the user's search term.

Common Use Cases and Queries

Because EBS MLS tables store each translation separately, reporting must always filter by LANGUAGE to avoid multiplying rows. A typical lookup joins the base and translation tables:

• Retrieve the localized name and description for a venue: SELECT b.venue_id, t.venue_name, t.description FROM ams_venues_b b, ams_venues_tl t WHERE b.venue_id = t.venue_id AND t.language = USERENV('LANG');
• Validate that a venue name is unique within a language by querying AMS_VENUES_TL_UK1.
• Audit translation currency using SOURCE_LANG and the WHO columns.
• Enforce security-group filtering by joining SECURITY_GROUP_ID to FND_SECURITY_GROUPS.

Related Objects

• AMS_VENUES_B — Base table; joined on AMS_VENUES_TL.VENUE_ID = AMS_VENUES_B.VENUE_ID (documented FK).
• AMS_VENUES_VL — The MLS view combining base and translated columns for user-facing queries.
• AMS_VENUES_TL_UK1 / AMS_VENUES_TL_U1 / AMS_VENUES_TL_PK — Unique indexes and primary key enforcing identity and name uniqueness.
• FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID (documented FK).
• FND_LANGUAGES — Validates the LANGUAGE column values.