Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Interface "PortfolioValuation"

Usage & Contents

used to produce

  • Asset Breakdowns AB001-AB007

  • Asset Structures AS003, AS004

contains

  • benchmark level key figures (duration etc.)

  • instrument level position for benchmark

Reporting Business Logic

  • for comparison with portfolio all same logic needed as stated under PortfolioValuation

Usage & Contents

used to produce

  • Asset Breakdowns (e.g. AB001-AB007)

  • Asset Structures (e.g. AS003, AS004)

  • Position Lists (e.g. PL001, PL002)

contains

  • portfolio level key figures (marketValue, duration etc.)

  • instrument level position for portfolio

Reporting Business Logic

  • aggregation from position to sector/portfolio level of simple and weighted figures

  • top n / bottom n, filtering, sorting

  • build hierarchical view from segment data

  • translation of segment labels

Path

/portfolio/valuation

Parameters

portfolioId*

string

The id of the portfolio (or consolidation) in the data source

reportingDate*

string (date)

The business date the valuations are queried for.

segmentationDate

string (date)

Date as of the instruments are segmented and the segmentation definition is valid (equals reportingDate if omitted)

Example call

/portfolio/valuation?portfolioId=E0002&reportingDate=2019-03-31&segmentationDate=2019-06-30

Schema

Consistency Rules

The following rules should be adhered to by any response and will eventually be checked when consuming a response:

Consistency Rules
  • [P01] All figures used within a valuation object must be defined in the figures declaration

  • [P02] All figures having an aggregationMethod <> none have to match the top level figure value when aggregating up the positions

  • [P03] All segmentationIds referenced within positions must be defined in the Segmentations call

  • [P04] All segmentIds referenced within positions must be defined under the corresponding segmentation in the Segmentations call

  • [P05] All segmentIds referenced within positions must be "leaf-level" segments within the segmentation (no more child segments)

Interface "BenchmarkValuation"

Path

/

benchmark

portfolio/valuation

Parameters

benchmarkId

portfolioId*

string

The id of the

benchmark

portfolio (or consolidation) in the data source

reportingDate*

string (date)

The business date the valuations are queried for.

segmentationDate

string (date)

Date as of the instruments are segmented and the segmentation definition is valid (equals reportingDate if omitted)

Example call

/

benchmark

portfolio/valuation?

benchmarkId

portfolioId=

B0002

E0002&reportingDate=2019-03-31&segmentationDate=2019-06-30

Schema

Response

Interface "BenchmarkValuation"

Usage & Contents

used to produce

  • Asset Breakdowns AB001-AB007

  • Asset Structures AS003, AS004

contains

  • benchmark level key figures (duration etc.)

  • instrument level position for benchmark

Reporting Business Logic

  • for comparison with portfolio all same logic needed as stated under PortfolioValuation

Consistency Rules

The following rules should be adhered to by any response and will be checked when consuming a response:

  • [B01] All figures used within a valuation object must be defined in the figures declaration

  • All figures having an aggregationMethod <> none have to match the top level figure value when aggregating up the positions

  • [B02] All segmentationIds referenced within positions must be defined in the Segmentations call

  • [B03] All segmentIds referenced within positions must be defined under the corresponding segmentation in the Segmentations call

  • All segmentIds referenced within positions must be "leaf-level" segments within the segmentation (no more child segments)

Path

/benchmark/valuation

Parameters

benchmarkId*

string

The id of the benchmark in the data source

reportingDate*

string (date)


segmentationDate

string (date)


Example call

/benchmark/valuation?benchmarkId=B0002&reportingDate=2019-03-31&segmentationDate=2019-06-30

Schema

Response