Managing Unknown Results in Your Position Limits Dashboard


There are a few reasons you may experience Unknowns in your Position Limits dashboard, and in this article, we outline some of the key causes and resolutions to bring your environment back to health. 

Data Issues

The first point of action is to check the Missing Data, as this will highlight properties or values that are missing or need to be remapped.


Incorrect Contract Code

You may receive an Unknown where the CommoditySymbol you are providing for a specific contract from your data provider does not match the contract code that FIA Tech has for this specific contract. To locate the list of CommoditySymbols used by FIA Tech, please click on the FIA tab within the main Position Limits dashboard. From here, you will see a list of contract codes for a specific market (the system is set to default to AFET). By clicking on the Exchange (drop-down on the left-hand side), you can select the particular operating MIC you are looking for and will then be able to see the contract codes that are associated with that MIC. 


In order to correct this incorrect data, we recommend correcting the CommoditySymbol that is being provided in your position file to match that of FIA Tech. However, if you are unable to update the positions file with the correct CommoditySymbol, you could create an override that applies when a Market is "XXXX" to then override the CommoditySymbol you are currently providing to the correct CommoditySymbol that FIA Tech has designated for this contract. Please see the below example:


Duplicate Unknowns Caused by One Missing CommoditySymbol

As the rules are connected and aggregate into each other one incorrect CommoditySymbol can prevent other rules from being calculated, so you may see many unknowns due to one CommoditySymbol being incorrect. This is why the first step should also be to solve any items in Missing Data.

Incorrect MIC

The Market input value should be populated with the MIC for the primary market that the instrument is traded on. Please ensure that you provide the segment MIC in your positions file. 

Example of how Market is defined in the XML file:


To ensure that you are mapping to the correct MIC, please refer to the Position Limits: Exchange Coverage page, which you can access here. If the incorrect market is supplied, FundApps will not be able to match the appropriate CommoditySymbol.

When providing the MIC in your positions file, you will need to supply the segment MIC for the specific contract it is traded on. However, you may notice that the Position Limits dashboard will list the exchange as the operating MIC as FIA Tech map based on the operating MIC. For example, the above MIC will be supplied as "XMRV" in the positions file but is highlighted as "BMEX" in the dashboard.


Limit Effective From is Missing

We periodically scrape contract trading calendar data that is published by the relevant exchanges. If you see an unknown with the message “Limit Effective From is Missing”, this is usually caused by an issue with the calendar data. Please contact FundApps Support, and we will investigate these Unknowns for you.


Some exchanges require an input value for OpenInterestAllMonths, and Unknowns will appear if this is not supplied. It can be sourced via exchange websites, similar to here.

As always, we highly recommend providing all properties directly in your position file to ensure data integrity and futureproofing. However, if a tactical solution is required in the interim, an override could be used to temporarily provide this information. 

Was this article helpful?
0 out of 0 found this helpful
Share article