on 08-02-2010 11:11 AM
Hello Experts,
While importing material records automatically MDM throws a structural exception. When i try importing the same exception file using Import Manager Import status=Ready for Import and the records are imported successfully.
The same Import map and properties when applied on the TEST environment also works properly for both Automatic and Manual import.
Can anyone advice a solution to this.
Thanks in advance,
Elizabeth.
Issue resolved.. Thanks Narendra, your solution worked...Just export and import the same map and save update.
Thanks,
Rohit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Elizabeth,
We are having the same issue and looks like you got the answer, so could you please share the solution with us?
Thanks,
Rohit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Elizabeth
After connecting to the exception file via import manager pls use the save update option for the import map.
Also see the parent exception folder there will be a file which contains useful information and the record on which the structural exception has occured.
hope this helps-Ravi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Elizabeth,
A log/exception file gets created outside Structural Exception folder( i.e in Exception Folder).Please navigate to this folder and manually delete this file (xml format). And, then try posting a new file to ready folder.
Please let me know the result of this trial.
Regards,
Vinay
Edited by: Vinay Simha on Aug 20, 2010 10:12 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Elizabeth.
How many records are you trying to import? If it is huge, try to import less records(say 1 or 2) and check if it is importing in the automatic scenario. Let me know if it works?
Regards
Bala
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jacob,
As you said you are using standard schema of MATMAS05 i would suggest just check your map configuration setting in import manager & source file heading details which you are importing & also check log files at MDS server level will give log details
if your problem not resolved kindly revert back with log details so we can help you
Thanks,
Jignesh Patel
Hi Jacob,
Just check your source file if any new segment occur or segment value is repeating but ideally it should not because in manual import it will work by ignoring this value where during automiz it gives an error
Also i mention in previous thread provide us MDM server log details snaps when structural exception occure along with date and time information so based on log detail we can provide suggestion
Thanks,
Jignesh Patel
Edited by: jignesh patel on Aug 20, 2010 1:43 PM
Hello Elizabeth,
Can you please mention the exact version of your MDM server.
We faced similar problem where the files were moving to exception without any error.
We raised SAP message for this and found that this was the bug in MDM 7.1.04.145.
Which has been fixed in MDM 7.1.04.153.
Regards,
Shaailesh.
Hi,
Structural exception only come when your file structure not in proper format or XSD schema not assign properly
i would suggest just check port setting in that which remote system assign, Map and XML Schema
Hope this will resolved your problem if not then revert back
Thanks,
Jignesh Patel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Elizabeth,
What is your MDM version?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
81 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.