Results for “aml_business_event_types_tl”

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

Overview

AML_BUSINESS_EVENT_TYPES_TL is the translation (TL) table for the AML_BUSINESS_EVENT_TYPES_B base table within the AMS (Marketing) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to define the meaning and description of business event types held in AML_BUSINESS_EVENT_TYPES_B, allowing each business event type to carry language-specific display text. The table is owned by the AMS schema — referenced as AMS.AML_BUSINESS_EVENT_TYPES_TL — and is marked VALID in the data dictionary.

In Oracle EBS multilanguage design, the _B table stores language-independent attributes while the _TL table stores translatable attributes keyed by BUSINESS_EVENT_TYPE_ID and LANGUAGE. Under the heuristic Data Vault classification mined from the foreign-key structure, this table is satellite-leaning: it hangs off the base entity through its foreign key to AML_BUSINESS_EVENT_TYPES_B and adds descriptive, context-dependent attributes rather than introducing new relationships.

Key Information Stored

The documented physical schema contains 12 columns. The most significant are:

• BUSINESS_EVENT_TYPE_ID — the surrogate identifier for the business event type. It forms the leading column of the composite primary key AML_BUSINESS_EVENT_TYPES_TL_PK and is the foreign key pointing back to AML_BUSINESS_EVENT_TYPES_B.
• LANGUAGE — the language code for the translated row; the second column of the primary key and the discriminator that permits multiple language rows per event type.
• SOURCE_LANG — indicates the language of the source text from which the translation derives.
• MEANING — the translatable short display name of the business event type.
• DESCRIPTION — the longer translatable description of the event type.
• SECURITY_GROUP_ID — the security grouping column; the metadata records a foreign key to FND_SECURITY_GROUPS.
• ZD_EDITION_NAME — the editioning column used under the EBS 12.2 online patching (ad/zd) architecture.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard EBS audit columns.

Business-key candidates are documented through unique indexes. AML_BUSINESS_EVENT_TYPES_TL_PK is the primary key on (BUSINESS_EVENT_TYPE_ID, LANGUAGE). A second unique index, AML_BUSINESS_EVENT_TYPE_TL_U1, is defined on (BUSINESS_EVENT_TYPE_ID, LANGUAGE, ZD_EDITION_NAME), and AML_BUSINESS_EVENT_TYPES_TL_UK is documented on (LANGUAGE, MEANING). These identify natural-key alternatives to the surrogate BUSINESS_EVENT_TYPE_ID.

Common Use Cases and Queries

The table is typically joined to its base table to resolve the human-readable label for a stored event type, filtered by the session language. A standard reporting pattern is:

• SELECT b.business_event_type_id, t.meaning, t.description FROM ams.aml_business_event_types_b b, ams.aml_business_event_types_tl t WHERE b.business_event_type_id = t.business_event_type_id AND t.language = USERENV('LANG');
• Lookup of a single label: SELECT meaning FROM ams.aml_business_event_types_tl WHERE business_event_type_id = :id AND language = :lang.
• Translation completeness audit: compare rows per BUSINESS_EVENT_TYPE_ID across languages to find event types lacking a row for a required LANGUAGE.
• Duplicate-meaning detection using AML_BUSINESS_EVENT_TYPES_TL_UK on (LANGUAGE, MEANING).

Related Objects

• AML_BUSINESS_EVENT_TYPES_B — the base table; joined on AML_BUSINESS_EVENT_TYPES_TL.BUSINESS_EVENT_TYPE_ID = AML_BUSINESS_EVENT_TYPES_B.BUSINESS_EVENT_TYPE_ID.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID for function security.
• FND_LANGUAGES — the conventional source for valid LANGUAGE values.
• FND_APPLICATION — contextual reference for the AMS application owning these objects.
• AML_BUSINESS_EVENT_TYPES_VL — the conventional multilingual view exposing base and translated columns together.