Logic App Standard vs Consumption connecting to SAP via On-premise Gateway

Question

Logic App Standard vs Consumption connecting to SAP via On-premise Gateway

Alexandros Pagonis 0

Hi,

I am migrating from Consumption Logic Apps to Standard Logic App. We currently have a working integration with SAP HANA, via an On-Premise Gateway.

Existing Logic Apps use the "Send a message to SAP" action and it's working fine, i.e.:

User's image

Trying to use the exact same logic on a Standard Logic App I am getting a "Bad Request" error, both in local development (vs code) as well as in the Azure Portal. i.e.:

User's image

Does there need to be something different in SAP's or the Gateway's configuration when moving from Consumption to Standard?

Thank you in advance!

2 answers

Your answer

Answer 1

Sonny Gillissen 3,751 Volunteer Moderator

Hi @Alexandros Pagonis @Alexandros Pagonis

Thanks for reaching out on Microsoft Q&A.

What connection file are you using for connecting the Logic App Standard (LAS) to SAP? Is it the same as the one you used for the Logic App Consumption (LAC)?

If so, please note that the LAC can make use of the V1 connection files whereas LAS needs a V2 connection file.

To validate whether you’re using V2 you can go into the connection file and see if you’ve got “access policies” available in the side menu. If not, you’re using V1.

When you’ve deployed the connection file be sure to ser “kind” to “V2”. In my experience deploying SAP connection files didn’t always work properly, so manually recreating it from your LAS would probably also work.

Please let me know if my answer was helpful. If so please click “Accept answer” and upvote it. Feel free to drop additional queries in the comments.

Kind regards,

Sonny

Alexandros Pagonis 0 Reputation points

2023-03-02T00:27:15.1666667+00:00

Accidentally double posted.
Alexandros Pagonis 0 Reputation points

2023-03-02T00:31:38.62+00:00

Hello @Sonny Gillissen ,

Firstly, thank you so much for getting back to me!

I have already tried creating the connection directly from within the LAS in the Portal, and the resulting Sap api connection does indeed have the "Access Policies" in the sidebar, though the "Bad Request" error persists. The same was true with the connections that were resulting when creating them locally and deploying them.

Thanks again,

Alex
Sonny Gillissen 3,751 Reputation points Volunteer Moderator

2023-03-02T20:49:34.9066667+00:00

Hi @Alexandros Pagonis @Alexandros Pagonis

Ran some test in my lab environment, and I think Ive found the issue. The only supported action for SAP in a Logic App Standard at the moment is the "[RFC] Call function in SAP (preview)" action:

Did you copy the contents of your LAC to the LAS? If so, this technically works perfect for most actions, however for SAP this is not guaranteed.

In your case you could best "rebuild" the functionality using the "[RFC] Call function in SAP (preview)" as it works kinda the same as the "Send a message to SAP".

Please let me know if I can be of any help still.
Alexandros Pagonis 0 Reputation points

2023-03-03T09:24:14.3733333+00:00

Hello @Sonny Gillissen ,

I did indeed remake the flow manually, as it's usually more work to fix every action that breaks by copying the old JSON file.

What I found on my research was that the Action you're pointing out was using a new built-in connector, rather than a managed one.

You are able to find all the old Actions if you use the "SAP" category found on the "Azure" section rather than the "Built-in" section. Will these not work for LAS?

I did try to use the Built-in action but it needs a username/password on it's connection, something we are not using in our current integration.
Sonny Gillissen 3,751 Reputation points Volunteer Moderator

2023-03-03T10:09:32.11+00:00

Yes, you're right. These do work as well (sorry looked over it). Could you please send a screenshot of your LAS connections (in the side menu), specifically the JSON view? Be sure to remove privacy details as GUIDs.
Alexandros Pagonis 0 Reputation points

2023-03-03T11:53:52.6+00:00

Hello @Sonny Gillissen ,

Of course,

Thank you yet again for all your help so far.
Sonny Gillissen 3,751 Reputation points Volunteer Moderator

2023-03-03T12:38:23.77+00:00

Thanks! Checked it with my working environment, seems completely fine to me. What triggered me though was your remark on "it needs a username/password on it's connection, something we are not using in our current integration". What do you actually mean with that?

Answer 2

Hi @Alexandros Pagonis

Did some digging: could it be the, due to the newly created connection, the SAP managed connector IP changed, and that you should whitelist it on your firewall for the connection to work?

Please check the link below with the outbound managed connector IP addresses:

https://learn.microsoft.com/en-us/connectors/common/outbound-ip-addresses#azure-logic-apps

Please let me know if this was helpful! If so, please click "Accept answer" and upvote it.

Feel free to drop any comments on this thread if you'd like to further discuss this topic.

Share via

Logic App Standard vs Consumption connecting to SAP via On-premise Gateway

2 answers

Your answer