Skip to content

Commit f84d509

Browse files
author
ecfan
committed
Add links
1 parent e9adaf1 commit f84d509

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

articles/logic-apps/connectors/sap-create-example-scenario-workflows.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -34,6 +34,11 @@ Both Standard and Consumption logic app workflows offer the SAP *managed* connec
3434

3535
The **Trigger by background program** setting lets the underlying IDoc transport tRFC call **`IDOC_INBOUND_ASYNCHRONOUS`** to complete immediately, rather than block the connection until the IDoc finishes processing. However, this setting works only if the IDoc doesn't include the [Express behavior overwriting segment, per SAP Support Note 1777090 - IDocs are processed immediately despite having the "Trigger by background program" option selected in WE20 - SAP for Me](https://me.sap.com/notes/0001777090).
3636

37+
For more information, see the following resources:
38+
39+
- [SAP Support Note 1845390 - Poor performance when posting idocs with report RBDAPP01 - SAP for Me](https://me.sap.com/notes/1845390/E)
40+
- [SAP Support Note 1333417 - Performance problems when processing IDocs immediately - SAP for Me](https://me.sap.com/notes/1333417/E)
41+
3742
[!INCLUDE [api-test-http-request-tools-bullet](../../../includes/api-test-http-request-tools-bullet.md)]
3843

3944
<a name="receive-messages-sap"></a>

0 commit comments

Comments
 (0)