cancel
Showing results for 
Search instead for 
Did you mean: 

duplicate elements in Idoc

Former Member
0 Kudos

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

Accepted Solutions (0)

Answers (5)

Answers (5)

Former Member
0 Kudos

Hi,

even if the thread is answered:

please check note 1268238 for this problem

regards

Michael

Former Member
0 Kudos

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

Former Member
0 Kudos

Hi Jochen,

Here E1DATEM segment and field MSGFN ,check the occurences,Mapping and Context.

reg,

suresh.

Former Member
0 Kudos

Hi @ll

as I said before, it seems to be a temporarly error of the idoc adapter.

It interprets the data incorrect.

the ouput of the SAP R/3 was different from the Inbound of the XI

thanks to all for helping

Kind regards

Jochen

Former Member
0 Kudos

jochen,

check ur mapping..

there cud b a duplicate mapping or something similar..

Vishal

Former Member
0 Kudos

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

Boris_Rubarth
Product and Topic Expert
Product and Topic Expert
0 Kudos

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