PermIds for BKWN.S and EXOR.AS

simon.keel

Hello

I'm looking for the permids for RIC BKWN.S and RIC EXOR.AS. Are those not available?

Thanks

Simon

Jirapongse

@simon.keel

The product has updated EXOR.AS (https://permid.org/1-21910130143).

Jirapongse

@simon.keel

Thanks for reaching out to us.

BKWN.S is a delisted RIC. I found this https://permid.org/1-55835531326 for BKWN.S^D12.

I am unable to find the PermID for EXOR.AS so I will contact the PermID support team to verify it.

simon.keel

Hi @Jirapongse

Do you have any update on this? Also, I cannot find the RICs

5830.T, 5832.T, 5831.T in the permid database.

Is there a way I can contact PermId support team directly?

Thanks and best

Simon

Jirapongse

@simon.keel

I think the PermID has not been updated for the new RICs.

I checked and found those RICs are changed from other RICs.

• 5830.T is from 8385.T (https://permid.org/1-55837429836)
• 5831.T is from 8355.T (https://permid.org/1-55837433292)
• 5832.T is from 8382.T (https://permid.org/1-55837434644)

I will contact the PermID team to verify it.

Another way to contact the PermID team is through the feedback email (permid.feedback@refinitiv.com).

simon.keel

Hi @Jirapongse

Are there any updates on this? Still see the same issues after all, the ticker changes have not been reflected in permid yet.

Thanks for checking and best

Simon

Jirapongse

@simon.keel

I didn't receive any updates from that team.

I have contacted them again for an update.

Sorry for this inconvenience.

simon.keel

Hi @Jirapongse

On another note, Norton LifeLock has changed name and ticker to GEN DIGITAL (GEN), and its still not reflected in

https://permid.org/1-55835348722

Could you please also check with the data team?

Thanks and best

Simon

Jirapongse

@simon.keel

Thank you so much.

I have forwarded it to the product team.

Jirapongse

@simon.keel

I found that https://permid.org/1-55835348722 has been updated.

I am chasing the updates on the following items.

5830.T: (https://permid.org/1-55837429836)
5831.T: (https://permid.org/1-55837433292)
5832.T: (https://permid.org/1-55837434644)
EXOR.AS: https://permid.org/1-21910130143

Jirapongse

@simon.keel

There is an ongoing issue with the automated data ingestion process. Therefore, the product team has manually updated the following PermIDs.

• 5830.T: (https://permid.org/1-55837429836)
• 5831.T: (https://permid.org/1-55837433292)
• 5832.T: (https://permid.org/1-55837434644)

It will take a few more days to handle EXOR.AS (https://permid.org/1-21910130143).

simon.keel

@Jirapongse

Thanks a lot for the heads up, good to see we are moving. I can confirm the fixes. The two outstanding issues I still see from my side are RXO and AMERCO (tickers RXO and UHALB) for which I'm unavailable to find permids for. Here are references:

https://finance.yahoo.com/quote/RXO?p=RXO&.tsrc=fin-srch

https://finance.yahoo.com/quote/UHALB?p=UHALB&.tsrc=fin-srch

Could you also please look into these two?

Thanks a lot for all your help and best

Simon

Jirapongse

@simon.keel

For the new items, we need to wait for the fix of the automated data ingestion process.

david.snowsill

Hi @Jirapongse

Do we have any time timeframe on the fix to the automated data ingestion process?

Jirapongse

@david.snowsill

Sorry. The product team still didn't provide any timeframe for the fix.

I will ask them again for the timeframe.