Search Results new_process_name




Overview
Explore in AI Chat

Overview

The AMW.AMW_EXCEPTIONS_TL table is a translation (TL) table within the Oracle E-Business Suite 12.1.1 / 12.2.2 environment, owned by the AMW schema. It stores translated exception justifications used by the Application Management Warehouse / exception management functionality. The _TL suffix indicates this object follows the standard Oracle Multi-Language Support (MLS) pattern: the base exception record resides in a corresponding _B table, and language-specific text — in this case the justification narrative and process display names — is held here, keyed by both EXCEPTION_ID and LANGUAGE.

From a Data Vault modeling perspective, the heuristic classification of this object is satellite-leaning. It behaves as a descriptive satellite attached to the core exception entity (AMW_EXCEPTIONS_B), carrying language-dependent descriptive attributes rather than acting as a hub or a link. The design is consistent with EBS reference-data storage typical of the AMW module.

Key Information Stored

The table contains 13 documented columns. The most significant are:

  • EXCEPTION_ID — Number; the exception identifier and the primary join key back to AMW_EXCEPTIONS_B.
  • LANGUAGE — The language code for the translated row; combined with EXCEPTION_ID, this forms the composite business key of the MLS pattern.
  • SOURCE_LANGUAGE — Stores the source language from which the translation originated.
  • SOURCE_LANG — An additional source-language column retained for MLS compatibility.
  • JUSTIFICATION — VARCHAR2(4000); the translated justification narrative for the exception.
  • OLD_PROCESS_NAME — VARCHAR2(80); the process display name of a deleted or replaced process.
  • NEW_PROCESS_NAME — VARCHAR2(80); the process display name of an added or replacing process. This is the column implicated by the user's search term "new_process_name" and is central to change-tracking of process substitutions.
  • SECURITY_GROUP_ID — Used in hosted (multi-tenant) environments to partition records.
  • Standard Who columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — provide audit lineage for each translated row.

No surrogate sequence column beyond EXCEPTION_ID is documented; the effective unique business key is the EXCEPTION_ID plus LANGUAGE combination.

Common Use Cases and Queries

Typical usage centers on retrieving justified process changes and multilingual exception reporting. A common pattern joins the translation table to its base table for a specific language:

  • Retrieve the translated justification for an exception: SELECT JUSTIFICATION FROM AMW.AMW_EXCEPTIONS_TL WHERE EXCEPTION_ID = :id AND LANGUAGE = USERENV('LANG');
  • Report on process replacements by selecting OLD_PROCESS_NAME and NEW_PROCESS_NAME alongside the justification.
  • Audit trail reporting using LAST_UPDATE_DATE to track when a translated justification changed.
  • Hosted-environment filtering by SECURITY_GROUP_ID to isolate tenant-specific translations.

Related Objects

  • AMW.AMW_EXCEPTIONS_B — The base table; joined on EXCEPTION_ID, holding the language-independent exception record.
  • FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID; controls hosted-environment access.
  • APPS.AMW_EXCEPTIONS_TL — The APPS synonym/view layer through which the table is normally accessed.
  • FND_LANGUAGES — Implicit relationship via LANGUAGE for language validation.
  • FND_APPLICATION / AMW module views — Reporting views built over the exception tables.