Set up and map LSEG DataScope market data

Modified on Mon, 16 Nov at 5:23 PM

Print

Set up the LSEG DataScope integration (formerly Reuters, then Refinitiv), which imports FX rates, interest rates, commodity prices, energy prices, bond prices, FX option data and fund prices into TS. Then map each rate or price in TS to its code at LSEG.

Before you start

  • Save the DataScope login as a credential in Settings › Credentials. See Credentials and Password.
  • To fetch historical data, the service must be included in your agreement with LSEG.

Steps

Open the integration

  1. Go to Register › Autopilot.
  2. In the list on the Autopilot page, select the DataScope integration.

Fill in the settings

  1. Open the Basic tab.

    The Basic tab of the LSEG Datascope Import integration, with the Credentials, Historical, Filter, General Settings and Intraday sections under Settings

  2. Under Credentials, in CREDENTIAL ID, choose the DataScope credential.

    TS logs the imports automatically, so there's no log setting to select.

  3. Under Historical, select FETCH HISTORICAL if you want to fetch historical data.
  4. For historical data, enter the first and last dates in FETCH FROM and FETCH TO.
  5. Under Filter, select the template to use:

    • FETCH END OF DAY: you get the closing prices. Depending on the currencies and the time you schedule the fetch, you get the closing rate from the last banking day, or from the same day if you fetch late.
    • FETCH INTRADAY: you get a snapshot of the rates available at that moment. For intraday FX rates in a table of their own, see Intraday FX rates.

    The fields each template fetches are listed under Available fields below.

  6. Under General Settings, choose whether to select OVERWRITE ON MERGE:

    • Selected: a rate is overwritten if a new one is available on the next run.
    • Not selected: TS keeps the rates already imported and only fills in the ones missing from the previous run.

Map the market data

On the Mappings tab, each tab holds one kind of market data. In each row, the rate or price in TS is under SystemData, and the LSEG data under Supplier Data:

  • SUPPLIER CODE: the LSEG code, the RIC.
  • BID COLUMN NAME, ASK COLUMN NAME and DATE COLUMN NAME: the LSEG fields TS reads. When they're Not set, TS uses the defaults in the table.
TabBID COLUMN NAMEASK COLUMN NAMEDATE COLUMN NAME
FXBid PriceAsk PriceTrade Date
Market Data (interest rates)Bid PriceAsk PriceTrade Date
CommodityUniversal Bid PriceUniversal Ask PriceTrade Date
BondBid PriceAsk PriceTrade Date
Fund(none)Universal Close PriceTrade Date
For FX rates and interest rates, TS also fetches Universal Bid Price and Universal Ask Price. It uses them when Bid Price and Ask Price have no values.

FX rates

Map FX rates on the FX tab.

The FX tab under Mappings, with USD, EUR and NOK against SEK mapped to the supplier codes SEK=, EURSEK=R and NOKSEK=R, and the column names not set

The PLN rate is a fixing, so enter Close Price in both BID COLUMN NAME and ASK COLUMN NAME.

Interest rates

Map interest rates on the Market Data tab. Some IBOR rates need a slash (/) before the RIC. Some examples:

RateSUPPLIER CODE
STIBOR/STISEK1WDFI=
CIBOR/CIDKK1MD=
EURIBOR/EURIBOR1MD=
PLN IBOR/WIPLN3MD=

Delayed rates

Some fixing rates used at the short end of the yield curve are published one or more days late. Market valuation needs a complete yield curve, so the delay can leave rates missing on the valuation date.

To value your positions every day, set up two separate curves for these fixing rates:

  1. On the Market Data tab, map both curves with the same SUPPLIER CODE.
  2. On the curve for market valuation, enter Today in DATE COLUMN NAME.

    The Market Data tab under Mappings, with the market valuation curve Stibor MV 1W mapped to the supplier code /STISEK1WDFI= and Today highlighted in Date Column Name

Commodities

Map commodity prices on the Commodity tab. To set a close price on a commodity, import its price quoted against every currency you have commodity deals in.

The Commodity tab under Mappings, with diesel NWE in USD mapped as a cash price and two forward prices, with periods CASH, 1CMM and 2CMM

  1. In Currency, choose the currency the price is quoted against.
  2. In Commodity, choose the commodity.
  3. In PERIOD, enter the period:

    • Cash price: enter CASH.
    • Forward prices with one code for each month, such as ULSDCNWEMc1 and ULSDCNWEMc2: enter the period of each code, for example 1CMM and 2CMM.
    • Forward prices with one code for several months, such as MAL 24M: leave it blank.
  4. In MARKET DATA TYPE, choose Commodity.
  5. In SUPPLIER CODE, enter the code:

    • Cash prices: enter a code for each cash price you need, for example MAL0 for Aluminium/USD cash and MALEUR0 for Aluminium/EUR cash.
    • Forward prices for the third Wednesday ahead: enter the code and the number of months, for example MAL 24M for prices 24 months ahead. You won't find this code in DataScope.

    The Commodity tab under Mappings, with aluminium LME in USD mapped as a cash price, MAL0, and as a forward price with no period, with MAL 12M highlighted in Supplier Code

Energy

Map energy prices on the Energy tab. Add one row for each energy and contract.

  1. Select Add.
  2. In Currency, choose the currency, for example EUR.
  3. In Energy, choose the energy, for example SYS, SE3 or SE2.
  4. In MARKET DATA TYPE, choose the type, for example Power.
  5. In SUPPLIER CODE, enter the type of contract followed by the number of tenors, for example M2, Q3 or Y4.

    In the example below, the power prices read Settlement Price in both BID COLUMN NAME and ASK COLUMN NAME.

    The Energy tab under Mappings, with EUR power prices for SYS, SE3 and SE2 mapped to supplier codes such as Q8, Y10, M6, M2, Q3 and Y4, with Settlement Price as the bid and ask column names

Bonds

Map bond prices on the Bond tab.

  1. Select Add.
  2. In SUPPLIER CODE, enter the RIC.
  3. In ISIN, enter the ISIN used in the bond's definition.

    The Bond tab under Mappings, with three securities mapped by supplier code and ISIN, two reading Close Price as the bid and one as the ask

FX options

Map FX option data on the FX Options tab. Add one row for each currency pair, period and option type.

  1. Select Add.
  2. In Base Asset, choose the base currency, for example USD.
  3. In Price Asset, choose the price currency, for example JPY.
  4. In PERIOD, enter the period, for example 1W, 1M or 1Y.
  5. In PUT OR CALL, choose the option type, for example Call.
  6. In MARKET DATA TYPE, choose FxOption.
  7. In SUPPLIER CODE, enter the LSEG code for the currency pair and period, for example USDJPYV1W for USD/JPY 1W, USDJPYV3M for 3M and USDJPYV1Y for 1Y.

    The FX Options tab under Mappings, with USD/JPY calls mapped by period to supplier codes such as USDJPYV1W, USDJPYV3M and USDJPYV1Y, with market data type FxOption

Funds

Map fund prices (NAV) on the Fund tab.

  1. Select Add.
  2. In MARKET DATA DEFINITION, choose the fund.
  3. In SUPPLIER CODE, enter the code.

    The Fund tab under Mappings, with a fund mapped by ISIN and supplier code, and Ask Column Name and Date Column Name not set

Available fields

The LSEG fields each template fetches, for use as column names:

LSEG fieldEnd of day templateIntraday template
RICYesYes
Ask PriceYesYes
Universal Ask PriceYesYes
Bid PriceYesYes
Universal Bid PriceYesYes
Low PriceYesYes
High PriceYesYes
Mid PriceYesYes
Universal Close PriceYesNo
Trade DateYesYes
Expiration DateYesYes
Universal Close Price DateYesNo
Previous Close PriceNoYes
Previous Close DateNoYes
Primary ActivityNoYes
Secondary ActivityNoYes
Bid YieldYesYes
Settlement PriceYesYes
Last PriceNoYes
Close PriceYesNo
Lot SizeYesYes
YieldYesNo
Close YieldNoYes

Related articles

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article

More in Market data

Still need help? Reach people who already know your configuration.

Submit a ticket