Search Results amw_ap_executions




Overview
Explore in AI Chat

Overview

AMW_AP_EXECUTIONS is a transactional table in the AMW (Internal Controls Manager) product of Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. It stores the execution history of Audit Procedures and their individual procedural steps. Each row represents a discrete execution event captured against an Audit Procedure revision and, where applicable, a specific Audit Procedure Step, recording who performed the execution, when it occurred, and its resulting status.

Under the heuristic Data Vault classification mined from the foreign key structure, this table is identified as standalone. In Data Vault modeling terms, this suggests the table behaves more like a transaction or event record than a classic hub, link, or satellite construct, since its foreign keys resolve to multiple parent dimensions without participating in a broader shared-hub network. The classification is advisory only and reflects the mined key topology rather than a normative Oracle design statement.

Key Information Stored

The table contains 20 documented columns. The most significant are:

The unique index AMW_AP_EXECUTIONS_U1 spans AUDIT_PROCEDURE_REV_ID, PK1, PK2, PK3, EXECUTION_TYPE, and AP_STEP_ID, making this set the business-key candidate that governs uniqueness of an execution within the context of a procedure revision and step.

Common Use Cases and Queries

Typical usage centers on audit execution tracking and compliance reporting. A frequent pattern retrieves all executions against a procedure revision:

SELECT execution_id, ap_step_id, executed_on, executed_by, status
FROM   amw.amw_ap_executions
WHERE  audit_procedure_rev_id = :rev_id
ORDER BY executed_on;

To trace step-level completion, join to the step definition: SELECT e.execution_id, e.status FROM amw.amw_ap_executions e, amw.amw_ap_steps_b s WHERE e.ap_step_id = s.ap_step_id AND e.status = 'COMPLETE'. Reporting on execution ownership aggregates EXECUTED_BY, and filtering by SECURITY_GROUP_ID enforces access control consistent with the EBS security model. Because rows are immutable once created (except for audit columns), the table is well suited to historical and trend analysis of control activity.

Related Objects

  • AMW_AUDIT_PROCEDURES_B — joined on AUDIT_PROCEDURE_REV_ID; supplies the procedure revision definition.
  • AMW_AP_STEPS_B — joined on AP_STEP_ID; supplies the step definition.
  • FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID; governs row-level visibility.
  • AMW Internal Controls Manager concurrent programs and audit reports that consume execution history for control monitoring.
  • Standard EBS audit-trail views built over CREATED_BY and LAST_UPDATED_BY against FND_USER.