In this article

Overview

Use this account type to connect the SAP S/4HANA Snaps to SAP S/4HANA On-Premise instance using SSL-based authentication.

Prerequisites

Valid gateway system (which includes Host, Port, Client, Logon Language, Path prefix, and Service collection URL).
Valid certificates (Key store, Trust store, Key/Trust store password, and Key alias)

Limitations and Known Issues

None.

Account Settings

Parameter	Data Type	Description	Default Value	Example
Label	String	Unique name for the account.	N/A	SAPS4HANA_SSL_Auth_Acc
User Id	String	Required. The user name to connect to the SAP S/4HANA On-Premise server.	N/A	newaccountuser
Passphrase	String	Required. The password of the entered user name to connect to the SAP S/4HANA On-Premise server.	N/A	z00md0g!pack@Heavy/
Host	String	Required. The host server name of SAP S/4HANA On-Premise server.	N/A	newhost.example.com
Port	String	Required. The port of SAP S/4HANA On-Premise server.	N/A	35004
Client	String	Required. The client id of the SAP S/4HANA On-Premise server to which the user has access to.	N/A	100
Logon Language	String	Required. The logon language for specified Application Server.	N/A	EN
Path prefix	String	Required. The prefix of the gateway endpoint path. Path prefix specifies a text element to add to the start of the URL used for connections to the service. Path prefix is used to build a Catalog URL and fetch associated service collection. Syntax `http(s)://<host>:<port>/<Path prefix>`	/sap/opu/odata	/sap/opu/odata
Service collection URL	String	Required. The service collection URL of the gateway endpoint path. Service collection URL specifies the relative path from where the catalog service is retrieved. Also, specify the sap-client following the URL.	/iwfnd/catalogservice/ServiceCollection	/iwfnd/catalogservice/ServiceCollection
Key store	String	Required. The location of the key store file. It can be in the SLDB or any other unauthenticated endpoint such as https://...	N/A	https://example.com/keystore_path/file.p12
Trust store	String	Required. The location of the trust store file. It can be in the SLDB or any other unauthenticated endpoint such as https://...	N/A	https://example.com/truststore_path/file.jks
Key/Trust store password	String	Required. Password for key/trust store. It is used for both, Key store and Trust store, if both are defined.	N/A	z00mD0g!/
Key alias	String	Required. The alias for the Key/Trust store password.	N/A	0017017439

Troubleshooting

Error	Reason	Resolution
IO/Error Cause: File not found on at <--- path --->.	The file path entered is incorrect.	Ensure that the file path is correct.
IO/Error Failed to decrypt safe contents entry: javax.crypto.BadPaddingException: Given final block not properly padded.	Key store password is incorrect. Such issues can arise if an incorrect key is used during decryption.	Ensure that the files (key store or trust store) exist and are readable. Ensure that you enter the correct password.
PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target.	Valid certification path to requested target is not found.	Verify that your key/trust store format is correct (JKS, JCEKS, and PKCS12 are supported). Verify that the uploaded key/trust store files are correct . Ensure that the files (key store or trust store) exist and are readable.
IO/Error Cause: toDerInputStream rejects tag type <--- type number --->.	toDerInputStream rejects tag type <--- type number --->, the input file is rejected.	Verify that your key/trust store format is correct (JKS, JCEKS, and PKCS12 are supported). Verify if the uploaded key/trust store files are correct. Ensure that the files (key store or trust store) exist and are readable.
Detect premature EOF.	The file is empty.	Ensure that the files (key store or trust store) exist and are readable.

Additional Information

SAP Gateway

SAP Gateway, an integral part of SAP NetWeaver, lets you connect devices, environments, and platforms to SAP systems. It uses the Open Data Protocol (OData) so you can use any programming language or model to connect to SAP and non-SAP applications. SAP S/4HANA uses SAP Gateway and OData services to bring business data to compelling SAP Fiori apps. Snaps in the SAP S/4HANA Snap Pack use an SAP Gateway URL to access the S/4HANA services.

SAP S/4HANA Gateway URL
Format	http(s)://<host>:<port>/<Path Prefix>/<Service collection URL>? sap-client=<Client Entry Number>&sap-language=<Logon Language>
Example	https://s4hana.example.com:44300/sap/opu/odata/iwfnd/catalogservice/ServiceCollection?sap-client=100&sap-language=EN

SSL Connection

SAP S/4HANA allows users to access the SAP gateway and APIs using X509 certificate authentication. To implement this certificate-based authentication (SSL), you need to upload the key/trust store files on your SnapLogic tenant and configure this account accordingly. Refer the following resources for more details about the SAP security and SAP SSL certificate settings.

Snap Pack History

Click here to expand...

Release	Snap Pack Version	Date	Type	Updates
February 2024	main168	14 Feb 2024	Stable	Updated and certified against the current SnapLogic Platform release.
November 2023	main155	08 Nov 2023	Stable	Updated and certified against the current SnapLogic Platform release.
August 2023	main150	20 Oct 2023	Stable	Enhanced the input schema for the SAP S/4HANA Create Snap.
August 2023	main140	18 Sep 2023	Latest	Fixed the encoding of special characters in the SAP S/4HANA Update Snap.
August 2023	main138	16 Aug 2023	Stable	Fixed an issue in the SAP S/4HANA Create Snap where a few fields were missing in the schema population in the Mapper Snap. Fixed the encoding issue in the SAP S/4HANA Update Snap.
May 2023	main130	10 May 2023	Stable	Upgraded with the latest SnapLogic Platform release.
February 2023	main114	09 Feb 2023	Stable	Upgraded with the latest SnapLogic Platform release.
November 2022	main113	10 Nov 2022	Stable	Upgraded with the latest SnapLogic Platform release.
August 2022	main111	11 Aug 2022	Stable	Upgraded with the latest SnapLogic Platform release.
4.29	main108	14 May 2022	Stable	Upgraded with the latest SnapLogic Platform release.
4.28	main100	12 Feb 2022	Stable	Upgraded with the latest SnapLogic Platform release.
4.27 Patch	main95	17 Dec 2021	Latest	Enhanced the SAP S/4 HANA Snaps to support sub-entities and pagination support. Removed unnecessary datatype conversions. Reduced metadata request volume. Fixed issues in concurrency exception and potential Snap crashes.
4.27	main93	13 Nov 2021	Stable	Upgraded with the latest SnapLogic Platform release.
4.26	main88	14 Aug 2021	Stable	Upgraded with the latest SnapLogic Platform release.
4.25	main73	08 May 2021	Stable	Upgraded with the latest SnapLogic Platform release.
4.24	main73	13 Feb 2021	Stable	Upgraded with the latest SnapLogic Platform release.
4.23	main7430	14 Nov 2020	Stable	Enhances the Snap Pack to handle batch and custom query operations: Introduces the SAP S/4HANA Batch Read Snap that enables retrieving batches of records from an SAP S/4HANA On-Premise instance. Introduces the SAP S/4HANA Batch Write Snap that enables writing batches of records to an SAP S/4HANA On-Premise instance. Introduces the SAP S/4HANA Read Custom Query Snap that enables retrieving multiple records from an SAP S/4HANA On-Premise instance, based on custom queries. Introduces the SAP S/4HANA SSL Auth Account type to enable SSL-based authentication on an SAP S/4HANA On-Premise instance. Adds the Count field to the SAP S/4HANA Read Snap to allow returning the total number of records retrieved.
4.22 Patch	422patches6973	07 Oct 2020	Latest	Enhances the SAP S/4HANA Snap Pack with the following additions: Three new Snaps: SAP S/4HANA Batch Read SAP S/4HANA Batch Write SAP S/4HANA Read Custom Query One new account SAP S/4HANA SSL Auth Account. A new Count field in the SAP S/4HANA Read Snap.
4.22	main6403	12 Sep 2020	Stable	Upgraded with the latest SnapLogic Platform release.
4.21	snapsmrc542	09 May 2020	Stable	Initial release.

SnapLogic Documentation

SAP S/4HANA SSL Auth Account