Search Results amw_control_assertions_pk

Overview

The AMW_CONTROL_ASSERTIONS table is a core data object within the Oracle E-Business Suite (EBS) module AMW - Internal Controls Manager. It functions as a junction or intersection table, establishing and storing the many-to-many relationships between internal controls and business process assertions. This table is fundamental to the Internal Controls Manager's architecture, enabling the linkage of specific control activities to the high-level financial reporting and operational assertions they are designed to validate. Its existence is critical for compliance frameworks, such as Sarbanes-Oxley (SOX), as it documents the control framework's coverage of key risk assertions.

Key Information Stored

The primary data stored in this table consists of foreign key references that map controls to assertions. The key column is the primary key, CONTROL_ASSERTION_ID, which uniquely identifies each relationship record. The most significant foreign key column is CONTROL_REV_ID, which references the AMW_CONTROLS_B table to identify a specific control revision. While the provided metadata does not explicitly list the column for the assertion, standard practice in AMW dictates a corresponding foreign key column (typically ASSERTION_ID) linking to the assertion definition table (e.g., AMW_ASSERTIONS_TL). The table's structure ensures referential integrity and maintains a historical record of which controls are associated with which assertions across different revisions.

Common Use Cases and Queries

This table is primarily queried for control design analysis, audit reporting, and gap assessment. Common scenarios include generating a matrix report of all controls mapped to a specific assertion (e.g., "Completeness" or "Valuation") and identifying controls that are not linked to any assertion, which may indicate a control coverage gap. A typical SQL pattern involves joining AMW_CONTROL_ASSERTIONS with AMW_CONTROLS_B and the assertions table.

• Sample Query (Control-to-Assertion Mapping):
  SELECT acb.control_name, aat.name AS assertion_name
  FROM amw_control_assertions aca,
  amw_controls_b acb,
  amw_assertions_tl aat
  WHERE aca.control_rev_id = acb.control_rev_id
  AND aca.assertion_id = aat.assertion_id
  AND aat.language = USERENV('LANG');
• Use Case: Auditors and control owners use this data to validate that all key financial report assertions have sufficient control coverage documented within the system.

Related Objects

The AMW_CONTROL_ASSERTIONS table has direct dependencies with several other key AMW objects. Its primary relationship, as defined by its foreign key, is with the AMW_CONTROLS_B table, which stores the core control definition and revision details. It also has a critical, though not explicitly listed in the snippet, relationship with the assertion master table, likely AMW_ASSERTIONS_B or its translation table AMW_ASSERTIONS_TL. The table is protected by the primary key constraint AMW_CONTROL_ASSERTIONS_PK. As a central relationship table, it is frequently referenced by various Internal Controls Manager reports, user interfaces, and APIs that manage the control-assertion lifecycle.