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
+12-2Lines changed: 12 additions & 2 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: 02/10/2024
10
+
ms.date: 04/18/2024
11
11
---
12
12
13
13
# Connect to SAP from workflows in Azure Logic Apps
@@ -1082,7 +1082,7 @@ See the steps for [SAP logging for Consumption logic apps in multitenant workflo
1082
1082
1083
1083
---
1084
1084
1085
-
## Enable SAP client library (NCo) logging and tracing (Built-in connector only)
1085
+
## Enable SAP client library (NCo) logging and tracing (built-in connector only)
1086
1086
1087
1087
When you have to investigate any problems with this component, you can set up custom text file-based NCo tracing, which SAP or Microsoft support might request from you. By default, this capability is disabled because enabling this trace might negatively affect performance and quickly consume the application host's storage space.
1088
1088
@@ -1097,6 +1097,16 @@ You can control this tracing capability at the application level by adding the f
1097
1097
* **SAP_RFC_TRACE_DIRECTORY**: The directory where to store the NCo trace files, for example, **C:\home\LogFiles\NCo**.
1098
1098
1099
1099
* **SAP_RFC_TRACE_LEVEL**: The NCo trace level with **Level4** as the suggested value for typical verbose logging. SAP or Microsoft support might request that you set a [different trace level](#trace-levels).
1100
+
1101
+
> [!NOTE]
1102
+
>
1103
+
> For Standard logic app workflows that use runtime version 1.69.0 or later, you can enable
1104
+
> logging for multiple trace levels by separating each trace level with a comma (**,**).
1105
+
>
1106
+
> To find your workflow's runtime version, follow these steps:
1107
+
>
1108
+
> 1. In the Azure portal, on your workflow menu, select **Overview**.
1109
+
> 2. In the **Essentials** section, find the **Runtime Version** property.
1100
1110
1101
1111
* **SAP_CPIC_TRACE_LEVEL**: The Common Programming Interface for Communication (CPI-C) trace level with **Verbose** as the suggested value for typical verbose logging. SAP or Microsoft support might request that you set a [different trace level](#trace-levels).
0 commit comments