Results for “process_org”

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

Overview

APPS.AMW_ORG_RELATIONS_V is a reporting view in the Oracle E-Business Suite Audit Management (formerly Enterprise Territory and Resource Management / ETRM) module. It exposes the parent-child hierarchy that exists between audit processes (also referred to as processes or audit units) within a given operating unit or organization. The view joins the process relationship table to the process basic-information view twice — once for the parent side and once for the child side — to translate internal numeric identifiers into readable names and descriptive attributes.

Its primary role is to surface the organizational structure of audit processes so that reports, dashboards, and OAF (Oracle Application Framework) pages can present a drillable hierarchy. Because the view embeds context-sensitive URL strings, it is also used by the application tier to build navigation links directly to process detail pages, risk tabs, and control tabs. The column significant_process_flag identifies whether a process has been flagged as significant for audit-planning purposes, which drives prioritization and coverage analysis.

Underlying Base Objects

The view is defined over the following objects:

• AMW_PROCESS_ORG_RELATIONS apor — the relationship (edge) table holding parent_process_id, child_process_id, instance_id, and organization_id.
• AMW_PROCESS_ORG_BASICINFO_V apobv1 — aliased as the parent side, joined on organization_id and process_id = parent_process.
• AMW_PROCESS_ORG_BASICINFO_V apobv2 — aliased as the child side, supplying the descriptive columns for the child process.
• AMW_WF_HIERARCHY_PKG.find_transition_order — a PL/SQL function returning the reverse transition order of the hierarchy instance.
• AMW_Utility_PVT.get_proc_org_opinion_status — returns the certification status opinion for the child process within its organization.

The metadata provided documents no additional base tables directly; the view derives its descriptive attributes entirely from the process-organization basic-info view, which itself resolves party names, risk counts, and control counts.

Key Columns

• PARENT_PROCESS_NAME / CHILD_PROCESS_NAME — readable names of the parent and child processes.
• PARENT_PROCESS_ID / CHILD_PROCESS_ID — numeric identifiers for the hierarchy edges.
• INSTANCE_ID — identifies the hierarchy instance to which the relationship belongs.
• TRANSITION_REVERSE_ORDER — computed ordering value used to sequence the hierarchy.
• SIGNIFICANT_PROCESS_FLAG — indicates whether the child process is designated significant, the column referenced by the search query.
• STANDARD_PROCESS_FLAG, APPROVAL_STATUS, CERTIFICATION_STATUS, CERTIFICATION_STATUS_CODE — lifecycle and compliance attributes.
• RISK_COUNT, CONTROL_COUNT — aggregate counts of associated risks and controls.
• PROCESS_OWNER_ID, PROCESS_OWNER_NAME — the responsible owner.
• ORG_NAME, PROCESS_ORG_ID, PROCESS_ID — organizational context and identifiers.
• URLSTRING, RISKCNTURL, CTRLCNTURL — pre-built OAF navigation links.

Common Use Cases and Queries

A frequent requirement is to isolate hierarchy edges whose child process carries the significant flag, for coverage or audit-scope reporting:

SELECT parent_process_name,
       child_process_name,
       significant_process_flag,
       risk_count,
       control_count,
       org_name
FROM   apps.amw_org_relations_v
WHERE  significant_process_flag = 'Y'
ORDER  BY parent_process_name, child_process_name;

Another common pattern is navigating the hierarchy for a specific instance or organization to render an indented process tree in a dashboard:

SELECT LPAD(' ', 2 * (LEVEL - 1)) || child_process_name process_name,
       transition_reverse_order
FROM   apps.amw_org_relations_v
WHERE  instance_id = :instance_id
CONNECT BY PRIOR child_process_id = parent_process_id
START WITH parent_process_id IS NULL
ORDER SIBLINGS BY transition_reverse_order;

Because the view also exposes certification status and URLs, it supports compliance reporting on which significant processes remain uncertified, and it supplies the OAF links used when building custom or extended audit-management pages. In all cases queries should be schema-qualified and executed under an APPS-enabled responsibility consistent with standard EBS security practice.