Results for “qrm_disc_analysis_tb_v”

32 results




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

Overview

QRM_DISC_ANALYSIS_TB_V is a dictionary view in the APPS schema that exposes deal-level information for Oracle Risk Management (QRM) analyses, with each row grouped by time-bucket period. It is a reporting and integration construct rather than a base table: the view flattens deal, transaction, and valuation attributes onto a time-bucket start and end date, allowing risk and treasury users to query analysis results across defined reporting horizons without joining the underlying QRM tables themselves. The view is defined to enforce user access to company information, so the rows returned are already filtered by the security context established for the session. This makes it suitable for use in concurrent programs, Discoverer/OBI reports, and downstream integration extracts where company-level data restriction is mandatory. Because it exposes both the deal's native amounts and its translated USD and set-of-books (SOB) equivalents, together with revaluation and translation rates, it is particularly relevant to FX revaluation and fair-value reporting, including queries that search on the revaluation price/rate attributes.

Underlying Base Objects

The view is defined over a set of QRM and XTR synonyms and one FND package. Documented referenced objects are: FND_GLOBAL (package), QRM_CURRENT_DEALS_V (view), QRM_DEALS_ANALYSES, QRM_DEAL_CALCULATIONS, QRM_SAVED_ANALYSES_COL, QRM_TB_CALCULATIONS, XTR_DEAL_SUBTYPES, XTR_DEAL_TYPES, XTR_PARTY_INFO, and XTR_PRODUCT_TYPES. Functionally, QRM_CURRENT_DEALS_V supplies the deal/transaction attributes; QRM_DEALS_ANALYSES and QRM_SAVED_ANALYSES_COL link deals to saved analyses; QRM_DEAL_CALCULATIONS and QRM_TB_CALCULATIONS provide calculated amounts and the time-bucket boundaries (which surface as TB_START_DATE and TB_END_DATE); the XTR_* synonyms supply deal type, subtype, party, and product classifications. FND_GLOBAL is used to resolve the session's responsibility, user, and org context so that company-level access is enforced at query time.

Key Columns

Identity and classification columns include ANALYSIS_NAME, DEAL_NO, TRANSACTION_NO, COMPANY_CODE, DEALER_CODE, CLIENT_CODE, CPARTY_CODE, PORTFOLIO_CODE, DEAL_CCY, PRODUCT_TYPE, USER_DEAL_TYPE, USER_DEAL_SUBTYPE, MARKET_TYPE, and INSTR_TYPE. Time-bucket columns TB_START_DATE and TB_END_DATE define the grouping period. Amount columns include BUY_AMOUNT, SELL_AMOUNT, FOREIGN_AMOUNT, DOMESTIC_AMOUNT, BASE_CCY_AMOUNT, CONTRA_CCY_AMOUNT, FACE_VALUE, and PREMIUM_AMOUNT, each repeated in USD and SOB variants (for example BUY_AMOUNT_USD, BUY_AMOUNT_SOB, CONTRA_CCY_AMOUNT_USD). Valuation and rate columns include FX_REVAL_RATE, MM_REVAL_RATE, FX_TRANS_RATE, MM_TRANS_RATE, FAIR_VALUE, and FAIR_VALUE_USD, along with ACCRUED_INTEREST (aliased ACCRUED_INTEREST_PRICE), DISCOUNT_YIELD, TRANSACTION_RATE, and quantity measures such as QUANTITY_REMAINING_USD and QUANTITY_REMAINING_SOB. Option-related fields include CALL_OR_PUT, OPTION_STYLE, KNOCK_TYPE, KNOCK_LEVEL, and KNOCK_EXECUTE_DATE.

Common Use Cases and Queries

Typical uses include time-bucketed exposure reporting, FX revaluation review, fair-value analysis, and company-restricted extracts. A revaluation-focused query might filter on rate presence and period:

  • SELECT ANALYSIS_NAME, DEAL_NO, COMPANY_CODE, DEAL_CCY, TB_START_DATE, TB_END_DATE, FX_REVAL_RATE, MM_REVAL_RATE, FAIR_VALUE_USD FROM APPS.QRM_DISC_ANALYSIS_TB_V WHERE ANALYSIS_NAME = :p_analysis AND TB_START_DATE >= :p_from AND TB_END_DATE <= :p_to ORDER BY COMPANY_CODE, TB_START_DATE;
  • SELECT COMPANY_CODE, TB_START_DATE, SUM(BUY_AMOUNT_USD), SUM(SELL_AMOUNT_USD), SUM(FAIR_VALUE_USD) FROM APPS.QRM_DISC_ANALYSIS_TB_V GROUP BY COMPANY_CODE, TB_START_DATE ORDER BY TB_START_DATE;
  • SELECT DEAL_NO, TRANSACTION_NO, INSTR_TYPE, DISCOUNT_YIELD, TRANSACTION_RATE FROM APPS.QRM_DISC_ANALYSIS_TB_V WHERE MARKET_TYPE = :p_market AND COMPANY_CODE IN (SELECT COMPANY_CODE FROM APPS.QRM_DISC_ANALYSIS_TB_V WHERE 1=1);

Because access is enforced through FND_GLOBAL, results depend on the responsibility and org context of the session; queries executed outside an initialized EBS session may return no rows. Access to the view requires the QRM responsibility and appropriate grants on APPS.QRM_DISC_ANALYSIS_TB_V.