Results for “amw_constraints_tl”

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

Overview

AMW_CONSTRAINTS_TL is the translation (TL) table for the AMW_CONSTRAINTS_B base table within the Oracle E-Business Suite Internal Controls Manager module (product code AMW). Its documented role is to hold name and description information for records stored in AMW_CONSTRAINTS_B. The "_TL" suffix identifies it as a multilingual/translated table, meaning it stores language-dependent attributes keyed by CONSTRAINT_ID and LANGUAGE. In EBS 12.1.1 and 12.2.2 the AMW product is flagged as obsolete, and the ETRM metadata explicitly states the object is "Not implemented in this database" — meaning it exists in the data model definition but is not physically deployed in the current instance.

From a Data Vault modeling perspective, the mined FK structure classifies this table as standalone (not a hub, link, or satellite). This is a heuristic suggestion rather than a definitive classification: the table's only documented foreign key points to FND_SECURITY_GROUPS, and it carries no dependent downstream relationships of its own.

Key Information Stored

The table is documented with 11 columns. The most significant are listed below, distinguishing the surrogate primary key from business-key candidates.

• CONSTRAINT_ID — Surrogate identifier referencing the parent AMW_CONSTRAINTS_B row; part of the composite primary key.
• LANGUAGE — Language code for the translated row; the second component of the primary key.
• NAME — Language-specific name of the constraint; a documented business-key candidate.
• DESCRIPTION — Language-specific descriptive text for the constraint.
• SOURCE_LANG — The source language from which the translation was derived.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, controlling row-level security.
• LAST_UPDATE_DATE / LAST_UPDATED_BY — Standard EBS WHO columns recording the last change and its author.
• CREATION_DATE / CREATED_BY — Standard EBS WHO columns recording row inception.
• LAST_UPDATE_LOGIN — Login identifier associated with the most recent update.

The primary key is AMW_CONSTRAINTS_TL_PK (CONSTRAINT_ID, LANGUAGE). Two unique indexes act as business-key candidates: AMW_CONSTRAINTS_TL_U1 (CONSTRAINT_ID, LANGUAGE) mirrors the PK, while AMW_CONSTRAINTS_TL_U2 (LANGUAGE, NAME) enforces uniqueness of the name within a language.

Common Use Cases and Queries

Because AMW is obsolete, the primary use cases are migration, archival, or data-quality auditing rather than active functional reporting. A typical pattern joins the TL row to its base record and filters by language:

• Retrieving the translated name and description for a constraint:
  SELECT c.constraint_id, t.language, t.name, t.description FROM amw_constraints_b c, amw_constraints_tl t WHERE c.constraint_id = t.constraint_id AND t.language = USERENV('LANG');
• Validating translation coverage — identifying base rows lacking a row for a given language via an outer join.
• Enforcing the U2 business-key candidate by detecting duplicate NAME values within a LANGUAGE.
• Applying security filtering through SECURITY_GROUP_ID before publishing extracts.

Queries should always restrict by LANGUAGE to avoid returning every translated variant of the same constraint.

Related Objects

• AMW_CONSTRAINTS_B — The base table this TL row translates; joined on CONSTRAINT_ID.
• FND_SECURITY_GROUPS — Referenced by the SECURITY_GROUP_ID foreign key.
• AMW_CONSTRAINTS_TL_PK — The primary key constraint (CONSTRAINT_ID, LANGUAGE).
• AMW_CONSTRAINTS_TL_UK — Unique constraint over NAME and LANGUAGE.
• AMW_CONSTRAINTS_TL_U1 / AMW_CONSTRAINTS_TL_U2 — Unique indexes supporting business-key uniqueness.
• FND_LANGUAGES — Reference for the LANGUAGE and SOURCE_LANG values.

All relationships should be treated as documentation-only where the object is not physically implemented.