ERPi ships with a Master and Work Repository that you can import into the Master/Work Repository used specifically for ERPi.
There should not be a need to export and import the scenarios from one environment to another.
Thanks JeffJon, but what I need migrated is the custom open interface adapters I have built, i.e. the Others source system type in ERPi.
That error is raised due to an object in the import file having an identifier which already exists in the target repository.
You can manually change the "com.sunopsis.dwg.dwgobj.SnpImportRep" object section of the import XML file to use a unique identifier.
which is the ID of your scenario?
in which mode are you importing?
I would check in TEST work rep which object has the same id.
For that you can query the database tables.
The Internal ID of the scenario I am going to import is 64501.
I have tried importing in all modes, INSERT, UPDATE and INSERT & UPDATE
There are no scenarios in the TEST environment, the scenario I want to import will be the first one.
UPDATE on this issue for those that are interested. What I ended up doing was re-numbering the Work Repository in TEST to a different ID number. I was then able to import all the scenarios I needed from DEV and so far ERPi is communicating fine with ODI so I don't think the IDs of 500 & 501 are required.
Well when ERPI/FDMEE is installed IDs are automatically set to 500/501 so you can avoid issues when applying patches, etc.
64501 has not to represent an scenario in your target rep. It may be another object you created and unfortunately ID corresponds with the one you are importing. If you query your target rep database you can find which is the object with ID 64501.