Results for “az_flow_phases_v”

36 results




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

Overview

The AZ_FLOW_PHASES_V view is a reporting and integration object owned by the APPS schema within the Oracle E-Business Suite. It belongs to the AZ – Application Implementation product, the module that underpins the Oracle Application Implementation Wizard (AIM) and related setup/configuration utilities. The view is documented as VALID and is provided to give developers, integrators, and reporting tools "easy access to Wizard workflows and their phase." In practice, this means the view flattens the relationship between a Wizard product flow (a logical grouping of setup activities) and the individual phases that those flows belong to, exposing a compact, denormalized result set of flow-to-phase mappings.

Because it is a view rather than a base table, AZ_FLOW_PHASES_V carries no storage of its own; it is a query definition that reads from the AZ implementation tables and presents a joined, de-duplicated result. This makes it well suited to read-only consumption in custom reports, concurrent programs, discoverer workbooks, and external integrations that need to enumerate the phases associated with application implementation workflows.

Underlying Base Objects

The ETRM 12.1.1 / 12.2.2 documentation records that the view is defined over two referenced base objects, both accessed through SYNONYM entries in the APPS schema:

  • AZ_PRODUCT_FLOWS – the table that stores the product flows (workflows) available in the implementation wizard. The view references this object through the alias AZPF, using its ITEM_TYPE, PROCESS_NAME, and APPLICATION_ID columns.
  • AZ_PRODUCT_PHASES – the table that stores the phases associated with each application. The view references this object through the alias AZPP, using its PHASE and APPLICATION_ID columns.

The documented view text shows that the join is performed on APPLICATION_ID, matching flows to phases within the same application. A DISTINCT clause is applied to the projected column list, ensuring that any duplication introduced by the join is collapsed before results are returned to the caller. This is an important characteristic for consumers, since it confirms that the view is intended as a distinct mapping set rather than a transactional detail source.

Key Columns

The view exposes three columns, each inherited from the base objects:

  • ITEM_TYPE – sourced from AZ_PRODUCT_FLOWS.ITEM_TYPE. It identifies the item type that the flow is associated with, effectively tagging each row to the Wizard entity being implemented.
  • PROCESS_NAME – sourced from AZ_PRODUCT_FLOWS.PROCESS_NAME. This is the name of the Wizard workflow or process that the flow represents, and together with ITEM_TYPE identifies the flow within the result set.
  • PHASE – sourced from AZ_PRODUCT_PHASES.PHASE. It indicates the implementation phase to which the flow belongs, providing the phase dimension for filtering or grouping.

Collectively, these three columns allow a consumer to answer questions such as "which phases exist for this item type" or "which flows are active in a given phase," without needing to join the underlying tables manually.

Common Use Cases and Queries

Typical usage includes generating implementation phase reports, driving custom Wizard dashboards, and validating configuration data during EBS upgrades or implementations. A basic query to list all flow-to-phase mappings is:

  • SELECT item_type, process_name, phase FROM apps.az_flow_phases_v;

To restrict output to a specific item type, a predicate can be applied directly to the exposed column:

  • SELECT process_name, phase FROM apps.az_flow_phases_v WHERE item_type = :p_item_type ORDER BY phase, process_name;

For phase-level reporting, the view supports straightforward aggregation, for example counting the flows within each phase:

  • SELECT phase, COUNT(DISTINCT process_name) flow_count FROM apps.az_flow_phases_v GROUP BY phase ORDER BY phase;

Because the view performs the APPLICATION_ID join internally and returns a distinct set, it is safe to embed in reporting queries without additional de-duplication. It is read-only by design, so all customizations should treat AZ_FLOW_PHASES_V as a query source only, never as a target for DML.