Search Results xtr_rm_md_sets

Overview

The QRM_ANALYSIS_SETTINGS table is a core configuration entity within the Oracle E-Business Suite (EBS) Risk Management (QRM) module. It serves as the master repository for defining and storing the parameters of a specific risk analysis scenario. Each record represents a unique, named analysis configuration that dictates how the QRM engine will process and evaluate financial risk data. The table's role is pivotal, as it centralizes the operational settings that link various other QRM components—such as filters, time buckets, and market data sets—into a cohesive analysis definition. This configuration-driven approach allows for the consistent execution, scheduling, and historical tracking of complex risk simulations.

Key Information Stored

While the full column list is not detailed in the provided metadata, the primary and foreign key relationships reveal its critical structural elements. The table is uniquely identified by a composite primary key consisting of ANALYSIS_NAME and HISTORY_FLAG. The ANALYSIS_NAME column stores the unique identifier for the analysis configuration. The HISTORY_FLAG is a critical column that enables versioning, distinguishing between the current active settings and historical snapshots of past configurations. Other significant columns, inferred from foreign key constraints, include FILTER_NAME (linking to QRM_FILTERS), TB_NAME (linking to QRM_TIME_BUCKETS), MD_SET_CODE (linking to XTR_RM_MD_SETS for market data), GL_CALENDAR_ID (linking to GL_TRANSACTION_CALENDAR), and PROCESS_ID (linking to FND_CONCURRENT_REQUESTS for submission tracking).

Common Use Cases and Queries

The primary use case is the setup and execution of risk analysis jobs. Administrators create or update records in this table to define new what-if scenarios or modify existing ones. A common operational query is to retrieve all active configurations for a reporting interface or to audit historical changes. For example:

• SELECT analysis_name, filter_name, tb_name FROM qrm.qrm_analysis_settings WHERE history_flag = 'N' ORDER BY analysis_name;

Another critical pattern involves joining with the FND_CONCURRENT_REQUESTS table to monitor the status of a submitted analysis job using the PROCESS_ID. The table is also central to data lineage and impact analysis; understanding which configurations use a specific filter or time bucket often requires querying this table.

Related Objects

The QRM_ANALYSIS_SETTINGS table maintains integral relationships with several key EBS objects, as documented by its foreign keys:

• QRM_FILTERS: Joined via QRM_ANALYSIS_SETTINGS.FILTER_NAME. Defines the data subset for the analysis.
• QRM_TIME_BUCKETS: Joined via QRM_ANALYSIS_SETTINGS.TB_NAME. Specifies the time horizons for cash flow aggregation.
• XTR_RM_MD_SETS: Joined via QRM_ANALYSIS_SETTINGS.MD_SET_CODE. Provides the market data (rates, prices) used in valuation and simulation.
• GL_TRANSACTION_CALENDAR: Joined via QRM_ANALYSIS_SETTINGS.GL_CALENDAR_ID. Supplies the calendar for date arithmetic and working days.
• FND_CONCURRENT_REQUESTS: Joined via QRM_ANALYSIS_SETTINGS.PROCESS_ID. Tracks the submitted concurrent request for the analysis job.
• QRM_ANALYSIS_ATTS: This child table references QRM_ANALYSIS_SETTINGS via its composite key (ANALYSIS_NAME, HISTORY_FLAG), storing additional attribute-level settings for each analysis.