Search Results azw_ia_role

Overview

AZ_TASKS_V is an Oracle E-Business Suite reporting view owned by the APPS schema. It presents a consolidated, denormalized projection of workflow task instances created by Oracle ETRM (Enterprise Tax and Regulatory Management) processes. The view joins task-level workflow data from the Oracle Workflow runtime tables against the ETRM configuration table AZ_PROCESSES, producing one row per workflow activity with its associated tax context, assigned user, status, and elapsed duration.

The view is restricted to ETRM workflows by the predicate wi.item_type LIKE 'AZW%', so it exposes only those item types generated by AZW-prefixed ETRM process definitions. It is used primarily for operational reporting and monitoring of in-progress and historical ETRM task activity, and as a data source for custom dashboards, extracts, and integration interfaces that need to reconcile ETRM workflow state with the underlying tax context identified by the attribute AZW_IA_CTXT_ID — the identifier most frequently referenced by users searching for azw_ia_ctxt_id.

Underlying Base Objects

The view is defined over five referenced base objects, all exposed to APPS through synonyms:

• AZ_PROCESSES — ETRM configuration table mapping an item type and process name to a context identifier and context name.
• WF_ITEMS — Oracle Workflow item instances, supplying item type, item key, root activity, and begin/end dates.
• WF_ITEM_ACTIVITY_STATUSES — Per-activity execution status within each workflow item.
• WF_ITEM_ATTRIBUTE_VALUES — Workflow item attribute values; the view self-joins this table twice, once for attribute AZW_IA_ROLE (assigned user) and once for attribute AZW_IA_CTXT_ID (tax context identifier).
• WF_PROCESS_ACTIVITIES — Process definition activity instances, joined on process_name = 'ROOT' to link the root activity to the item.

The joins correlate item type and item key across the workflow tables and correlate item type, root activity, and the numeric context identifier against AZ_PROCESSES, ensuring only tasks with a valid ETRM context are returned.

Key Columns

• ITEM_TYPE, ITEM_KEY — Workflow instance identity; ITEM_TYPE always matches the AZW% pattern.
• ROOT_ACTIVITY — Name of the top-level workflow process that owns the task.
• CONTEXT_ID — Numeric ETRM context identifier, obtained by converting the AZW_IA_CTXT_ID attribute text value with TO_NUMBER.
• CONTEXT_NAME — Descriptive context name from AZ_PROCESSES for the matching context.
• BEGIN_DATE, END_DATE — Task start and completion timestamps; END_DATE is null for open tasks.
• ASSIGNED_USER — First 100 characters of the AZW_IA_ROLE attribute value, identifying the user or role assigned to the activity.
• ACTIVITY_ID — The workflow process activity instance identifier.
• STATUS — Decoded activity status: 'A' for ACTIVE, 'C' for any completed or otherwise terminal status.
• DURATION — Approximate elapsed duration, computed as the month difference multiplied by 31; uses SYSDATE when END_DATE is null.

Common Use Cases and Queries

Typical usages include monitoring open ETRM tasks, auditing how long activities remain assigned to a given user, and resolving a task back to its tax context via AZW_IA_CTXT_ID. The following examples illustrate common access patterns.

• Open tasks with their assigned user and tax context:

  SELECT item_type, item_key, context_id, context_name,
         assigned_user, begin_date, duration
  FROM   apps.az_tasks_v
  WHERE  status = 'A'
  ORDER BY begin_date;

• Task history for a specific context identified through azw_ia_ctxt_id:

  SELECT item_key, root_activity, assigned_user,
         status, begin_date, end_date, duration
  FROM   apps.az_tasks_v
  WHERE  context_id = :p_context_id
  ORDER BY begin_date DESC;

• Aging report of tasks exceeding a threshold:

  SELECT item_key, assigned_user, context_name, duration
  FROM   apps.az_tasks_v
  WHERE  status = 'A'
  AND    duration > 30;

Because the view derives DURATION from SYSDATE for open tasks, results vary between executions; report consumers should note this non-deterministic behavior when reconciling historical extracts.