Skip to content

Commit c037123

Browse files
committed
edits for Acrolinx
1 parent 6c52b4a commit c037123

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/logic-apps/connectors/sap-generate-schemas-for-artifacts.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ ms.date: 04/15/2025
1717

1818
[!INCLUDE [logic-apps-sku-consumption-standard](../../../includes/logic-apps-sku-consumption-standard.md)]
1919

20-
This how-to guide shows how to create an example logic app workflow that generates schemas for SAP artifacts. The workflow starts with a **Request** trigger that can receive HTTP POST requests from your SAP server. The workflow then generates schemas for the specified IDoc and BAPI by using the SAP action named **Generate schemas** that sends a request to your SAP server. To send this request, you can use either the generic SAP managed connector action named **Send message to SAP**, or you can use the specific SAP managed or built-in action named **[BAPI] Call method in SAP**. This SAP action returns an [XML schema](#sample-xml-schemas) without the contents or data in the XML document itself. The workflow then uploads the schemas returned by the response to an integration account by using a Azure Resource Manager connector operation.
20+
This how-to guide shows how to create an example logic app workflow that generates schemas for SAP artifacts. The workflow starts with a **Request** trigger that can receive HTTP POST requests from your SAP server. The workflow then generates schemas for the specified IDoc and BAPI by using the SAP action named **Generate schemas** that sends a request to your SAP server. To send this request, you can use either the generic SAP managed connector action named **Send message to SAP**, or you can use the specific SAP managed or built-in action named **[BAPI] Call method in SAP**. This SAP action returns an [XML schema](#sample-xml-schemas) without the contents or data in the XML document itself. The workflow then uploads the schemas returned by the response to an integration account by using an Azure Resource Manager connector operation.
2121

2222
Schemas contain the following parts:
2323

@@ -122,7 +122,7 @@ Based on whether you have a Consumption or Standard workflow, follow the corresp
122122
123123
For more information about the **Send** SAP action, see [Message schemas for IDoc operations](/biztalk/adapters-and-accelerators/adapter-sap/message-schemas-for-idoc-operations).
124124

125-
If you have the option to browse and select the folders along this path, follow these steps:
125+
If you're able to browse and select the folders along this path, follow these steps:
126126

127127
1. In the **sapActionUris Item - 1 ActionUri** box, from the dropdown list, select **BAPI**, **IDOC**, **RFC**, or **TRFC**.
128128

0 commit comments

Comments
 (0)