Search Results executed_on

Overview

AMW.AMW_AP_EXECUTIONS is a transactional table in the Oracle E-Business Suite Audit Management (AMW) application schema. It holds execution records for audit procedures and audit steps, capturing when an audit procedure (AP) or an individual audit step (STEP) was executed, by whom it was performed, the resulting status, and any descriptive work notes. The table operates at the intersection of two parent business objects — audit procedure revisions and audit steps — and therefore serves as the historical execution ledger for the AMW audit workflow.

Under the heuristic Data Vault classification supplied in the metadata, this object is modeled as a standalone table. It carries foreign-key references outward to AMW_AUDIT_PROCEDURES_B, AMW_AP_STEPS_B, and FND_SECURITY_GROUPS, but no documented object references AMW_AP_EXECUTIONS in return. In Data Vault terms, it functions as a satellite-like structure attached to the audit procedure step combination, with the composite unique index capturing an effective business key of AUDIT_PROCEDURE_REV_ID, PK1, PK2, PK3, EXECUTION_TYPE, and AP_STEP_ID. The ETRM dependency extract confirms the object references no other database object directly, reinforcing its leaf position in the dependency chain.

Key Information Stored

Each row represents a single execution instance of an audit procedure or audit step. The most significant columns are:

• EXECUTION_ID — surrogate primary key; execution identifier.
• AUDIT_PROCEDURE_REV_ID — revision identifier of the parent audit procedure; part of the unique business key.
• AP_STEP_ID — identifier of the audit step executed; part of the unique business key.
• EXECUTION_TYPE — values AP (Audit Procedure) or STEP (Audit Step); distinguishes the level of granularity of the execution.
• EXECUTED_ON — the date the procedure or step was executed.
• EXECUTED_BY — identifier of the person who performed the execution, typically an FND_USER reference.
• STATUS — execution status (30 characters), used to track workflow progression.
• WORK_DESC — a 4000-character free-text work description captured at execution time; this is the column most frequently queried by end users looking for execution notes.
• PK1, PK2, PK3 — hold Project, Organization, and Task identifiers respectively, providing the project-accounting context.
• PK4, PK5 — reserved, not used.
• SECURITY_GROUP_ID — used for hosted environments; foreign key to FND_SECURITY_GROUPS.
• OBJECT_VERSION_NUMBER — optimistic locking column.
• Standard WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) support auditing and interface tracking.

The unique index AMW_AP_EXECUTIONS_U1 (AUDIT_PROCEDURE_REV_ID, PK1, PK2, PK3, EXECUTION_TYPE, AP_STEP_ID) is the documented business-key candidate, preventing duplicate execution records for the same audit step within the same project/organization/task context.

Common Use Cases and Queries

Typical reporting on this table centers on audit execution history, execution status tracking, and textual work notes. A common pattern retrieves executions joined to their parent procedures and steps, filtered by project and status:

• Audit execution history by procedure revision — join to AMW_AUDIT_PROCEDURES_B to resolve procedure names.
• Step-level execution reporting — join to AMW_AP_STEPS_B on AP_STEP_ID to report per-step results.
• Work description search — filter on WORK_DESC using UPPER(WORK_DESC) LIKE '%...%' for keyword lookups.
• Status dashboards — GROUP BY STATUS and EXECUTION_TYPE to summarize counts per status.
• Executor productivity — GROUP BY EXECUTED_BY, EXECUTED_ON to analyze throughput.

A representative query follows:

• SELECT e.EXECUTION_ID, e.AUDIT_PROCEDURE_REV_ID, e.AP_STEP_ID, e.EXECUTION_TYPE, e.STATUS, e.EXECUTED_ON, e.EXECUTED_BY, e.WORK_DESC FROM AMW.AMW_AP_EXECUTIONS e WHERE e.EXECUTION_TYPE = 'STEP' AND e.STATUS IS NOT NULL ORDER BY e.EXECUTED_ON DESC;

Related Objects

The table participates in the following documented relationships:

• AMW.AMW_AUDIT_PROCEDURES_B — referenced via AUDIT_PROCEDURE_REV_ID; the parent audit procedure revision.
• AMW.AMW_AP_STEPS_B — referenced via AP_STEP_ID; the parent audit step definition.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; governs multi-organization security in hosted deployments.
• FND_USER — implicit reference from EXECUTED_BY to resolve executor names.

No documented object references AMW_AP_EXECUTIONS, confirming its position as a dependent transaction table within the AMW audit execution model.