When integrating SAP with Azure Logic Apps, one of the first steps is to obtain XSD schemas that describe the structure of SAP artifacts like IDocs and RFCs. These schemas are essential for building workflows that send or receive data from SAP.
To generate these schemas, you typically create a Logic App Standard workflow and use the Generate Schema action from the SAP built-in connector. This action introspects the connected SAP system and produces the necessary schema files based on the selected artifact.
For an IDoc, we must provide:
- The IDoc Type
- The Release number
- The Version number
- The Direction to specify if we intend to send or receive the IDoc.
Bug Description
While migrating existing workload from BizTalk Server to Azure Logic Apps, we noticed inconsistencies when generating IDoc schemas via the “Generate Schema” Logic App action.
Specifically, when comparing introspection results between the “Generate Schema” action from Logic App and the “Consume Adapter Service” wizard of the BizTalk Server Extension for Visual Studio 2019, we noticed that:
- Some schemas differed in their structure. E.g. Some element names were different or missing altogether.
- The schemas XML namespaces were different. E.g. When introspecting the ALE AUDIT IDoc type, the “Generate Schema” action returned:
http://Microsoft.LobServices.Sap/2007/03/Types/Idoc/3/ALEAUD01//30C
instead of:http://Microsoft.LobServices.Sap/2007/03/Types/Idoc/3/ALEAUD01//731
Upon further investigation, it became evident that the Logic App’s Generate Schema action does not respect the specified release number for the IDoc. Instead, it appears to return the schema for the first available release, resulting in inaccurate schemas.
We raised this issue with Microsoft Support, and the Logic Apps Product Group confirmed the behavior as a bug. They acknowledged that the release parameter is currently ignored by the connector, and a fix is planned for deployment across Azure.
Temporary Workaround
Until the fix is deployed, our current workaround is to continue using schemas generated by the BizTalk Server Extension for Visual Studio. It provides reliable and accurate schema definitions that align with the intended IDoc version and release.