Results for “email_subject”

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

Overview

AMS_CONTENT_RULES_TL is the translation (TL) table for content rules defined within Oracle EBS Marketing (AMS). In the Oracle E-Business Suite multilingual architecture, a _TL table stores the language-specific, displayable attributes of a base entity whose language-independent data resides in a corresponding _B (base) table. AMS_CONTENT_RULES_TL therefore holds the translatable text associated with each content rule row in AMS_CONTENT_RULES_B, enabling the same content rule identifier to present language-appropriate descriptive text to users across different session languages.

Content rules in AMS govern how marketing content is selected, personalized, or delivered for objects in the Marketing module. The _TL table preserves the same CONTENT_RULE_ID as the base table but stores one row per installed language, keyed by the pair (LANGUAGE, CONTENT_RULE_ID). From a Data Vault modeling perspective, the metadata classifies this object heuristically as satellite-leaning — a reasonable suggestion, since a _TL table behaves like a descriptive satellite attached to the base hub/link represented by AMS_CONTENT_RULES_B. The table is owned by the AMS schema and is marked VALID in the documented release metadata for Oracle EBS 12.1.1 and 12.2.2.

Key Information Stored

The table documents ten physical columns. The most significant are the following.

• CONTENT_RULE_ID — The identifier of the content rule. This is the join back to AMS_CONTENT_RULES_B and is part of the composite primary key AMS_CONTENT_RULES_TL_PK.
• LANGUAGE — The language code for the translation row. Together with CONTENT_RULE_ID it forms the primary key AMS_CONTENT_RULES_TL_PK, and it is also the leading column of the unique index AMS_CONTENT_RULES_TL_U1 (CONTENT_RULE_ID, LANGUAGE).
• SOURCE_LANG — The language in which the source text was originally authored, used by the translation framework to track the basis of the translated content.
• EMAIL_SUBJECT — The translatable subject line text associated with the content rule, the primary user-facing attribute in this table for email-oriented content rules.
• SECURITY_GROUP_ID — The security group that owns the row, referencing FND_SECURITY_GROUPS. This enforces multi-org/multi-security-group access isolation.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — The standard Oracle EBS WHO columns capturing audit and concurrency information for each translation row.

The surrogate key is the composite primary key AMS_CONTENT_RULES_TL_PK (LANGUAGE, CONTENT_RULE_ID). The business-key candidate surfaced by the metadata is the unique index AMS_CONTENT_RULES_TL_U1 (CONTENT_RULE_ID, LANGUAGE), which differs from the PK only in column order and prevents duplicate translations of the same rule in the same language.

Common Use Cases and Queries

The most common reporting pattern joins the translation table to the base table to retrieve a rule's language-independent attributes together with its translated text. For example:

• Retrieve translated email subjects for all content rules in a given language: SELECT b.content_rule_id, t.email_subject FROM ams_content_rules_b b, ams_content_rules_tl t WHERE b.content_rule_id = t.content_rule_id AND t.language = USERENV('LANG');
• Detect rules missing a translation in a target language, useful before deploying to a new locale: query AMS_CONTENT_RULES_B with a NOT EXISTS against AMS_CONTENT_RULES_TL for the desired LANGUAGE.
• Audit rows by security group: filter AMS_CONTENT_RULES_TL by SECURITY_GROUP_ID joined to FND_SECURITY_GROUPS to reconcile rules visible to a given operating unit or security context.
• Translation maintenance and lifecycle reporting using LAST_UPDATED_BY and LAST_UPDATE_DATE to identify stale or recently retranslated content.

Because the table carries the standard WHO audit columns, it also supports change-tracking extracts and data migration validation when content rules are moved between environments.

Related Objects

• AMS_CONTENT_RULES_B — The base table holding language-independent content rule attributes. Joined on AMS_CONTENT_RULES_TL.CONTENT_RULE_ID = AMS_CONTENT_RULES_B.CONTENT_RULE_ID; the documented foreign key AMS_CONTENT_RULES_TL.CONTENT_RULE_ID → AMS_CONTENT_RULES_B enforces this relationship.
• FND_SECURITY_GROUPS — Referenced through AMS_CONTENT_RULES_TL.SECURITY_GROUP_ID, providing the security group definition for the row.
• AMS_CONTENT_RULES_TL_PK — The composite primary key constraint (LANGUAGE, CONTENT_RULE_ID).
• AMS_CONTENT_RULES_TL_U1 — The unique index on (CONTENT_RULE_ID, LANGUAGE) backing the business-key candidate.
• FND_LANGUAGES — Not a documented foreign key here, but the standard reference source for valid LANGUAGE values in the EBS translation framework.