RfcNotHandled Error - SAP to Logic App Integration

Arunkumar Sivanantham 26

SAP system is getting RFC not handled error when system sends more than 1 idoc to logic apps.
I couldn't find any error in logic app and SAP on premise data gateway as well.

For example, If SAP sends 2 idoc, Logic app will receive only 1 idoc. Remaining 1 will be stuck in SAP system itself with the error of RFC not hanled.

Below is the SAP adapter logs which I got when SAP sends idoc to logic app.

correlationCode=Broker shortMessage=SAP client library version '3.0.0.42' - build '3.0.25.0' exception=<null> connectionId=<null>
correlationCode=Broker shortMessage=Request culture is 'en-US' - 'en' exception=<null> connectionId=<null> correlationId=<null>

Do I have to add any additional setting in on presmie data gateway?

For the reference, I have attached SAP and logic app work flow error.

Mike Urnun 9,666 Reputation points Microsoft Employee

2022-10-26T05:39:27.81+00:00
Hello @Arunkumar Sivanantham - Thanks for posting on MS Q&A!

I'm not familiar with the SAP systems but I'll check internally for anyone who might be able to help with your question. In the meantime, I've come across the following resources that may be of interest to you:

Logic App SAP connector IDoc support – going under the hood

SAP configuration to test sending IDOCs to Azure Logic Apps

SAP sending IDOC to Azure Logic Apps and reply channel failure
Mike Urnun 9,666 Reputation points Microsoft Employee

2022-10-27T00:28:09.71+00:00

@Arunkumar Sivanantham Since I haven't heard back, I wanted to follow up. Are you still have the issue described above?
Arunkumar Sivanantham 26 Reputation points

2022-10-28T02:28:48.74+00:00

@Mike Urnun As checked, The resources that mentioned in the comments is not helping to idenitfy the issue.
Since, Out logic app connection is stable and receiving the data from SAP system.
But the problem is partial data receiving.

For example, If SAP sends 2 idoc, Logic app will receive only 1 idoc. Remaining 1 will be stuck in SAP system itself with the error of RFC not hanled.
Mike Urnun 9,666 Reputation points Microsoft Employee

2022-10-31T02:00:02.523+00:00

Hello @Arunkumar Sivanantham - Just checking in to see if you've reviewed the answer posted by @David Burg below?

Accepted answer

David Burg 406 Reputation points Microsoft Employee

2022-10-28T19:45:16.297+00:00

The SAP error message doesn't make much sense here because it should be the same RFC called whether the payload has 1 or more IDocs of the same type. What batching setting are you using?

Also in the gateway you can enable additional logging to get a trace message for every inbound RFC call seen. The event type is 'RfcServerCallBack', it logs at Informational level and includes the transactionId (TID) for such tRFC call. If the call doesn't show in the trace, it didn't make it to the application. There is an unlikely possibility that the SAP .NET Connector client library rejects the call prior to calling back the application (in which case you would need different logging for NCo trace which SAP support will ask of you).

For the UX:

Or by hand:
<setting name="SapTraceLevel" serializeAs="String">
<value>Informational</value>
</setting>

in Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config

The gateway service needs to be restarted for the tracing configuration change to take effect.
Please sign in to rate this answer.
Arunkumar Sivanantham 26 Reputation points

2022-11-09T07:00:55.79+00:00

@David Burg

After enalbing the logs in onpremise data gateway, Able to reproduce root cause.
Basically afte SAP trigger, The idoc, (DOPack) is going to different idoc type(PGI) . Due to that, RFC is getting failed in SAP.

I have created 2 different idoc type using same program id in logic apps.

Error :
TryReceive. IDOC inbound, skipping non-IDOC / non-matching action filter http://Microsoft.LobServices.Sap/2007/03/Idoc/3/ZDOPack//750/Receive. Looking for 'http://Microsoft.LobServices.Sap/2007/03/Idoc/3/ZDO1//750/Receive'.

IDOC inbound, action filter is present and this IDOC 'http://Microsoft.LobServices.Sap/2007/03/Idoc/3/ZDELSTA01//750/Receive' is not allowed per the filter.

David Burg 406 Reputation points Microsoft Employee

2022-11-09T08:42:57.437+00:00

The action filter is an optional feature for the trigger. Simply remove any value from it to receive all IDocs and RFC calls.

Arunkumar Sivanantham 26 Reputation points

2022-11-10T02:20:58.227+00:00

Let me check

David Burg 406 Reputation points Microsoft Employee

2022-11-10T04:52:01.677+00:00

Yes, remove that entry from the array and leave the array empty.

Arunkumar Sivanantham 26 Reputation points

2022-11-23T09:11:05.383+00:00

Thanks @David Burg .
After removing the array action filter, All idocs are receiving successfully in the logic app.
So, I created a separate logic app to filter out the idocs type.
Thanks for the help.
Sign in to comment

1 additional answer

Sanjay Dinda 1 Reputation point

2022-11-24T09:33:49.967+00:00

Hello Guys, I know my question is not directly linked with this. For IDOC based integration this is fine and i loved it. However when it comes to Sales transaction which I am receiving SMART to CAR ( billing info), can i use this IDOC based integration with Azure ? I am just thinking my volume of data will be extremely big.
Please sign in to rate this answer.
David Burg 406 Reputation points Microsoft Employee

2022-11-24T17:25:43.023+00:00

The SAP trigger is of the webhook callback kind, so you are limited by the concurrency degree of the SAP RFC Server registration, the HTTP output limits of the OPDG host, the inbound limits of consumption workflow. These limits allow a high volume by default, both in number of total calls and message size of individual call. The limiting factor most likely to be reach first is the concurrency degree of the SAP RFC Server registration. I recommend doing a load test in a non-production environment to validate the system's end-to-end capacity to handle your specific load pattern.

https://learn.microsoft.com/azure/logic-apps/logic-apps-limits-and-config?tabs=consumption%2Cazure-portal
Sign in to comment