Search Results amw_risk_ctrl_interface_pk

Overview

AMW_RISK_CTRL_INTERFACE is a staging table in the AMW (Internal Controls Manager) product module of Oracle EBS, owned by the AMW schema. It serves as the interface table used by Web ADI (Web Applications Desktop Integrator) when uploading Risk and Control records into the application. Rather than writing directly to the production risk and control tables, Web ADI loads incoming spreadsheet data into this interface table, where each row undergoes validation, error flagging, and subsequent processing before being promoted into the base AMW transaction tables. The table is documented in both ETRM 12.1.1 and 12.2.2 with status VALID.

The table carries a wide footprint of 208 columns in the documented 12.1.1 physical schema. Its structure reflects the dual nature of the data it carries: each record combines both Risk attributes and Control attributes in a single staging row, allowing Web ADI to upload a risk and its associated controls together. From a Data Vault modeling perspective, the metadata classifies this object as standalone (no foreign key dependencies mined from the FK structure), which suggests it behaves more like a raw staging hub with no enforced parent relationships rather than a dependent satellite. The Data Vault classification is heuristic and should be treated as a modeling suggestion only.

Key Information Stored

The surrogate primary key is RISK_CONTROL_INTERFACE_ID, enforced through the primary key constraint AMW_RISK_CTRL_INTERFACE_PK and also supported by the unique index AMW_RISK_CTRL_INTERFACE_U1 on the same column. This identifier uniquely distinguishes each interface row; it is a system-generated key rather than a business key.

Among the more significant columns are:

• RISK_CONTROL_INTERFACE_ID — surrogate primary key for each staged row.
• BATCH_ID — groups rows uploaded together in a single Web ADI batch.
• REQUESTOR_ID — identifies the user who submitted the upload.
• INTERFACE_STATUS and ERROR_FLAG — track processing state and validation outcome.
• RISK_NAME, RISK_DESCRIPTION, RISK_TYPE_CODE, RISK_IMPACT_CODE, RISK_LIKELIHOOD_CODE — the core risk attributes being staged.
• CONTROL_NAME, CONTROL_DESCRIPTION, CONTROL_TYPE_CODE, CONTROL_AUTOMATION_TYPE_CODE, CONTROL_APPROVAL_STATUS_CODE — the core control attributes.
• PROCESS_ID and PARENT_PROCESS_ID — tie the staged risk/control to a business process hierarchy.
• PROCESS_NAME and PROCESS_CODE — descriptive process identifiers.
• RISK_ATTRIBUTE_CATEGORY and CONTROL_ATTRIBUTE_CATEGORY — drive the descriptive flexfield context.
• CONTROL_COMP1 through CONTROL_COMP30, plus CONTROL_ATTRIBUTE1 through CONTROL_ATTRIBUTE15 — flexfield segments and component values.
• RISK_TYPE1 through RISK_TYPE30 — repeated risk type slots supporting multi-value risk classification.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard audit columns.

The remaining columns include object references (CONTROL_OBJ1–CONTROL_OBJ30), assertions (CONTROL_ASSERT1–CONTROL_ASSERT30), effectiveness flags, and miscellaneous UOM and classification fields.

Common Use Cases and Queries

The principal use case is monitoring and troubleshooting Web ADI risk/control uploads. Validation personnel query the table to find rows that failed processing, and to review pending batches before they are promoted.

To list failed rows for a batch:

• SELECT RISK_CONTROL_INTERFACE_ID, RISK_NAME, CONTROL_NAME, ERROR_FLAG, INTERFACE_STATUS FROM AMW.AMW_RISK_CTRL_INTERFACE WHERE BATCH_ID = :batch_id AND ERROR_FLAG = 'Y';

To review all rows for a given requestor:

• SELECT RISK_CONTROL_INTERFACE_ID, RISK_NAME, CONTROL_NAME, CREATION_DATE FROM AMW.AMW_RISK_CTRL_INTERFACE WHERE REQUESTOR_ID = :user_id ORDER BY CREATION_DATE DESC;

Reporting queries typically aggregate by INTERFACE_STATUS to gauge upload throughput, or join back to process definitions using PROCESS_ID to confirm the staged records map to valid processes. Because the table is a transient staging area, retention policies normally purge successfully processed rows after promotion.

Related Objects

The metadata records no enforced foreign keys to this table (standalone classification), so related objects are identified by shared business columns and integration flow rather than FK constraints:

• AMW_RISK_CTRL_INTERFACE_PK / AMW_RISK_CTRL_INTERFACE_U1 — the primary key constraint and unique index on RISK_CONTROL_INTERFACE_ID.
• Base AMW risk and control tables — target tables populated when staged rows are promoted from this interface.
• AMW process and subprocess tables — joined via PROCESS_ID and PARENT_PROCESS_ID.
• Web ADI integrator definitions — the upload layout that maps spreadsheet columns to this table's columns.
• FND_USER — referenced via REQUESTOR_ID and CREATED_BY/LAST_UPDATED_BY for user attribution.
• Concurrent request tables (FND_CONCURRENT_REQUESTS) — the Web ADI import job that processes this staging table.

Because the object is proprietary to AMW and Oracle confidential, direct DML against it should be avoided except under Oracle guidance; interface processing is normally driven through the supported Web ADI and concurrent program flows.