Search Results amw_process_names_vl

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

Overview

AMW_PROCESS_NAMES_VL is a language-specific (VL suffix) view owned by the APPS schema within Oracle E-Business Suite, belonging to the AMW - Internal Controls Manager product module. Its purpose is to present a complete, translated representation of process entities by combining the descriptive, language-dependent text stored in AMW_PROCESS_NAMES_TL with the operational, non-displayed attributes held in AMW_PROCESS. The view returns exactly one row per process revision, specifically the latest revision, and resolves display text according to the session language of the querying user. In reporting and integration contexts, this view serves as the standard presentation layer for AMW process data: rather than joining the base and translation tables manually, developers and report authors query the view to obtain both the human-readable process name and description and the underlying technical attributes such as process code, approval status, and descriptive flexfield segments in a single selectable object.

Underlying Base Objects

The view is defined over two documented base tables. The first is AMW_PROCESS (aliased AOP), which stores the non-translated process definition data, including revision tracking, approval status, category, and flexfield attributes. The second is AMW_PROCESS_NAMES_TL (aliased APTL), which stores the translated DISPLAY_NAME and DESCRIPTION values keyed by language. The join condition is APTL.PROCESS_REV_ID = AOP.PROCESS_REV_ID combined with a language filter APTL.LANGUAGE = USERENV('LANG'), which restricts the translation row to the language of the current session. A correlated subquery further constrains results so that only the highest revision number per process is returned: AOP.REVISION_NUMBER = (SELECT MAX(AOP2.REVISION_NUMBER) FROM AMW_PROCESS AOP2 WHERE AOP2.PROCESS_ID = AOP.PROCESS_ID). The SELECT DISTINCT clause guards against duplicate rows arising from the join. The view therefore relates to its base objects as a denormalized, language-aware read interface rather than as a stored entity.

Key Columns

• DISPLAY_NAME / DESCRIPTION — Translated, user-facing text sourced from AMW_PROCESS_NAMES_TL in the session language.
• PROCESS_ID — Identifier of the process entity, stable across its revisions.
• PROCESS_REV_ID — Identifier of the specific process revision; the join key between AMW_PROCESS and the translation table.
• REVISION_NUMBER — Revision sequence value; the view exposes only the maximum revision per PROCESS_ID.
• PROCESS_CODE — Non-translated code value used for integration and keying.
• APPROVAL_STATUS / PROCESS_CATEGORY — Headline lifecycle and classification attributes of the process.
• NAME — The base (non-translated) name held in AMW_PROCESS.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield context and segment columns.
• SECURITY_GROUP_ID — Security grouping attribute for multi-org-style access control.
• OBJECT_VERSION_NUMBER — Optimistic locking version for the row.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY, CREATED_FROM — Standard audit columns carried from AMW_PROCESS.

Common Use Cases and Queries

Typical uses include reporting current process definitions by name, populating LOV or list display in custom AMW extensions, and extracting process data for integration or reconciliation against approval status. Because the view resolves language automatically and returns only the latest revision, callers avoid redundant filtering logic. A representative query follows:

SELECT PROCESS_ID, PROCESS_CODE, DISPLAY_NAME, DESCRIPTION, APPROVAL_STATUS, PROCESS_CATEGORY, REVISION_NUMBER FROM APPS.AMW_PROCESS_NAMES_VL WHERE APPROVAL_STATUS = 'APPROVED' ORDER BY DISPLAY_NAME;

A second pattern retrieves flexfield detail for a specific process:

SELECT DISPLAY_NAME, ATTRIBUTE_CATEGORY, ATTRIBUTE1, ATTRIBUTE2 FROM APPS.AMW_PROCESS_NAMES_VL WHERE PROCESS_CODE = :p_code;

Where translation coverage is a concern, the view intentionally excludes processes lacking a row in AMW_PROCESS_NAMES_TL for the session language, so integrations requiring all processes regardless of translation should query AMW_PROCESS directly. The view is documented as VALID and is referenced across AMW reporting surfaces.