Responding back to SAP from Logic App

So you’ve registered SAP as a trigger in Azure Logic Apps, enabling SAP to call it as for any other RFC. But how do you parse the SAP request and respond back to it with actual content and not just a vanilla OK? If you enable the support for multiple RFCs by your Logic App…

1

New Logic App connector error responses to SAP

The next update to On-Premises Data Gateway SAP Adapter component for Azure Logic Apps SAP connector will include implementation of error condition translation to ABAP exception or BAPI return depending of what is available in the invoked RFC metadata. This will come in use when using the SAP trigger of the connector (when a message…

0

SAP Type handling connection parameter

From our internal testing, the new connection parameter (Safe Typing check-box): The change is about to merge to our master branch for deployment in the following days. The update to the connector in the cloud will work in pair with a pending update to the On-Premises Data Gateway, while remaining backward compatible with current version…

0

Continued: Strongly typed date, time and numerical fields from SAP DATS, TIMS and NUMC support in Azure Logic Apps SAP connector

We’re about to release the type handling improvements for Azure Logic App SAP connector previously announced here. The connection will have a new Boolean (true-false) parameter “SafeTyping”, enabling to treat DATS and TIMS as string rather than their XML equivalents xs:date and xs:time (where xmlns:xs=”http://www.w3.org/2001/XMLSchema”). This is an opt-in behavior as we encourage our user…

0

Logic Apps SAP connector BAPI support – going under the hood

In the series of posts about Logic Apps SAP connector I am talking today about some details of the implementation for the support of BAPIs. Similar to my recent post on IDoc action url and schema generation (IDoc post), when you are using BAPIs with Logic Apps SAP connector, you will need an action URL…

0

Logic App SAP connector IDoc support – going under the hood

While working on a customer inquiry, I recently investigated the details of our logic for IDoc support, including browsing which are available in the SAP system, forming the hierarchical view to pick an action URL from and generating the metadata / XML schema for the request-response payload. The following details are not a public contract,…

0

Logic App SAP trigger: ERROR Gateway not connected to local R/3

When using a SAP system topology where the SAP Gateway does not run the SAP DIALOG process, and registering a new Logic App SAP trigger, you may get the SAP failure: ERROR Gateway not connected to local R/3 This is happening because Logic Apps is providing the SAP Gateway information for the RFC server registration…

0

Only the Logic App new SAP connector for new Logic Apps

We’ve flagged the older Application Server – Message Server SAP connectors for retirement, both fully replaced with the new SAP connector supporting both connection scenarios. They will continue to function for all existing Logic Apps. When creating new Logic Apps in the designer, only the new SAP connector will now appear. This connector has all…

0

Why the new SAP connector for Logic Apps

When you search for the keyword SAP in the Azure Logic Apps designer action card, you will see three connectors, four actions (and one trigger, not shown here): Why did we introduce earlier this year this new SAP connector in addition to the earlier SAP Application Server and SAP Message Server connectors? The new connector…

3

Azure Logic Apps connected to SAP, and now what?

So we’ve released to public preview the SAP connector for Azure Logic Apps which lets you call or be called as RFCs, BAPIs, as well as send and receive IDOCs. But beyond the technical aspect, what does that mean in terms of business process, patterns you can enable with these? What does it really mean…

0