Results for “md_set_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

QRM_ANALYSIS_SETTINGS is a core configuration table in the Oracle E-Business Suite Risk Management (QRM) module. It stores the definition and parameter settings for each risk analysis performed within the application, acting as the central registry of named analyses and the rules that govern how each one is executed, filtered, and displayed. Every saved analysis — whether used for currency exposure, market risk, counterparty risk, or portfolio valuation — derives its behavior from a row in this table.

The table resides in the QRM schema and is valid in both Oracle EBS 12.1.1 and 12.2.2. Its primary key, QRM_ANALYSIS_SETTINGS_PK, is composed of the composite key (ANALYSIS_NAME, HISTORY_FLAG). A unique index, QRM_ANALYSIS_SETTINGS_U1, extends this with ZD_EDITION_NAME, reflecting the editioning model introduced with online patching in 12.2.2. The documented physical schema contains 38 columns.

From a Data Vault modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification. QRM_ANALYSIS_SETTINGS functions primarily as a descriptive satellite attached to the ANALYSIS_NAME business key, with its HISTORY_FLAG and ZD_EDITION_NAME attributes supporting historization and EBS editioning.

Key Information Stored

The table’s columns cluster into several functional groups. Identification and business-key columns include ANALYSIS_NAME, the human-readable business key for the analysis; HISTORY_FLAG, which distinguishes current versus historical or archived versions of an analysis definition; and ZD_EDITION_NAME, the editioning discriminator required in 12.2.2. The surrogate primary key QRM_ANALYSIS_SETTINGS_PK is defined over ANALYSIS_NAME and HISTORY_FLAG.

Analysis behavior and display parameters are controlled by columns such as ANALYSIS_TYPE, STYLE, DATE_TYPE, and CURRENCY_SOURCE, which determine how the analysis is categorized, rendered, and how currency figures are sourced. STATUS and DIRTY track the lifecycle and modification state of the analysis. THRESHOLD_NUM and THRESHOLD_TYPE store the numeric threshold and comparison rule used for exception or breach reporting.

Time and reporting context is captured by START_DATE, END_DATE, START_DATE_REF, END_DATE_REF, START_DATE_OFFSET, END_DATE_OFFSET, START_OFFSET_TYPE, END_OFFSET_TYPE, BUSINESS_WEEK, and GL_CALENDAR_ID. Display and precision behavior is governed by SHOW_TOTALS, CURR_REPORTING, CURRENCY_USED, DEC_PLACES, and UNITS. Operational columns include PROCESS_ID, which links an analysis to a concurrent request, and LAST_RUN_DATE, the timestamp of the most recent execution. Standard audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) complete the row.

Common Use Cases and Queries

The table is most commonly queried to enumerate analyses, inspect their configuration, or drive reports on runtime status and scheduling. A typical pattern selects active analyses and their last run information:

• Listing all current analyses: SELECT analysis_name, analysis_type, status FROM qrm_analysis_settings WHERE history_flag = 'N';
• Identifying analyses not yet run: filter on last_run_date IS NULL AND status = 'ACTIVE'.
• Auditing time-window configuration: select START_DATE_REF, END_DATE_REF, START_DATE_OFFSET, END_DATE_OFFSET, and BUSINESS_WEEK for a given ANALYSIS_NAME.
• Reporting on threshold rules: retrieve THRESHOLD_NUM and THRESHOLD_TYPE alongside ANALYSIS_NAME for breach-monitoring dashboards.
• Correlating analyses to concurrent programs via PROCESS_ID joined to FND_CONCURRENT_REQUESTS.

Related Objects

QRM_ANALYSIS_SETTINGS participates in several documented foreign-key relationships:

• QRM_FILTERS — joined via QRM_ANALYSIS_SETTINGS.FILTER_NAME; supplies the filter definition applied to the analysis.
• QRM_TIME_BUCKETS — joined via QRM_ANALYSIS_SETTINGS.TB_NAME; defines the time bucket used for aggregating results.
• XTR_RM_MD_SETS — joined via QRM_ANALYSIS_SETTINGS.MD_SET_CODE; provides the market data set driving valuation.
• GL_TRANSACTION_CALENDAR — joined via QRM_ANALYSIS_SETTINGS.GL_CALENDAR_ID; supplies the accounting calendar context.
• FND_CONCURRENT_REQUESTS — joined via QRM_ANALYSIS_SETTINGS.PROCESS_ID; links analyses to their concurrent execution records.
• QRM_ANALYSIS_ATTS — referenced via ANALYSIS_NAME and HISTORY_FLAG; stores additional attributes for each analysis and is a child of this table.