Results for “amw_controls_tl_u1”

5 results




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

Overview

AMW.AMW_CONTROLS_TL is the translation table for the Oracle E-Business Suite Audit Management and Workflow (AMW) module, which provides the control definitions used by the GRC (Governance, Risk, and Compliance) components of EBS. The table stores the language-specific, translatable attributes of a control — its name, description, and several assessment-related text fields — for each supported language. Every logical control revision is stored once in the base table AMW_CONTROLS_B and once per translated language in this table, keyed by the pair (CONTROL_REV_ID, LANGUAGE). The "_TL" suffix follows the standard EBS convention for multilingual translation entities.

Under a heuristic Data Vault classification, this object is satellite-leaning: it hangs off the AMW_CONTROLS_B parent and carries descriptive, language-dependent attributes rather than acting as a hub or a many-to-many link. It is not a true Data Vault satellite, but it behaves like one — a dependent descriptive structure keyed to a parent business key plus a language discriminator.

Key Information Stored

The most important columns are:

The unique index AMW_CONTROLS_TL_U1 (CONTROL_REV_ID, LANGUAGE) is the business-key candidate, distinct from the surrogate primary key AMW_CONTROLS_TL_PK, which is functionally the same column pair. The table resides in APPS_TS_TX_DATA; its unique index resides in APPS_TS_TX_IDX.

Common Use Cases and Queries

Translation tables are queried whenever control text must be presented in a specific language. The pattern below joins the base table to its translation, filtered by language:

SELECT b.CONTROL_REV_ID, t.NAME, t.DESCRIPTION
FROM   AMW.AMW_CONTROLS_B b,
       AMW.AMW_CONTROLS_TL t
WHERE  b.CONTROL_REV_ID = t.CONTROL_REV_ID
AND    t.LANGUAGE = USERENV('LANG');

Reporting scenarios include multilingual control catalogs, compliance evidence packets, and internal audit workpapers where control descriptions must match the reviewer's locale. A typical lookup for a single business key uses the unique index:

SELECT NAME, DESCRIPTION
FROM   AMW.AMW_CONTROLS_TL
WHERE  CONTROL_REV_ID = :control_rev_id
AND    LANGUAGE = :lang;

Common maintenance operations include verifying coverage (controls missing a translation for a given language) and validating SOURCE_LANG against LANGUAGE. Administrators also use this table when reviewing Configuration Assessment text stored in VERIFICATION_INSTRUCTION.

Related Objects

  • AMW.AMW_CONTROLS_B — the base (untranslated) control table; the primary parent. Joined on CONTROL_REV_ID.
  • FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for hosted deployments.
  • AMW_CONTROLS_T — the translation view/interface layer that resolves the active language. Listed as referencing AMW_CONTROLS_TL.
  • AMW_CONTROLS_VL — the standard EBS view-over-B-and-TL pattern exposing both base and translated columns to the application.
  • The AMW control APIs and concurrent programs operate against AMW_CONTROLS_B and this translation table together when creating or updating controls.

Together these objects form the control-definition layer of the AMW/GRC schema in EBS 12.1.1 and 12.2.2.