Results for “ap_step_samplesize”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The AMW_AP_INTERFACE table is an Audit Procedure Interface table within the Oracle E-Business Suite Internal Controls Manager module (AMW). It stores information about Audit Procedure upload data originating from WebADI, Oracle's desktop integration framework used for bulk data entry through spreadsheets. In the context of Oracle EBS 12.1.1 and 12.2.2, this table functions as a staging and interface area where Audit Procedure records are collected, validated, and processed before being committed to their final destination tables.

Internal Controls Manager supports the documentation, testing, and assessment of internal controls in support of regulatory compliance initiatives such as Sarbanes-Oxley. Audit Procedures represent the specific test steps performed against controls, and this interface table allows users to upload them in volume rather than entering them individually through the application forms. It should be noted that the AMW product is documented as obsolete in the ETRM metadata, and this specific object is marked as not implemented in the reference database, meaning its presence depends on the deployment configuration.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure identifies this table as standalone. This suggests it is best modeled as an independent hub or staging entity rather than as a link or satellite, since no outgoing foreign keys to parent tables were identified. The relationship data confirms that AMW_AUDIT_PROCEDURE_INTERFACE references this table rather than the reverse.

Key Information Stored

The table contains 40 documented columns. The most significant include:

• AP_INTERFACE_ID — The surrogate primary key, enforced by the AMW_AP_INTERFACE_PK constraint. A unique index, AMW_AP_INTERFACE_U1, also exists on this column, making it the documented business-key candidate as well.
• BATCH_ID — Groups records uploaded together in a single WebADI session, enabling batch-level processing and error reconciliation.
• AP_NAME and AP_DESCRIPTION — The name and descriptive text of the audit procedure being uploaded.
• AP_APPROVAL_STATUS_CODE and AP_END_DATE — Approval workflow state and the effective end date of the procedure.
• CONTROL_NAME — Identifies the control to which the audit procedure relates.
• AP_STEP_NAME, AP_STEP_DESCRIPTION, AP_STEP_SAMPLESIZE, and AP_STEP_SEQNUM — Details of the individual test step, including its sequence and sample size.
• REVISE_AP_FLAG — Indicates whether the upload revises an existing procedure.
• PROCESS_FLAG, ERROR_FLAG, and INTERFACE_STATUS — Control columns governing interface processing state and error handling.
• DESIGN_EFFECTIVENESS, OP_EFFECTIVENESS, and CLASSIFICATION — Assessment attributes for the control being tested.
• AP_ATTRIBUTE_CATEGORY through AP_ATTRIBUTE1–15 — The standard EBS descriptive flexfield segment columns.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN — Standard WHO audit columns.

Common Use Cases and Queries

The primary use case is monitoring and troubleshooting WebADI uploads of audit procedures. A typical query identifies records pending processing or flagged in error:

• SELECT batch_id, ap_name, interface_status, error_flag, process_flag FROM amw_ap_interface WHERE process_flag = 'N';
• SELECT batch_id, COUNT(*) FROM amw_ap_interface GROUP BY batch_id HAVING COUNT(*) > 1;

Reporting scenarios include batch reconciliation, error-rate analysis across uploads, and auditing which users submitted procedure changes. Because the table carries WHO columns, trend reports on creation activity are straightforward.

Related Objects

The documented relationship data identifies the following dependencies:

• AMW_AUDIT_PROCEDURE_INTERFACE — References AMW_AP_INTERFACE via AP_INTERFACE_ID, forming the only documented foreign key relationship.
• AMW_AUDIT_PROCEDURE — The resultant destination table for successfully processed procedure records.
• AMW_CONTROL — Supplies control context matched through CONTROL_NAME.
• WebADI integration APIs and concurrent programs that read AMW_AP_INTERFACE and populate downstream audit procedure tables.