MDM Imprt exceptions

[Former Member]

Hi All,

There is a non-SAP system from where the records come into Inbound ready folder of MDserver. The issue is I could able to see a few xml files in the import exception folder. When I donloaded those XML files and cross checked whether those records are there in MDserver or not, to my surprise the records are there in MDserver! As far as my knowledge whenever a Import exception occurs at a particular record, that record is blocked and the other records are processed. My questions are 1. How the records which are there in the Import exception folders are reaching MDM? 2. Is it possible to clear the exception folder? If so how? 3. How to prevent this?

Thanks,

Thamizharasi N

[Former Member]

Hi Thamizharasi,

Kindly update/close this thread.

Thank you.

[Former Member]

Hi Thamizharasi,

Please find below my answers regarding your queries:

1. How the records which are there in the Import exception folders are reaching MDM?

Answer : The case may be such that the records currently in exception file might have been sent to MDM earlier also and then no exception would have occured and those records got created in MDM. Otherwise system just blocks the records having some exception and does not create them in MDM.

2. Is it possible to clear the exception folder? If so how?

Answer : Yes you can clear exception folder. It is required to examine XML files to check for the reason of Exception, so it is better if you first download those XML files and then delete them from Exception folder.

For deletion, you would require to first delete XML file in ImportX, StructuralX or ValueX folders(under Exception folder of Port) and then delete the summary files from Exception folder. But you should have the authorization to delete the files from FTP folder.

Also as suggested in the above post, you can write a program to automate the deletion.

3. How to prevent this?

Answer : There are many checks that should be taken care of if you want that there should not be any exception. Please find below some of the checks:

• All the data contained in source XML file should be already existing in MDM lookup tables.
• Remote System Key mappings should have been updated for the lookup values to enable automatic value mapping.
• Also if you want to ignore the value exception, then you can set the MDIS unmapped value Handling to Ignore.

Above are some of the checks for Value Exception.

For Structural exception, you need to make sure that your XML Schema is correct and source XML file conforms to the schema and contains valid data values for various fields.

For Structural exceptions you cannot prevent them from happening if there is some inconsistency, but you can control the flow of data after Structural Exception happens.

You need to set "Block on Structural Exception" to No if you want other data coming to port to get processed. Otherwise to block data set this property to Yes.

This setting needs to be done in MDM Console.

I hope this helps. Thank you.

[Former Member]

Hello Thamizharasi N,

You need to check, the import action that has been set in the import map and the uniqueness criteria that has been set.

The records are going into Import Exception because of the this reason, since these records are already present in the repository.

As for the process that you say, that record should be blocked, there are property that you need to set in console, for the port, block on exception or not. If this set, the port will be blocked unless you clear the folder.

One way to get the exact error, is import the file through ports.

To clear the Exception folder, is easy, you can develop a custom FTP program that check the folder and clears it, but while Root cause analysis, you will require the XML's for cross reference and understanding where it went wrong.

[Former Member]

Hi Thami

yeah stil records will reach to mdm   , ya its possible to clear exception folder,

follow the link to reach to exception folder----

http://help.sap.com/saphelp_mdm71/helpdata/en/49/bcad6ac9e359cce10000000a42189c/content.htm

to prevent this error---

check the xml schema uploaded in console and xml imported, both are same or not, is there any field missing or not,  .........

Regards

Nitish