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
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 690 Datastream
- 1.4K DSS
- 629 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 559 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
- 279 Open PermID
- 45 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 715 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
- 121 Open DACS
- 1.1K RFA
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 95 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛