Search Results amw_risk_type_u2

Overview

The AMW.AMW_RISK_TYPE table is a reference and classification object within the Oracle E-Business Suite (EBS) Enterprise Treasury and Risk Management (ETRM) module. It stores the risk type associated with each risk, acting as a child entity to the base risk definition held in AMW.AMW_RISKS_B. Because it captures the descriptive attributes of a risk instance, revised under a specific risk revision, the table supports the categorization and enrichment of risk records across the ETRM data model. Its columns are largely made up of a surrogate identifier, business-key attributes, standard "Who" audit columns, and a full descriptive flexfield (DFF) block, which positions it as a flexible classificatory extension to the parent risk record.

From a dimensional modeling perspective, the heuristic Data Vault classification mined from the foreign-key structure is standalone. In practice, AMW_RISK_TYPE behaves as a satellite-like detail table keyed to a risk revision, since it maintains descriptive and descriptive-flexfield context for a given RISK_REV_ID rather than existing as an independent hub or a pure many-to-many link.

Key Information Stored

The table consists of 26 documented columns. The most significant are:

• RISK_TYPE_ID — the surrogate primary key, enforced by AMW_RISK_TYPE_PK and the unique index AMW_RISK_TYPE_U1.
• RISK_REV_ID — the risk revision identifier, a foreign key to AMW.AMW_RISKS_B that anchors each risk-type row to a specific revision.
• RISK_TYPE_CODE — the business-meaningful code describing the risk type (length 30); together with RISK_REV_ID, it forms the unique business key via index AMW_RISK_TYPE_U2.
• ATTRIBUTE_CATEGORY — the descriptive flexfield structure-defining column, identifying which DFF context applies.
• ATTRIBUTE1 through ATTRIBUTE15 — 150-character DFF segments carrying user-defined, client-specific risk attributes.
• SECURITY_GROUP_ID — a foreign key to FND_SECURITY_GROUPS, used to isolate records in hosted or multi-org environments.
• OBJECT_VERSION_NUMBER — the optimistic locking column used to detect concurrent updates.
• LAST_UPDATE_DATE, CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard "Who" audit columns that record insertion and update provenance.

The distinction between the surrogate key (RISK_TYPE_ID) and the business-key candidates (RISK_REV_ID + RISK_TYPE_CODE) is important for integration and de-duplication logic, since downstream ETL frequently maps external codes to the business key rather than the internal identifier.

Common Use Cases and Queries

Typical usage centers on risk reporting, code-to-ID mapping, and DFF-driven analysis. A common query retrieves all risk types for a given revision:

SELECT RISK_TYPE_ID, RISK_REV_ID, RISK_TYPE_CODE
FROM   AMW.AMW_RISK_TYPE
WHERE  RISK_REV_ID = :p_risk_rev_id;

Mapping a business code to its surrogate identifier for integration purposes uses the unique business key:

SELECT RISK_TYPE_ID
FROM   AMW.AMW_RISK_TYPE
WHERE  RISK_REV_ID = :p_risk_rev_id
AND    RISK_TYPE_CODE = :p_code;

Flexfield-based reporting joins the DFF segments and filters by context:

SELECT RISK_TYPE_ID, RISK_TYPE_CODE, ATTRIBUTE_CATEGORY, ATTRIBUTE1
FROM   AMW.AMW_RISK_TYPE
WHERE  ATTRIBUTE_CATEGORY = :p_context;

Auditing and reconciliation queries leverage the "Who" columns and OBJECT_VERSION_NUMBER to detect records modified after a given date or to detect concurrent-update conflicts.

Related Objects

The following objects are the most significant dependencies and references:

• AMW.AMW_RISKS_B — joined on RISK_REV_ID; the parent base risk table that this table extends with risk-type detail.
• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID; governs record visibility in hosted environments.
• AMW_RISK_TYPE_U1 — the unique index on RISK_TYPE_ID, backing the primary key.
• AMW_RISK_TYPE_U2 — the unique index on (RISK_REV_ID, RISK_TYPE_CODE), enforcing the business key.
• AMW_RISK_TYPE_PK — the primary-key constraint on RISK_TYPE_ID.

Collectively these objects define how risk-type information is keyed, secured, and linked to the broader ETRM risk model.