Search Results amw_process_names_pkg

Overview

AMW_PROCESS_NAMES_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under ETRM as an "OTHER" API object. It belongs to the Application Management Workspace (AMW) product family, which provides the foundation for Oracle's HTML-based application management and process definition functionality. The package serves as the maintenance layer for the AMW_PROCESS_NAMES_TL table—the translated ("TL") child of the AMW_PROCESS entity—which stores the language-specific, user-facing names of the business processes defined within the AMW framework. In this role the package encapsulates the standard Oracle multi-language seed-data pattern: insert, lock, update, and delete operations for a single row, plus language installation and initial seed loading of translated name rows. The package status is VALID, and the documented dependency list is minimal, referencing only the SYS.STANDARD package and being referenced by no other packages, which indicates a terminal, self-contained utility layer rather than a shared library invoked extensively across the data dictionary.

Key Procedures and Functions

ETRM documents six procedures and functions in this package. Their documented purposes are as follows:

• INSERT_ROW — Inserts a new translated process-name row into AMW_PROCESS_NAMES_TL, including the required language and source-language columns and the standard WHO audit columns.
• LOCK_ROW — Acquires a row-level lock on an existing translated name record to prevent concurrent modification during an update transaction, returning the locked row for downstream processing.
• UPDATE_ROW — Applies changes to an existing translated process-name row, updating the descriptive name text and the WHO audit columns (last updated by, last update date, last update login).
• DELETE_ROW — Removes a single translated name row from AMW_PROCESS_NAMES_TL, typically during cleanup of obsolete language rows or re-seeding operations.
• ADD_LANGUAGE — Registers the process name for an additionally installed language by creating the corresponding translated row, supporting Oracle's multi-language translation model that maintains one row per language per process.
• LOAD_SEED_DATA — Populates the translated name table with the initial seed rows shipped by Oracle for a given language, executed as part of the multi-language seed-data load process when a language is installed or upgraded.

These six routines form a conventional TL-table maintenance cluster and are typically used together by the AMW translation/seed infrastructure and by any form or program that creates, edits, or removes AMW process names in a specific language.

Tables Accessed

The package reads and writes three tables through APPS synonyms:

• AMW_PROCESS — The base (non-translated) process definition table. It provides the parent process identifier and the language-independent attributes of the process to which the translated name belongs.
• AMW_PROCESS_NAMES_TL — The primary target of the package, holding one translated name row per process per language. All six routines operate directly on this table.
• FND_LANGUAGES — Oracle's standard languages table, used to validate the selected language, determine the source (base) language, and drive the ADD_LANGUAGE and LOAD_SEED_DATA processing.

Usage Notes

Because AMW_PROCESS_NAMES_PKG has no referencing packages and minimal dependencies, it is most commonly invoked in two contexts. First, during multi-language installation and patching, where the Oracle Multi-Language Seed Data Load process calls LOAD_SEED_DATA (and, for newly added languages, ADD_LANGUAGE) to populate AMW_PROCESS_NAMES_TL. Second, it can be called from the AMW process-definition Forms or OAF-based maintenance pages—or from custom code performing direct DML—whenever a process name must be created, changed, locked, or removed for a particular language, preserving the segregation between the base AMW_PROCESS table and its translated name rows. As with all TL-table packages, direct DML against AMW_PROCESS_NAMES_TL outside these routines risks losing synchronization between language rows. The object is fully VALID in both EBS 12.1.1 and 12.2.2, and the ETRM documentation records no parameter lists, so implementers should rely on its documented functional role rather than on signatures.