MDIS - Structural Exception

[Former Member]

We are using SAP MDM 5.5. SP6

We are having some issues with our development repository. This repository is not used every day but when we have some testing this is used.

While using MDIS and loading the files, some files will to go exception -> StructuralX folder. When I looked at the console -> Reports, the message was

u201CSome portions of this import map are out of date. Solution: Please, Launch the Import Manager GUI, preferably using the original source file that the map was generated for, otherwise the same source file and Save Update [File->Save Update] the mapu201D

When I use the exception file in the Import manager File->Save Update this file works. But same issue was there with some other file. If we use same File->Save Update for that file then it works.

This issue is not with every files but some files and they are in exception.

What is the permanent solution to this problem?. This issue was not there earlier. We canu2019t handle manually every files has this issue

Steve.

[Former Member · Accepted solution]

Hi Steve,

This is true that Save Update option Saves an update of the current map.

This issue is not with every files but some files and they are in exception.

I would suggest, say you have single file in structure exception folder, take a copy of this file and put it on desktop. So that you have same two files one in exception folder and other on your desktop. Now open file which is in structure Exception folder with MDM Import manager using Port(Exception) and Remote System. Now after mapping missing fields and values go for SAVE UPDATE option so that it saves the update of the current map.

Now take a copy of this desktop file and put it there in Ready folder and check is it going to import successfully or still going to exception folder using MDIS. If it is still going to exception folder then open this same file with Import Manager using option open existing map and go for SAVE option rather than SAVE UPDATE, this will overwrite your this existing map with this new map. Make sure that this exception file contains all the fields which were present earlier. On a safer side, you can go for SAVE option but not on the existing map but can do file save as New Map so that your existing map does not effected. Now using console give this new map name in your port and check. This will resolve your problem.

Regards,

Mandeep Saini

[Former Member]

Hi steve

Structural exceptions happen if the schema associated to port and the incoming file for import has any differences like field length has been changed, new field type introduced.... so on.

You need to connect to files in exception folder and save update the map to resolve all issues. Permanent solution will be to connect to a source file which contains all fields as in repository and save update the map in one go instead of doing this in bits and pieces.

BR-

Ravi

[former_member205403]

Hi Steve,

Issue that you are facing is already addressed by SAP in the Note 1290407 - Error: "Some portions of this import map are out of date..."

Please go through the Note for the solution and revert if you have any query.

Regards,

Shiv

[Former Member]

Hi,

Structural exception usually occurs when any file contains new field which was not used before in the import map.

To eliminate this issue, you can remove the the new field from the souce file if you do not require .

If you really require the field, open the map with souce file with which you have developed the map and map the required

field and finally use save update option.There is no other alternative solution in MDM 5.5.

Due to the inconstiencies in the import map, some fields are geting unmapped in the import map eventhough those fileds are mapped in the previous imports.In this case also we will get structural exception.SAP suggests to use save update option in MDM 5.5.

Thanks,

Narendra