Search Results dependency_parent_id

Overview

AZ_GROUPS_V is a language-dependent reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the AZ product, Application Implementation, which underpins the Oracle Applications Wizard and related setup flows. The view presents human-readable display names for Wizard process groups by resolving either a lookup meaning or an application name, depending on which identifying attribute is populated on the underlying group row.

The view exists because the base table AZ_GROUPS stores only coded identifiers — a lookup code or an application identifier — rather than translated text. AZ_GROUPS_V joins those codes to the appropriate language-dependent source, so reports, Discoverer workbooks, OAF pages, and custom concurrent programs can present group names in the session user's language without duplicating translation logic. Because it consolidates two mutually exclusive resolution paths into a single result set, the view behaves as a unified catalog of process groups. It is read-only by design; all maintenance occurs against the base table. The view carries no status of its own beyond the derived STATUS column described below.

Underlying Base Objects

The view is defined as a UNION of two SELECT statements over the following documented objects:

• AZ_GROUPS (referenced through a synonym) — the driving table in both branches, supplying group identity, ordering, hierarchy, dependency, and audit columns.
• FND_LOOKUPS — joined in the first branch on LOOKUP_TYPE = 'AZ_PROCESS_GROUPS' and LOOKUP_CODE; the lookup MEANING supplies DISPLAY_NAME. This branch is restricted to rows where AG.LOOKUP_CODE IS NOT NULL.
• FND_APPLICATION_VL — joined in the second branch on APPLICATION_ID; the translated APPLICATION_NAME supplies DISPLAY_NAME. This branch is restricted to rows where AG.APPLICATION_ID IS NOT NULL.
• FND_GLOBAL (package) — referenced indirectly for session context such as language and user identity, which governs which translation row the VL and lookups objects return.

The two branches are mutually exclusive by their WHERE predicates, so no GROUP_ID is duplicated across the union. A given group resolves its display name either from the AZ_PROCESS_GROUPS lookup or from the application name, never both.

Key Columns

• GROUP_ID — primary identifier of the process group; joins back to AZ_GROUPS.
• PROCESS_TYPE — classifies the process group within the wizard framework.
• DISPLAY_NAME — the translated name, drawn from FND_LOOKUPS.MEANING or FND_APPLICATION_VL.APPLICATION_NAME.
• DISPLAY_ORDER — controls presentation sequence in wizard listings.
• STATUS / COMPLETE_FLAG — STATUS derives from COMPLETE_FLAG via DECODE, mapping 'N' to 'A' (active) and all other values to 'C' (complete).
• APPLICATION_ID and LOOKUP_CODE — indicate which resolution path produced the row.
• COLOR_CODE — presentation attribute used by the wizard UI.
• HIERARCHY_PARENT_ID, HIERARCHY_PARENT_PROCESS_TYPE, DEPENDENCY_PARENT_ID, DEPENDENCY_PARENT_PROCESS_TYPE — define parent/child grouping and prerequisite relationships.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical uses include troubleshooting wizard group configuration, building setup validation reports, and populating custom dashboards with translatable group names.

• List active groups in display order:

  SELECT group_id, process_type, display_name, display_order
  FROM   az_groups_v
  WHERE  status = 'A'
  ORDER BY display_order;

• Identify groups resolved via lookup versus application:

  SELECT group_id, display_name, lookup_code, application_id
  FROM   az_groups_v
  WHERE  lookup_code IS NOT NULL;

• Traverse hierarchy relationships:

  SELECT h.group_id, h.display_name, p.display_name parent_name
  FROM   az_groups_v h, az_groups_v p
  WHERE  h.hierarchy_parent_id = p.group_id;

Because the view exposes no bind variables, filtering on GROUP_ID, PROCESS_TYPE, or STATUS keeps query cost low. Note that FND_GLOBAL session context determines the language returned, so results differ by login environment. Oracle proprietary and confidential.