Azure

SAP to Logic App Error – “SEGMENT_UNKNOWN”

Featured

After working through our first issues with SAP that I talked about in my last blog post, we started to see that not all our outbound IDOCS where making it to our receiving Logic App.

When investigating we came across another issue, this time we saw errors on both the SAP side and Logic App side:

1. SAP errors in SM58

The RequestContext on the IReplyChannel was closed

SAP developer did find that we had errors in our SAP outbound queue (SM58 – Transactional RFC) and the Status Text on the outbound messages was “The RequestContext on the IReplyChannel was closed“.

2. Errors on On-Premise Data Gateway

Exception Details: SAP.Middleware.Connector.RfcAbapException: SEGMENT_UNKNOWN

This error shows up when you have enabled extended SAP logging on the On-Premise Data Gateway.

David Burg a Senior Software Engineer at Microsoft explains in this blog article how to turn on the extended logging.

The Fix

As we were investigating these errors we also noticed that the outbound IDOC that was working was a standard out of the box IDOC. We noticed that the IDOCS that were failing have SAP Extensions on them. If you haven’t heard of SAP IDOC extensions, they are a method to extend out of the box messages with custom fields/elements. You can read more about extensions here.

When you look up these errors, you start to get a lot of articles related to BizTalk Server integration with SAP. Having been a BizTalk Developer in the past I can recall having similar issues.

Kent Weare who has written many blog posts on integrating with SAP had written this blog post on integrating with SAP when you have extended IDOCS: https://kentweare.blogspot.com/2008/09/biztalk-sap-adapter-and-extended-sap.html In one of the comments he mentioned about ensuring IDOC Extensions are released.

So you have to work with your SAP Developer to ensure your IDOC extensions are released. If you are moving from SAP PI/PO like our situation, the IDOCS did not have to be released, so you could run into this situation.

IDOC extensions are release using TCODE WE31 and you can find the segment names that are associated with the IDOC extension using TCODE WE30.

Here is the display extension screen for the standard ORDERS05 with our company extension:

In TCODE WE31, your IDOC needs to have the “Released” field checked:

What this does then when using Logic Apps is it creates another IDOC in your list, with your company prefix.

Hope this helped you out if you ran into this issue. Please let me know if you found this article helpful and be sure to follow me on twitter.

SAP To Logic App Error – “no SAP ErrInfo available”

Luciano Barbieri1 Comment

We have a project underway to integrate Logic Apps with SAP S4 Hana. We made good progress connecting to and sending messages to SAP, but ran into some issues when trying to get IDOC’s sent out from SAP to Logic Apps.

We have an Integrated Service Environment (ISE) that we run our Logic Apps thru, but unfortunately the SAP ISE connector has not been released as of yet (February 2020). Our only option at this time is to connect to our SAP environment using a On-Premise Data Gateway.

One day I hope to come back and write some posts with step-by-step instructions, but for now take a look at Microsoft’s SAP connector documentation for information on connecting your Logic Apps to SAP.

The issue we were experiencing would occur when we went to enable our trigger. After Enabling the Logic App, our Trigger History would show a “Failed” trigger status.

When clicking on the Failed Status, the History would show a Code of “BadRequest”.

Clicking on “Output Link” reveals the following error message:

Failed to process request. Error details: ‘no SAP ErrInfo available

"body": {
     "error": {
         "code": "GeneralBadRequest",
         "message": "Failed to process request. Error details: 'no SAP ErrInfo available\nRETURN CODE: 20'.",
         "target": "CommonAdapter"
     }
 }

And then subsequent runs would show the following trigger output:

"body": {
    "error": {
        "code": "GeneralBadRequest",
        "message": "Failed to process request. Error details: 'Cannot modify function handlers of server <Some Long ID> unless it is stopped (current state: Broken)'.",
        "target": "CommonAdapter"
    }
}

This GeneralBadRequest error continues to appear until you restart the On-Premise Data Gateway. At which point the first run reverts back to original error and subsequent runs back to this latest error.

Unfortunately these are very generic error messages that don’t provide much context as to what the actual issue is. So the solution below has helped us, but in your case it could be something else.

There is a way to enable extended SAP logging on the On-premise Data Gateway. David Burg is a Senior Software Engineer at Microsoft who has written a lot of different articles on SAP connectivity with Logic Apps. Half-way down this article David explains how to turn on the extended logging. Unfortunately this extended logging did not provide further details, as well as Microsoft Support was not able to narrow down our issue.

In the end, after many weeks of trying to troubleshoot we discovered what our issue was. During our configuration of our trigger, our BASIS team mentioned our System ID was 30 and that our Gateway Service was “sapgw30“.

During our troubleshooting we never received any error messages in regards to the Gateway Service, so nothing ever led us to believe “sapgw30” was invalid. Also coming from many years of BizTalk Development, this looks like a proper GatewayService.

Finally one of our consultants found the following SAP Community thread: https://answers.sap.com/questions/482451/sapncodll-rfc-server-connection-issues.html
The response in this article that finally gave us our fix?

Instead of service name (sapgwnn) enter the port number of the ABAP gateway. The default gateway port number is 33nn, where nn is the instance number.

Once we updated our Logic App Trigger – GatewayService to “3330” everything started working as it should.

If this helps you out, please let me know in the comments section below. Also be sure to follow me on twitter.