Skip to Content

Changes for page GET Invoice - SAP S/4HANA

Last modified by Erik Bakker on 2023/01/30 13:43
From version 28.2
edited by Erik Bakker
on 2022/05/02 12:50
Change comment: Update document after refactoring.
To version 29.2
edited by Erik Bakker
on 2022/05/02 12:52
Change comment: Update document after refactoring.

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -POST Order - SAP S/4HANA
1 +POST Invoice - SAP S/4HANA
Content
... ... @@ -2,20 +2,19 @@
2 2  {{container layoutStyle="columns"}}
3 3  (((
4 4  == About ==
5 -With the help of this store item, you can easily perform operations in the Salesforce system with the help of eMagiz. This store item provides several flows related to standard operations and the associated system messages of these operations. All flow items support OAuth2 connectivity to Salesforce’s REST API.
5 +With the help of this store item, you can easily perform a POST Order operation within the SAP S/4HANA system with the help of eMagiz. This store item provides the needed logic, authentication, and definitions to execute the POST Order call. Note that Basic Authentication connectivity is used to connect to SAP S/4HANA’s REST API.
6 6  
7 7  == Documentation ==
8 8  
9 9  ==== 1. How to use====
10 -With this store component, you can easily set up a connection to Salesforce to perform operations within the system. A flow can easily be copied to retrieve information from another Salesforce endpoint and the general format of the system message definition accepted by Salesforce.
10 +With the help of this store item, you can easily perform a POST Order operation within the SAP S/4HANA system with the help of eMagiz. This store item provides the needed logic, authentication, and definitions to execute the POST Order call. Note that Basic Authentication connectivity is used to connect to SAP S/4HANA’s REST API.
11 11  
12 12  ==== 2. Keynotes & restrictions====
13 13  
14 -* Note that the eMagiz user must have an app in the Salesforce environment for the OAuth2 connectivity to successfully connect.
15 -* All responses from Salesforce 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 -* All decimal values should be converted to doubles or floats. Salesforce returns all decimal values with exponents. For example, the field AnnualRevenue might be 52.E03, which is only allowed by xs:double or xs:float.
17 -* To obtain fields using a GET HTTP method for operations like Accounts, Invoices, etc., the eMagiz user must specify a SOQL query in the HTTP Outbound Gateway in the flow. An example is given in each flow, although it is advised to limit the number of rows you want to retrieve from the API.
18 -* Check out the following link for more context on the OAuth2.0 protocol in relation to Salesforce: [[https:~~/~~/developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/intro_oauth_and_connected_apps.htm>>url:https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/intro_oauth_and_connected_apps.htm]]
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]]
19 19  
20 20  ==== 3. License Information====
21 21  Part of the standard license agreement as agreed upon when using the store for the first time.