Search Results amw_ctrl_ext_b




Overview
Explore in AI Chat

Overview

AMW_CTRL_EXT_B is a table in the Oracle E-Business Suite Internal Controls Manager (AMW) module, which is classified as obsolete in Release 12.1.1 and 12.2.2. The table stores extensible attribute details for controls, providing the flexible attribute framework that allowed organizations to capture organization-specific data about internal controls beyond the standard seeded columns. AMW supported governance, risk, and compliance functionality, and its attribute model mirrored the descriptive flexfield-adjacent design pattern used elsewhere in EBS, where a fixed set of generic columns is reserved for customer-defined values.

Physically, the table is owned by the AMW schema and contains 101 documented columns in the 12.1.1 electronic technical reference manual. Despite being listed, the ETRM metadata records that the object is not implemented in the sampled database. From a heuristic Data Vault modeling perspective, AMW_CTRL_EXT_B suggests a satellite classification: it carries descriptive and audit attributes keyed to a parent business entity, rather than acting as a standalone hub or a link between independent entities. The relationship metadata classifies it as standalone, reflecting that its foreign key dependency is a single lookup reference rather than a wide network of relationships.

Key Information Stored

The table is dominated by generic extensible attribute columns, which are the primary reason it exists. The most significant columns include:

The surrogate key is EXTENSION_ID. CONTROL_ID functions as the business join to the control master data, and the combination of CONTROL_ID with ATTR_GROUP_ID is a plausible natural uniqueness candidate, though the ETRM metadata does not document an explicit unique index. The character, numeric, date, and UOM blocks are intentionally sized to cover a broad range of customer extension needs without schema changes.

Common Use Cases and Queries

Because the table is obsolete, current implementations are unlikely to query it directly. Historical reporting and migration work remain the primary use cases. A typical query retrieves extension values for a specific control:

  • Joining AMW_CTRL_EXT_B to CST_REVENUE_COGS_CONTROL on CONTROL_ID to display a control with its customer-defined attributes.
  • Filtering by ATTR_GROUP_ID to isolate a particular attribute context for a control.
  • Extracting non-null character attributes to reconcile legacy control metadata during migration to a successor GRC platform.
  • Auditing change history using LAST_UPDATE_DATE, LAST_UPDATED_BY, and CREATION_DATE to identify when extension data was loaded or modified.

Common SQL patterns project only the populated attribute columns, since most of the 101 columns are sparse. Reporting typically pivots C_EXT_ATTR, N_EXT_ATTR, and D_EXT_ATTR values into labeled columns using an attribute definition table, if one exists in the same module.

Related Objects

The documented foreign key relationship is narrow, but the following objects are the most significant in practice:

  • CST_REVENUE_COGS_CONTROL — referenced by AMW_CTRL_EXT_B.CONTROL_ID; the parent control definition providing the join anchor.
  • AMW_CTRL_EXT_TL — the translated or attribute-definition counterpart that typically describes the meaning of the generic attribute columns.
  • AMW_CTRLS_B and AMW_CTRLS_TL — the base control tables that define the controls whose extensions are stored here.
  • AMW_ATTR_GROUPS — supplies the ATTR_GROUP_ID context labels for the extension values.
  • AMW_WORK_ITEMS — relates through WORK_ID and WORK_TYPE_ID for workflow linkage.
  • FND_LOOKUPS — commonly used to resolve UOM and other coded extension values.