Problem with an Receiver Idoc adapter

[Former Member]

Hi.

We have just went from XI 3.0 to PI.7.10.

The Receiver idoc adapter is set up in the same way as it was in XI.

The problem is when two different interfaces runs at the same time I got data into the DC40-record which not belongs too this idoc but from an another interface/idoc.

The idocs are different messagetypes.

In this case the field MESCOD which belongs to one of the idocs also appered in the idoc where the field MESCOD not should be used.

Any idea whats wrong ?

/Per-Arne

[Former Member · Accepted solution]

>>I got data into the DC40-record which not belongs too this idoc but from an another interface/idoc.

You mean EDI_DC40 in message mapping or in the receiver SAP system?

If it is in message mapping,then you need to re-check that.

If you are getting in receiver SAP system,then check sxmb_moni in XI side and see which Receiver IDOC adapter is actually triggered by which interface,its possible that configuration may have got mixed up and its triggering the wrong receiver communication channel.

Thanks

Aamir

[Former Member · Accepted solution]

Thanks.

Checked sxmb_moni as you said.

In the OutboundBinding-node I can see the right idocadapter is used

where 'Apply Control Record Values from Payload' is enabled.

<SAP:ChannelName>IDOC_INBOUND_U01_110</SAP:ChannelName>

In the IdocOutbound-node I can see the message code 'EXT' which should'nt be there.

- <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">

<SAP:TABNAM>EDI_DC40</SAP:TABNAM>

<SAP:MANDT>001</SAP:MANDT>

<SAP:DOCREL>710</SAP:DOCREL>

<SAP:DOCNUM>0000000000033474</SAP:DOCNUM>

<SAP:DIRECT>2</SAP:DIRECT>

<SAP:IDOCTYP>OILLDD01</SAP:IDOCTYP>

<SAP:CIMTYP />

<SAP:MESTYP>OILLDD</SAP:MESTYP>

<SAP:MESCOD>EXT</SAP:MESCOD>

Too be more specific about the interface.:

I got one file in from a file adapter and out of that file I produce two idocs into R3 whit

two different idocs-adapters.

I think you are right about that the configuration may be mixed up.

Any idea of what I can do?

It may be an PI 7.10 bug ?

Shall I delete all config objects and so set config up from scrach again ?

/Per-Arne

[Former Member · Accepted solution]

Hi and thanks for your help.

I solved the problem with a workaround in the Repository Mapping.

i.e. I manually filled out the fields in EDI-DC40 record. MESCOD = ' ' in the idoc whitch failed.

But I still mea there is a problem with the idoc-adapter in PI 7.10.

/Per-Arne

[Former Member]

Hi,

Have you imported the IDOC meta data in IDX2 of your ABAP Stack of PI 7.10?

Regards,

Sarvesh Desai

[Former Member]

Thanks.

I use a Logical System(LS).

When I got the probleme I created a new idocadapter to take care of the idoc with MESCOD and in this adapter I disabled the "Apply Control Record Values from Payload". The other idoc (without MESCOD)I use an adapter where "Apply Control Record Values from Payload" are enabled.

In IDX2 I can see all messagetypes I use so that looks ok.

/Per-Arne

[Former Member]

Hi,

Are you using a Party at the reciever side or is it a Logical System(LS). Have you tried by enabling the " Apply Control Record values from Payload" in the IDOC receiver channel?

Regards,

Sarvesh Desai

[Former Member]

Hi Per-Arne,

Could you please check your partner profile settings. Make sure that for the IDOC which does not expect the MESCOD, in Partner profile please remove the Message Code.

Regards,

Sarvesh Desai

[Former Member]

Thank's for your answer. The partner profile looks ok for both idocs. i.e the idoc with MESCOD is ok and the idoc which should'nt have the MESCOD is set to a blank value.