problem about nasdaq basic RIC trade_date

Hi, everyone,
I subscribed code list RICs at nasdaq basic market's pre-market time. But seen from logs from RefreshMsg, I found FID TRADE_DATE is always the date of previous trade date, which is not corret. So How can I get the accurate premarket TRADE_DATE ? Below is my log
Many thanks, expecting your reply.
Best Answer
-
Hi @wangfugen just to add to @Umer Nalla answer below. TRADE_DATE is the trade date of thetrade in TRDPRC_1 - pre-market trades (ie those outside the normal Nasdaq trading session) are considered non-last eligible. Which means they dont go through the TRDPRC_1 trade stack and as such the TRADE_DATE is still showing from the previous day.
To get the pre-market trades you need to look at the non last eligible trade stack, which is in IRGPRC. You will need to look at the field IRGDATE (4349) to see the premarket trade date info (equally IRGTIM_MS for the time, IRGVOL etc etc too.
0
Answers
-
Hi @iscas.wang
The TRADE_DATE field is 'The date of the value in the field TRDPRC_1'.
If you believe any data is incorrect or the field is not providing the information you require, then I recommend you raise a ticket with our Content Helpdesk who can help you identify the correct field(s) that meets your requirements. Please ensure you raise a Content type ticket - not an API related one.
0 -
Hi @iscas.wang just to add to @umer.nalla answer below. TRADE_DATE is the trade date of thetrade in TRDPRC_1 - pre-market trades (ie those outside the normal Nasdaq trading session) are considered non-last eligible. Which means they dont go through the TRDPRC_1 trade stack and as such the TRADE_DATE is still showing from the previous day.
To get the pre-market trades you need to look at the non last eligible trade stack, which is in IRGPRC. You will need to look at the field IRGDATE (4349) to see the premarket trade date info (equally IRGTIM_MS for the time, ORGVOL etc etc too.
0 -
@Tim Smith
Thanks for your quick reply. According to your answer, I confirmed the two fields (IRGDATE, IRGTIM_MS) . More question, what about the fields for post-market? Thanks
0 -
Hi @iscas.wang. Same for post-trade (after hours). They are not last eligible so go through the same set of fields as the pre-trading session.
Tim
0
Categories
- All Categories
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 33 Data Model Discovery
- 682 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.8K Refinitiv Data Platform
- 622 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
- 84 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛