Search Results amw_setup_risk_types_vl




Overview
Explore in AI Chat

Overview

The AMW_SETUP_RISK_TYPES_VL view is a translation-enabled (VL, "view language") database object belonging to the AMW product family, which corresponds to Oracle Internal Controls Manager. Internal Controls Manager was an E-Business Suite application that supported SOX-oriented compliance workflows, letting organizations define risks, controls, test plans, and remediation procedures. Within that functional model, setup risk types act as user-defined reference data that let compliance administrators categorize and group risks for reporting, hierarchy building, and control mapping.

This particular view exposes the risk type definitions maintained in the application's setup area, combining the base, language-independent attributes with the language-specific name and description. Because it is a VL view, it automatically filters the translated text to the session's current language, using the standard EBS multilingual mechanism (USERENV('LANG')). As a view rather than a table, it holds no data of its own; it is a read-only projection intended for forms, concurrent programs, and custom reports.

The ETRM documentation explicitly records this object as "Not implemented in this database," meaning the view exists in the application's metadata dictionary but its defining database object may not be physically present in a given environment. This is a significant point for administrators and developers: the view is a reference definition, not a guaranteed runtime object, so its presence depends on whether the AMW module was configured in that instance.

Underlying Base Objects

The view definition is a two-table join with a language filter. It selects from AMW_SETUP_RISK_TYPES_B (the base or "_B" table) and AMW_SETUP_RISK_TYPES_TL (the translation or "_TL" table), joining them on SETUP_RISK_TYPE_ID and restricting the translation rows to the current session language.

The join condition B.SETUP_RISK_TYPE_ID = T.SETUP_RISK_TYPE_ID combined with T.LANGUAGE = USERENV('LANG') ensures each risk type is returned once, in the user's preferred language. No other base objects are documented as referenced.

Key Columns

  • ROWID / ROW_ID — the physical row identifier, selected from the base table; useful for direct DML on the underlying table in controlled scripts.
  • SETUP_RISK_TYPE_ID — the primary surrogate key uniquely identifying each risk type.
  • RISK_TYPE_CODE — a user-facing short code used in lookups and interfaces.
  • PARENT_SETUP_RISK_TYPE_ID — a self-referencing key enabling a hierarchy of risk types; null for top-level entries.
  • START_DATE / END_DATE — effective-dating columns controlling when a risk type is active.
  • NAME / DESCRIPTION — the translated display text sourced from the _TL table.
  • Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.
  • SECURITY_GROUP_ID — the multi-org security grouping used by AMW.
  • OBJECT_VERSION_NUMBER — optimistic locking control column.
  • TAG — a context or grouping tag.

Common Use Cases and Queries

Typical uses include populating flexfield-style value sets, driving LOVs in compliance forms, and building reports that list the risk type hierarchy. A basic listing query retrieves the translated names for the current language:

  • SELECT setup_risk_type_id, risk_type_code, name, description FROM amw_setup_risk_types_vl ORDER BY name;
  • SELECT p.name AS parent_name, c.name AS child_name FROM amw_setup_risk_types_vl c, amw_setup_risk_types_vl p WHERE c.parent_setup_risk_type_id = p.setup_risk_type_id;
  • SELECT setup_risk_type_id, name FROM amw_setup_risk_types_vl WHERE sysdate BETWEEN start_date AND NVL(end_date, sysdate + 1);

Because the view is documented as not implemented in this database, run a dictionary check (for example, a query against ALL_VIEWS) before relying on it in custom code, and confirm whether Internal Controls Manager setup is active in the target environment.