Search Results process_risk_id

Overview

The AMW.AMW_PROCESS_RISK_CONTROLS table is an Oracle E-Business Suite table owned by the AMW schema, delivered as part of the Application Management Workspace (AMW) and Enterprise Tax/Treasury Risk Management (ETRM) functionality. It is documented as a VALID object registered under FND Design Data AMW.AMW_PROCESS_RISK_CONTROLS, stored in the APPS_TS_TX_DATA tablespace with a 10 percent PCTFREE setting. The object models the association between process-level risks and the internal controls that mitigate them within an enterprise risk management framework.

From a heuristic Data Vault modeling perspective, this object is classified as standalone. That classification is a modeling suggestion only; it implies the table does not behave cleanly as a pure hub, link, or satellite, but instead functions as an associative or reference entity carrying its own surrogate identity. Its structure — a unique surrogate key plus descriptive and flexfield columns — is consistent with a link-style table that resolves a many-to-many relationship between risks and controls while carrying secondary descriptive attributes.

Key Information Stored

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

• PROCESS_RISK_CONTROL_ID — the surrogate primary key, enforced by unique index AMW_PROCESS_RISK_CONTROLS_U1. This is the unique identifier for each risk-to-control association record.
• PROCESS_RISK_ID — the process risk identifier. This is the column the user searched for; it links the control association back to the originating process risk. Note that although the metadata lists this as a business-relevant foreign key candidate, no FK constraint is documented for it in the supplied relationship data.
• CONTROL_ID — the control identifier, documented as referencing CST_REVENUE_COGS_CONTROL. This column establishes which control is being applied to the process risk.
• SECURITY_GROUP_ID — used to scope records in hosted (multi-tenant) environments; documented as referencing FND_SECURITY_GROUPS.
• OBJECT_VERSION_NUMBER — used for optimistic locking during concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard WHO audit columns tracking creation and modification.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — a Descriptive Flexfield (DFF) structure that allows customers to extend the table with site-specific attributes without modifying the base schema.

Two unique index candidates are documented: AMW_PROCESS_RISK_CONTROLS_U1 on PROCESS_RISK_CONTROL_ID (the surrogate primary key) and AMW_PROCESS_RISK_CONTROLS_PK. No separate business-key unique index appears in the metadata, so the surrogate key serves as the sole documented uniqueness guarantee.

Common Use Cases and Queries

Because Oracle explicitly marks this object as Oracle Internal Use Only and unsupported for direct application data access, all queries should be treated as read-only reporting or diagnostic in nature, and never as a substitute for standard Oracle EBS APIs.

A typical lookup resolves all controls attached to a given process risk:

• SELECT process_risk_control_id, process_risk_id, control_id FROM amw.amw_process_risk_controls WHERE process_risk_id = :risk_id;

Risk assessors frequently need the reverse view — identifying which process risks are mitigated by a specific control:

• SELECT process_risk_id, control_id FROM amw.amw_process_risk_controls WHERE control_id = :control_id;

For auditing or harvesting customer flexfield extensions, the DFF columns are queried in combination with attribute_category. Reporting extracts commonly join back to CST_REVENUE_COGS_CONTROL via CONTROL_ID and to FND_SECURITY_GROUPS via SECURITY_GROUP_ID. Concurrency diagnostics may inspect OBJECT_VERSION_NUMBER to detect lock contention in integrated environments.

Related Objects

Based on the documented foreign key and dependency metadata, the following objects are most significant:

• AMW.AMW_PROCESS_RISK_CTRL_AP — references this table via PROCESS_RISK_CONTROL_ID; the primary downstream dependent.
• CST_REVENUE_COGS_CONTROL — referenced by CONTROL_ID, supplying the control master data.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID for hosted security scoping.
• FND Design Data AMW.AMW_PROCESS_RISK_CONTROLS — the registration entry governing DFF and customization metadata.
• The process risk parent table implied by PROCESS_RISK_ID — though no FK is documented, this column logically anchors each record to its process risk.