You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/logic-apps/connectors/sap.md
+28-28Lines changed: 28 additions & 28 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ author: daviburg
7
7
ms.author: daviburg
8
8
ms.reviewer: estfan, azla
9
9
ms.topic: how-to
10
-
ms.date: 04/11/2025
10
+
ms.date: 04/14/2025
11
11
12
12
#customer intent: As a developer, I want to know the prerequisites and details about using SAP with Azure Logic Apps, so I can connect to an SAP server from my Consumption or Standard workflow.
13
13
---
@@ -678,7 +678,7 @@ To send IDocs from SAP to your logic app workflow, follow these steps to set up
678
678
To send IDocs from SAP to your workflow, you need to set up the minimum configuration by following these steps:
679
679
680
680
1.[Create an RFC destination](#create-rfc-destination).
681
-
1.[Create an ABAP connection](#create-abap-connection).
681
+
1.[Create an Advanced Business Application Programming (ABAP) connection](#create-abap-connection).
682
682
1.[Create a receiver port](#create-receiver-port).
683
683
1.[Create a sender port](#create-sender-port).
684
684
1.[Create a logical system partner](#create-logical-system-partner).
@@ -929,11 +929,11 @@ Based on whether you have a Consumption workflow in multitenant Azure Logic Apps
929
929
930
930
1. If your Consumption logic app resource isn't already enabled, on your logic app menu, select **Overview**. On the toolbar, select **Enable**.
931
931
932
-
1. On the designer toolbar, select **Run Trigger** > **Run** to manually start your workflow.
932
+
1. On the designer toolbar, select **Run** > **Run** to manually start your workflow.
933
933
934
934
1. To trigger your workflow, send a message from your SAP system.
935
935
936
-
1. Return to your logic app's **Overview** pane. Under **Runs history**, find any new runs for your workflow.
936
+
1. Return to your logic app's **Overview** page. Under **Runs history**, find any new runs for your workflow.
937
937
938
938
1. Open the most recent run, which shows a manual run. Find and review the trigger outputs section.
939
939
@@ -945,7 +945,7 @@ Based on whether you have a Consumption workflow in multitenant Azure Logic Apps
945
945
946
946
1. To trigger your workflow, send a message from your SAP system.
947
947
948
-
1. Return to your workflow's **Overview** pane. Under **Run History**, find any new runs for your workflow.
948
+
1. Return to your workflow's **Overview** page. Under **Run History**, find any new runs for your workflow.
949
949
950
950
1. Open the most recent run, which shows a manual run. Find and review the trigger outputs section.
951
951
@@ -1183,7 +1183,7 @@ After your SAP operations run in your logic app workflow, you can review the tel
1183
1183
1184
1184
The following screenshot shows the Azure portal where the Application Insights resource has the **Logs** page open:
1185
1185
1186
-
:::image type="content" source="./media/sap/application-insights-query-panel.png" alt-text="Screenshot shows Azure portal with Application Insights open to the Logs pane for creating queries." lightbox="./media/sap/application-insights-query-panel.png":::
1186
+
:::image type="content" source="./media/sap/application-insights-query-panel.png" alt-text="Screenshot shows Azure portal with Application Insights open to the Logs page for creating queries." lightbox="./media/sap/application-insights-query-panel.png":::
1187
1187
1188
1188
1. On the **Logs** page, you can create a [query](/kusto/query/) by using the [Kusto Query Language (KQL)](/kusto/concepts/) based on your specific requirements.
1189
1189
@@ -1201,31 +1201,31 @@ After your SAP operations run in your logic app workflow, you can review the tel
1201
1201
1202
1202
The following screenshot shows the example query's metrics results table:
1203
1203
1204
-
:::image type="content" source="/media/sap/application-insights-metrics.png" alt-text="Screenshot shows Application Insights with the metrics results table." lightbox="/media/sap/application-insights-metrics.png":::
1204
+
:::image type="content" source="./media/sap/application-insights-metrics.png" alt-text="Screenshot shows Application Insights with the metrics results table." lightbox="./media/sap/application-insights-metrics.png":::
1205
1205
1206
-
***MaxUsedCount** is "The maximal number of client connections that were simultaneously used by the monitored destination." as described in the [SAP NCo documentation](https://support.sap.com/en/product/connectors/msnet.html#section_512604546). You can use this value to understand the number of simultaneously open connections.
1206
+
| Column | Description |
1207
+
|--------|-------------|
1208
+
|**MaxUsedCount**| "The maximal number of client connections that were simultaneously used by the monitored destination." as described in the [SAP NCo documentation](https://support.sap.com/en/product/connectors/msnet.html#section_512604546). You can use this value to understand the number of simultaneously open connections. |
1209
+
|**valueCount**| Shows **2** for each reading because metrics are generated at 30-second intervals. Application Insights aggregates these metrics by the minute. |
1210
+
|**DestinationName**| Contains a character string that is a Microsoft SAP Adapter internal name. |
1207
1211
1208
-
* The **valueCount** column shows **2** for each reading because metrics are generated at 30-second intervals. Application Insights aggregates these metrics by the minute.
1212
+
To better understand this Remote Function Call (RFC) destination, use this value with `traces`, for example:
1209
1213
1210
-
* The **DestinationName** column contains a character string that is a Microsoft SAP Adapter internal name.
1211
-
1212
-
To better understand this Remote Function Call (RFC) destination, use this value with `traces`, for example:
0 commit comments