Question: I am getting "Structure Issue" error during ingest. Why? What can be dane to fix the error?
Answer: When a file is ingested the system needs to understand to which ShareClass, Sub-Fund, and Fund given record is linked. There are several ways to perform the matching, for example a Share Class can be identified by ISIN, and a Fund can be matched by LEI or fund name. Sometimes data from the file being ingested suggest a fund structure which cannot be matched directly to the existing fund structure in the system and this causes 'Fund Structure' issue which would require either a change in the file or amending the fund structure in the system to match the file.
The error message describes the issue providing "Fund Name Including Umbrella" followed by Fund domicile and the link type.
For example a message "System Fund 'Pzena Value Funds plc|IE' can be matched both to Fund: 'Pzena Value Funds plc|IE' by: fndlei,fndnam,shared_sf, and to: 'Pzena Value Funds plc|IE' by: fndnam,shared_sf" means that:
• in the system there is a Fund named "Pzena Value Funds plc" domiciled in IE
• the fund can be linked to two funds from the inbound file:
1) To a fund "Pzena Value Funds plc" domiciled in IE, by it's LEI, Fund Name, and shared Sub-Funds
2) To a fund "Pzena Value Funds plc" domiciled in IE, by Fund Name, and shared Sub-Funds
It means that the first fund can be matched by LEI, but the second fund cannot be matched by LEI.
When we look at the actual data we can see that the file seems to be suggesting that we have two Umbrellas (two different LEI) with the same name and domicile:
In this particular case we also get a validation issue:
LEI '549300FBF4M1MFEE0U65' has incorrect check digits. Expected to end with: '64', but found: '65'.
So the problem is that the file specifies incorrect LEI. This type of issue is usually introduced by Excel when you add a record manually Excel tries to help by bumping values by 1. Unfortunately it does not make sense in case of LEI.
Another example
Message "ShareClass IE000DXLG3T9 can be matched to: IE000DXLG3T9 by: cod_isin,cod_itnscr, but also to: IE000YIQZ0H6 by: cod_itnscr"
Means:
1) The file has record with share class IE000DXLG3T9
2) The system cannot decide which share class would that be in the system, because:
• On one hand there is a share class IE000DXLG3T9 with matching cod_isin and cod_itnscr
• But at the same time there is a share class IE000YIQZ0H6 with matching cod_itnscr
As a result the record from the file you are trying to ingest can be linked to two share classes in the system.
Values of cod_itnscr should be unique in Dataglide. Currently value "IE000YIQZ0H6-USD" is set both to IE000DXLG3T9 and IE000YIQZ0H6.