Search Results amw_assess_procedure_steps_pk

Overview

The table AMW_ASSESS_PROCEDURE_STEPS_B resides in the AMW schema, the database account associated with Oracle Internal Controls Manager (ICM), a GRC-adjacent application that shipped alongside Oracle E-Business Suite releases 12.1.1 and 12.2.2. The documented product classification is AMW - Internal Controls Manager (Obsolete), indicating that the object belongs to a component that Oracle has since desupported and that is not implemented in the reference database from which the ETRM metadata was mined. The table stores information about assessment procedure steps — the individual, sequenced activities that make up an assessment procedure executed during an internal-controls or SOX-compliance testing cycle.

The "AMW" prefix identifies the application module, while the trailing "_B" conforms to the standard EBS convention denoting a base (or "B") table that is typically paired with a translated "_T" counterpart. Its heuristic Data Vault classification, mined from the foreign-key structure, is standalone, meaning it is not strongly integrated into a hub-and-link topology and may be modeled as an independent satellite or reference table rather than as a core hub or link. Every row is uniquely identified by the primary key constraint AMW_ASSESS_PROCEDURE_STEPS_PK, defined on the single column ASSESS_PROCEDURE_STEP_ID.

Key Information Stored

The physical schema documented for ETRM 12.1.1 defines 26 columns. The most significant are:

• ASSESS_PROCEDURE_STEP_ID — the surrogate primary key, sourced from the sequence behind AMW_ASSESS_PROCEDURE_STEPS_PK. This is the only guaranteed-unique identifier and is the column referenced by any child object.
• ASSESS_PROCEDURE_ID — the foreign key to AMW_ASSESS_PROCEDURES_B. This is the de facto business-key candidate that ties each step back to its parent assessment procedure.
• SEQNUM — the ordinal position of the step within the procedure, controlling execution and display order.
• SAMPLESIZE — the number of items or transactions designated for testing at that step, a central quantity in sampling-based control assessment.
• OBJECT_VERSION_NUMBER — the optimistic-locking token used by the EBS framework to detect concurrent row updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard EBS "WHO" audit columns stamped by the application's audit framework.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard descriptive-flexfield block, providing fifteen customer-configurable columns plus a context column for extensibility without schema changes.

No secondary unique index is documented beyond the primary key, so ASSESS_PROCEDURE_ID plus SEQNUM should be treated as a business rule rather than a database-enforced constraint.

Common Use Cases and Queries

Because the object is obsolete and typically absent from production 12.1.1 / 12.2.2 instances, its value today is principally historical, archival, and migration-oriented. Documented scenarios include:

• Reporting the ordered step list for a given procedure: SELECT step_id, seqnum, samplesize FROM amw_assess_procedure_steps_b WHERE assess_procedure_id = :p_id ORDER BY seqnum;
• Auditing who last modified a step, using LAST_UPDATED_BY joined to FND_USER and LAST_UPDATE_DATE as the timestamp.
• Counting steps per procedure to size a testing workload or to verify completeness of an assessment plan.
• Extracting legacy ICM configuration prior to an upgrade or a move to Oracle Advanced Controls / Fusion GRC, mapping ASSESS_PROCEDURE_ID and SEQNUM to the target model.
• Reconciling sample-size totals at the procedure level by aggregating SAMPLESIZE grouped by ASSESS_PROCEDURE_ID.

Queries should always qualify the AMW schema and anticipate that the table may not exist, so existence checks against ALL_TABLES are advisable in generic scripts.

Related Objects

The relationship metadata identifies one documented foreign key and one dependent direction:

• AMW_ASSESS_PROCEDURES_B — the parent table referenced via ASSESS_PROCEDURE_ID; joining the two reconstructs the procedure-to-step hierarchy.
• AMW_ASSESS_PROCEDURES_T — the translated companion of the parent, supplying language-specific procedure names for multilingual reporting.
• AMW_ASSESS_PROCEDURE_STEPS_T — the expected translated counterpart of this table, conventionally keyed on ASSESS_PROCEDURE_STEP_ID plus LANGUAGE.
• FND_USER — joined through CREATED_BY and LAST_UPDATED_BY to resolve user identity.
• FND_APPLICATION / FND_OBJECTS — standard EBS metadata joins for resolving the AMW application and its concurrent or form-based access paths.

Because the classification is standalone, no documented child foreign keys point into this table; downstream dependencies, if any, must be discovered through the broader AMW assessment-result objects rather than through declared constraints.