Timestamps of deletions in TRTH market by price data
In market BY price data (level 2) we can use fields LV_TIM_MS or LV_TIM_NS to get the timestamp of updates. However if an update consist of just DELETE updates, these fields are not set and the only time related fields left to use are TIMACT_MS or TIMACT_NS. However sometimes TIMACT get substantially behind LV_TIM and is clearly wrong. See example. How can we determine the timestamp of the DELETE update then? If an order is deleted how can we get the exchange timestamp of the deletions? Example:
7203.T,Market By Price,2018-01-14T23:14:48.223296470Z,+9,Raw,UPDATE,UNSPECIFIED,,,,4742,,1808,0
,,,,Summary,,,,,,,,,6
,,,,FID,17,,ACTIV_DATE,2018-01-14,
,,,,FID,4148,,TIMACT_MS,83688151,
,,,,FID,6516,,BOOK_STATE,3,X
,,,,FID,6517,,HALT_REASN," ",
,,,,FID,6614,,TRD_STATUS,1,"N "
,,,,FID,14269,,TIMACT_NS,23:14:48.151798000, <<<<<< The same as LV_TIM_NS
,,,,MapEntry,,UPDATE,,,,,,76900000A,8
,,,,FID,3427,,ORDER_PRC,7690,
,,,,FID,3428,,ORDER_SIDE,2,ASK
,,,,FID,4356,,ACC_SIZE,2300,
,,,,FID,3430,,NO_ORD,7,
,,,,FID,6527,,LV_TIM_MS,83688151,
,,,,FID,6529,,LV_DATE,2018-01-14,
,,,,FID,3886,,ORDER_TONE," ",
,,,,FID,14268,,LV_TIM_NS,23:14:48.151798000,
,,,,MapEntry,,UPDATE,,,,,,79900000A,8
,,,,FID,3427,,ORDER_PRC,7990,
,,,,FID,3428,,ORDER_SIDE,2,ASK
,,,,FID,4356,,ACC_SIZE,65500,
,,,,FID,3430,,NO_ORD,40,
,,,,FID,6527,,LV_TIM_MS,83688151,
,,,,FID,6529,,LV_DATE,2018-01-14,
,,,,FID,3886,,ORDER_TONE," ",
,,,,FID,14268,,LV_TIM_NS,23:14:48.151798000,
7203.T,Market By Price,2018-01-14T23:14:58.370949512Z,+9,Raw,UPDATE,UNSPECIFIED,,,,4742,,1824,0
,,,,Summary,,,,,,,,,6
,,,,FID,17,,ACTIV_DATE,2018-01-14,
,,,,FID,4148,,TIMACT_MS,83688151,
,,,,FID,6516,,BOOK_STATE,3,X
,,,,FID,6517,,HALT_REASN," ",
,,,,FID,6614,,TRD_STATUS,1,"N "
,,,,FID,14269,,TIMACT_NS,23:14:48.151798000, <<<<<< 10 secs in the past
,,,,MapEntry,,ADD,,,,,,B-M+C,8
,,,,FID,3427,,ORDER_PRC,,
,,,,FID,3428,,ORDER_SIDE,1,BID
,,,,FID,4356,,ACC_SIZE,100,
,,,,FID,3430,,NO_ORD,1,
,,,,FID,6527,,LV_TIM_MS,83698299,
,,,,FID,6529,,LV_DATE,2018-01-14,
,,,,FID,3886,,ORDER_TONE,MA,
,,,,FID,14268,,LV_TIM_NS,23:14:58.299739000,
7203.T,Market By Price,2018-01-14T23:14:58.826936990Z,+9,Raw,UPDATE,UNSPECIFIED,,,,4742,,1840,0
,,,,Summary,,,,,,,,,6
,,,,FID,17,,ACTIV_DATE,2018-01-14,
,,,,FID,4148,,TIMACT_MS,83688151,
,,,,FID,6516,,BOOK_STATE,3,X
,,,,FID,6517,,HALT_REASN," ",
,,,,FID,6614,,TRD_STATUS,1,"N "
,,,,FID,14269,,TIMACT_NS,23:14:48.151798000, <<<<<<<<< Still 10 sec in the past, no other timestamp to be used for DELETE update
,,,,MapEntry,,DELETE,,,,,,B-M+C,0
7203.T,Market By Price,2018-01-14T23:15:02.263153413Z,+9,Raw,UPDATE,UNSPECIFIED,,,,4742,,1856,0
Best Answer
-
This is an issue on Elektron feed and the fix has been scheduled for mid-May.
The current Elektron Market By Price data for Tokyo Stock Exchange does not provide a timestamp for delete orders, and it reflected on TRTH as a result.
0
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛