Search Results process_category_code

Overview

AMW_CURR_APPROVED_REV_ORG_V is a reporting view within the Oracle E-Business Suite Internal Controls Manager (AMW) module. Its documented purpose is to present the current approved organization process revisions — that is, the set of organization-level process revisions that have completed approval and remain active. The view name encodes its intent precisely: AMW (module), CURR (current), APPROVED (approved revisions only), REV (revision), ORG (organization scope), and _V (view).

In the EBS 12.1.1 and 12.2.2 release context, note that the AMW product is documented as obsolete (Internal Controls Manager has been superseded by later GRC functionality). Consequently, the object may not be implemented in a given database. The ETRM metadata states explicitly: "Not implemented in this database," and lists no documented base objects or owner. In environments where the object persists, it remains useful for reporting and integration over the historical process/organization approval model.

The view's particular relevance to the search term process_category_code is direct: it exposes both PROCESS_CATEGORY_CODE and its translated counterpart PROCESS_CATEGORY as first-class columns, making it a natural source for segmenting approved process revisions by category.

Underlying Base Objects

The view text (as documented) selects from two base objects:

• AMW_PROCESS_ORGANIZATION (aliased A) — the primary organization/process revision table providing approval, certification, audit, and process metadata.
• AMW_PROCESS_NAMES_TL (aliased AP_TL) — the translatable (TL) name table providing DISPLAY_NAME and DESCRIPTION in the user's session language.

The two are joined on AP_TL.PROCESS_REV_ID = A.RL_PROCESS_REV_ID, with the language restriction AP_TL.LANGUAGE = USERENV('LANG'). The "current approved" filter is enforced in the WHERE clause: A.APPROVAL_DATE IS NOT NULL AND A.APPROVAL_END_DATE IS NULL. This combination returns only revisions that have been approved and have not yet been superseded or closed — the definition of a currently effective approved revision.

Key Columns

• PROCESS_ORGANIZATION_ID / PROCESS_ID / PROCESS_ORG_REV_ID — primary identifying keys for the organization-process association, the process, and the specific organization revision.
• RL_PROCESS_REV_ID — the revision identifier used to join to the TL name table (the join key).
• DISPLAY_NAME / DESCRIPTION — localized process name and description sourced from AMW_PROCESS_NAMES_TL.
• PROCESS_CATEGORY_CODE / PROCESS_CATEGORY — the coded and descriptive classification of the process; the focus of the user's search.
• REVISION_NUMBER, START_DATE, END_DATE, APPROVAL_DATE, APPROVAL_END_DATE, DELETION_DATE — revision lifecycle and effective-dating attributes.
• APPROVAL_STATUS, CERTIFICATION_STATUS, LAST_AUDIT_STATUS — status indicators for governance tracking.
• LAST_CERTIFICATION_DATE, LAST_AUDIT_DATE, NEXT_AUDIT_DATE — key governance dates.
• CONTROL_COUNT / RISK_COUNT — aggregated counts of controls and risks associated with the process revision.
• STANDARD_PROCESS_FLAG, SIGNIFICANT_PROCESS_FLAG, STANDARD_VARIATION — flags distinguishing standard and significant processes.
• PROCESS_TYPE, CONTROL_ACTIVITY_TYPE, RISK_CATEGORY, ORGANIZATION_ID — additional classification attributes.

Common Use Cases and Queries

Typical scenarios include compliance dashboards, audit planning, and downstream integration where only currently approved revisions are relevant. A common starting query filters by process category:

• SELECT PROCESS_ORGANIZATION_ID, ORGANIZATION_ID, PROCESS_CODE, PROCESS_CATEGORY_CODE, PROCESS_CATEGORY, APPROVAL_DATE FROM AMW_CURR_APPROVED_REV_ORG_V WHERE PROCESS_CATEGORY_CODE = :category_code;

Other frequent patterns:

• Locating significant processes for an organization: ... WHERE ORGANIZATION_ID = :org_id AND SIGNIFICANT_PROCESS_FLAG = 'Y';
• Audit scheduling by next audit date: ... WHERE NEXT_AUDIT_DATE BETWEEN :from AND :to;
• Control/risk weighting by category: SELECT PROCESS_CATEGORY_CODE, SUM(CONTROL_COUNT), SUM(RISK_COUNT) ... GROUP BY PROCESS_CATEGORY_CODE;

Because the view is defined over an obsolete module and may not be implemented, always verify object existence in the target instance before relying on it.