Hi Eric
I had the same issue recently, I resolved by loading the required hierarchy into a 7.6 environment using the legacy version then exporting that hierarchy with the latest version of MxLoader, this gives you the correct PARENT attribute values for the FAILURELIST object. Then load that into your MAS environment, assuming you are loading into an empty environment the first FAILURELIST value generated in the db should be 2 and this should match up with the PARENT values you exported from the 7.6 environment to maintain the same hierarchy.
I appreciate you may not have the additional 7.6 environment but that was the easiest way to resolve that I could think of. The other potential solution is an automation script on an inbound MIF FAILURELIST message which picks up the FAILURELIST id for the failurecode in the message and uses that to populate the PARENT field.
Hope this helps, Phil
------------------------------
Phil Naylor
MACS EU
------------------------------