Search Results risk_rev_num

Overview

AMW.AMW_RISKS_B is the base table within the Oracle E-Business Suite (EBS) Enterprise Tax, Risk, and Compliance Management (ETRM) module that stores the master definition of a risk record. It resides in the AMW schema and is registered as FND Design Data object AMW.AMW_RISKS_B, with a status of VALID in both the 12.1.1 and 12.2.2 releases. As the designation "risk base table" implies, this object holds the language-independent, revision-controlled core attributes of a risk, while translatable text is deferred to a companion table. In a Data Vault modeling context, the table exhibits hub-leaning behavior: it anchors a stable RISK_REV_ID business key and is referenced by several downstream link and satellite-style objects, so it can reasonably be treated as a hub for risk revisions. The physical storage is allocated in the APPS_TS_TX_DATA tablespace with a PCT FREE of 10, and the unique index AMW_RISKS_B_U1 is placed in APPS_TS_TX_IDX.

Key Information Stored

The table contains 38 documented columns. The most significant include:

• RISK_REV_ID — the surrogate primary key (AMW_RISKS_B_PK) and the column enforced as unique through AMW_RISKS_B_U1, making it the principal business-key candidate for joins.
• RISK_ID — the logical risk identifier, distinct from the revision-level key.
• RISK_IMPACT — a VARCHAR2(30) column capturing the assessed impact of the risk; this is the field most commonly returned when users search on "risk_impact".
• LIKELIHOOD — a VARCHAR2(30) column storing the probability rating associated with the risk.
• RISK_TYPE — a VARCHAR2(30) classification column defining the category of risk.
• APPROVAL_STATUS and APPROVAL_DATE — the workflow approval state and timestamp of the risk record.
• RISK_REV_NUM, LATEST_REVISION_FLAG, and CURR_APPROVED_FLAG — revision management and currency indicators.
• MATERIAL and CLASSIFICATION — supplemental risk attributes.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the descriptive flexfield structure and its fifteen segments, each VARCHAR2(150).
• SECURITY_GROUP_ID — used in hosted environments and constrained by a foreign key to FND_SECURITY_GROUPS.
• OBJECT_VERSION_NUMBER — supports optimistic locking, which is essential for concurrent updates in 12.1.1 and 12.2.2.
• REQUESTOR_ID and ORIG_SYSTEM_REFERENCE — origin and ownership tracking.
• Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and END_DATE for effective-dating.

Common Use Cases and Queries

Typical usage centers on risk registers, impact-likelihood assessments, and approval reporting. A frequent query pattern retrieves the current approved revision:

SELECT r.RISK_ID, r.RISK_IMPACT, r.LIKELIHOOD, r.RISK_TYPE
FROM AMW.AMW_RISKS_B r
WHERE r.CURR_APPROVED_FLAG = 'Y' AND r.LATEST_REVISION_FLAG = 'Y';

To obtain the human-readable name of a risk, join to the translation table: AMW_RISKS_TL tl ON tl.RISK_REV_ID = r.RISK_REV_ID. For impact-scoring analyses, group by RISK_IMPACT or LIKELIHOOD. Because RISK_IMPACT and LIKELIHOOD are VARCHAR2(30) rather than numeric, reporting layers frequently map these codes to a lookup or value set before aggregation. The descriptive flexfield columns allow client-specific extensions to be surfaced in the same query without altering the base schema.

Related Objects

AMW_RISKS_B participates in a hub-leaning relationship set. The most significant related objects are:

• AMW_RISKS_TL — references RISK_REV_ID and supplies translated risk text.
• AMW_FIN_ITEM_ACC_RISK — links financial item accounts to a risk via RISK_REV_ID.
• RCI_ORG_CERT_RISKS_F — the organization certification risk fact view/table, joined on RISK_REV_ID.
• AMW_RISK_ASSOCIATIONS — associates risks with other entities through RISK_REV_ID.
• AMW_RISK_TYPE — resolves risk type definitions against RISK_REV_ID.
• FND_SECURITY_GROUPS — the referenced parent of SECURITY_GROUP_ID for hosted deployments.

These relationships confirm the table as the central anchor for risk-related certification, association, and financial mapping data across the ETRM data model.