Search Results qrm_deal_calculations




Overview
Explore in AI Chat

Overview

The QRM_DEAL_CALCULATIONS table is a core data repository within the Oracle E-Business Suite's Risk Management (QRM) module. It functions as a master table for storing immutable, calculated attributes for financial deals. Its primary role is to serve as a system of record for the results of complex risk calculations, such as those for valuation or exposure, which are performed once per deal and market data scenario. By persisting these time-invariant results, the table enables efficient reporting, downstream analytical processing, and error tracking without requiring recalculation, thereby optimizing performance in the computationally intensive QRM environment.

Key Information Stored

The table's structure is designed to uniquely identify a specific calculation instance and its results. While the full column list is not detailed in the provided metadata, the documented primary and unique keys reveal its critical identifying dimensions. The primary key is a surrogate key, DEAL_CALC_ID, which provides a unique system identifier for each row. The business key is defined by a unique constraint (QRM_DEAL_CALCULATIONS_UK1) on the combination of DEAL_NO, MARKET_DATA_SET, and TRANSACTION_NO. This combination ensures that calculations are stored per deal, per specific set of market data inputs, and per transaction or calculation run. The table's description indicates it holds the resultant calculated attributes themselves, which are not expected to change for that specific calculation context.

Common Use Cases and Queries

A primary use case is retrieving calculated deal metrics for risk reporting and analysis. For instance, a report showing the calculated net present value (NPV) for a portfolio of deals under a specific market scenario would join this table to the QRM_DEALS_ANALYSES table. Another critical use is troubleshooting; the foreign key relationship with QRM_DEAL_CALC_ERRORS allows support teams to link error records directly to the specific calculation run that failed. A common query pattern involves fetching the latest calculation for a deal:

  • SELECT * FROM QRM.QRM_DEAL_CALCULATIONS qdc WHERE qdc.DEAL_NO = '<deal_number>' AND qdc.TRANSACTION_NO = (SELECT MAX(TRANSACTION_NO) FROM QRM.QRM_DEAL_CALCULATIONS WHERE DEAL_NO = qdc.DEAL_NO AND MARKET_DATA_SET = qdc.MARKET_DATA_SET);

This table is also essential for Treasury Board (TB) reporting processes, as indicated by its relationship with QRM_TB_CALCULATIONS.

Related Objects

The QRM_DEAL_CALCULATIONS table is central to the QRM calculation architecture, with several key objects referencing it via foreign keys as documented:

  • QRM_DEALS_ANALYSES: References via DEAL_CALC_ID. This links detailed, potentially time-varying deal analysis data to the immutable calculation context.
  • QRM_DEAL_CALC_ERRORS: References via the composite key (TRANSACTION_NO, DEAL_NO, MARKET_DATA_SET). This relationship enables error logging specific to a calculation run.
  • QRM_TB_CALCULATIONS: References via the composite key (TRANSACTION_NO, DEAL_NO, MARKET_DATA_SET). This links the core deal calculations to subsequent Treasury Board reporting outputs.