Search Results amw_controls_b




Overview
Explore in AI Chat

Overview

The AMW_CONTROLS_B table is the core base table for storing non-translatable control attributes within the Oracle E-Business Suite module AMW (Internal Controls Manager). It served as the primary entity for defining and managing internal controls, which are processes or procedures implemented to mitigate business risks and ensure compliance. As the "B" suffix indicates, it follows the standard Oracle Applications pattern where a base table holds language-independent data, while a corresponding translation table (AMW_CONTROLS_TL) stores language-specific descriptions. It is critical to note that the provided ETRM metadata explicitly states this module is "Obsolete" and that the table is "Not implemented in this database," indicating it was part of a decommissioned or superseded functionality in the documented versions (12.1.1 / 12.2.2). Its role was foundational, acting as the parent record for a control's core definition, linked to assertions, objectives, and purposes.

Key Information Stored

The primary data stored in AMW_CONTROLS_B pertains to the immutable attributes of a control. The central column is CONTROL_REV_ID, which serves as the unique primary key identifier for a specific control revision. While the full column list is not detailed in the excerpt, typical attributes in such a base table would include creation date, created by, last update date, last updated by, and key status or versioning flags. The "non-translatable" designation means this table houses data that does not change per language, such as IDs, dates, numeric values, and codes, as opposed to descriptive text like control names or detailed procedures, which would reside in AMW_CONTROLS_TL.

Common Use Cases and Queries

When the module was active, this table was central to control management and reporting. Common use cases included auditing the control framework, generating control inventories, and linking controls to financial assertions or business processes. A fundamental query would join the base table with its translation table to retrieve a complete control record. Given the obsolete status, direct operational use in EBS 12.1.1/12.2.2 is unlikely, but historical data analysis or migration projects might reference it. A sample query pattern would be:

  • SELECT b.CONTROL_REV_ID, tl.CONTROL_NAME, b.CREATION_DATE FROM AMW_CONTROLS_B b, AMW_CONTROLS_TL tl WHERE b.CONTROL_REV_ID = tl.CONTROL_REV_ID AND tl.LANGUAGE = USERENV('LANG');

Related Objects

AMW_CONTROLS_B has defined relationships with several key tables in the (obsolete) Internal Controls Manager schema, as per the foreign key metadata. The primary related objects are:

  • AMW_CONTROLS_TL: The translation table, dependent on CONTROL_REV_ID, for multilingual control descriptions.
  • AMW_CONTROL_ASSERTIONS: Links controls to financial statement assertions (e.g., completeness, valuation).
  • AMW_CONTROL_OBJECTIVES: Associates controls with specific operational or compliance objectives.
  • AMW_CONTROL_PURPOSES: Classifies controls by their purpose (e.g., preventive, detective, corrective).

These relationships illustrate that AMW_CONTROLS_B was the central hub from which a control's definitions, classifications, and translations were extended.