Search Results amw_rcm_org_interface_u1

Overview

AMW.AMW_RCM_ORG_INTERFACE is a WebADI interface table in the Oracle E-Business Suite Risk and Control Management (RCM) module, part of the Applications Management (AMW) product family. The table exists in Oracle EBS 12.1.1 and 12.2.2 with status VALID, and is documented in FND Design Data under AMW.AMW_RCM_ORG_INTERFACE. Its stated purpose is to support WebADI uploads of risks and controls for an organization, meaning it functions as a staging area through which spreadsheet-based mass maintenance is passed before validation and posting to the base RCM risk and control tables. The table resides in the APPS_TS_INTERFACE tablespace with a PCT Free of 10, a configuration typical of interface objects in EBS that are periodically purged after concurrent program processing. No foreign key relationships are documented, and the heuristic Data Vault classification is therefore standalone; from a modeling standpoint it is best treated as a persistent staging satellite rather than a hub or link, since its key is a system-generated identifier rather than a natural business key.

Key Information Stored

The table documents 172 columns, of which the metadata names the primary structural and descriptive attributes. The surrogate primary key is RCM_ORG_INTERFACE_ID, defined by primary key constraint AMW_RCM_ORG_INTERFACE_PK and enforced additionally by the unique index AMW_RCM_ORG_INTERFACE_U1 on the same column. BATCH_ID is the principal business-key candidate for grouping a single WebADI upload; the nonunique index AMW_RCM_ORG_INTERFACE_N1 on (BATCH_ID, CREATED_BY) exists to support retrieval of a batch by its originating user. The most operationally significant columns include CONTROL_APPLICATION_ID, which identifies the control application reference and is the column users most frequently search on; CONTROL_NAME, CONTROL_DESCRIPTION, CONTROL_TYPE_CODE, CONTROL_LOCATION_CODE, CONTROL_SOURCE, CONTROL_SOURCE_TYPE, and CONTROL_AUTOMATION_TYPE_CODE, which describe the control being uploaded; RISK_NAME, RISK_DESCRIPTION, RISK_IMPACT_CODE, RISK_LIKELIHOOD_CODE, RISK_APPROVAL_STATUS_CODE, and RISK_APPROVAL_DATE, which describe the associated risk; and the processing columns INTERFACE_STATUS, ERROR_FLAG, PROCESS_FLAG, PROCESS_NAME, and PROCESS_CODE, which govern concurrent request selection and error reporting. PROCESS_ID and REQUESTOR_ID tie the row to the originating process and the requesting party. Standard Who columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) are present, and ORGANIZATION_ID scopes the row to a specific organization. The remaining columns comprise repeating CONTROL_OBJ, CONTROL_ASSERT, CONTROL_COMP, and RISK_TYPE groups plus descriptive attributes such as MATERIAL, PREVENTIVE_CONTROL, DETECTIVE_CONTROL, and DISCLOSURE_CONTROL.

Common Use Cases and Queries

The dominant use case is monitoring and troubleshooting WebADI risk and control uploads. A typical query retrieves all rows awaiting processing for a batch:

• SELECT RCM_ORG_INTERFACE_ID, CONTROL_NAME, RISK_NAME, ERROR_FLAG, INTERFACE_STATUS FROM AMW.AMW_RCM_ORG_INTERFACE WHERE BATCH_ID = :p_batch_id AND PROCESS_FLAG = 'N';
• SELECT BATCH_ID, CREATED_BY, COUNT(*) FROM AMW.AMW_RCM_ORG_INTERFACE WHERE ERROR_FLAG = 'Y' GROUP BY BATCH_ID, CREATED_BY;
• SELECT RCM_ORG_INTERFACE_ID, CONTROL_APPLICATION_ID, CONTROL_NAME FROM AMW.AMW_RCM_ORG_INTERFACE WHERE CONTROL_APPLICATION_ID = :p_control_application_id;

These patterns support reconciliation of upload counts against the target RCM tables, identification of rejected rows before purge, and audit-style reporting on who uploaded which controls for a given organization. Because the table sits in APPS_TS_INTERFACE, purge and archive strategies should be aligned with the concurrent program that consumes it.

Related Objects

The metadata records no foreign keys, so relationships are functional rather than declarative. The most significant associated objects are the base RCM risk and control tables into which validated rows are posted, referenced primarily through CONTROL_APPLICATION_ID and ORGANIZATION_ID; the concurrent program and its execution records that drive processing, linked via PROCESS_ID, PROCESS_NAME, and PROCESS_CODE; the FND standard Who columns that relate the row to FND_USER through CREATED_BY, LAST_UPDATED_BY, and REQUESTOR_ID; and the WebADI upload definitions that generate the batch content keyed by BATCH_ID. Reporting on this table is normally joined to HR organizations on ORGANIZATION_ID and to the error log surfaced through INTERFACE_STATUS and ERROR_FLAG.