XI Outbound IDoc different from SAP R/3 Inbound Idoc

[Former Member]

Hi,

I am having a problem in processing an IDoc from XI to SAP.

We have created a custom IDoc, which will be populated in XI and then sent through to SAP R/3, which will then process the information in the IDoc.

I have imported the IDoc into XI and have been able to do the mappings and populate the IDoc from the XI side of things. If I check the IDoc adapter, the populated IDoc leaves XI with the correct information and with multiple segments.

If I now go and check the IDoc that has arrived in SAP R/3, it only contains the first segment. The other segments that were populated in the IDoc that left XI are now not there. Also some of the information that was in the IDoc leaving XI is different to the information in the IDoc that has arrived in XI.

I do not experience the same problem when I populate a standard SAP IDoc.

Has anyone experienced this problem with a custom IDoc before?

Thanks,

Miguel

[Former Member · Accepted solution]

HI Miguel,

For every segment you map see to that you have segment attribute filled in

"segment = some seriel number" in the inbound idoc going from XI.

e.g <E1BP7011_1 SEGMENT=1>

Hope this helps to fix your issue

Regards

Vishnu

[Former Member · Accepted solution]

Hi Vishnu,

For every new segment that I populate, I increase the segment number by 1. So that means that my first segment has a value of 1, my second segement a value of 2, my third segment a value of 3 etc.

I am still experiencing the same problem though. Only that first segment is arriving in SAP R/3.

Any other suggestions perhaps?

Thanks,

Miguel

[Former Member · Accepted solution]

HI Miguel,

can u paste the IDOC XML, let me have a look

Regards

Vishnu

[Former Member · Accepted solution]

Hi Vishnu,

This is the XML file coming out of XI:

<?xml version="1.0" encoding="UTF-8" ?>

- <ZOEM01>

- <IDOC BEGIN="">

- <ZOEM SEGMENT="1">

<RCVPRN>TSYSTEM</RCVPRN>

<VTRNR>5500015146</VTRNR>

<BSTDK>20050305</BSTDK>

<LABNK>00038</LABNK>

<IDNKD>FHA5930-A</IDNKD>

<VRKME>EA</VRKME>

<KWERK>4601</KWERK>

<DFABL />

<BELNR>80084023</BELNR>

<VEMNG>0000000090</VEMNG>

- <ZOEM1 SEGMENT="2">

<EDATUV>20050305</EDATUV>

<EDATUB>20050305</EDATUB>

<WMENG>000000000000000</WMENG>

<FZABR>0000005270</FZABR>

</ZOEM1>

- <ZOEM1 SEGMENT="3">

<EDATUV>20050307</EDATUV>

<EDATUB>20050307</EDATUB>

<WMENG>000000000000260</WMENG>

<FZABR>0000005530</FZABR>

</ZOEM1>

</ZOEM>

</IDOC>

</ZOEM01>

Thanks very much for your help,

Miguel

[Former Member · Accepted solution]

Hi Miguel,

what I see missing is, a number for BEGIN and the control record of the Idoc

check this link and the topic (Fields of the IDoc Control Record)

http://help.sap.com/saphelp_nw04/helpdata/en/ab/bdb13b00ae793be10000000a11402f/frameset.htm

you have to have another segment (just on top of all segments)after the <IDOC BEGIN="1">

e.g (similar to this with appropriate values)

<EDI_DC40 SEGMENT="1">

<TABNAM>EDI_DC40</TABNAM>

<DIRECT>2</DIRECT>

<IDOCTYP></IDOCTYP>

<MESTYP></MESTYP>

<SNDPOR></SNDPOR>

<SNDPRT></SNDPRT>

<RCVPOR></RCVPOR>

</EDI_DC40>

Hope this fixes your problem

Regards

Vishnu

[Former Member · Accepted solution]

Hi Vishnu,

I had tried populating the BEGIN statement with 1 and also without any value, but with both attempts I could not get the IDoc to come through correctly.

The reason that I don't have a Control Record, is because in my Communication Channel I unselected Apply Control Record from the Payload. This allows XI to automatically populate this control record in the IDoc Adapter and then also I do not need to fill in the values.

Your link did highlight to me, a place where I had not checked yet. In transaction IDX2, the metadata for the IDoc is kept. When I went to check my IDoc data in IDX2, it still had an earlier version of the IDoc and therefore the IDoc adapter was not using the correct metadata. I deleted the basic type and recreated it and now the IDoc is being pushed across to SAP R/3 correctly.

Thanks very much for your help and patience!

Regards,

Miguel