Search Results amw_assessment_components




Overview
Explore in AI Chat

Overview

The AMW_ASSESSMENT_COMPONENTS table is a data object within the Oracle E-Business Suite module AMW — Internal Controls Manager. It holds information about assessment components, which represent the individual building blocks evaluated during an internal control assessment. In the Oracle EBS 12.1.1 and 12.2.2 environments, this table is documented as part of the ETRM (E-Business Suite Technical Reference Manual) object inventory but is explicitly flagged as obsolete and "Not implemented in this database." This designation indicates that the object is retained in documentation and legacy reference material for historical completeness, but it is not physically deployed in the current instance. Consequently, it should not be relied upon for active development, customization, or reporting in 12.1.1 or 12.2.2 environments.

The metadata classifies AMW_ASSESSMENT_COMPONENTS heuristically as a "standalone" table in Data Vault terms. Under a Data Vault modeling suggestion, this object would be treated as a hub-like entity because it carries its own surrogate primary key (ASSESSMENT_COMPONENT_ID) and a distinct unique business-key index (AMW_ASSESSMENT_COMPONENTS_U1) on the same column. Its only foreign key links to FND_SECURITY_GROUPS, which is a security construct rather than a core business relationship, reinforcing the standalone classification.

Key Information Stored

The table is documented with 29 physical columns in the AMW owner schema. The most significant columns include:

The distinction between the surrogate primary key and the unique index is noteworthy: in this table the same column serves both purposes, so no separate business-key column exists beyond ASSESSMENT_COMPONENT_ID.

Common Use Cases and Queries

Because the object is documented as obsolete and not implemented, practical use cases are primarily retrospective or analytical. Historical migrations, archive validation, and upgrade-impact assessments may still reference the object when comparing pre-12.1.1 schemas or third-party integrations that expected this structure. A representative query pattern based on the documented columns is:

  • Selecting all components for a given assessment: SELECT ASSESSMENT_COMPONENT_ID, COMPONENT_CODE, OBJECT_TYPE, OBJECT_ID FROM AMW_ASSESSMENT_COMPONENTS WHERE ASSESSMENT_ID = :assessment_id;
  • Retrieving descriptive flexfield detail: SELECT ATTRIBUTE_CATEGORY, ATTRIBUTE1, ATTRIBUTE2 FROM AMW_ASSESSMENT_COMPONENTS WHERE SECURITY_GROUP_ID = :sgid;
  • Auditing recency: SELECT ASSESSMENT_COMPONENT_ID, LAST_UPDATE_DATE, LAST_UPDATED_BY FROM AMW_ASSESSMENT_COMPONENTS ORDER BY LAST_UPDATE_DATE DESC;

Reporting use cases center on reassembling assessment structures for compliance reviews, confirming whether legacy assessments mapped components through COMPONENT_CODE, and reconciling counts against parent assessment records. Any such query should first verify that the table exists in the target instance, since the metadata states it is not implemented.

Related Objects

The following objects are relevant by documented relationship data or by functional proximity within the AMW module:

  • FND_SECURITY_GROUPS — referenced via the documented foreign key AMW_ASSESSMENT_COMPONENTS.SECURITY_GROUP_ID.
  • AMW_ASSESSMENTS — the presumed parent entity linked through ASSESSMENT_ID, grouping components into an assessment.
  • AMW_ASSESSMENT_COMPONENTS_PK — the primary key constraint on ASSESSMENT_COMPONENT_ID.
  • AMW_ASSESSMENT_COMPONENTS_U1 — the unique index on ASSESSMENT_COMPONENT_ID, serving as the business-key candidate.
  • FND_OBJECTS / FND_OBJECT_INSTANCES — likely referenced indirectly by the OBJECT_TYPE and OBJECT_ID columns for polymorphic object resolution.
  • FND_DESCR_FLEX_COLUMN_USAGES — defines the ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 flexfield context for this and similar AMW tables.

Together these relationships frame AMW_ASSESSMENT_COMPONENTS as a security-scoped, DFF-enabled child of an assessment structure, notwithstanding its currently obsolete status in Oracle EBS 12.1.1 and 12.2.2.