ek.get_data returns wrong informations

vuk.magdelinic
vuk.magdelinic
in Eikon Data APIs

Hi,


Our process of pulling data is to pull TR.FiIssuerOrganization using ISIN of a security via ek.get_data and then use that org_id to perform another ek.get_data call to get all the fields needed for that organization.

However, we've been getting some cases where the information seemed incorrect. I'll be listing out several case examples:

1. ISIN="KR6066261AA9"

- Below is the data from isin pull

- ['KR6066261AA9', '165496', 'LGCRPS', 'LGCRP', 'S&I CORP']

- Below is the data from org_id pull

- ['165496', '3 Banken Portfolio-Mix A', '', 'http://www.sni.co.kr/', '82237731114', '', '', '', '', '', '', '', '', None, '', '', '4295881132', 'Austria', '2002-01-01', None, '', '', 'Service Company', 'Service - Other']

As you can see, the get_data pulled a Fund profile instead of S&I Corp.


2. ISIN=

- Below is the data from isin pull

- ['CND100045HT7', '75877', 'SHSHI', 'GEFRN', 'SHANGHAI SHIMAO CO LTD']

- Below is the data from org_id pull

- ['75877', 'Shanghai Shimao Co Ltd', 'http://www.shimaoco.com', '862120203388', '862120203399', 60102030, '600823', 15979976791.86, 2615, '', 'AAA', 'Real Estate Development', '', '2021-12-31', 149304753980, '4297714707', 'China', '1992-07-01', None, '', '', 'Other Financial', 'Real Estate Investment Trust']

As you can see, The ticker information of one doesn't match the other. (SHSHI != 600823)


3. ISIN="SGXF51098246"

- Below is the data from isin pull

- ['SGXF51098246', '42122', 'HPPS', 'HLDIN', 'HOTEL PROPERTIES LTD']

- Below is the data from org_id pull

- ['42122', 'Hotel Properties Ltd', 'https://www.hotelprop.com.sg/', '6567345250', '6567320347', 25301020, 'H15', 1788711560.93, '', '', '', 'Hotels, Resorts & Cruise Lines', None, '2020-12-31', 3388229000, '5042257290', 'Singapore', '1980-01-28', None, '', '', 'Service Company', 'Lodging']

As you can see, The ticker information of one doesn't match the other. (HPPS != H15)


I would consider Case2 and Case3 to be similar but these are the three cases we've observed so far and would like to know how we can pull the correct information.


Thank you so much for your time.

Tagged:

Best Answer

  • Alex Putkov.1
    Alex Putkov.1
    Answer ✓

    @vuk.magdelinic

    1. If you don't restrict the type of input, you're running the risk of ambiguity, where the same exact code may refer to multiple entities, as is the case in this example. 165496 is the Org ID for S&I Corp, and it's also WKN (German Wertpapierkennnummer) for 3 Banken Portfolio-Mix T fund. To restrict the input type to Org ID, append "@orgid" to the Org ID number. E.g.

    ek.get_data('165496@orgid', ['TR.CommonName'])

    returns "S&I Corp".

    2. You didn't specify the fields you're using, but I'm guessing you're not using the same field names in the 1st and 2nd request, as the 1st request returns the fixed income ticker for the bond with ISIN CND100045HT7, whereas the 2nd request returns the exchange ticker for the issuer's common stock.

    3. Same as #2.

Categories