Search Results amw_risk_ctrl_interface_n1

Overview

AMW.AMW_RISK_CTRL_INTERFACE is an open interface table in the Oracle E-Business Suite governance, risk, and compliance (GRC) module, owned by the AMW schema. Its documented purpose is to serve as the staging area for Web ADI (Application Desktop Integrator) uploads of Risk and Control records. Rather than acting as an analytical fact or reference entity, the table functions as a transient landing zone: rows are inserted through the Web ADI spreadsheet interface, validated, processed by a concurrent program into the base Risk and Control tables, and then purged or flagged by status.

The table resides in the APPS_TS_INTERFACE tablespace, which is standard for EBS interface objects, and is classified with PCT Free 10. The metadata assigns a heuristic Data Vault classification of "standalone," meaning the table does not participate in an explicit hub-link-satellite network in the mined FK structure. As a modeling suggestion, it is more accurately treated as a landing/satellite staging structure keyed by a surrogate identifier, with a single documented foreign key to AMW_PROCESS_OBJECTIVES_B.

Because it is an interface table, its lifecycle is short-lived and its contents are not authoritative. Downstream validation writes an ERROR_FLAG, an INTERFACE_STATUS, and a PROCESS_FLAG, enabling retry logic and error reporting before the interface row is transferred to the permanent Risk and Control repositories.

Key Information Stored

The table is extremely wide, with 208 documented columns, reflecting the many descriptive flexfield attributes and array-style repeating segments that the Web ADI upload template supports. The following columns are the most significant for identification, processing, and reporting:

• RISK_CONTROL_INTERFACE_ID — surrogate primary key, enforced by unique index AMW_RISK_CTRL_INTERFACE_U1. This is the only documented unique business-key candidate and is the identifier used for row-level row selection during processing.
• BATCH_ID — groups interface rows from a single Web ADI upload; indexed nonuniquely by AMW_RISK_CTRL_INTERFACE_N1 together with CREATED_BY, which supports batch isolation and user-level reporting.
• CONTROL_ATTRIBUTE_CATEGORY — the descriptive flexfield structure-defining column for the Control DFF; the value determines which CONTROL_ATTRIBUTE1 through CONTROL_ATTRIBUTE15 segments are contextually valid.
• CONTROL_ATTRIBUTE1 … CONTROL_ATTRIBUTE15 — the Control descriptive flexfield segments, each VARCHAR2(150), populated according to the category selected.
• RISK_ATTRIBUTE_CATEGORY and RISK_ATTRIBUTE1 … RISK_ATTRIBUTE15 — the equivalent descriptive flexfield structure-defining column and segments for the Risk side of the interface record.
• CONTROL_NAME, CONTROL_DESCRIPTION, CONTROL_TYPE_CODE, CONTROL_APPROVAL_STATUS_CODE — core Control business attributes carried on the interface.
• RISK_NAME, RISK_DESCRIPTION, RISK_TYPE_CODE, RISK_LIKELIHOOD_CODE, RISK_IMPACT_CODE, RISK_APPROVAL_STATUS_CODE — core Risk business attributes.
• PROCESS_OBJECTIVE_ID, PROCESS_OBJECTIVE_NAME, PROCESS_ID, PARENT_PROCESS_ID — links the imported Risk/Control to the Process Objective and Process hierarchy; PROCESS_OBJECTIVE_ID is the documented foreign key target.
• ERROR_FLAG, INTERFACE_STATUS, PROCESS_FLAG — validation and lifecycle control columns that drive retry and purge logic.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard EBS Who columns, used for batch ownership and audit.

Common Use Cases and Queries

Typical scenarios center on validating and reconciling Web ADI uploads before or after transfer to the base tables.

• Identify rows for a specific upload batch:

  SELECT RISK_CONTROL_INTERFACE_ID, CONTROL_NAME, RISK_NAME, INTERFACE_STATUS
  FROM   AMW.AMW_RISK_CTRL_INTERFACE
  WHERE  BATCH_ID = :batch_id;

• Report failed validation rows: filter on ERROR_FLAG = 'Y' or INTERFACE_STATUS not equal to the processed status, then inspect the CONTROL_APPROVAL_STATUS_CODE and RISK_APPROVAL_STATUS_CODE.
• Inspect descriptive flexfield population by category:

  SELECT CONTROL_ATTRIBUTE_CATEGORY, COUNT(*)
  FROM   AMW.AMW_RISK_CTRL_INTERFACE
  GROUP  BY CONTROL_ATTRIBUTE_CATEGORY;

• Join to the process objective hierarchy to confirm the imported Risk/Control is attached to the correct objective and process.
• Purge/staging housekeeping: delete processed rows by BATCH_ID after the concurrent program completes, since no archival requirement applies to an interface table.

Related Objects

• AMW.AMW_PROCESS_OBJECTIVES_B — referenced by the documented foreign key AMW_RISK_CTRL_INTERFACE.PROCESS_OBJECTIVE_ID, joining the interface row to its Process Objective.
• AMW.AMW_RISK_CTRL_INTERFACE_U1 — unique index on RISK_CONTROL_INTERFACE_ID, enforcing the surrogate primary key.
• AMW.AMW_RISK_CTRL_INTERFACE_N1 — nonunique composite index on BATCH_ID and CREATED_BY, supporting batch and user filtering.
• The AMW Risk and Control base tables — the destination repositories populated by the interface processing concurrent program.
• The Web ADI upload template and its concurrent processor — the inbound mechanism and the program that reads, validates, and transfers rows from this table.
• FND Flexfield definitions — provide the structure and segment definitions associated with CONTROL_ATTRIBUTE_CATEGORY and RISK_ATTRIBUTE_CATEGORY.