Search Results amw_threshold_values




Overview
Explore in AI Chat

Overview

The AMW_THRESHOLD_VALUES table is a configuration data object within the Oracle EBS Internal Controls Manager (AMW) product module. As documented in the ETRM metadata for releases 12.1.1 and 12.2.2, the table stores the threshold range of values expressed in percent. These percent-based ranges are used to classify or bucket numeric results—most commonly deficiency or significance ratings produced by control testing, risk assessment, and audit workflows—so that downstream processing can categorise an outcome as, for example, low, medium, or high severity based on where the calculated percentage falls.

The object is a standalone table owned by the AMW schema, with status VALID. Under the heuristic Data Vault classification mined from its foreign-key structure, it is modelled as a standalone entity rather than a true hub, link, or satellite. This classification reflects the fact that the table behaves essentially as a reference or lookup structure: it defines configuration rows keyed by a single surrogate identifier, with one outbound reference to an Oracle Applications security construct. Treating it as a standalone reference table is a reliable modelling suggestion, since the rows represent defined threshold bands rather than transactional events or relationships between business entities.

Key Information Stored

The documented physical schema comprises eleven columns. The most significant are:

  • THRESHOLD_ID — the surrogate primary key, enforced by AMW_THRESHOLD_VALUES_PK. This column uniquely identifies each threshold band and is the column referenced by dependent data.
  • START_PERCENT_VALUE and END_PERCENT_VALUE — the lower and upper bounds of the percent range. Together these form the principal business-key candidates, since a given threshold band is meaningfully distinguished by its numeric interval.
  • IMAGE_FILE — the name or reference of the associated image (typically an icon or graphic) rendered when a result falls within the defined range, supporting visual severity indicators in the AMW user interface.
  • SECURITY_GROUP_ID — the security group to which the threshold row belongs, providing multi-tenant or organisational partitioning of configuration data.
  • Standard EBS audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER — which capture row-level Who columns and support optimistic locking during concurrent updates.

Common Use Cases and Queries

Typical usage involves resolving a computed percentage to its corresponding band, and reporting on the configured threshold definitions. A representative join pattern is:

  • Band resolution: SELECT threshold_id, start_percent_value, end_percent_value, image_file FROM amw.amw_threshold_values WHERE :result_pct BETWEEN start_percent_value AND end_percent_value;
  • Threshold definition report: SELECT threshold_id, start_percent_value, end_percent_value, image_file FROM amw.amw_threshold_values ORDER BY start_percent_value;
  • Security-scoped lookup: filtering by SECURITY_GROUP_ID to retrieve only the threshold set applicable to a given security group.
  • Interface/integration extracts that publish the threshold bands to external audit or GRC systems for consistent severity classification.

Related Objects

The documented foreign-key relationship defines the table's principal external dependency: AMW_THRESHOLD_VALUES.SECURITY_GROUP_ID references FND_SECURITY_GROUPS, meaning threshold configuration is partitioned by Oracle Applications security group. The primary key THRESHOLD_ID is referenced by dependent AMW tables that store threshold results and test outcomes, which are resolved against these bands during control assessment and reporting. Because the ETRM metadata is limited to the standalone classification, the most reliable external join documented is to FND_SECURITY_GROUPS on SECURITY_GROUP_ID; other AMW objects consuming THRESHOLD_ID should be confirmed against the live data dictionary.