Results for “qrm_deal_calc_errors”

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

Overview

QRM_DEAL_CALC_ERRORS is a table within the QRM (Risk Management) module of Oracle E-Business Suite, valid across 12.1.1 and 12.2.2. Its documented purpose is to store error and warning messages generated during quantitative analysis runs over deals and market data. Each row captures a diagnostic outcome associated with a specific analysis, deal, transaction, and market data set, allowing risk analysts and support staff to trace why a particular calculation failed, was skipped, or produced a warning. The table operates as a logging and exception-tracking structure that sits alongside the core calculation result tables in the QRM schema.

From a heuristic Data Vault modeling perspective, the metadata suggests this object is satellite-leaning. Although it contains a composite unique key comprising ANALYSIS_NAME, DEAL_NO, ERROR_CODE, MARKET_DATA_SET, and TRANSACTION_NO, the table predominantly records descriptive and diagnostic attributes tied to a parent calculation context rather than acting as a pure hub of business entities. It functions best understood as a descriptive satellite attached to the deal calculation process, with the unique key serving as the business key that distinguishes individual error records.

Key Information Stored

The table contains 17 documented columns. The most significant are:

• ANALYSIS_NAME — Identifies the analysis or risk calculation batch that produced the error or warning.
• DEAL_NO — The deal number associated with the failing or warning calculation.
• TRANSACTION_NO — The transaction identifier, forming part of the foreign key relationship to QRM_DEAL_CALCULATIONS and the composite unique key.
• MARKET_DATA_SET — The market data set context used during the analysis; central to the composite business key and frequently the focus of user queries.
• ERROR_TYPE — Classifies the record as an error or a warning, enabling severity-based filtering.
• ERROR_CODE — The code identifying the specific condition encountered, forming part of the composite unique key.
• TOKEN_NAME and TOKEN_VALUE — Hold parameterized message tokens and their substituted values, allowing the error text to be reconstructed with deal-specific detail.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program and request context, identifying the batch job that generated the record.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns tracking record creation and modification.

The composite unique index QRM_DEAL_CALC_ERRORS_U1 (ANALYSIS_NAME, DEAL_NO, ERROR_CODE, MARKET_DATA_SET, TRANSACTION_NO) is the documented business-key candidate. The metadata does not document a separate single-column surrogate primary key, so the composite unique key effectively serves that role.

Common Use Cases and Queries

Typical use cases include troubleshooting failed risk analyses, auditing data quality across market data sets, and building exception reports for a given analysis run.

• Retrieve all errors for a specific analysis: SELECT * FROM QRM.QRM_DEAL_CALC_ERRORS WHERE ANALYSIS_NAME = :analysis AND ERROR_TYPE = 'ERROR';
• List errors tied to a particular market data set: SELECT DEAL_NO, ERROR_CODE, TOKEN_NAME, TOKEN_VALUE FROM QRM.QRM_DEAL_CALC_ERRORS WHERE MARKET_DATA_SET = :mds;
• Cross-reference with calculated results: SELECT e.* FROM QRM.QRM_DEAL_CALC_ERRORS e JOIN QRM.QRM_DEAL_CALCULATIONS c ON e.TRANSACTION_NO = c.TRANSACTION_NO;
• Trace errors back to the concurrent request that produced them using REQUEST_ID and PROGRAM_ID.
• Aggregate warning counts by deal to identify recurring data issues: SELECT DEAL_NO, COUNT(*) FROM QRM.QRM_DEAL_CALC_ERRORS WHERE ERROR_TYPE = 'WARNING' GROUP BY DEAL_NO;

Related Objects

The primary documented relationship is the foreign key from QRM_DEAL_CALC_ERRORS.TRANSACTION_NO (and related DEAL_NO and MARKET_DATA_SET columns) to QRM_DEAL_CALCULATIONS. Supporting objects include QRM analysis definition and market data tables referenced indirectly through ANALYSIS_NAME and MARKET_DATA_SET, plus standard EBS concurrent program and request tables (FND_CONCURRENT_REQUESTS, FND_CONCURRENT_PROGRAMS) used to interpret REQUEST_ID and PROGRAM_ID. Reporting typically joins this table against the calculation results table and deal master data to present error and warning diagnostics alongside their originating calculations.