on 06-12-2008 12:27 PM
Hi @ll;
I´m facing an interessant error.
In a material master szenario we are sending some Idocs from SAP R/3 4.6c via XI to MS Database.
Today a mapping error occured that was caused by duplicate elements in the Idoc (KNOMAS01)
sample
<E1DATEM SEGMENT="1">
<MSGFN>004</MSGFN>
<MSGFN>004</MSGFN>
<KEY_DATE>20080612</KEY_DATE>
<KEY_DATE>20080612</KEY_DATE>
</E1DATEM>
as you can see all elements are duplicated. The node e.g. E1DATEM only occures once.
There are several idocs of that type sended to XI, but only one of them has that error.
I thought I can fix it by deleting the idoc meta data using idx2, but this didn´t solce the error.
When we have a look at the idoc (we05 or function module IDOC_READ_COMPLETELY) at sender side,
it looks quite normal without duplicate elements
<E1DATEM SEGMENT="1">
<MSGFN>004</MSGFN>
<KEY_DATE>20080612</KEY_DATE>
</E1DATEM>
I tested it alos in our QXI and it worked quite good.
what is causing this error?
how to solve this issue?
I hope anybody has a idea for this strange beahaviour.
Kind regards
Jochen
Hi,
even if the thread is answered:
please check note 1268238 for this problem
regards
Michael
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jochen,
did you ever find a solution for you problem?
It just happened to me pratically in the same way.
Outbound Idoc in ECC 6.0:
Segment ZSMMMWPORICEVEND
TYPE Q001
OBJECT 5679906
TIMESTAMP 20090716114333
Inbound message XML payload after IDOC Adapter transformation, prior to message mapping in PI 7.0
- <ZSMMMWPORICEVEND SEGMENT="1">
<TYPE>Q001</TYPE>
<TYPE>Q001</TYPE>
<OBJECT>5679906</OBJECT>
<OBJECT>5679906</OBJECT>
<TIMESTAMP>20090716114333</TIMESTAMP>
<TIMESTAMP>20090716114333</TIMESTAMP>
It exactly duplicated all the elements in the segment.
Any advice?
Best Regards,
Alessandro
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jochen,
Here E1DATEM segment and field MSGFN ,check the occurences,Mapping and Context.
reg,
suresh.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
jochen,
check ur mapping..
there cud b a duplicate mapping or something similar..
Vishal
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi guys;
sorry it´s such a strange situation and so it´s not easy to understand.
The errors occurs already after the idoc inbound adapter of the XI.
Mapping would be done after that step.
The mapping fails because the input structure (IDOC) is corrupted
it is definitely no error of the mapping.
I just send the same data again and it works well.
obviously it was a temporary problem.
anybody has seen this before?
Kind regards
Hi Jochen,
I am not sure if I understand the situation:
is the xml extract you presented the result of the mapping?
Then the first idea is: error in mapping - probably you already thought of that...
Regards,
Boris
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
76 | |
9 | |
8 | |
7 | |
6 | |
5 | |
5 | |
5 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.