Changes for page GET Order - SAP S/4HANA
Last modified by Erik Bakker on 2023/01/30 13:44
From version 29.1
edited by Erik Bakker
on 2022/05/02 12:52
on 2022/05/02 12:52
Change comment:
There is no comment for this version
To version 4.1
edited by Erik Bakker
on 2022/05/02 08:17
on 2022/05/02 08:17
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - POSTOrder - SAPS/4HANA1 +SOAP Web service Connectivity - Parent
-
... ... @@ -1,1 +1,1 @@ 1 -Main.eMagiz Store. System Connectors.WebHome1 +Main.eMagiz Store.Accelerators.WebHome - Content
-
... ... @@ -1,32 +1,40 @@ 1 1 {{container}} 2 2 {{container layoutStyle="columns"}} 3 3 ((( 4 -= =About ==5 - Withthe help of this storeitem,you can easilyperform a POST Order operationwithintheSAPS/4HANAsystemwith thehelp of eMagiz. Thisstoreitem providestheneeded logic,authentication,anddefinitions toexecutethePOST Orderall. NotethatBasicAuthenticationconnectivity isusedtoconnectto SAP S/4HANA’s REST API.4 += About = 5 +This store element will allow you to create an easy connection to SOAP based web services. XML data can be send to these web services, and for each connectivity type there is a Flow Fragment available. 6 6 7 -= =Documentation ==7 += Documentation = 8 8 9 - ====1. How to use====10 -With th e help of this storeitem, you can easilyperformaPOST OrderoperationwithintheSAPS/4HANA system with the helpf eMagiz. This storeitemprovidesthe needed logic,authentication,and definitionsto execute the POST Order call. Note that BasicAuthenticationconnectivity isusedto connectto SAP S/4HANA’s REST API.9 + **~1. How to use** 10 +With this store component, you can easily set up a connection to a REST endpoint using various authentication mechanisms while taking the response into account. 11 11 12 - ====2. Keynotes & restrictions====12 +**2. Keynotes & restrictions ** 13 13 14 -* Note that the eMagiz user must have an SAP S/4HANA environment for the Basic Authentication connectivity to successfully connect. 15 -* All responses from SAP S/4HANA can contain null values for fields that are not filled in. These fields are removed with an XSLT Transformer and then validated against the response system message. eMagiz users should take note that after this transformation, all attributes are transformed to String types. This means that further transformation is required before passing the gateway message validation. Especially Integers, Decimals, and Enumerations should be transformed, but also Booleans and other non-string types. 16 -* To test out operations, an API key header can be added for a sandbox environment. This allows for extensive testing with demo data through SAP Business Hub. 17 -* For more information on the SAP S/4HANA API please check out the following link:: [[https:~~/~~/api.sap.com/package/SAPS4HANACloud/all>>url:https://api.sap.com/package/SAPS4HANACloud/all]] 14 +a. Note that you need to select the valid authentication based on the requirement of the external system. 18 18 19 - ====3. License Information====16 +**3. License Information** 20 20 Part of the standard license agreement as agreed upon when using the store for the first time. 21 21 22 -==== 4. Relevant eMagiz Academy Microlearnings==== 19 +**4. Relevant eMagiz Academy Microlearnings** 20 +[[https:~~/~~/emagiz.github.io/docs/microlearning/intermediate-rest-webservice-connectivity-index>>url:https://emagiz.github.io/docs/microlearning/intermediate-rest-webservice-connectivity-index]] 23 23 24 -[[https:~~/~~/emagiz.github.io/docs/microlearning/intermediate-rest-webservice-connectivity-index>>url:https://emagiz.github.io/docs/microlearning/intermediate-rest-webservice-connectivity-index]] 25 25 26 - //Would you please consult the privacy policy of eMagiz at the following link://[[https:~~/~~/www.emagiz.com/privacy-policy/?>>url:https://www.emagiz.com/privacy-policy/?]])))23 +Would you please consult the privacy policy of eMagiz at the following link: [[https:~~/~~/www.emagiz.com/privacy-policy/?>>url:https://www.emagiz.com/privacy-policy/?]]))) 27 27 28 28 29 29 30 -((())) 27 +((((% border="2" cellpadding="10" cellspacing="10" style="width:292px" %) 28 +|=(% style="width: 45px;" %)#|=(% style="width: 241px;" %)Option 29 +|(% style="width:45px" %) a|(% style="width:241px" %) OAuth 2.0 - Authorization Code 30 +|(% style="width:45px" %) b|(% style="width:241px" %) REST - Basic Auth 31 +|(% style="width:45px" %) c|(% style="width:241px" %) REST - Client Certificate 32 +|(% style="width:45px" %) d|(% style="width:241px" %) REST - Header Mapper 33 +|(% style="width:45px" %) e|(% style="width:241px" %) OAuth 2.0 - Client Credentials 34 +|(% style="width:45px" %) f|(% style="width:241px" %) REST - SSL 35 +|(% style="width:45px" %) g|(% style="width:241px" %) Dynamic Token 36 +|(% style="width:45px" %) h|(% style="width:241px" %) Token 37 +|(% style="width:45px" %) i|(% style="width:241px" %) No Authentication (Fire & Forget) 38 +))) 31 31 {{/container}} 32 32 {{/container}}