Search Results risk_rev_id

Overview

The AMW_RISKS_B table is the base data table for storing risk definitions within the Oracle E-Business Suite (EBS) module AMW, or Internal Controls Manager. This module, now marked as obsolete, was designed for managing enterprise risk and compliance frameworks, particularly in relation to financial controls and the Sarbanes-Oxley Act. The table serves as the central repository for core, non-translatable attributes of a risk entity. Each record represents a unique risk definition identified by its primary key, RISK_REV_ID. As a base table, it is designed to be joined with its corresponding translation table, AMW_RISKS_TL, to obtain language-specific names and descriptions.

Key Information Stored

Based on the provided ETRM metadata and standard Oracle EBS table design patterns, the AMW_RISKS_B table contains the core structural and audit information for a risk. The definitive primary key column is RISK_REV_ID, which uniquely identifies each risk revision. While the full column list is not provided, typical columns in such a base table would include CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY for audit trails, and a set of attributes defining the risk's properties. These properties likely include risk codes, categorization identifiers (like risk type or process hierarchy links), status flags (e.g., 'DRAFT', 'APPROVED'), effective dates, and references to owning organizations or risk owners. The metadata explicitly states this table is "Not implemented in this database," indicating it may be a reference object from an earlier version or a stub in certain installations.

Common Use Cases and Queries

The primary use case for querying AMW_RISKS_B is to extract a master list of defined risks for reporting, integration, or data validation purposes. Common queries would join it with the translation table to produce a comprehensible report. A typical pattern would involve selecting active risks with their descriptions in a specific language. For example:

• Basic Risk Listing: SELECT b.RISK_REV_ID, tl.RISK_NAME, tl.DESCRIPTION, b.STATUS_CODE FROM AMW_RISKS_B b, AMW_RISKS_TL tl WHERE b.RISK_REV_ID = tl.RISK_REV_ID AND tl.LANGUAGE = USERENV('LANG');
• Audit Trail Query: Identifying recently modified risks by joining with FND_USER for usernames.
• Integration Feed: Extracting risk identifiers and key attributes for loading into a downstream data warehouse or governance, risk, and compliance (GRC) system.

Related Objects

The most direct and critical related object is the AMW_RISKS_TL table, which holds the translated names and descriptions for the risks defined in AMW_RISKS_B. The foreign key relationship is explicitly documented: AMW_RISKS_TL.RISK_REV_ID references AMW_RISKS_B.RISK_REV_ID. The primary key constraint AMW_RISKS_B_PK enforces uniqueness on the RISK_REV_ID column. Given the module's function, AMW_RISKS_B likely has relationships (direct or indirect) with other AMW tables storing control assessments, process hierarchies, and issue registrations, though these are not detailed in the provided metadata. As the module is obsolete, development or integration with these tables is strongly discouraged in favor of supported alternatives.