Search Results ap_status




Overview
Explore in AI Chat

Overview

AMW.AMW_AUDIT_PROCEDURE_INTERFACE is an Oracle E-Business Suite interface table owned by the AMW schema (the Application Management Workspace / audit management module) and stored in the APPS_TS_TX_DATA tablespace. Its documented purpose is to serve as an interface table for audit task results uploaded through WebADI, the desktop-integrated spreadsheet loader commonly used to bulk-load EBS data. In EBS 12.1.1 and 12.2.2 the AMW schema hosts internal controls, audit procedures, and compliance-related entities, and interface tables such as this one act as a staging area between uploaded spreadsheet data and the validation/import logic that moves records into the permanent audit transaction tables.

From a data modeling perspective, the metadata heuristic classifies this object as standalone, meaning it is not modeled as a strict hub, link, or satellite. As a modeling suggestion, it could reasonably be treated as a satellite-like staging table that carries both descriptive audit attributes (names, descriptions, effectiveness ratings) and foreign-key references to parent audit entities, without a documented surrogate primary key. The table is VALID and exposed with 72 documented columns in the ETRM 12.1.1 physical schema.

Key Information Stored

The row-level identifiers and controlling keys include BATCH_ID (groups an upload set), AP_INTERFACE_ID (the primary interface row identifier), and AP_ASSOCIATION_ID. Business keys that tie a row back to the underlying audit structure are AUDIT_PROCEDURE_ID, AUDIT_PROCEDURE_REV_ID, AUDIT_PROJECT_ID, ORGANIZATION_ID, CONTROL_ID, TASK_ID, and STEP_ID. The column the user searched for, CONTROL_DESCRIPTION (VARCHAR2(4000)), holds the narrative definition of the control under test and sits alongside CONTROL_NAME (VARCHAR2(240)). Related control attributes are CONTROL_OBJECTIVE, CONTROL_OPINION, CONTROL_OPINION_ID, and KEY_CONTROL.

Effectiveness fields DESIGN_EFFECTIVENESS and OP_EFFECTIVENESS (each VARCHAR2(30)) capture the assessment outcome, complemented by summary and detail columns such as CTRL_DESIGN_SUMMARY, CTRL_DESIGN_DESCRIPTION, CTRL_OPERATING_SUMMARY, and CTRL_OPERATING_DESCRIPTION. Task/step execution data is carried in AP_STATUS, STEP_STATUS, AP_EXECUTED_ON, STEP_EXECUTED_ON, AP_EXECUTEDBY_NAME, and STEP_EXECUTEDBY_NAME. Interface-processing control columns include PROCESSED_FLAG, ERROR_FLAG, and INTERFACE_STATUS. Standard WHO audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) and the fifteen ATTRIBUTE flex columns are also present, along with STEPS_ATTACHMENT_URL.

Common Use Cases and Queries

Typical usage centers on monitoring and troubleshooting WebADI uploads of audit results. Query patterns filter on batch and interface status to find rows that failed validation:

  • SELECT BATCH_ID, AP_INTERFACE_ID, CONTROL_NAME, CONTROL_DESCRIPTION, INTERFACE_STATUS, ERROR_FLAG FROM AMW.AMW_AUDIT_PROCEDURE_INTERFACE WHERE PROCESSED_FLAG = 'N' AND ERROR_FLAG = 'Y';
  • Joining to AMW_AP_INTERFACE on AP_INTERFACE_ID to reconcile staged rows with the parent audit procedure interface record.
  • Reporting on DESIGN_EFFECTIVENESS and OP_EFFECTIVENESS by AUDIT_PROJECT_ID to summarize control assessment results.
  • Tracking upload provenance via CREATED_BY and CREATION_DATE for audit trail purposes.

Related Objects

The documented foreign keys define the principal dependencies:

These joins support validation before promotion of staged rows into the audit execution tables, and they anchor reporting that ties uploaded control descriptions and effectiveness ratings back to their governing audit procedure, project, and control definitions.