Search Results amw_risk_type_pk

Overview

The AMW_RISK_TYPE table resides in the AMW schema, which is associated with the Oracle Internal Controls Manager (ICM) product family. In the ETRM metadata provided, the product is flagged as Obsolete, and implementation/DBA notes record that the object is not implemented in this database. This means AMW_RISK_TYPE is a legacy or unreleased schema artifact rather than an actively populated operational table in the referenced 12.1.1 / 12.2.2 environments. Its documented purpose is straightforward: it stores the risk type classification for each risk record maintained within the AMW risk management data model.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign-key structure is standalone (neither a hub, link, nor satellite in strict terms). This suggests it is best modeled as an independent reference or detail entity that carries its own surrogate key and points outward to parent keys (risk revision and security group) rather than acting as a junction or dependent satellite. Analysts building a warehouse layer should treat it as a low-cardinality reference dimension tied to a risk revision.

Key Information Stored

Although the documented physical schema lists 26 columns, the most significant business content is concentrated in a small subset:

• RISK_TYPE_ID — the surrogate primary key, enforced by AMW_RISK_TYPE_PK and additionally unique via index AMW_RISK_TYPE_U1.
• RISK_REV_ID — foreign key to AMW_RISKS_B, linking a risk type entry to its parent risk revision. Combined with RISK_TYPE_CODE, it forms the second unique business key (AMW_RISK_TYPE_U2).
• RISK_TYPE_CODE — the human-readable classification code for the risk type; part of the composite business key.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, governing row-level access control and multi-org/virtual-private-database visibility.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle Applications Framework (OAF) to detect concurrent updates.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle flexfield (DFF) descriptor columns for extensible, client-defined risk type attributes.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN, providing standard WHO-column tracking.

The distinction between the surrogate primary key (RISK_TYPE_ID) and the business-key candidate (RISK_REV_ID plus RISK_TYPE_CODE) is important: the surrogate isolates the physical identifier, while the composite unique index reflects the true business meaning — one risk type code per risk revision.

Common Use Cases and Queries

Because the table is documented as not implemented, live queries are unlikely in current 12.1.1 / 12.2.2 instances. Where the object is present (for example, in an upgraded or migrated ICM environment), typical scenarios include resolving risk classifications for a risk revision and enforcing security-filtered reporting. A representative pattern joins the parent risk base table:

• Retrieve all risk types for a given risk revision: SELECT RISK_TYPE_CODE, RISK_TYPE_ID FROM AMW_RISK_TYPE WHERE RISK_REV_ID = :risk_rev_id;
• Security-scoped lookup: filter by SECURITY_GROUP_ID to respect the calling user's accessible security groups.
• Extract flexfield attributes: select ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 for reporting on customized risk type metadata.
• Concurrency check: compare OBJECT_VERSION_NUMBER before issuing an update through OAF.

Reporting use cases center on risk categorization analytics — grouping risks by type code across revisions to support audit and compliance dashboards.

Related Objects

• AMW_RISKS_B — parent entity joined via AMW_RISK_TYPE.RISK_REV_ID = AMW_RISKS_B.RISK_REV_ID.
• FND_SECURITY_GROUPS — referenced through AMW_RISK_TYPE.SECURITY_GROUP_ID for access control.
• AMW_RISK_TYPE_PK / AMW_RISK_TYPE_U1 / AMW_RISK_TYPE_U2 — indexes that define uniqueness and drive lookup performance.
• AMW_* risk tables — the broader ICM risk model that references risk type classifications.
• FND_* WHO columns — standard application framework audit infrastructure underpinning the CREATED_BY and LAST_UPDATED_BY attributes.

Given the obsolete designation, integration efforts should confirm object existence before relying on AMW_RISK_TYPE as a data source.