What may be happening is that you have used an FMS group to redirect the AppxIO files (in other words, the AppxIO files are not in their usual location when you do the export). That means that the Portdata files are not in their usual location either. When Appx tries to import (using your Oracle FMS group), it can't find the Portdata files (thus the File Does Not Exist error).

If that is the case, this is easy to fix. Find the FMS group that holds your AppxIO files (let's call that the APPXIO FMS group) it has an FMS type of 1. Make a note of the FMS Path for that FMS group. Now find your Oracle FMS group (let's say that one is named ORACLE) and it has an FMS type of 5. Now make a new FMS group (type 1 this time), but give it the same name as your ORACLE FMS group. In this new ORACLE (type 1) FMS group, enter the FMS path that you wrote down from the APPXIO FMS group.

That should take care of the problem.

The root of the problem is that Portdata files are always AppxIO files - when you try to import from Portdata into Oracle, Appx is using the ORACLE FMS group to find the Portdata files. Since you don't have a type 1 FMS group named ORACLE, Appx is looking in the default location for the Portdata files - and they're not there. Creating a new type 1 FMS group with the same names as your type 5 ORACLE group will give Appx a way to find the Portdata files.