Search Results amw_ap_steps_b_pk

Overview

AMW_AP_STEPS_B is a base table in the AMW (Internal Controls Manager) product module of Oracle E-Business Suite, present in both release 12.1.1 and 12.2.2 under the AMW schema. The table stores information about the audit steps associated with audit procedures. Each row represents a discrete step that belongs to a parent audit procedure, giving the Internal Controls Manager the granularity it needs to model how a control test or audit procedure is actually executed and sampled.

From a Data Vault modeling perspective, the heuristic classification for this table is standalone. Mined from its foreign key structure, it does not participate in a classic hub-and-satellite or link topology; it behaves as an independent entity keyed by its own surrogate identifier. Modelers should treat it as a self-contained detail entity rather than a dependent child in a Data Vault sense, even though it is functionally dependent on an audit procedure at the application level.

Key Information Stored

The table is defined with 32 documented columns in the ETRM 12.1.1 physical schema. The most significant are summarized below.

• AP_STEP_ID — surrogate primary key, enforced by the AMW_AP_STEPS_B_PK constraint and additionally by the unique index AMW_AP_STEPS_B_U1. This is the deployment's genuine business-key candidate and the value referenced by downstream execution rows.
• AUDIT_PROCEDURE_ID — identifies the parent audit procedure to which the step belongs, establishing the logical parent-child linkage.
• SEQNUM and CSEQNUM — ordering attributes that control the sequence in which steps are applied within a procedure.
• SAMPLESIZE — the number of items to be sampled or tested when the step is executed.
• FROM_REV_NUM and TO_REV_NUM — revision-range bounds that determine which procedure revisions the step is valid for.
• ORIG_SYSTEM_REFERENCE and REQUESTOR_ID — traceability and ownership attributes supporting migration and accountability.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, providing multi-org and security-group isolation.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF/BC4J persistence layer.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard who-column audit trail.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the conventional Oracle EBS descriptive flexfield (DFF) column set for extensible attributes.

The surrogate key AP_STEP_ID is distinct from the business-key candidates surfaced through the unique index; in this table the two coincide, as the unique index covers the primary key column itself.

Common Use Cases and Queries

Typical reporting on this table centers on reconstructing the step structure of an audit procedure and measuring the sample volumes assigned to each step. A representative query joins the steps to their executions through the shared AP_STEP_ID column:

• List steps for a procedure, ordered by sequence: SELECT ap_step_id, seqnum, samplesize FROM amw.amw_ap_steps_b WHERE audit_procedure_id = :p_proc_id ORDER BY seqnum;
• Reconcile steps against executed results: SELECT s.ap_step_id, s.seqnum, e.* FROM amw.amw_ap_steps_b s, amw.amw_ap_executions e WHERE s.ap_step_id = e.ap_step_id;
• Security-scoped extraction for a specific operating unit: filter on SECURITY_GROUP_ID after joining FND_SECURITY_GROUPS.
• DFF-driven reporting: query ATTRIBUTE_CATEGORY and the relevant ATTRIBUTEn columns to surface client-specific extensions.
• Audit-trail and change analysis: use LAST_UPDATE_DATE, LAST_UPDATED_BY, and OBJECT_VERSION_NUMBER to detect modifications and concurrent updates.

Related Objects

• AMW_AP_EXECUTIONS — references this table through AP_EXECUTIONS.AP_STEP_ID → AMW_AP_STEPS_B.AP_STEP_ID; the primary downstream consumer of step definitions.
• FND_SECURITY_GROUPS — referenced by AMW_AP_STEPS_B.SECURITY_GROUP_ID, governing row-level security visibility across operating units.
• AMW_AP_STEPS_TL — the translated (TL) companion table that holds language-dependent step text for the base rows stored here.
• The parent audit procedure table in the AMW schema, linked through AUDIT_PROCEDURE_ID, defining the procedural context for each step.
• Standard AMW audit-integrity and internal-control reporting views that aggregate steps and executions for control-test compliance reporting.