Search Results control_report_id




Overview

AMW_CONTROL_REPORTS is a table that belongs to the AMW product, historically known as Internal Controls Manager, within the Oracle E-Business Suite environment. According to the ETRM metadata and the documentation excerpt, this table is classified as obsolete, with the description explicitly stating that it is "No longer used." In both Oracle EBS 12.1.1 and 12.2.2, no functional implementation relies on this object, and the metadata confirms that the table is not implemented in the database. The AMW module itself, Internal Controls Manager, has been superseded by later compliance and governance tooling, and this table reflects the legacy schema of that retired functionality.

From a data modeling perspective, the provided metadata assigns a heuristic Data Vault classification of "standalone." This suggests that, were the table modeled within a Data Vault architecture, it would not be treated as a dependent satellite or a linking table connecting multiple hubs, but rather as an independent structure. Because the object is obsolete and not implemented, this classification should be regarded strictly as a modeling suggestion rather than an operational characterization.

Key Information Stored

Although the table is obsolete, the documented physical schema for AMW_CONTROL_REPORTS lists 26 columns. The most significant of these relate to the primary key, surrogate identity, audit tracking, and cross-references to control and security definitions.

Together, these columns indicate that AMW_CONTROL_REPORTS was designed to associate variable control definitions with reports, secured by EBS security groups and audited through standard EBS conventions.

Common Use Cases and Queries

Because the table is obsolete and not implemented in a current database, there are no supported production use cases in Oracle EBS 12.1.1 or 12.2.2. Any query against this object would fail with an invalid table or view error unless legacy data remains in an archived instance.

Historically, a typical query pattern would join the table to its control and security group parents, for example:

  • Join AMW_CONTROL_REPORTS to CST_REVENUE_COGS_CONTROL on CONTROL_ID to retrieve the associated control definition.
  • Join AMW_CONTROL_REPORTS to FND_SECURITY_GROUPS on SECURITY_GROUP_ID to resolve the security organization or group responsible for the record.
  • Filter by CONTROL_REPORT_ID or REPORT_ID to isolate a specific report-to-control assignment.

In modern implementations, these reporting needs are addressed through the replacement compliance modules, and the table should not be referenced in new customizations, reports, or interfaces.

Related Objects

The following objects are documented as related to AMW_CONTROL_REPORTS through foreign key relationships or shared key structures:

  • CST_REVENUE_COGS_CONTROL — Referenced via the CONTROL_ID foreign key; this table holds control definitions related to revenue and cost of goods sold processing.
  • FND_SECURITY_GROUPS — Referenced via the SECURITY_GROUP_ID foreign key; provides the security grouping used to partition records.
  • AMW_CONTROL_REPORTS_PK — The primary key constraint defined on CONTROL_REPORT_ID.
  • AMW_CONTROL_REPORTS_U1 — A unique index on CONTROL_REPORT_ID, supporting business-key uniqueness.

No other significant dependents, views, or APIs are documented for this object. Because AMW_CONTROL_REPORTS is obsolete and unimplemented, integrators should treat it as a historical schema artifact rather than an active component of the Oracle EBS data model.