What is the timezone for the field "LV_DATE" in MBP data
In my MbP subscription, I have received an update message with different value in field "ACTIV_DATE" and "LV_DATE", are they expected to be in the GMT timezone? Any possible reason for the inconsistency?
RespMsg : modelType="MarketByPrice" hMask="81" iMask="0" respType="Update" respTypeNum="INSTRUMENT_UPDATE_UNSPECIFIED"
Manifest : hMask="1" seqNum="47158" filteredCount="0" filteredTime="0"
Payload :
Map hMask="0" iMask="6" keyType="DataBuffer::Buffer" dataDefCount="0" count="6" totalCountHint="0"
SummaryData :
Fieldlist hMask="0" cMask="0" dictId="0" fieldListNum="0" count="3" defID="0"
FieldEntry mask="0" fieldID="17" fieldName="ACTIV_DATE" dataType="DataBuffer::Date" value="30 MAR 2020"
FieldEntry mask="0" fieldID="4148" fieldName="TIMACT_MS" dataType="DataBuffer::UInt" value="78300228"
…...
MapEntry hMask="0" action="Add" key="18900.000000000B" keyDataType="DataBuffer"
Fieldlist hMask="0" cMask="0" dictId="0" fieldListNum="0" count="7" defID="0"
FieldEntry mask="0" fieldID="3886" fieldName="ORDER_TONE" dataType="DataBuffer::StringRMTES" value="0"
FieldEntry mask="0" fieldID="3428" fieldName="ORDER_SIDE" dataType="DataBuffer::Enumeration" value="1:BID"
FieldEntry mask="0" fieldID="6527" fieldName="LV_TIM_MS" dataType="DataBuffer::UInt" value="78300228"
FieldEntry mask="0" fieldID="3427" fieldName="ORDER_PRC" dataType="DataBuffer::Real" value="18900"
FieldEntry mask="0" fieldID="4356" fieldName="ACC_SIZE" dataType="DataBuffer::Real" value="1"
FieldEntry mask="0" fieldID="3430" fieldName="NO_ORD" dataType="DataBuffer::UInt" value="1"
FieldEntry mask="0" fieldID="6529" fieldName="LV_DATE" dataType="DataBuffer::Date" value="31 MAR 2020"
Best Answer
-
Hi @kc.lam
I am not a content expert, but from a technical perspective the Summary Data field ACTIV_DATE applies to the whole of the order book, whereas the LV_DATE field only applies to the individual order book entry.
According to the documentation,
ACTIV_DATE + TIMACT_MS represents the last activity date + time (GMT) for any order on the instrument’s order book
LV_DATE + LV_TIM_MS represent the date + time (GMT), an aggregated MBP row was most recently updated.
My guess is that Activity represent trading activity, whereas Update means changes to an order book row such as change in total number of shares (ACC_SIZE) in a row or number of orders in a row (NO_ORD) and so on...
But as I am not a content expert, I recommend you check this with the Content team via MyRefinitiv.
0
Answers
Categories
- All Categories
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 684 Datastream
- 1.4K DSS
- 613 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 248 ETA
- 552 WebSocket API
- 37 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 629 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
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 191 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 86 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛