Detailed breakdown of sample XML payloads for RFC, BAPI and IDOC integration with SAP from Azure Logic Apps.

1. Sample payloads for SAP
Integration via Azure Logic Apps
David Burg
November 2019

2. ©Microsoft Corporation
Azure
Starting with the basic
Azure Logic Apps SAP Connector
Integration solution in the Azure hybrid cloud
https://azure.microsoft.com/en-
us/services/logic-apps/
REST-native, serverless, codeless, massively
scalable, several hundred connectors,
enterprise grade service.
Introduction to the connector for SAP
https://docs.microsoft.com/en-us/azure/logic-
apps/logic-apps-using-sap-connector
All the requests-responses are XML. Logic App
has native XML support and to Json
conversion
https://docs.microsoft.com/en-us/azure/logic-
apps/workflow-definition-language-functions-
reference#manipulation-functions-json--xml

3. ©Microsoft Corporation
Azure
3 types of possible communication with SAP
RFC BAPI IDOC
Remote Function Call – SAP’s standard
interface to communicate between systems
https://en.wikipedia.org/wiki/Remote_Function
_Call
Business API – higher level access, manipulate
business objects via functions (API)
maintaining data consistency
https://en.wikipedia.org/wiki/Business_Applicat
ion_Programming_Interface
Intermediate Document – SAP’s format for
business transactions, e.g. purchase, invoice,
shipment, etc.
https://en.wikipedia.org/wiki/IDoc

4. Optional XML prolog
This is optional and the SAP Connector will work with or without it.
The SAP .NET Connector library on which the connector is built is Unicode native. Do send XML
documents encoded with UTF-8.
Read more about the prolog here:
https://www.w3schools.com/xml/xml_syntax.asp

5. RFCs

6. Hello world RFC call
RFC name
Namespace for all RFCs.
This example uses default
namespace (xmlns=…). You can
also assign and use namespace
aliases (xmlns:aliasXyz=…).
Simple input parameter

7. RFC with table parameter
This test RFC and its group of test RFCs
are available out of the box in any SAP
system.
The table parameter name
(TCPICDAT).
This specific row type contains a
single field named LINE. Table line
types may contain n fields.
The table line type is ABAPTEXT.
This element repeats for each row
in the table.

8. Table with anonymous field
This line type structure contains a single
anonymous field (i.e. the field has no
name assigned).
Character for hex code 002F is
reserved in SAP field name and
used here as escape character.
Note that complex types are
declared under separate
namespace. This new XML
namespace declaration set a
new default for the current
node and all its child elements.

9. Namespaces prefixes sample
All prefixes can be declared at once or any
amount of prefix may be declared as
attribute to any node.
‘RFC’ namespace is used for the
root and parameters of basic
type.
Note that complex types are
declared under separate
namespace ‘RFC types’.

10. Full samples as files (double click file to open)

11. BAPIs

12. Get list of Banks
<GETLIST
xmlns="http://Microsoft.LobServices.Sap/2007/03/Ba
pi/BUS1011/">
<BANK_CTRY>US</BANK_CTRY>
<MAX_ROWS>10</MAX_ROWS>
</GETLIST>
The BAPI method ‘Get list’.
When an object is selected in the designer,
the set of available methods is provided as
simple drop-down in the Logic App
designer.
The business object for bank (BUS1011).
The Call BAPI API on SAP connector
provides a searchable list in the Azure
Logic Apps Designer. Typing ‘bank’
keyword will filter to all business object
types for bank including this BUS1011.
Limits the number of items in the response

13. Create a Bank object
<CREATE
xmlns="http://Microsoft.LobServices.Sap/2007/03/Ba
pi/BUS1011/">
<BANK_ADDRESS>
<BANK_NAME
xmlns="http://Microsoft.LobServices.Sap/2007/03/Ty
pes/Rfc/">VERIZON BANK</BANK_NAME>
<REGION
xmlns="http://Microsoft.LobServices.Sap/2007/03/Ty
pes/Rfc/"></REGION>
<STREET
xmlns="http://Microsoft.LobServices.Sap/2007/03/Ty
pes/Rfc/">15</STREET>
<CITY
xmlns="http://Microsoft.LobServices.Sap/2007/03/Ty
pes/Rfc/">JODHPUR</CITY>
</BANK_ADDRESS>
<BANK_CTRY>US</BANK_CTRY>
<BANK_KEY>{0}</BANK_KEY>
</CREATE>
Create method
Same business object
Beware per system configured SAP
validation rule(s). For instance, the
key may have to be an ABA bank
identifier in the USA.

14. Get Bank details
<GETDETAIL
xmlns="http://Microsoft.LobServices.Sap/2007/03/Ba
pi/BUS1011/">
<BANKCOUNTRY>US</BANKCOUNTRY>
<BANKKEY>{0}</BANKKEY>
</GETDETAIL>
Update this key to a value
existing in your test SAP system.

15. Full sample as files (double click file to open)

16. IDOCs

17. Plain SAP IDOC XML

18. ©Microsoft Corporation
Azure
Plain SAP IDOC XML
Generating the schema
Use SAP Logon GUI application and T-Code WE-60 to access
SAP Documentation and generate per IDOC type / per IDOC
extension XML schema (XSD file)
Usage
This format and payload is generic to SAP. Find explanation of
each field built-in SAP dialog and in SAP documentation as
well as many online public resources.

19. Full sample as files (double click file to open)

20. With ‘BizTalk’-style
namespaces

21. ©Microsoft Corporation
Azure
‘BizTalk’s’ SAP IDOC XML (and Flat
File)
Generating the schema
Use Azure Logic Apps SAP Connector built-in schema
generation action and generate per IDOC type / per IDOC
extension XML schema (XSD file)
Usage
This format and payload is most convenient if you are
migrating from BizTalk. Learn more in BizTalk Server’s public
documentation at:
https://docs.microsoft.com/en-us/biztalk/adapters-and-
accelerators/adapter-sap/send-idocs-to-sap-using-biztalk-
server
Flat-file IDOC in XML message is also supported in Azure
Logic App SAP Connector.

22. Root node, namespaces declarations
http://schemas.microsoft.com/2003/10/Serialization/
http://Microsoft.LobServices.Sap/2007/03/Types/Idoc/Common/
Find detailed explanation about the IDOC URI in this blog post:
https://www.linkedin.com/pulse/logic-app-sap-connector-idoc-support-going-under-hood-david-burg/
The idocData node can be repeated to form a batch of IDOCs to send in a single call.

23. IDOC Data element
One Control Record
N Data Records

24. Control Record sample
SAP Official doc for the control record:
- click here -

25. Data Record plain Segments
Data Record segment name
This sample is using SAP’s format for dates.
Strong typed documents can use native XML types,
e.g.
9999-12-31
23:59:59
More at
https://www.w3schools.com/xml/schema_dtypes_date.
asp

26. Data Record Group Segments
Group parent node
N child nodes

27. Optional IDOC transport ID for tRFC
Last Data Record segment node
closing
IDOC Data node closing
GUID will form the tRFC TID for
duplicate transport detection.
This node can be omitted.
Recommend to set the tRFC TID
instead via connector API
parameter, see:
https://docs.microsoft.com/en-
us/connectors/sap/#send-idoc

28. Full samples as file (double click file to open)

29. ©Microsoft Corporation
Azure
Resources
Free Azure Account Author’s blog
https://azure.microsoft.com/en-us/free/
Find this deck and more posts about Azure,
Logic Apps, SAP, XML, Json at my blog:
https://www.linkedin.com/in/daviburg/detail/re
cent-activity/posts/

30. © Copyright Microsoft Corporation. All rights reserved.