Skip to Content
avatar image
Former Member

MDM 7.1: StructuralX but not action required when handling exception

When I run MECCM, a structuralX exception is created, so I go into the exception Port, fixed the error, saved the mapping and imported the data. The exception file was deleted.

Again, I run the transaction program for the exact same material, and AGAIN, a structuralX exception was created. But when I go into the exception Port in Import Manager, without making ANY mapping changes, the file was automatically "Ready for Import".

So my question is, if the 2nd time around, when I didn't need to make any changes to the mapping and the file was ready for import, why was an exception created?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Jul 08, 2009 at 06:47 PM

    I was using an import map that was Transported from a different repo, and that seemed to be causing the problem.

    Anyone else run into the issue where transported mappings do not work in the new repository?

    Add comment
    10|10000 characters needed characters exceeded