Search Results parent_setup_risk_type_id

Overview

APPS.AMW_SETUP_RISK_TYPES_VL is a multilingual (language-resolved) view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It is the reporting and integration interface for Setup Risk Type definitions used within the Oracle Enterprise Governance, Risk, and Compliance (EGRC) / Application Management Workspace (AMW) module, which underpins the Risk and Control Management (RCM) functionality. The "_VL" suffix indicates the view resolves translated name and description columns from a translation table against the session language, so consumers see a single row per risk type in the appropriate language rather than one row per installed language.

The view has a documented status of VALID and is registered in FND Design Data as AMW.AMW_SETUP_RISK_TYPES_VL. Its primary function is to expose a denormalized, ready-to-query representation of the underlying Setup Risk Types entities for use in data loading routines, reports, and custom integrations. Note that the ETRM metadata documents no explicitly referenced base objects, but the naming convention and dependent program references make the underlying structure apparent.

Underlying Base Objects

Although the documented metadata lists no base objects, the standard multi-lingual view pattern for this module defines AMW_SETUP_RISK_TYPES_VL as a join between two tables:

• AMW_SETUP_RISK_TYPES_B — the base (non-translated) table holding the primary key SETUP_RISK_TYPE_ID and the language-independent attributes such as RISK_TYPE_CODE and hierarchy linkage.
• AMW_SETUP_RISK_TYPES_TL — the translation table supplying SETUP_RISK_TYPE_NAME and SETUP_RISK_TYPE_DESCRIPTION for the current language, joined on SETUP_RISK_TYPE_ID.

The view is referenced by the concurrent/load programs AMW_LOAD_RCM_ORG_DATA and AMW_LOAD_RC_DATA, which import risk and control data into the RCM repository. Any change to the underlying setup tables is therefore immediately visible to those programs through this view.

Key Columns

• SETUP_RISK_TYPE_ID — surrogate primary key identifying the risk type record.
• RISK_TYPE_CODE — the user-visible alphanumeric code (VARCHAR2(30)). This is the column users most frequently search on and is typically the business key referenced in mappings, hierarchies, and external extracts.
• PARENT_SETUP_RISK_TYPE_ID — self-referencing foreign key enabling a parent-child hierarchy among risk types, supporting rolling roll-ups in risk reporting.
• SETUP_RISK_TYPE_NAME and SETUP_RISK_TYPE_DESCRIPTION — language-resolved text (VARCHAR2(240) and VARCHAR2(4000)) sourced from the TL table.
• START_DATE / END_DATE — effective dating controlling when a risk type is active.
• SECURITY_GROUP_ID — used by the AMW/EGRC security model to segregate data across organizations.
• OBJECT_VERSION_NUMBER and TAG — standard EBS concurrency and synchronization columns.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, plus ROW_ID.

Common Use Cases and Queries

Typical uses include: validating risk type codes before loading RCM data; feeding lookup lists in custom forms or BI Publisher reports; and extracting the risk type hierarchy for cross-module reconciliation.

Sample query retrieving active risk types with names:

SELECT setup_risk_type_id,
       risk_type_code,
       setup_risk_type_name,
       parent_setup_risk_type_id
FROM   apps.amw_setup_risk_types_vl
WHERE  TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, TRUNC(SYSDATE))
ORDER  BY risk_type_code;

Filtering by a specific code searched via risk_type_code:

SELECT risk_type_code, setup_risk_type_name, setup_risk_type_description
FROM   apps.amw_setup_risk_types_vl
WHERE  risk_type_code = :risk_type_code;

Join the view to the base table for hierarchy traversal, or simply rely on PARENT_SETUP_RISK_TYPE_ID to self-join for multi-level roll-ups.