Search Results process_risk_control_id

Overview

The AMW.AMW_PROCESS_RISK_CONTROLS table belongs to the AMW schema, which supports the Oracle Internal Controls Manager (ICM) product within Oracle E-Business Suite. ICM is used by organizations to document, assess, and monitor internal controls in support of regulatory compliance initiatives such as Sarbanes-Oxley. Within that architecture, tables carrying the AMW prefix generally store the transactional and definitional records that tie business processes to the risks they present and to the controls designed to mitigate those risks.

The ETRM documentation for this object explicitly states that the table is obsolete. This is the single most important fact recorded against it. The object remains marked VALID in the data dictionary, meaning the physical table still exists in the schema, but Oracle no longer describes it as an active part of the product data model. Any functional reliance on it should be treated as unsupported.

From a data modeling perspective, the metadata classifies this object heuristically as standalone, with no downstream dependencies other than a single child table. Under a Data Vault style reading, it would most naturally be treated as a link table, since its business purpose is to associate a process risk with a control. This is offered only as a modeling suggestion; the object is not part of any documented Data Vault implementation.

Key Information Stored

The documented schema for release 12.1.1 contains 26 columns. The most significant are:

• PROCESS_RISK_CONTROL_ID — the surrogate primary key, enforced by AMW_PROCESS_RISK_CONTROLS_PK and backed by a unique index, AMW_PROCESS_RISK_CONTROLS_U1. This single column is both the technical key and the only documented business-key candidate.
• PROCESS_RISK_ID — identifies the process risk being associated. Notably, no foreign key is documented for this column, which is consistent with the object's superseded status.
• CONTROL_ID — identifies the control linked to the risk. A foreign key is documented to CST_REVENUE_COGS_CONTROL, an unusual target for an ICM table.
• SECURITY_GROUP_ID — the multi-org style security grouping, with a documented foreign key to FND_SECURITY_GROUPS.
• OBJECT_VERSION_NUMBER — the standard optimistic locking column used across EBS tables for concurrent update protection.
• The standard WHO audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — capture row provenance.
• The fifteen ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 descriptive flexfield columns provide the standard extensibility slots.

No descriptive columns such as names, descriptions, or dates are documented, reinforcing that the table served purely as an intersection between risk and control records.

Common Use Cases and Queries

Because the table is documented as obsolete, it should not appear in new development, custom concurrent programs, or reporting extracts. Its realistic use cases are legacy and forensic in nature:

• Upgrade and migration analysis. Determining whether historical ICM risk-to-control associations from an earlier release were carried forward into the current ICM data model.
• Data archival. Extracting and preserving the contents before the table is dropped in a future patch or during a schema cleanup.
• Impact assessment. Confirming that no custom code, view, or interface still references the table.

A straightforward extraction pattern joins the relationship to its child table:

SELECT p.PROCESS_RISK_CONTROL_ID, p.PROCESS_RISK_ID, p.CONTROL_ID, p.SECURITY_GROUP_ID
FROM AMW.AMW_PROCESS_RISK_CONTROLS p
WHERE p.SECURITY_GROUP_ID = :security_group_id;

To detect residual dependencies, query the dictionary:

SELECT * FROM DBA_DEPENDENCIES
WHERE REFERENCED_NAME = 'AMW_PROCESS_RISK_CONTROLS';

Related Objects

The documented FK metadata identifies a small dependency set:

• AMW_PROCESS_RISK_CTRL_AP — the only table documented as referencing this object, via PROCESS_RISK_CONTROL_ID. Even this child table carries the "_AP" suffix typical of Oracle Applications obsolete objects.
• CST_REVENUE_COGS_CONTROL — referenced by CONTROL_ID; the target points outside the AMW schema, which is atypical and likely a mapping artifact.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID; the standard EBS security grouping definition.

No AMW views, concurrent programs, or public APIs are documented as depending on this table. Consultants should verify current 12.2.2 dictionaries directly, as the object may have been removed entirely in later releases.