Search Results amw_setup_risk_types_b




Overview
Explore in AI Chat

Overview

The AMW_SETUP_RISK_TYPES_B table is a foundational setup entity within the Oracle E-Business Suite Internal Controls Manager (AMW) module. It stores the master definitions of risk types that are catalogued and managed by an organization's internal controls and risk management function. Each row represents a discrete, version-tracked risk type that can be assigned to assessments, control evaluations, and audit activities throughout the AMW product suite.

The table resides in the AMW schema and is present in both Oracle EBS 12.1.1 and 12.2.2. It is a multi-org-secured object, as evidenced by the presence of the SECURITY_GROUP_ID foreign key referencing FND_SECURITY_GROUPS, which governs record-level access based on the security model in force.

From a data modeling perspective, the mined FK structure classifies this table as a standalone object — effectively a hub candidate. It holds the canonical list of risk type definitions, with no inbound foreign keys from other tables documented, so it functions as a reference or master dimension rather than as a transactional or linking entity.

Key Information Stored

The table comprises 13 documented columns. The most significant are:

  • SETUP_RISK_TYPE_ID — The surrogate primary key, enforced by the constraint AMW_SETUP_RISK_TYPES_B_PK. Uniquely identifies each risk type record.
  • RISK_TYPE_CODE — The business-facing code or short name for the risk type. This is the primary business-key candidate and is typically the value users select when classifying a risk.
  • PARENT_SETUP_RISK_TYPE_ID — A self-referencing identifier enabling a hierarchical (parent-child) arrangement of risk types, supporting nested risk taxonomies.
  • START_DATE and END_DATE — Define the effective date range during which the risk type is active and usable. Records outside this window are considered expired.
  • SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS; controls which security group owns and can access the record.
  • TAG — A free-form attribute used for supplementary classification or grouping.
  • OBJECT_VERSION_NUMBER — Supports optimistic locking and concurrent-update control.

The remaining columns are standard WHO audit fields: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. These supplement — but do not define — the entity.

Common Use Cases and Queries

Typical uses of this table include populating risk-type lookups in AMW configuration screens, building risk classification hierarchies for reporting, and validating risk-type assignments during assessment processing.

Retrieve all currently active risk types for a security group:

SELECT setup_risk_type_id, risk_type_code, parent_setup_risk_type_id
FROM amw.amw_setup_risk_types_b
WHERE security_group_id = :p_security_group_id
AND TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, SYSDATE);

Traverse the hierarchy to locate child risk types under a given parent:

SELECT b.risk_type_code, b.setup_risk_type_id
FROM amw.amw_setup_risk_types_b b
WHERE b.parent_setup_risk_type_id = :p_parent_id;

These patterns are commonly embedded in PL/SQL validation routines, concurrent programs that extract risk catalogs, and BI Publisher reports presenting risk taxonomy structures.

Related Objects

The most significant related objects include:

  • FND_SECURITY_GROUPS — Joined via AMW_SETUP_RISK_TYPES_B.SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID; governs record-level security.
  • AMW_SETUP_RISK_TYPES_TL — The translation table providing language-specific risk type names and descriptions, joined by SETUP_RISK_TYPE_ID.
  • AMW_RISKS_B / AMW_RISKS — Risk records that reference a risk type to classify the nature of the identified risk.
  • AMW_ASSESSMENTS_B — Assessment definitions that may be scoped or filtered by risk type.
  • AMW_SETUP_RISK_TYPES_B (self-join) — Used to resolve parent-child hierarchy through PARENT_SETUP_RISK_TYPE_ID.

Implementers extending AMW should treat this table as a controlled reference source and preserve the integrity of SETUP_RISK_TYPE_ID and RISK_TYPE_CODE when integrating with downstream risk and control processes.