Results for “amw_process_vl”

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

Overview

AMW_PROCESS_VL is a seeded, valid database view owned by the APPS schema within the Oracle E-Business Suite Internal Controls Manager (AMW) product. Internal Controls Manager supports configuration, certification, and management of process controls, risks, and compliance initiatives, and is commonly deployed alongside the governance, risk, and compliance capabilities in EBS 12.1.1 and 12.2.2. The suffix "_VL" identifies this object as a "view with language" — that is, a view constructed to expose translation-aware display columns from a translated (_TL) table joined to the base entity table. In the AMW schema, AMW_PROCESS_VL provides the language-aware presentation layer for risk library processes, surfacing the display name and description in the session user's language alongside the denormalized process attributes maintained on the base process record. It functions as the primary read-only access point for reporting, concurrent program processing, form blocks, and integration queries that need process metadata rendered in the current user's language. Because the view resolves the language at runtime through a join with the translations table, it returns consistent, audience-appropriate text without requiring applications or reports to perform their own language resolution.

Underlying Base Objects

According to the documented view definition, AMW_PROCESS_VL is constructed from two base objects joined on the process revision identifier:

• AMW_PROCESS (aliased AP) — the primary process entity table that stores the denormalized process header data, including identifiers, flags, counts, ownership, certification status, and audit columns.
• AMW_PROCESS_NAMES_TL (aliased AP_TL) — the language-specific translations table that holds the display name and description for each process revision.

The join condition is AP_TL.PROCESS_REV_ID = AP.PROCESS_REV_ID, restricted by AP_TL.LANGUAGE = USERENV('LANG'). This means the view returns the translated name and description matching the language of the current session, while all other attributes are drawn from the base AMW_PROCESS table. Although the ETRM metadata notes no separately documented base objects, the view text itself is explicit about its two-table origin.

Key Columns

• DISPLAY_NAME, DESCRIPTION — language-resolved text sourced from AMW_PROCESS_NAMES_TL.
• PROCESS_ID, PROCESS_REV_ID, REVISION_NUMBER, PROCESS_CODE, NAME — process identity and revision tracking.
• APPROVAL_STATUS, APPROVAL_DATE, APPROVAL_END_DATE, CERTIFICATION_STATUS — workflow and certification state.
• STANDARD_VARIATION — a key column relevant to the user's search; it records the standard variation classification for the process, distinguishing standard and non-standard process variants.
• STANDARD_PROCESS_FLAG, SIGNIFICANT_PROCESS_FLAG, PROCESS_CATEGORY, PROCESS_TYPE, CLASSIFICATION — process classification and significance attributes.
• CONTROL_COUNT, RISK_COUNT, ORG_COUNT, RISK_COUNT_LATEST, CONTROL_COUNT_LATEST — aggregate counts of associated controls, risks, and organizations.
• PROCESS_OWNER_ID, FINANCE_OWNER_ID, APPLICATION_OWNER_ID — owner references.
• START_DATE, END_DATE, DELETION_DATE, SECURITY_GROUP_ID, OBJECT_VERSION_NUMBER — lifecycle and multi-tenant/security metadata.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, REQUEST_ID, PROGRAM_ID, and the ATTRIBUTE1–15 flexfield columns.

Common Use Cases and Queries

Typical uses include risk library reporting, process certification dashboards, and integration extracts that require language-resolved process names. A representative query filtering on standard variation is:

• SELECT display_name, process_code, standard_variation, certification_status FROM amw_process_vl WHERE standard_variation IS NOT NULL;
• SELECT p.display_name, p.risk_count, p.control_count FROM amw_process_vl p WHERE p.standard_process_flag = 'Y';

Because the view resolves language via USERENV('LANG'), no additional language predicate is required by consuming queries.