Search Results qrm_saved_analyses_row




Overview
Explore in AI Chat

Overview

The QRM_SAVED_ANALYSES_ROW table is a core data repository within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 Risk Management (QRM) module. It functions as the detailed results table for saved financial analyses. As described in the ETRM, this table stores the individual rows of data that are displayed below the column headers in the Analysis Results interface. Its primary role is to persist the output of complex risk and financial simulations, enabling users to save, recall, and compare different analysis scenarios over time. This persistence is critical for audit trails, historical comparison, and regulatory reporting within the treasury and risk management functions of an organization.

Key Information Stored

The table's structure is designed to hold the granular, line-item results of a saved analysis. The documented primary key, consisting of ANALYSIS_NAME and SEQ_NO, reveals the fundamental data model: each saved analysis is uniquely identified by a name, and within that analysis, each result row is assigned a sequence number. While the full column list is not provided in the excerpt, typical columns in such a table would include the analysis identifier (ANALYSIS_NAME), the row sequence (SEQ_NO), and a set of value columns representing the calculated metrics or outputs for that specific row (e.g., cash flow amounts, risk exposures, valuation figures, scenario identifiers, time periods, or instrument identifiers). The SEQ_NO ensures the original presentation order and structure of the analysis results are maintained.

Common Use Cases and Queries

The primary use case is the retrieval and reporting on saved risk analyses. Financial controllers and treasury analysts use this data to review past simulations, generate comparative reports, and support decision-making. A common query pattern involves filtering by ANALYSIS_NAME to fetch all result rows for a specific report. For instance, to extract a complete saved analysis for review or integration into a custom dashboard, a query such as SELECT * FROM QRM.QRM_SAVED_ANALYSES_ROW WHERE ANALYSIS_NAME = '<Your_Analysis_Name>' ORDER BY SEQ_NO; would be used. Another critical use case is data purging or archiving, where analyses beyond a certain date range are identified via related metadata tables and then removed from this detail table.

Related Objects

This table is intrinsically linked to other QRM analysis objects. It is a child table to a master analysis header table, which likely stores metadata such as the analysis owner, creation date, description, and parameters used for the run. This parent table, possibly named QRM_SAVED_ANALYSES or similar, would have a foreign key relationship to ANALYSIS_NAME. Furthermore, the QRM_SAVED_ANALYSES_ROW table may be referenced by summary or aggregate views that provide a higher-level perspective on analysis results. The primary key constraint QRM_SAVED_ANALYSES_ROW_PK enforces data integrity for these relationships. All interactions typically occur through the QRM application's standard user interface or its underlying packaged APIs, which manage the creation, deletion, and querying of saved analyses.