SAP Market Risk Analyzer: NPV, Sensitivities and VaR

The Market Risk Analyzer is the SAP TRM component that values financial positions and measures market risk — net present value, sensitivities, scenarios and value-at-risk. It's the engine behind two questions every treasury has to answer: what are our positions worth right now? and how much could market moves cost us? It's one of the three Analyzers in TRM, and the one the risk team lives in. The critical thing to hold onto: everything it produces is computed from market data — so its output is only ever as good as the rates and curves you feed it. Get the market data wrong and the Analyzer will confidently produce precise, wrong numbers.

What it does

The Market Risk Analyzer takes the positions TRM holds and does two kinds of work on them:

• Valuation — what each instrument and position is worth now: present value / mark-to-market.
• Risk measurement — how that value could change: sensitivities, scenarios, and value-at-risk.

Together, that's the "value and risk" half of TRM — the counterpart to the Transaction Manager's "deals and positions" half, while the achieved performance of that same book is the Portfolio Analyzer's job.

Valuation

The core is valuation — computing the present value of the deals and positions in the book. This is what turns a portfolio of contracts into a number you can report, mark to market, and feed into hedge accounting. It's driven by discounting future cash flows on the relevant curves, which is exactly why the market data — the curves, the rates, the prices — is the beating heart of the whole thing.

The objects behind the numbers

Every Market Risk Analyzer number is the product of a handful of configuration objects, and knowing them is what lets you answer "where did that NPV come from?":

• Evaluation type — the central one. It controls which market data a calculation uses: on its Market Data Categories tab you assign yield curve types, exchange rate types, FX volatility types and basis spread curve types. SAP states that the evaluation type's settings are required to calculate the NPV of financial transactions and treasury positions, and the Analyze NPV, Calculate Net Present Values, Calculate Market Risk Key Figures and sensitivity apps all let you choose one.
• Valuation rules — how particular products are valued, assigned to the evaluation type.
• Yield curve types — defined in Customizing under General Settings (Define Yield Curve Types) from reference interest rates in ascending order of term; those rates are the curve's grid points. The risk-based NPV is calculated on these curves and can include credit spreads.
• Financial objects — the Analyzers don't read deals directly; each deal is represented by a financial object, created automatically when financial object integration is active (or manually in JBDO).
• Analysis structure — in the Customizing activity Select Analysis Structure Category you choose the generated analysis structure, the static one, or both. With the static structure, market risk key figures are calculated from market risk key figure sets (Manage Market Risk Key Figure Sets) in two steps: a run stores the basic values — NPVs, profits and losses, delta positions per financial object — and CDS queries do the final calculation.

JBRX and TPM60 match the transaction-codes reference. Keep AISGENKF and the batch run apart: AISGENKF sits in the menu under Market Risk Analyzer > Information System > Key Figure Analysis, while the batch calculation for key figure sets is RAEP1_KFSET under Tools.

The risk measures

Beyond "what's it worth," the Analyzer measures "what could happen":

• Sensitivities — how much a position's value moves when a rate or price moves (the FX and interest-rate exposures, quantified). SAP delivers key figures such as basis point value, modified duration, convexity, yield to maturity and the option sensitivities delta, gamma, theta and vega.
• Scenarios / simulation — what the book would be worth under defined market conditions.
• Value-at-risk — a statistical estimate of potential loss over a horizon at a chosen confidence level, via historical simulation, the variance/covariance approach or Monte Carlo simulation.

Results are read in the Analyzer Information System, which lets you navigate a portfolio or risk hierarchy from the total down to single records. These are the numbers that inform risk decisions and feed the limits and reporting the risk function runs on.

How it connects to the Transaction Manager and market data

Upstream sits the Transaction Manager: its deals, via their financial objects, are the population every analysis runs over. The same pricing also serves accounting — NPVs saved with TPM60 feed key-date valuation, which is why the risk view and the accounting view have to reconcile. And every calculation reads the rates loaded through the market data interfaces (TBDM, TBD4, TBEXN) or maintained by hand, as exchange rates are in OB08, selected by rate type and assembled by the evaluation type. A wrong rate type in an evaluation type is a configuration error that produces a plausible number.

Market data is everything

Why it matters

The Market Risk Analyzer produces the numbers that drive decisions and reporting — the valuations in the accounts, the exposures the risk team manages, the measures behind hedging and limits. When those numbers are trusted, the risk function works on facts; when they're suspect, every downstream decision inherits the doubt. Its job is to make the value and risk of the book knowable — accurately, which means with clean data behind it.

Why Market Risk Analyzer numbers mislead

• Bad or stale market data. The number-one cause of wrong output — garbage rates in, garbage risk numbers out, silently.
• Inconsistent data sources. Different rate types or evaluation types feeding different calculations, so numbers don't reconcile.
• Misreading the measures. Treating a statistical measure like value-at-risk as a certainty rather than what it is.
• Config without understanding. Setting up evaluation types, valuation rules and yield curve types without understanding the financial maths they implement, so errors go uncaught.

Feed the Market Risk Analyzer clean, controlled, consistent market data, understand the measures it produces, and it becomes the reliable value-and-risk engine of TRM — the place the whole risk function's numbers come from. Neglect the data, and it becomes a very sophisticated way to be precisely wrong. In a calculation engine, the inputs are the product.

See also market data in treasury systems and what is SAP Treasury and Risk Management.