Search Results run_analysis_cp




Overview
Explore in AI Chat

Overview

QRM_PA_CALCULATION_P is a PL/SQL package in the APPS schema that supports Oracle E-Business Suite Treasury (formerly ETRM) deal analysis and calculation processing. Its role is to perform quantitative analysis over treasury deals — computing gaps, thresholds, signed amounts, and converted amounts — and to purge obsolete analysis data. The package operates against the QRM (Treasury deal analysis) family of tables and interleaves with deal and bond reference data such as QRM_DEALS_S and XTR_BOND_ISSUES. This package is central to the analytical tier of Treasury: it evaluates selected deals against configured filters and settings and persists calculation results for downstream reporting within Oracle Treasury.

Key Procedures and Functions

  • RUN_ANALYSIS — Executes a deal analysis run. This is the master entry point that drives the calculation cycle for the analysis set.
  • RUN_ANALYSIS_CP — A concurrent-program wrapper around the general analysis logic, configured for processing in the concurrent manager environment.
  • RUN_ANALYSIS_AM — An alternate analysis entry point, typically associated with an alternate processing mode for the same underlying calculation routine.
  • REMOVE_EXPIRED_DEALS — Cleanses analysis output by removing deals whose validity has lapsed, keeping the analysis set current.
  • GET_THRESHOLD_DATE — Derives the threshold date used to bound the analysis window and drive date-based evaluations.
  • GET_GAP_DATE — Computes a gap date, used in timing and maturity gap reporting for deals and instruments.
  • GET_SIGNED_AMOUNT — Returns an amount with its correct directional sign, applying the deal’s buy/sell or long/short perspective.
  • CONVERT_AMOUNTS — Applies currency conversion so that amounts across differing currencies can be aggregated for analysis.
  • FILTER_MEASURE — Evaluates a measure against configured filter criteria, determining whether the record participates in the analysis result.

Tables Accessed

The package reads and writes QRM_ANALYSIS_ATTS, QRM_ANALYSIS_SETTINGS and QRM_ANA_ATTS_LOOKUPS to obtain attribute definitions, run-time settings and valid lookup values that govern how analyses are parameterised. It reads QRM_DEALS_S for deal header information and QRM_DEALS_ANALYSES for the analyses associated with a deal. Output and error data are written to QRM_DEAL_CALCULATIONS and QRM_DEAL_CALC_ERRORS, with QRM_TB_CALCULATIONS capturing table-level calculation results. Filtering logic uses QRM_FILTERS and QRM_FILTER_CONDITIONS. Instrument-level dates for bond computations come from XTR_BOND_COUPON_DATES and XTR_BOND_ISSUES, with counterparty data from XTR_PARTY_INFO. DBMS_SQL is employed for dynamic SQL, and DUAL provides scalar evaluation. Notably, the package also depends on the SYS/SYSTEM-owned QRM_VARCHAR_TABLE type — the object the user searched for — which serves as a collection type for passing variable-length-string lists between the analysis routines.

Usage Notes

QRM_PA_CALCULATION_P is normally invoked indirectly: Oracle Treasury submits the analysis routines through concurrent programs and supporting forms, which call RUN_ANALYSIS, RUN_ANALYSIS_CP, or RUN_ANALYSIS_AM. The package is a dependency target within APPS, so invoking application logic that triggers an analysis will reach it automatically. The presence of the QRM_VARCHAR_TABLE dependency indicates that callers and internal routines pass collections of string identifiers (filter names, attribute keys) rather than scalar parameters. The package is not documented as being referenced by any other PL/SQL package, confirming that integration is via the standard Treasury application layer and its concurrent manager infrastructure rather than through point-to-point APIs. For custom extensions, the safest approach is to schedule or submit Treasury’s analysis concurrent programs rather than call the package directly, since RUN_ANALYSIS* routines expect the surrounding concurrent context and configuration records to be in place. All references in the above analysis resolve through APPS synonyms; the code is valid and marked as a standard component in both 12.1.1 and 12.2.2.