Results for “amw_wf_processes_v”

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

Overview

AMW_WF_PROCESSES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the AMW – Internal Controls Manager product. The view exposes the set of Oracle Workflow processes defined in the application, together with the item types to which those processes belong, resolved to the session's language. Its documented purpose is to display Workflow processes and their item types, making it a lightweight reference source for reports, integrations, and diagnostic queries that need a human-readable listing of process definitions without navigating the Workflow configuration tables directly.

The view is documented as VALID in ETRM for both Oracle EBS 12.1.1 and 12.2.2. Its definition is stable across those releases because it depends only on the core Workflow definition tables, which are not affected by the Online Patching editioning model introduced in 12.2. In practice, the view functions in the same manner in both release lines: it returns one row per defined Workflow process per language, filtered to active (not end-dated) definitions.

Underlying Base Objects

The view is defined over two Oracle Workflow base tables:

• WF_ACTIVITIES — the runtime definition table holding each activity, its type, item type, version, and effective date range.
• WF_ACTIVITIES_TL — the language-specific translation table supplying the display name for each activity, keyed by name, version, item type, and language.

The join is performed on NAME, VERSION, and ITEM_TYPE, ensuring that the translated row matches the exact activity definition. The view restricts WF_ACTIVITIES to rows where END_DATE IS NULL and TYPE = 'PROCESS', so only current, non-retired process definitions are returned. The translation side is filtered by WA_TL.LANGUAGE = USERENV('LANG'), meaning results are returned in the language of the active session rather than in all installed languages. No other base objects are documented for this view, and no AMW-specific tables are referenced; the view is a thin projection over standard Workflow metadata.

Key Columns

• DISPLAY_NAME — the translated, user-facing name of the process, sourced from WF_ACTIVITIES_TL.DISPLAY_NAME in the session language. This is the value suitable for presentation in reports and list-of-values queries.
• NAME — the internal, untranslated process name from WF_ACTIVITIES.NAME. This is the identifier used programmatically, for example when launching or querying a process by its technical key.
• ITEM_TYPE — the Workflow item type to which the process belongs, from WF_ACTIVITIES.ITEM_TYPE. This groups processes by their owning workflow definition and is the natural join key when relating the view to other Workflow metadata.

Because NAME and ITEM_TYPE together identify a process definition, and VERSION is not exposed, the view is intended for current-state reference rather than historical or version-specific analysis.

Common Use Cases and Queries

Typical uses include populating a process selection list in an Internal Controls Manager report, validating that an expected process exists and is active, and joining to other Workflow views or AMW objects by ITEM_TYPE to enrich reporting. A basic listing follows:

• SELECT item_type, name, display_name FROM apps.amw_wf_processes_v ORDER BY item_type, display_name;
• SELECT name, display_name FROM apps.amw_wf_processes_v WHERE item_type = :p_item_type;
• SELECT COUNT(*) FROM apps.amw_wf_processes_v WHERE name = :p_process_name;

Note the language filter: a session whose USERENV('LANG') has no corresponding WF_ACTIVITIES_TL rows will return no data. Queries used in concurrent programs or interfaces should therefore bind an explicit session language or join directly to the base tables if translation-independent results are required.