Search Results amw_evaluations_tl_u1

Overview

AMW.AMW_EVALUATIONS_TL is the translation table (_TL) for the base table AMW.AMW_EVALUATIONS within the Oracle E-Business Suite Advanced Management Module (AMW) schema. Its role is to store language-specific renderings of translatable text attributes—principally the COMMENTS field—for each evaluation record, thereby supporting Oracle EBS Multi-Language Support (MLS) functionality in both 12.1.1 and 12.2.2 environments. The object resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10 and is flagged as VALID in the ETRM documentation, with FND Design Data registered as AMW.AMW_EVALUATIONS_TL.

From a dimensional or Data Vault modeling perspective, the metadata's heuristic classification identifies this table as standalone, meaning it neither references nor is referenced by other tables in the mined FK structure beyond its documented foreign key. A reasonable modeling suggestion is to treat AMW_EVALUATIONS_TL as a satellite that hangs off the conceptual AMW_EVALUATIONS hub, since each translation row carries descriptive, language-scoped text and standard WHO audit columns rather than acting as an independent business entity. Because the translation rows share the same EVALUATION_ID as the base table but are segregated by LANGUAGE, they behave like multi-active satellite rows keyed on the hub's identifier plus a language discriminator.

Key Information Stored

The table maintains a composite primary key, AMW_EVALUATIONS_TL_PK, defined on (EVALUATION_ID, LANGUAGE). The unique index AMW_EVALUATIONS_TL_U1 on (EVALUATION_ID, LANGUAGE) is the documented business-key candidate and mirrors that uniqueness constraint in the APPS_TS_TX_IDX tablespace. Notable columns include:

• EVALUATION_ID — NUMBER; the unique identifier inherited from the base AMW_EVALUATIONS table and the primary join key.
• LANGUAGE — VARCHAR2; the language of the current record, forming the second component of the composite key.
• SOURCE_LANG — VARCHAR2; the language that the text mirrors, enabling mirror-based translation and reflecting source-language changes until explicit translation occurs.
• COMMENTS — VARCHAR2(4000); the translatable descriptive text for the evaluation.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns recording creation and modification metadata.
• SECURITY_GROUP_ID — NUMBER; used for hosted or multi-tenant style environments and documented as referencing FND_SECURITY_GROUPS.
• OBJECT_VERSION_NUMBER — NUMBER; the optimistic locking column that guards concurrent updates.

Common Use Cases and Queries

The primary use case is retrieving localized evaluation text for display, reporting, or interface export. A typical pattern joins the translation table to the base table and filters on a specific language:

• Reporting in a single locale: SELECT EVALUATION_ID, COMMENTS FROM AMW.AMW_EVALUATIONS_TL WHERE LANGUAGE = 'US';
• Fallback alignment: compare LANGUAGE and SOURCE_LANG to identify rows that have not yet been translated and are still mirroring the source text.
• Concurrent update safety: read OBJECT_VERSION_NUMBER before update to enforce optimistic locking.
• Security scoping in hosted deployments: filter on SECURITY_GROUP_ID to restrict rows per tenant.
• Data extraction for ETL or Data Vault loads: use the composite key (EVALUATION_ID, LANGUAGE) as the natural business key.

Related Objects

The documented dependencies are limited, but the following objects are significant:

• AMW.AMW_EVALUATIONS — the base table whose EVALUATION_ID this translation table annotates.
• FND_SECURITY_GROUPS — referenced via the SECURITY_GROUP_ID foreign key relationship.
• AMW.AMW_EVALUATIONS_TL_U1 — the unique index enforcing the (EVALUATION_ID, LANGUAGE) business key.
• AMW_EVALUATIONS_TL (APPS synonym) — the APPS-owned synonym layer that references this object for application access.

Because the metadata classifies this object as standalone, no further inbound or outbound FK relationships are documented beyond the SECURITY_GROUP_ID reference, so integrators should rely on EVALUATION_ID as the connector to the parent evaluation entity.