Search Results amw_fin_stmnt_tl




Overview
Explore in AI Chat

Overview

AMW_FIN_STMNT_TL is a translation table (the _TL suffix denotes translated values) belonging to the AMW schema, which maps to the Oracle Internal Controls Manager (ICM) product family within Oracle E-Business Suite 12.1.1 and 12.2.2. Its stated purpose, per the ETRM documentation, is to hold the multilingual translations of Financial Statement names. Every row in this table represents an alternative-language rendering of a financial statement record, keyed by language so that users operating in different locales see statement titles in their own language.

Because AMW underpins Internal Controls Manager — the module used to define, document, and test internal controls in support of Sarbanes-Oxley and similar compliance regimes — financial statements defined here typically feed control-scoping, assertion mapping, and compliance reporting. The translated name is a display attribute rather than a transactional payload, which places the table at the descriptive/metadata layer of the ICM data model.

Under the heuristic Data Vault classification supplied with the metadata, this object is assessed as standalone. In Data Vault modeling terms it behaves closest to a multi-active satellite attached to the financial statement hub/link, because it stores dependent descriptive attributes (translated names) partitioned by language rather than acting as an independent hub or a relationship link. This classification should be treated as a modeling suggestion only; the operative integrity constraint is the documented unique index AMW_FIN_STMNT_TL_U1.

Key Information Stored

  • STATEMENT_GROUP_ID — Part of the composite primary key and a leading column of unique index AMW_FIN_STMNT_TL_U1. Identifies the statement group to which the translated statement belongs.
  • FINANCIAL_STATEMENT_ID — The second component of the composite primary key. Together with STATEMENT_GROUP_ID it identifies the specific financial statement within a group.
  • LANGUAGE — The third primary-key component, expressing the language of the translated row; in EBS this is normally an NLS language code, for example US or AR.
  • NAME — The translated, displayable name of the financial statement. This is the principal payload of the table.
  • SOURCE_LANGUAGE and SOURCE_LANG — Attributes identifying the language from which the translation derives, typically the base language of the source record (commonly US).
  • SECURITY_GROUP_ID — Row-level security discriminator linking the record to FND_SECURITY_GROUPS.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS WHO-column audit trail identifying who created and last amended the translated row, and from which login.
  • OBJECT_VERSION_NUMBER — Optimistic locking column required by the EBS 12.2.2 online patching and OAF framework.

The table documents 13 columns in the 12.1.1 physical schema. The surrogate/business-key distinction is important: the unique index AMW_FIN_STMNT_TL_U1 (STATEMENT_GROUP_ID, FINANCIAL_STATEMENT_ID, LANGUAGE) constitutes the business-key candidate, while the underlying base table AMW_FIN_STMNT_B typically carries the internal surrogate for the untranslated record.

Common Use Cases and Queries

The primary use case is retrieving a localized financial statement name for display or reporting. A typical pattern joins the translation table to the base table and filters by language:

  • Localized lookups: SELECT t.financial_statement_id, t.name FROM amw.amw_fin_stmnt_tl t WHERE t.language = 'US'.
  • Group-based scoping, using the leading PK column that the searcher referenced: SELECT * FROM amw.amw_fin_stmnt_tl WHERE statement_group_id = :group_id — the natural access path via index AMW_FIN_STMNT_TL_U1.
  • Completeness checks for translation projects: compare row counts per LANGUAGE against the base table to identify statements lacking a non-source translation.
  • Compliance reporting: join the translated names into control-assertion or SOX scoping reports so that statements appear in the correct regional language.
  • Audit/metadata queries: use the WHO columns to determine when and by whom a translated statement name was last modified.

Because the table is small and highly selective on the composite key, queries filtering on STATEMENT_GROUP_ID and FINANCIAL_STATEMENT_ID with an explicit LANGUAGE predicate will generally resolve through the unique index without additional tuning.

Related Objects

  • AMW_FIN_STMNT_B — The base (untranslated) financial statement table; AMW_FIN_STMNT_TL supplies its language-specific NAME values. Join on STATEMENT_GROUP_ID and FINANCIAL_STATEMENT_ID.
  • FND_SECURITY_GROUPS — Referenced through SECURITY_GROUP_ID, driving row-level security for translated statement rows.
  • AMW_FIN_STMNT_TL_U1 — The unique index enforcing the composite business key (no duplicate row per group, statement, and language).
  • AMW statement-group tables — Entities keyed by STATEMENT_GROUP_ID that organize statements into reporting structures.
  • Internal Controls Manager control/assertion tables — Downstream ICM objects that reference financial statements for scoping and testing; these consume the localized NAME at report runtime.
  • FND_LANGUAGES — Provides the installed-language context validating the LANGUAGE and SOURCE_LANGUAGE values.

Because AMW_FIN_STMNT_TL is classified as standalone, it exposes no outgoing foreign keys beyond SECURITY_GROUP_ID; integrity is maintained principally through the composite unique key and application logic.