Results for “ams_web_rules_tl”

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

Overview

AMS_WEB_RULES_TL is the translation (TL) table for web rules within the Oracle E-Business Suite Marketing (AMS) module. It stores the language-specific, translated content associated with a web rule record, allowing rule names and related textual attributes to be presented in multiple installed languages. The table resides in the AMS schema and holds 11 documented columns. In Oracle EBS, _TL tables typically pair with a base (_B) table that carries language-independent attributes, while the _TL table carries the translatable text keyed by a LANGUAGE code. This design supports Oracle's Multi-Language Support (MLS) architecture, enabling end users to view web rule definitions in their session language.

From a dimensional or Data Vault modeling perspective, the heuristic classification for this object is standalone, meaning the mined foreign-key structure does not tie it into a broader hub/link/satellite mesh beyond its single reference. Modeling it as a satellite attached to the web rules hub, keyed by RULE_ID and LANGUAGE, is a reasonable suggestion, but the authoritative treatment remains the EBS MLS translation table.

Key Information Stored

The table is organized around a composite primary key and a unique business-key index.

• Primary key — AWL_PK1 (LANGUAGE, RULE_ID): the composite key that uniquely identifies each translated row, combining the language code with the parent rule identifier.
• Unique index — AMS_WEB_RULES_TL_U1 (RULE_ID, LANGUAGE): the business-key candidate enforcing one translation per rule per language.
• RULE_ID: identifier linking the translated row to its parent web rule; also the join column to the base rule definition.
• RULE_NAME: the translated name of the web rule, the primary user-facing text attribute.
• LANGUAGE: the language code for the translated content.
• SOURCE_LANG: the language from which the translation originated, supporting MLS tracking.
• SECURITY_GROUP_ID: the security group governing row-level access; it references FND_SECURITY_GROUPS.
• OBJECT_VERSION_NUMBER: optimistic-locking version counter used by the EBS framework to detect concurrent updates.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN: the standard "Who" columns recording creation and last-modification metadata.

Common Use Cases and Queries

Typical usage centers on retrieving the correctly translated rule name for a given session language, and on auditing or reconciling translations across languages.

• Fetch a rule's name in a specific language:

  SELECT rule_id, rule_name FROM ams.ams_web_rules_tl WHERE language = USERENV('LANG') AND rule_id = :p_rule_id;

• List all translations for a set of rules to verify completeness:

  SELECT rule_id, language, rule_name FROM ams.ams_web_rules_tl WHERE rule_id IN (:ids) ORDER BY rule_id, language;

• Join to the base rule table on RULE_ID to combine language-independent and translated attributes.
• Detect missing translations by comparing installed languages against rows present per RULE_ID.
• Reporting on translation currency using LAST_UPDATE_DATE and SOURCE_LANG.

Related Objects

• FND_SECURITY_GROUPS: referenced by SECURITY_GROUP_ID; join on SECURITY_GROUP_ID to resolve security group definitions.
• AMS_WEB_RULES_B (base table): the language-independent parent, joined on RULE_ID.
• AMS_WEB_RULES_TL_U1 / AWL_PK1: the unique index and primary key that enforce translation integrity.
• FND_LANGUAGES: the language reference joined on LANGUAGE / SOURCE_LANG to resolve language names.
• AMS web rules APIs and concurrent programs: the MLS-enabled DML paths that maintain both the base and translation rows.

Because the documented relationships are limited to the SECURITY_GROUP_ID FK and the RULE_ID linkage, the table is best treated as a translation satellite to the web rules hub, not an independent transactional entity.