Results for “qrm_analysis_disc_v”

26 results




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

Overview

QRM_ANALYSIS_DISC_V is a reporting view in the Oracle E-Business Suite Risk Management (QRM) module, owned by the APPS schema. It exposes deals that have been processed and calculated by Risk Analysis, augmented with date-dependent attributes such as expiration, maturity, value, and start dates. The view consolidates instrument static data, deal calculation results, and currency-denominated monetary amounts into a single denormalized projection, which makes it suitable for downstream reporting, dashboards, and analytic extracts rather than transactional processing.

Because the view is defined in APPS and is marked VALID, it is queryable by any application user with the appropriate grants, and it is typically referenced by risk reporting tools, treasury extracts, and reconciliation queries. It is not a base table; it depends entirely on the underlying QRM calculation and current deals objects, so its data reflects whatever the most recent Risk Analysis run has produced. The title indicates the view surfaces "deals calculated by Risk Analysis, including date dependent attributes," confirming its role as a date-aware reporting layer over calculated risk positions.

Underlying Base Objects

The view is defined over the following documented objects:

  • QRM_CURRENT_DEALS_V (VIEW) — supplies the primary deal-level static attributes such as currencies, counterparties, portfolio codes, and instrument classification.
  • QRM_DEAL_CALCULATIONS (SYNONYM) — supplies the calculated monetary and analytic measures, including revaluation, fair value, accrual, and sensitivity figures.
  • QRM_TB_CALCULATIONS (SYNONYM) — referenced in the calculation join context for total-base style amounts.
  • XTR_DEAL_TYPES and XTR_DEAL_SUBTYPES (SYNONYMS) — provide user-defined deal type and subtype descriptions joined via DC-related keys.
  • FND_GLOBAL (PACKAGE) — used for session context such as organization and user identifiers.

Columns prefixed with V. originate from the deals view, while DC. columns originate from the calculations source. The join effectively pairs static instrument data with calculated results per deal and transaction.

Key Columns

Frequently used identity and classification columns include DEAL_NO, TRANSACTION_NO (with -4 mapped to NULL), COMPANY_CODE, DEALER_CODE, CPARTY_CODE, PORTFOLIO_CODE, PRODUCT_TYPE, MARKET_TYPE, and INSTR_TYPE. Date-dependent attributes include DEAL_DATE, START_DATE, END_DATE, VALUE_DATE, MATURITY_DATE, EXPIRATION_DATE, GAP_DATE, and KNOCK_EXECUTE_DATE.

Monetary measures are exposed in multiple currency bases: DEAL_CCY amounts (BUY_AMOUNT, SELL_AMOUNT, FOREIGN_AMOUNT, DOMESTIC_AMOUNT) alongside USD and SOB variants such as BASE_CCY_AMOUNT_USD, BASE_CCY_AMOUNT_SOB, FAIR_VALUE_USD, FAIR_VALUE_SOB, MATURITY_AMOUNT_USD, and ACCRUED_INTEREST_SOB. Risk analytics include DELTA, GAMMA, THETA, VEGA, RHO, DURATION, MODIFIED_DURATION, CONVEXITY, VOLATILITY, POS_BPV, and their POS_-prefixed position counterparts. These measures support value-at-risk and sensitivity reporting.

Common Use Cases and Queries

Typical scenarios include outstanding exposure reporting, fair value and accrual reconciliation, and sensitivity aggregation by portfolio or counterparty. Although OUTSTANDING_AMOUNT is not a literal column in this view, outstanding exposure is commonly derived from BUY_AMOUNT, SELL_AMOUNT, or FAIR_VALUE columns depending on business definition.

  • Exposure by portfolio: aggregate BUY_AMOUNT_USD and SELL_AMOUNT_USD grouped by PORTFOLIO_CODE.
  • Maturity ladder: group MATURITY_AMOUNT_USD by MATURITY_DATE or GAP_DATE.
  • Sensitivity reporting: sum DELTA, VEGA, and POS_BPV by CPARTY_CODE.
SELECT portfolio_code,
       SUM (buy_amount_usd) AS buy_usd,
       SUM (sell_amount_usd) AS sell_usd,
       SUM (fair_value_usd) AS fair_value_usd
  FROM apps.qrm_analysis_disc_v
 WHERE value_date >= :from_date
 GROUP BY portfolio_code;
SELECT cparty_code,
       SUM (pos_bpv) AS pos_bpv,
       SUM (delta)   AS delta,
       SUM (vega)    AS vega
  FROM apps.qrm_analysis_disc_v
 GROUP BY cparty_code;

Because results depend on the last Risk Analysis calculation run, queries should be scheduled after the calculation cycle to ensure currency and completeness of the calculated measures.