Clarify SAP stateful action requirements

Addresses ADO Task 31873254: [Docs][Content Health][S500 support bridge][Standard] SAP built-in doc - Remove link to old blog post, and list the built-in operations that have state

Author: daviburg

articles/logic-apps/connectors/sap.md

@@ -7,7 +7,7 @@ author: daviburg
 ms.author: daviburg
 ms.reviewer: estfan, azla
 ms.topic: how-to
-ms.date: 01/16/2025
+ms.date: 03/24/2025
 ---
 
 # Connect to SAP from workflows in Azure Logic Apps
@@ -167,7 +167,10 @@ SAP upgraded their .NET connector (NCo) to version 3.1, which changed the way th
 
   * For a Standard workflow in single-tenant Azure Logic Apps, see [Single-tenant prerequisites](#single-tenant-prerequisites).
 
-* By default, the SAP built-in connector operations are *stateless*. To run these operations in stateful mode, see [Enable stateful mode for stateless built-in connectors](../../connectors/enable-stateful-affinity-built-in-connectors.md).
+* By default, the SAP built-in connector operations are *stateless*. To run these operations in stateful mode, see [Enable stateful mode for stateless built-in connectors](../../connectors/enable-stateful-affinity-built-in-connectors.md). Stateful communications must remain on the same processing instance of the workflow application. For example, these actions include the following:
+  *  All actions that specify a **Session ID** value, e.g. the action named **[BAPI] Commit transaction**
+  *  All actions that specify a **Transaction ID** value, except the actions named **[IDOC - RFC] Confirm transaction Id** and **[IDoc] Get IDoc list for transaction**
+  *  **Respond to SAP server**
 
 * To use either the SAP managed or built-in connector trigger named **When a message is received**, complete the following tasks:
 
@@ -199,7 +202,7 @@ SAP upgraded their .NET connector (NCo) to version 3.1, which changed the way th
 
     In Standard workflows, the SAP built-in trigger named **When a message is received** uses the Azure Functions trigger instead, and shows only the actual callbacks from SAP.
 
-  * For the SAP built-in connector trigger named **When a message is received**, you have to enable virtual network integration and private ports by following the article at [Enabling Service Bus and SAP built-in connectors for stateful Logic Apps in Standard](https://techcommunity.microsoft.com/t5/azure-integration-services-blog/enabling-service-bus-and-sap-built-in-connectors-for-stateful/ba-p/3820381). You can also run the workflow in Visual Studio Code to fire the trigger locally. For Visual Studio Code setup requirements and more information, see [Create a Standard logic app workflow in single-tenant Azure Logic Apps using Visual Studio Code](../create-single-tenant-workflows-visual-studio-code.md). You must also set up the following environment variables on the computer where you install Visual Studio Code:
+  * For the SAP built-in connector trigger named **When a message is received**, you have to enable virtual network integration and private ports by following the article at [Enable stateful mode for stateless built-in connectors in Azure Logic Apps](../../connectors/enable-stateful-affinity-built-in-connectors.md). If you don't configure the workflow application per these prerequisites, the action named **Respond to SAP server** may lack the necessary state to properly function. You can also run the workflow in Visual Studio Code to fire the trigger locally. For Visual Studio Code setup requirements and more information, see [Create a Standard logic app workflow in single-tenant Azure Logic Apps using Visual Studio Code](../create-single-tenant-workflows-visual-studio-code.md). You must also set up the following environment variables on the computer where you install Visual Studio Code:
 
    - **WEBSITE_PRIVATE_IP**: Set this environment variable value to **127.0.0.1** as the localhost address. 
    - **WEBSITE_PRIVATE_PORTS**: Set this environment variable value to two free and usable ports on your local computer, separating the values with a comma (**,**), for example, **8080,8088**.