In this article
Use this template to document an account type ONLY IF there are more than three account types. Document each account type to be documented separately. Maintain them as child pages of the main Accounts page. Remove Prerequisites, Limitations, and Troubleshooting from the main Accounts page if using this template.
Provide an overview of the account type.
Use this account type to connect the SAP S/4HANA Snaps to SAP S/4HANA On-Premise using Basic Authentication.
Provide all prerequisites for configuring the account type or use 'None.' if there are no prerequisites.
List all account-based limitations as bullets. Use "None." if there are no limitations.
None.
Include a screenshot of the fully configured account. Do this for each account type. If the account type has fields that are auto-populated when you validate/authorize it, mention so before the screenshot. For example: To create your REST OAuth2 account in SnapLogic, you must provide at least your Client ID, Client secret, OAuth2 endpoint, and OAuth2 token and click Authorize. SnapLogic sends your account details to the OAuth2 endpoint specified and populates the Access token, Refresh token, and Access token expiration fields using the details received from that endpoint.
Parameter | Data Type | Description | Default Value | Example | |
---|---|---|---|---|---|
Label The field's name in the UI. Ensure that it is captured accurately so as not to confuse the user. | String The data type of the field. For example, string, numeric, alphanumeric, etc. Check box for check boxes | Required. Enter a Unique name for the account. Field Prefacing for Mandatory/Conditionally mandatory fields: ---------------------------------------------------------------------------------- If field is mandatory (has a * in the UI), add, "Required" in italics. See Label's description below. If a field becomes mandatory based on the configuration of another field then add, "Required if <field_name> is configured". If a field is applicable based on certain situations then add, "Applicable only to <situation>"; for example, "Applicable only when using SSL with KMS." These conditions must always be in italics and in the beginning of the description. These prefacing conditions must always be in italics and in the beginning of the field's description. | N/A N/A if there is no default value. | SAPS4HANA_Basic_Auth Use italics for examples. Show multiple examples to show variations. If N/A then no italics. | |
User Id | String | Required. Enter the user name to connect to the SAP S/4HANA On-premise server. | N/A | username | |
Passphrase | String | Required. Specify the password associated with the entered user name. | N/A | MyUser | |
Host | String | Required. Enter the host name of SAP S/4HANA On-premise server. | N/A | s4hana.example.com | |
Port | String | Required. Specify the port on which the SAP S/4HANA On-premise server listens for connection requests. | N/A | 44300 | |
Client | String | Required. Enter the client id of the SAP S/4HANA On-premise that you are authorized to access. | N/A | 100 | |
Logon Language | String | Required. Specify the logon language as specified in the Application Server. | N/A | EN | |
Path prefix | String | Required. Enter the prefix in the gateway endpoint path needed to build a Catalog URL and fetch associated service collection. For more information, see SAP Gateway in this page.
| /sap/opu/odata | /sap/opu/odata | |
Service collection URL | String | Required. Specify the relative path—from the gateway endpoint location—needed to retrieve the catalog service. For more information, see SAP Gateway in this page. | /iwfnd/catalogservice/ServiceCollection | /iwfnd/catalogservice/ServiceCollection | |
Trust all certificates | Check box | SAP S/4HANA Basic Auth Account trusts all certificates, by default. Deselect this check box when there is a third-party signed certificate to be authenticated.
| Selected | Selected |
Error | Reason | Resolution |
---|---|---|
Enter the error message that is displayed. PKIX path building failed: sun.security.provider.certpath. | Briefly describe why this error is triggered. An experienced user will be able to troubleshoot the error looking at the reason itself. Unable to find valid certification path to requested target. | List the steps that the user must take, if necessary, to rectify this error. If a procedure is extensive, add it as a separate section after this table and reference it with a link in this cell. Make sure that you have a valid certificate installed on your SAP S/4HANA server. Alternatively, you can check the Trust all certificates checkbox. |
Failed to validate account: Error on line 1: Content is not allowed in prolog. Cause: Error on line 1: Content is not allowed in prolog. (Reason: Exception occurred while processing the API metadata XML. Content is not allowed in prolog.; Resolution: Please file a defect against the snap) | Wrong logon details or the logon account is locked. |
|
Timeout when retrieving Entity suggestions | The list of API objects are displayed in the Snap Settings dialog, but the corresponding Entity suggestions time out. It is possible that the SAP S/4HANA is relatively new; in which case the transactions need to be performed in the backend as a way to force code compilation. | Alternatively, you can initiate the compilation externally through a browser using the link specific to the API object and entity. Once the page load is complete, try loading the entities list in Snap Settings. Example: https://<host>:<port>/sap/opu/odata/sap/ |
Snap[com.rojoconsultancy.sap.saps4hana. SAPS4HanaBasicAuthAccount error | This error occurs when the Snap version deployed is incorrect. | Raise an incident with SnapLogic to get this dependency (change of deployed Snap version) resolved. |
401 or an unauthorized error for the entity | This error occurs when the Account configuration is incorrect. | Make sure that you have entered the correct User Id, Passphrase and Client number "?sap-client=015 ". |
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 |
Contents of Gateway URL | |
Host | s4hana.example.com |
Port | 44300 |
Client | 100 |
Logon Language | EN |
Path prefix | /sap/opu/odata |
Service collection URL | /iwfnd/catalogservice/ServiceCollection |
The SAP S/4 HANA On-premise account specified in Snap settings must have specific authorizations to access the various OData APIs and to call the OData API Objects configured in the Snap.
To enable dynamic loading of objects and entities in the Snaps:
See User Authorization in SAP Help for a step-by-step procedure.
Provide links to the endpoint's official documentation, any relevant or related internal documentation, and any other links you have referred to on this page. Care should be taken when referencing external sites/documentation that it is an official site/documentation. Do not refer to forums such as stackoverflow.