Results for “az_processes_all_v”

38 results




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

Overview

AZ_PROCESSES_ALL_V is a language-aware, multi-organization-style view owned by the APPS schema in Oracle E-Business Suite release 12.1.1 and 12.2.2. It belongs to the Application Implementation (AZ) product family, which underpins the Oracle Application Implementation Wizard and related setup utilities. The view consolidates process definitions used by the Wizard into a single queryable interface, resolving internal identifiers to user-facing display names so that reports, forms, and integrations can present meaningful labels without joining to Workflow or lookup tables directly.

Functionally, the view answers the question "which Wizard processes exist, what are they called in the current session language, and what context governs them?" By exposing both language-dependent display names and status codes, it supports localization-aware reporting and enables administrators to audit the set of processes associated with a given item type, such as an Application Implementation template or a setup process group. Because the view filters on active (non-ended) workflow activities and AZ-prefixed item types, it returns only valid, currently effective process definitions.

Underlying Base Objects

The view is defined with an inner join across three documented objects, with an additional dependency on FND_GLOBAL for session language and organization context:

  • AZ_PROCESSES (synonym, resolving to the base processes table) — supplies the core process rows, including item type, process name, context, ordering, status, and type attributes.
  • WF_ACTIVITIES_VL (view) — the Workflow activities view provides the language-dependent DISPLAY_NAME and DESCRIPTION for each activity, matched on item type and process name.
  • FND_LOOKUPS (view) — supplies the meaning for the AZ_CONTEXT_TYPE lookup, translated into the CONTEXT_TYPE_NAME column.
  • FND_GLOBAL (package) — implicitly provides the language and context values used by the VL (language) views underlying the join, ensuring the returned names respect the user's session language.

The join predicates restrict results to item types and activity names beginning with AZ, exclude ended workflow activities (END_DATE IS NULL), and map the context type code to its lookup meaning. This means the view is not a straight projection of AZ_PROCESSES; it is a curated, filtered join that assumes proper Workflow activity definitions exist for each process row.

Key Columns

  • ITEM_TYPE — the Workflow item type (typically an AZ-prefixed type) that scopes the process.
  • PROCESS_NAME — the internal name of the Wizard process, matching the Workflow activity name.
  • DISPLAY_NAME — the language-dependent, user-visible name of the process from WF_ACTIVITIES_VL.
  • DESCRIPTION — language-dependent narrative description of the activity.
  • CONTEXT_ID, PARENT_ID, DISPLAY_ORDER — hierarchy and ordering metadata controlling how processes appear and nest.
  • STATUS_CODE / STATUS — indicates whether the process is active or otherwise available for use.
  • PROCESS_TYPE — classifies the process within the Wizard's processing model.
  • CONTEXT_TYPE and CONTEXT_TYPE_NAME — the context classification code and its translated lookup meaning.
  • CONTEXT_NAME, COMMENTS — free-form context identifier and administrative notes.

Common Use Cases and Queries

Typical scenarios include building Wizard process reports, validating that expected processes are active before running setup, and extracting display names for documentation or interfaces. A basic listing is:

SELECT item_type, process_name, display_name,
       status_code, context_type_name, display_order
FROM   apps.az_processes_all_v
WHERE  item_type = :item_type
ORDER  BY display_order;

To audit active processes only:

SELECT process_name, display_name, context_name
FROM   apps.az_processes_all_v
WHERE  status_code = 'ACTIVE'
AND    context_type_name = :context_type;

Always qualify the view with the APPS schema and, where possible, filter on ITEM_TYPE to limit the Workflow lookup join and improve performance.