Search Results qrm_filter_conditions




Overview
Explore in AI Chat

Overview

The QRM_FILTER_CONDITIONS table is a core data structure within the Oracle E-Business Suite (EBS) Risk Management (QRM) module. It functions as the repository for the detailed logical criteria that define a risk filter. In the context of QRM, filters are used to segment and analyze financial portfolios, exposures, and transactions based on specific attributes. This table stores the individual condition rows that collectively constitute a filter's definition, enabling complex, multi-criteria rule sets for risk assessment and reporting. Its existence is critical for the operational logic of QRM's analytical and simulation engines, which rely on these stored conditions to dynamically select and evaluate financial data.

Key Information Stored

The table's structure is designed to capture the components of a filter condition. The primary key is a composite of two columns, ensuring uniqueness for each condition line within a filter. The FILTER_NAME column is the foreign key that links the condition to its parent definition in the QRM_FILTERS table. The ROW_NUMBER column sequences the order of multiple conditions within a single filter, which is essential for proper logical evaluation. While the provided metadata does not list all columns, typical condition tables in this context would also include columns for the database column or attribute being tested (e.g., INSTRUMENT_TYPE, CURRENCY_CODE), the operator (e.g., '=', '>', 'IN'), and the comparison value or set of values. This design allows for flexible and granular filter construction.

Common Use Cases and Queries

The primary use case is the administrative review and audit of defined risk filters. Analysts or system administrators may query this table to understand the exact composition of a filter used in a critical risk report or simulation. A common query pattern retrieves all conditions for a specific filter, ordered for clarity. For example:

  • SELECT * FROM QRM.QRM_FILTER_CONDITIONS WHERE FILTER_NAME = 'HIGH_RISK_FX' ORDER BY ROW_NUMBER;

This is vital for troubleshooting, compliance documentation, and replicating filter logic in custom reports. Another scenario involves identifying all filters that use a particular financial instrument attribute, which would require querying on the condition's attribute column (not explicitly listed in the brief metadata but standard for such a table).

Related Objects

The QRM_FILTER_CONDITIONS table has a direct and fundamental relationship with the QRM_FILTERS table, which stores the master definition (header) information for each filter. As documented in the provided foreign key metadata:

  • Primary Parent Table: QRM_FILTERS
  • Relationship: The column QRM_FILTER_CONDITIONS.FILTER_NAME is a foreign key referencing the QRM_FILTERS table. This enforces referential integrity, meaning every condition must belong to a valid, existing filter header.

This table is also likely referenced by various QRM application programming interfaces (APIs) and online forms for filter maintenance, as well as by the QRM engine's runtime components that apply these filters to risk data sets. Understanding this parent-child relationship is essential for any join query aimed at presenting a complete filter definition.