Search Results ams_event_headers_all_tl_u1




Overview

AMS.AMS_EVENT_HEADERS_ALL_TL is the multi-lingual support (MLS) translation table for event headers defined in Oracle Marketing. Oracle Marketing is the module within Oracle E-Business Suite that manages marketing events, campaign activities, and related promotional content. Because event headers carry user-facing text such as event names, marketing messages, and descriptions, those attributes must be translatable into any language installed in the EBS instance. This table stores the translated and source-language rows that satisfy that requirement, allowing marketing content to be authored once and rendered in the session language of each user.

The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and it is owned by the AMS schema. In terms of Data Vault modeling heuristics, the metadata classifies this object as satellite-leaning. This is consistent with its structure: the translation row is dependent on a parent business entity (the base event header) and carries descriptive, language-specific attributes rather than acting as an independent hub or a pure associative link. A modeler would typically treat AMS_EVENT_HEADERS_ALL_TL as a satellite attached to the AMS_EVENT_HEADERS_ALL_B hub, keyed by the hub identifier plus the language discriminator.

Key Information Stored

The table contains twelve documented columns. Its structure separates the identity of the entity from its language-dependent descriptive payload:

Of these, EVENT_HEADER_ID and LANGUAGE are the business-key candidates surfaced through the unique index; the descriptive columns (name, message, description) constitute the translatable payload.

Common Use Cases and Queries

The most frequent access pattern is a language-restricted lookup of event header text, typically joining the translation table back to the base event header table to retrieve the untranslated control attributes alongside the translated text.

  • Reporting on event names and messages for a specific language, joining AMS_EVENT_HEADERS_ALL_TL to AMS_EVENT_HEADERS_ALL_B on EVENT_HEADER_ID.
  • Identifying which event headers have been translated versus which remain only in SOURCE_LANG, useful for translation-completeness audits.
  • Case-insensitive search by name using the function-based index, for example filtering on UPPER(EVENT_HEADER_NAME) LIKE UPPER(:search_term).
  • Checking security-group partitioning in hosted deployments by joining SECURITY_GROUP_ID to FND_SECURITY_GROUPS.

A representative query pattern selects the identifier, language, source language, and translated name from AMS.AMS_EVENT_HEADERS_ALL_TL, filtered by EVENT_HEADER_ID and LANGUAGE, and joins to AMS_EVENT_HEADERS_ALL_B for the base row attributes.

Related Objects

The following objects are most significant in relation to this table:

  • AMS.AMS_EVENT_HEADERS_ALL_B — the base event header table; AMS_EVENT_HEADERS_ALL_TL.EVENT_HEADER_ID participates in a foreign key to this table.
  • FND_SECURITY_GROUPS — referenced through the SECURITY_GROUP_ID foreign key.
  • AMS_EVENT_HEADERS_ALL_TL_U1 — the unique index on (EVENT_HEADER_ID, LANGUAGE) enforcing the translation primary key.
  • AMS_EVENT_HEADERS_ALL_TL_N1 — the non-unique index on (EVENT_HEADER_NAME, LANGUAGE).
  • AMS_EVENT_HEADERS_ALL_TL_NNAME — the function-based index on UPPER("EVENT_HEADER_NAME").
  • AMS.AMS_EVENT_HEADERS_ALL_VL — the conventional MLS view that exposes translated event header content for application and reporting use.