Search Results amw_assess_procedures_b




Overview
Explore in AI Chat

Overview

AMW_ASSESS_PROCEDURES_B is a core configuration and definition table within the Oracle E-Business Suite Internal Controls Manager (AMW) module. It holds information about assessment procedures — the reusable, versioned templates or definitions that describe how a specific control or compliance assessment is to be performed, scored, and documented. In the Internal Controls Manager workflow, procedures defined here are attached to assessments and controls, and they govern the steps executed during an assessment cycle.

The table resides in the AMW schema and is present in both Oracle EBS 12.1.1 and 12.2.2. Its documented ETRM structure contains 25 columns, with ASSESS_PROCEDURE_ID serving as the single-column primary key (AMW_ASSESS_PROCEDURES_B_PK). The _B suffix follows the standard EBS convention for a base (non-translated) entity table; translated or descriptive attributes are typically maintained by companion tables in the same product family.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign-key structure is standalone. This suggests the table functions as an independent hub-like record of the assessment procedure entity, with dependent detail (steps and associations) held in separate child tables rather than being self-referencing.

Key Information Stored

The most significant attributes fall into three groups — identity, effective-dating, and auditing/extension.

  • ASSESS_PROCEDURE_ID — the surrogate primary key that uniquely identifies each assessment procedure definition. It is the column referenced by all child tables.
  • START_DATE and END_DATE — effective-dating columns that delimit the active validity window of the procedure definition, supporting date-tracked or versioned procedure records.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN — the standard EBS WHO-column audit set that records who created and last modified the row and when.
  • OBJECT_VERSION_NUMBER — the optimistic locking column used by the Oracle Application Framework (OAF) and concurrent update protection.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the 15 flexfield-style descriptive columns reserved for extensibility and customer-specific or release-specific data.

The metadata documents only ASSESS_PROCEDURE_ID as a unique index; additional business-key candidates are not enumerated in the ETRM extract, so procedure names and codes are presumed to reside in related descriptive or translation tables rather than in this base table.

Common Use Cases and Queries

Typical use cases include auditing which assessment procedures are currently active, tracing which procedures are linked to assessment steps or associations, and reporting on procedure definition history. A standard query pattern joins the base table to its child tables on ASSESS_PROCEDURE_ID:

  • Selecting active procedures: filter on START_DATE <= SYSDATE and (END_DATE IS NULL OR END_DATE >= SYSDATE).
  • Audit reporting: order by LAST_UPDATE_DATE to identify recently changed procedure definitions and the responsible user via LAST_UPDATED_BY.
  • Impact analysis: join to AMW_ASSESS_PROCEDURE_STEPS_B and AMW_ASSESS_PROCEDURE_ASSOCS to find all steps and associations referencing a given procedure.
  • Extensibility reporting: query ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 where custom attributes have been populated.

Related Objects

The following objects reference or depend on AMW_ASSESS_PROCEDURES_B through the documented ASSESS_PROCEDURE_ID foreign key:

  • AMW_ASSESS_PROCEDURE_STEPS_B — child table storing the ordered steps belonging to each assessment procedure (join on ASSESS_PROCEDURE_ID).
  • AMW_ASSESS_PROCEDURE_ASSOCS — association table linking assessment procedures to controls, assessments, or other IM objects (join on ASSESS_PROCEDURE_ID).
  • AMW_ASSESS_PROCEDURES_B_PK — the primary key constraint enforcing uniqueness of ASSESS_PROCEDURE_ID.