Search Results amw_rcm_org_interface

Overview

AMW_RCM_ORG_INTERFACE is a staging and interface table in the Oracle E-Business Suite Internal Controls Manager (AMW) module. It is owned by the AMW schema and holds records uploaded through WebADI for the purpose of creating or updating risks and controls for an organization. In this capacity, the table acts as an inbound staging area: rows are loaded via the WebADI spreadsheet interface, validated by concurrent programs, and then consumed to create or revise the corresponding production risk and control records in the Internal Controls Manager data model. The table is therefore not a master data table but a transient integration artifact, and its contents are typically purged or retained only for audit reference after successful processing.

The 172-column structure reflects the breadth of the risk-and-control template used in the WebADI upload, encompassing process details, risk attributes, control attributes, and repeating arrays for control objectives, assertions, components, and risk types. From a heuristic Data Vault modeling perspective, the table can be treated as a standalone satellite — it carries descriptive, load-time attributes keyed to a single surrogate identifier — rather than as a hub or link, since no foreign key relationships were mined from the documented schema.

Key Information Stored

The primary key is RCM_ORG_INTERFACE_ID, enforced through the AMW_RCM_ORG_INTERFACE_PK constraint and also supported by the unique index AMW_RCM_ORG_INTERFACE_U1. This surrogate key is the only documented business-key candidate; no natural-key unique constraint is defined, meaning row identity is purely technical. BATCH_ID groups records loaded together in a single WebADI submission, enabling set-level tracking and reprocessing.

• Organizational context: ORGANIZATION_ID, REQUESTOR_ID, and BATCH_ID identify the operating unit, the submitter, and the upload batch.
• Processing state: INTERFACE_STATUS, PROCESS_FLAG, ERROR_FLAG, and PROCESS_NAME drive the validation and consumption cycle performed by AMW concurrent programs.
• Process attributes: PROCESS_NAME, PROCESS_CODE, PROCESS_ID, PROCESS_OBJECTIVE_NAME, and PROCESS_OBJ_DESCRIPTION carry the business process hierarchy.
• Risk attributes: RISK_NAME, RISK_DESCRIPTION, RISK_IMPACT_CODE, RISK_LIKELIHOOD_CODE, RISK_APPROVAL_STATUS_CODE, RISK_APPROVAL_DATE, RISK_CLASSIFICATION, and REVISE_RISK_FLAG.
• Control attributes: CONTROL_NAME, CONTROL_DESCRIPTION, CONTROL_TYPE_CODE, CONTROL_AUTOMATION_TYPE_CODE, CONTROL_APPROVAL_STATUS_CODE, CONTROL_LOCATION_CODE, PREVENTIVE_CONTROL, DETECTIVE_CONTROL, DISCLOSURE_CONTROL, KEY_MITIGATING, DESIGN_EFFECTIVENESS, and OP_EFFECTIVENESS.
• Repeating arrays: CONTROL_OBJ1–30, CONTROL_ASSERT1–30, CONTROL_COMP1–30, and RISK_TYPE1–30 store multi-value selections for objectives, assertions, components, and risk types.
• Audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE.

Common Use Cases and Queries

Typical uses include monitoring the status of WebADI uploads, diagnosing failed rows before they reach production tables, and reconciling batch volumes for audit purposes. A common pattern is to filter by batch and processing state:

• SELECT RCM_ORG_INTERFACE_ID, BATCH_ID, RISK_NAME, CONTROL_NAME, INTERFACE_STATUS, ERROR_FLAG FROM AMW.AMW_RCM_ORG_INTERFACE WHERE BATCH_ID = :batch_id;
• SELECT BATCH_ID, COUNT(*) FROM AMW.AMW_RCM_ORG_INTERFACE WHERE ERROR_FLAG = 'Y' GROUP BY BATCH_ID;

Reporting queries frequently join to the requestor and organization identifiers to attribute uploads to a user or operating unit, and to the approval status columns to gauge pending risk or control approvals within an upload batch.

Related Objects

The documented metadata records this table as standalone, with no mined foreign keys; its principal relationships are logical rather than declarative. The processing programs that consume it reference ORGANIZATION_ID against HR_OPERATING_UNITS, REQUESTOR_ID against FND_USER, and BATCH_ID and PROCESS_ID against the corresponding Internal Controls Manager production objects. Values staged in RISK_NAME, RISK_DESCRIPTION, CONTROL_NAME, and CONTROL_DESCRIPTION ultimately populate the AMW risk and control master tables after validation. Because the table is consumed by AMW WebADI and concurrent processing logic rather than by referential joins, dependency analysis should focus on the AMW interface and processing packages that select from and update these rows.