Results for “amw_risks_b”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AMW_RISKS_B is the base (or "B") table for risk definitions within the Oracle E-Business Suite Internal Controls Manager module, designated by the AMW product code. The ETRM documentation marks this module as obsolete, and the table is labeled "Not implemented in this database" in the source metadata, meaning it may not exist in every environment and is primarily of interest for historical, migration, or reference purposes. Functionally, the table stores the master record for each risk that an organization tracks — its impact, likelihood, type, classification, approval state, and revision lineage — and serves as the anchor to which multilingual descriptions and all downstream risk relationships are attached.

From a modeling perspective, the mined foreign-key structure classifies AMW_RISKS_B as hub-leaning under a Data Vault heuristic. This is a reasonable suggestion: RISK_REV_ID behaves as a stable, unique business key around which several dependent tables (translations and association links) cluster, which is characteristic of a hub entity.

Key Information Stored

The table contains 38 documented columns. The most operationally significant are:

• RISK_REV_ID — the surrogate primary key (AMW_RISKS_B_PK) and also the single unique-index column (AMW_RISKS_B_U1). It links the risk to every dependent object.
• RISK_ID — the logical risk identifier distinct from the revision-level key.
• RISK_REV_NUM — the revision number, supporting versioned risk records.
• RISK_IMPACT and LIKELIHOOD — the core scoring attributes used in risk assessment.
• RISK_TYPE — categorizes the risk for grouping and reporting.
• CLASSIFICATION and MATERIAL — flags/classifications influencing severity and disclosure.
• APPROVAL_STATUS, APPROVAL_DATE, and CURR_APPROVED_FLAG — track the approval workflow state.
• LATEST_REVISION_FLAG — identifies the current active revision.
• REQUESTOR_ID and ORIG_SYSTEM_REFERENCE — capture ownership and source-system traceability.
• SECURITY_GROUP_ID — the foreign key to FND_SECURITY_GROUPS, enforcing row-level access.
• OBJECT_VERSION_NUMBER, CREATION_DATE, LAST_UPDATE_DATE, CREATED_BY, and LAST_UPDATED_BY — standard EBS concurrency and audit columns.
• END_DATE — supports date-effectivity of the risk record.

Fifteen ATTRIBUTE (ATTRIBUTE_CATEGORY through ATTRIBUTE15) are also present as the standard EBS descriptive-flexfield columns.

Common Use Cases and Queries

Typical usage centers on retrieving the current, approved revision of a risk and joining it to its translated description. A common pattern filters on the latest approved revision:

• Reporting all current risks: SELECT * FROM AMW_RISKS_B WHERE LATEST_REVISION_FLAG = 'Y' AND CURR_APPROVED_FLAG = 'Y';
• Joining to translations: SELECT b.RISK_REV_ID, t.NAME, t.DESCRIPTION FROM AMW_RISKS_B b, AMW_RISKS_TL t WHERE b.RISK_REV_ID = t.RISK_REV_ID;
• Grouping by severity for dashboards: aggregate RISK_IMPACT and LIKELIHOOD to build a heat map.
• Audit and lineage: query RISK_REV_NUM and ORIG_SYSTEM_REFERENCE to trace revision history and external origins.
• Security-scoped extracts constrained by SECURITY_GROUP_ID.

Related Objects

AMW_RISKS_B participates in a well-defined set of relationships:

• AMW_RISKS_TL — translation table joining on RISK_REV_ID (this table is itself referenced by AMW_RISKS_TL.RISK_REV_ID).
• FND_SECURITY_GROUPS — referenced by AMW_RISKS_B.SECURITY_GROUP_ID.
• AMW_FIN_ITEM_ACC_RISK — associates financial statement items with risks via RISK_REV_ID.
• AMW_RISK_ASSOCIATIONS — links risks to related entities through RISK_REV_ID.
• AMW_RISK_TYPE — relates risk-type detail on RISK_REV_ID.
• RCI_ORG_CERT_RISKS_F — certification-to-risk association keyed on RISK_REV_ID.

These dependencies confirm AMW_RISKS_B as the central risk hub for the Internal Controls Manager schema.