Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Inbound idoc failing to reach SAP system.

gowrinath_gundu
Participant
0 Kudos

Hi All,

We are upgrading our SAP system from release 700 to 730. Post upgrade we have identified that idocs which are supposed to reach SAP as inbound are failing in Biz Talk with below message.

Error details: Microsoft.ServiceModel.Channels.Common.XmlReaderParsingException: The segment name is not valid for the IDOCTYP, Release, or CIMTYP. Segment name: E2EDT37003GRP   IDOCTYP: SHPMNT03    Release: 700    CIMTYP: . Ensure that your message xml validates against the operation schema.

This happening for only one inbound idoc which is using SHPMNT03 idoc.Whereas other inbound idoc which is using /AFS/ORDERS05 idoc is reaching SAP without any issues. I am bit confused why this is happening for idoc SHPMNT03.


Please let me know your thoughts.


Thanks,

Gowrinath.

2 REPLIES 2

Former Member
0 Kudos

Hi Gowri,

Before getting into the issue, the information shows it is still release 700, have you checked the port and release info ? Check Hotfix to add the "ReceivedIdocRelease" binding property for the WCF-SAP adapter to BizTa...

0 Kudos

Hi Ramya,

Thanks for your response.

In Biz Talk schema is designed for 700 release idoc.Whereas our system is upgraded to 731 release.

Hotfix is for Biz Talk. Can't we implement any solution in SAP side.

Thanks,

Gowrinath.