Since the upgrade of S/4HANA from version 2020 to 2023, we have been having issues with idoc segment versions. Biztalk is not accepting our current versions of idoc segments. I could raise the versions of all the afflicted versions, but is there an easier way to solve this? See below an example error message found in biztalk.

Many thanks in advance.

The adapter “WCF-SAP” raised an error message. Details “Microsoft.ServiceModel.Channels.Common.XmlReaderGenerationException: The segment or group definition E2EDP01008 was not found in the IDoc metadata. The UniqueId of the IDoc type is: IDOCTYP/3/ORDERS04/ZORDERS04_027/740. For Receive operations, the SAP adapter does not support unreleased segments.
at Microsoft.Adapters.SAP.TypedIdocBodyWriter.OnWriteBodyContents(XmlDictionaryWriter writer)
at System.ServiceModel.Channels.BodyWriterMessage.OnWriteBodyContents(XmlDictionaryWriter writer)
at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfMarshaller.CreateBizTalkMessageStream(Message wcfMessage, IAdapterConfigInboundMessageMarshalling config, TLConfig tlConfig, RLConfig rlConfig)
at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfMarshaller.CreateBizTalkMessage(IBaseMessageFactory messageFactory, IAdapterConfigInboundMessageMarshalling marshallingConfig, Message wcfMessage, TLConfig tlConfig, RLConfig rlConfig)
at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfMarshaller.CreateBizTalkSubmitMessage(IBaseMessageFactory factory, String inboundTransportLocation, String inboundTransportType, RLConfig config, Message wcfMessage, String ssoToken)
at Microsoft.BizTalk.Adapter.Wcf.Runtime.BizTalkSubmitBase..ctor(Message message, BizTalkEndpointContext endpointContext, ControlledTermination control, AsyncCallback realCallback, String ssoToken)
at Microsoft.BizTalk.Adapter.Wcf.Runtime.BizTalkRequestResponse..ctor(Message message, AsyncCallback callback, Object state, BizTalkEndpointContext endpointContext, String ssoToken, ControlledTermination control)
at Microsoft.BizTalk.Adapter.Wcf.Runtime.BizTalkOperation.Create(Message message, AsyncCallback callback, Object state, String ssoToken, Boolean bizTalkOneWay, BizTalkEndpointContext endpointContext, ControlledTermination control)
at Microsoft.BizTalk.Adapter.Wcf.Runtime.BizTalkServiceInstance.BeginOperation(Message message, AsyncCallback callback, Object state, Boolean bizTalkOneWay)”.

I tried sending the idoc as normal, but stumbled upon the issue described above