Looking for exchange timestamp for Osaka (i.e. JGBRU5) when subscribing market by price domain

wanted to ask when we subscribe to market by price domain we do not provide the set of fields that we require in the output of refresh message /update message
so if we want to get the exchange related timestamp that those fields must be already present in the existing refresh/update messages
we were told SALTIM_MS is the FID for the exchange timestamp, however this FID seems to be not available via market by price domain.
Is there any FIDs that we will give us the exchange timestamp when we use market by price domain ?
below is the sample Refresh message for JGBRU5 ,I dont see SALTIM_MS field have dome of the timestamp fields that we get in refresh message
RefreshMsg
streamId="5"
domain="MarketByPrice Domain"
solicited
state="Open / Ok / Unsupported view type / '*All is well'"
itemGroup="00 03"
permissionData="03 00 17 48 90 c0"
name="JGBRU5"
nameType="1"
serviceId="23"
serviceName="REUTERS_OTHER_INFO"
Payload dataType="Map"
Map totalCountHint="166"
SummaryData dataType="FieldList"
FieldList FieldListNum="32767" DictionaryId="1"
FieldEntry fid="1" name="PROD_PERM" dataType="UInt" value="4890"
FieldEntry fid="3" name="DSPLY_NAME" dataType="Rmtes" value="10YJGB SEP5"
FieldEntry fid="15" name="CURRENCY" dataType="Enum" value="392"
FieldEntry fid="17" name="ACTIV_DATE" dataType="Date" value="06 JUN 2025"
FieldEntry fid="259" name="RECORDTYPE" dataType="UInt" value="34"
FieldEntry fid="1709" name="RDN_EXCHD2" dataType="Enum" value="113"
FieldEntry fid="3423" name="PR_RNK_RUL" dataType="Enum" value="1"
FieldEntry fid="3425" name="OR_RNK_RUL" dataType="Enum" value="2"
FieldEntry fid="3694" name="MNEMONIC" dataType="Rmtes" value="01"
FieldEntry fid="4148" name="TIMACT_MS" dataType="UInt" value="48768649"
FieldEntry fid="5357" name="CONTEXT_ID" dataType="Real" value="4848.0"
FieldEntry fid="6401" name="DDS_DSO_ID" dataType="UInt" value="4347"
FieldEntry fid="6480" name="SPS_SP_RIC" dataType="Ascii" value=".[SPSLVATK1TK202"
FieldEntry fid="6516" name="BOOK_STATE" dataType="Enum" value="1"
FieldEntry fid="6517" name="HALT_REASN" dataType="Rmtes" value="(blank data)"
FieldEntry fid="6519" name="MKT_OR_RUL" dataType="Enum" value="1"
FieldEntry fid="6542" name="LEG_L2_RUL" dataType="Enum" value="(blank data)"
FieldEntry fid="6614" name="TRD_STATUS" dataType="Enum" value="1"
FieldEntry fid="14269" name="TIMACT_NS" dataType="Time" value="13:32:48:649:000:000"
FieldListEnd
SummaryDataEnd
MapEntry action="Add" key dataType="Buffer" value="3133 392E 3138 41 139.18A"
dataType="FieldList"
FieldList FieldListNum="32767" DictionaryId="1"
FieldEntry fid="3427" name="ORDER_PRC" dataType="Real" value="139.18"
FieldEntry fid="3428" name="ORDER_SIDE" dataType="Enum" value="2"
FieldEntry fid="3430" name="NO_ORD" dataType="UInt" value="1"
FieldEntry fid="3886" name="ORDER_TONE" dataType="Rmtes" value="(blank data)"
FieldEntry fid="4356" name="ACC_SIZE" dataType="Real" value="2.0"
FieldEntry fid="6527" name="LV_TIM_MS" dataType="UInt" value="45033773"
FieldEntry fid="6529" name="LV_DATE" dataType="Date" value="06 JUN 2025"
FieldListEnd
MapEntryEnd
MapEntry action="Add" key dataType="Buffer" value="3133 382E 3930 41 138.90A"
dataType="FieldList"
FieldList FieldListNum="32767" DictionaryId="1"
FieldEntry fid="3427" name="ORDER_PRC" dataType="Real" value="138.9"
FieldEntry fid="3428" name="ORDER_SIDE" dataType="Enum" value="2"
FieldEntry fid="3430" name="NO_ORD" dataType="UInt" value="1"
FieldEntry fid="3886" name="ORDER_TONE" dataType="Rmtes" value="(blank data)"
FieldEntry fid="4356" name="ACC_SIZE" dataType="Real" value="1.0"
FieldEntry fid="6527" name="LV_TIM_MS" dataType="UInt" value="45469501"
FieldEntry fid="6529" name="LV_DATE" dataType="Date" value="06 JUN 2025"
FieldListEnd
MapEntryEnd
Answers
-
Thank you for reaching out to us.
This forum is dedicated to software developers using LSEG APIs. The moderators on this forum do not have deep expertise in every bit of content available through LSEG products, which is required to answer content questions such as this one.
The best resource for content questions is the Helpdesk support team, which can be reached by submitting queries through LSEG Support. The support team will either have the required content expertise ready available or can reach out to relevant content experts to get the answer for you.
Please include the URL of this discussion in your raised question to prevent it from being redirected back to this Q&A forum.
0 -
Understood.
Thanks for your help. Will do.0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 37 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 697 Datastream
- 1.5K DSS
- 632 Eikon COM
- 5.2K Eikon Data APIs
- 12 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 4 Trading API
- 2.9K Elektron
- 1.4K EMA
- 256 ETA
- 563 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 281 Open PermID
- 46 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 749 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 27 DACS Station
- 122 Open DACS
- 1.1K RFA
- 107 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 96 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛