Results for “amw_control_assertions”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AMW_CONTROL_ASSERTIONS is a transaction table within the Oracle E-Business Suite Internal Controls Manager (AMW) module. Its documented purpose is to store the relations between controls and assertions — that is, the mapping that associates a specific control definition with the financial statement assertion (for example, existence, completeness, valuation, rights and obligations, or presentation and disclosure) that the control is designed to address. This relationship is central to the control-testing and certification workflow that AMW supported in early 12.1.1 environments.

AMW is flagged as obsolete in later releases, and the ETRM metadata explicitly notes that the object is "Not implemented in this database" in the documented instance. In Oracle EBS 12.2.2, the Internal Controls Manager functionality was superseded by the GRC (Governance, Risk, and Compliance) product family, so AMW_CONTROL_ASSERTIONS is generally encountered only in 12.1.1 or legacy data-migration contexts. When present, its heuristic Data Vault classification, mined from the foreign-key structure, is satellite-leaning: the table appears to hold descriptive state about a parent control revision rather than representing an independent business hub or a pure associative link.

Key Information Stored

The table is defined in the AMW schema with 28 documented columns, and the most significant are the following:

• CONTROL_ASSERTION_ID — the surrogate primary key, enforced by AMW_CONTROL_ASSERTIONS_PK and also carried by the unique index AMW_CONTROL_ASSERTIONS_U1. This is the only documented business-key candidate.
• CONTROL_REV_ID — foreign key to AMW_CONTROLS_B, identifying the control revision to which the assertion relationship applies.
• ASSERTION_CODE — the code denoting the specific assertion associated with the control.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, providing the multi-org / data-security partitioning.
• EFFECTIVE_DATE_FROM and EFFECTIVE_DATE_TO — the date range during which the assertion-to-control relationship is valid.
• OBJECT_VERSION_NUMBER — the optimistic-locking column used by the Oracle Application Framework (OAF) to detect concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard "Who" audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the reserved descriptive-flexfield columns available for client-specific extensions.

Common Use Cases and Queries

The primary use case is reporting the set of assertions covered by each control, typically joined to AMW_CONTROLS_B to obtain the control name and description. A representative query pattern is:

• SELECT ca.control_assertion_id, ca.control_rev_id, ca.assertion_code, cb.control_name FROM amw_control_assertions ca, amw_controls_b cb WHERE ca.control_rev_id = cb.control_rev_id;
• Filtering by security_group_id when extracting data for a specific organization or responsibility.
• Extracting records where effective_date_to is null or in the future to identify currently active assertion mappings.
• Identifying inactive or superseded mappings by comparing effective_date_from and effective_date_to against a reporting date.
• Data-migration and archival routines that move historical AMW control-to-assertion data into GRC or a data-warehouse staging table.

Related Objects

The following objects have a documented dependency on AMW_CONTROL_ASSERTIONS:

• AMW_CONTROLS_B — referenced by AMW_CONTROL_ASSERTIONS.CONTROL_REV_ID; the parent control revision table.
• FND_SECURITY_GROUPS — referenced by AMW_CONTROL_ASSERTIONS.SECURITY_GROUP_ID; supplies row-level security partitioning.
• The AMW assertion lookup and related AMW control-testing tables that consume ASSERTION_CODE for reporting.

Because the module is obsolete and the object may not exist in every database, administrators should verify its presence in the AMW schema before writing dependent queries or integrations.