Skip to content

Commit a27e8dd

Browse files
authored
Fix UX steps, art link, and other formatting
1 parent ffb59b5 commit a27e8dd

File tree

1 file changed

+28
-28
lines changed
  • articles/logic-apps/connectors

1 file changed

+28
-28
lines changed

articles/logic-apps/connectors/sap.md

Lines changed: 28 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: daviburg
77
ms.author: daviburg
88
ms.reviewer: estfan, azla
99
ms.topic: how-to
10-
ms.date: 04/11/2025
10+
ms.date: 04/14/2025
1111

1212
#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.
1313
---
@@ -678,7 +678,7 @@ To send IDocs from SAP to your logic app workflow, follow these steps to set up
678678
To send IDocs from SAP to your workflow, you need to set up the minimum configuration by following these steps:
679679

680680
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).
682682
1. [Create a receiver port](#create-receiver-port).
683683
1. [Create a sender port](#create-sender-port).
684684
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
929929

930930
1. If your Consumption logic app resource isn't already enabled, on your logic app menu, select **Overview**. On the toolbar, select **Enable**.
931931

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.
933933

934934
1. To trigger your workflow, send a message from your SAP system.
935935

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.
937937

938938
1. Open the most recent run, which shows a manual run. Find and review the trigger outputs section.
939939

@@ -945,7 +945,7 @@ Based on whether you have a Consumption workflow in multitenant Azure Logic Apps
945945

946946
1. To trigger your workflow, send a message from your SAP system.
947947

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.
949949

950950
1. Open the most recent run, which shows a manual run. Find and review the trigger outputs section.
951951

@@ -1183,7 +1183,7 @@ After your SAP operations run in your logic app workflow, you can review the tel
11831183

11841184
The following screenshot shows the Azure portal where the Application Insights resource has the **Logs** page open:
11851185

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":::
11871187

11881188
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.
11891189

@@ -1201,31 +1201,31 @@ After your SAP operations run in your logic app workflow, you can review the tel
12011201

12021202
The following screenshot shows the example query's metrics results table:
12031203

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":::
12051205

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. |
12071211

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:
12091213

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:
1213-
1214-
```Kusto
1215-
customMetrics
1216-
| extend DestinationName = tostring(customDimensions["DestinationName"])
1217-
| join kind=inner (traces
1218-
| extend DestinationName = tostring(customDimensions["DestinationName"]),
1219-
AppServerHost = tostring(customDimensions["AppServerHost"]),
1220-
SncMode = tostring(customDimensions["SncMode"]),
1221-
SapClient = tostring(customDimensions["Client"])
1222-
| where customDimensions contains "RfcDestinationMonitor"
1223-
)
1224-
on DestinationName , $left.DestinationName == $right.DestinationName
1225-
| where customDimensions contains "RfcDestinationMonitor"
1226-
| where name contains "MaxUsedCount"
1227-
| project AppServerHost, SncMode, SapClient, name, valueCount, valueSum, valueMin, valueMax
1228-
```
1214+
```Kusto
1215+
customMetrics
1216+
| extend DestinationName = tostring(customDimensions["DestinationName"])
1217+
| join kind=inner (traces
1218+
| extend DestinationName = tostring(customDimensions["DestinationName"]),
1219+
AppServerHost = tostring(customDimensions["AppServerHost"]),
1220+
SncMode = tostring(customDimensions["SncMode"]),
1221+
SapClient = tostring(customDimensions["Client"])
1222+
| where customDimensions contains "RfcDestinationMonitor"
1223+
)
1224+
on DestinationName , $left.DestinationName == $right.DestinationName
1225+
| where customDimensions contains "RfcDestinationMonitor"
1226+
| where name contains "MaxUsedCount"
1227+
| project AppServerHost, SncMode, SapClient, name, valueCount, valueSum, valueMin, valueMax
1228+
```
12291229

12301230
You can also create metric charts or alerts by using those capabilities in Application Insights, for example:
12311231

0 commit comments

Comments
 (0)