SAP S/4HANA Create

In this article


Use this Snap to create data objects in the SAP S/4HANA On-Premise instance.


Support for Ultra Pipelines

See Snap Support for Ultra Pipelines.

Limitations and Known Issues

  • The Snap does not support OData navigation link.

Snap Input and Output

Input/OutputType of ViewNumber of ViewsExamples of Upstream and Downstream SnapsDescription


  • Min: 1
  • Max: 1
  • Mapper Snap
  • Copy Snap
  • JSON Parser

Each input document contains data that must be created and written into the SAP S/4HANA On-Premise instance.



  • Min: 0
  • Max: 1
  • Mapper Snap
  • Copy Snap
  • XML Formatter
  • JSON Formatter

Each document contains the response of the creation of new records in the On-Premise instance.

Snap Settings

Parameter NameData TypeDescriptionDefault ValueExample 



Required. The name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your Pipeline.


SAP S/4HANA Create

API object


Required. Select the API that you want to access in SAP S/4HANA On-Premise instance. This drop-down list contains APIs available for the account configured in the Snap, each with a short description.


ZCRM_BUPA_ODATA_0001 (Odata Services for Business Partner)



Required. Select a business object (the Entity or Endpoint) for the API Object chosen above. 



Customized header

Use this field set to add customized HTTP request headers for implementing specific HTTP requests other than the ones listed in the Using Customized Headers section (SAP S/4HANA Read Snap). 

Only one customized header can be specified in each row. Click  to add a new row in this table and define the values accordingly. 

This field set comprises the following fields:

  • Field name
  • Field value

Define customized headers using Input Schema

Alternatively, you can define customized headers through Input Schema in combination with expressions. When using Input Schema, it is mandatory to define the HTTP request headers as expressions ('=' symbol enabled for Field name and Field value). 

Field name

StringThe field name of the customized HTTP request header.N/AIf-Match

Field value

StringThe field value for the above field in the customized HTTP request header.N/AW/"'82F636DC08F14D22260CE67E505C231D0D2ACD95'"
Input navigation levelIntegerSelect the depth of navigation for your input schema. 01

Connection details

Use this section of Snap Settings to specify the connectivity parameters: timeout, retry count and retry interval. 

This field set comprises the following fields:

  • TimeOut
  • Maximum request attempts
  • RetryInterval



Required. Enter, in seconds, the duration for which the Snap must try to establish connection with SAP S/4HANA On-Premise instance. If the connection cannot be established within this duration, the Snap times out, writes the event to the log, and waits until the specified RetryInterval before attempting to reconnect.



Maximum request attempts


Required. Specify an integer value to set the maximum number of reconnection attempts that the Snap must perform, in case of connection failure or timeout.





Required. Enter, in seconds, the duration for which the Snap must wait between two reconnection attempts, until the number of retries is reached.



Snap Execution


Indicates how the Snap must be executed. Available options are:

  • Validate & Execute: Performs limited execution of the Snap (up to 50 records) during Pipeline validation; performs full execution of the Snap (unlimited records) during Pipeline execution.
  • Execute only: Performs full execution of the Snap during Pipeline execution; does not execute the Snap during Pipeline validation.
  • Disabled: Disables the Snap and, by extension, its downstream Snaps.

Execute only

Validate & Execute



You have an empty field in the Field name/value field for the Customized header.

The Field name/value field must not be empty for the Customized header.

Enter a valid Field name/value for the Customized header.

API object does not exist.

Allowed API object format is <API ID>(Description).

Locate and select an API Object from the drop-down list.

Entity does not exist.

The entered Entity is not found in the SAP S/4HANA server.

Locate and select the Entity from the drop-down list.

The input payload is not found.

The input payload is not found.Fetch an input payload via Input Schema or input with the root key node Payload.

The input payload should be a JSON object.

The input payload is not passed as a JSON object. 

Ensure that the input payload coming from the upstream Snap is a JSON object.

Additional Information

Here is some information to assist you while using the SAP S/4HANA Create Snap.

Snap General Behavior 

The SAP S/4HANA Create Snap supports the following:

  • POST operation to create new data in the SAP S/4HANA On-Premise instance.
  • Customized HTTP Header. For more information, see Using Customized Headers (in SAP S/4HANA Read Snap).
  • Display of only the create-compatible input parameter set from the upstream input Snap.
  • Dynamic loading of API metadata with a Parent-child dependency structure. This means that you can:
    • Select an API object from the API Object field to view only entities that are related to the API object and support POST queries (create operations).
    • And then, select an entity to view and specify values for only create-compatible parameters related to this entity, in the input schema.

Input schema

The input schema for SAP S/4HANA Create Snap is divided into two parts: CustomizedHeader and Payload.

  • You can define customized headers for your HTTP requests using either the CustomizedHeader schema and as expressions or Customized header fieldset to manually enter the customized header names with values. If using the CustomizedHeader schema, it is mandatory to define the name and values as expressions to ensure the names and values provided are delivered to the API.  
  • Use the Payload schema for SAP S/4HANA Create Snap to define the input payload for an API call. This dynamically loads and represents all the parameters that you need for creating the data object (payload). 
    • If the upstream Snap can display the entire input schema like Mapper Snap, always select the Payload object in the schema to define your input payload in that Snap.
    • If your input payload is a JSON object, ensure that the text Payload is included as the key in the parent of your input.

Schema settings

Parameter Name  
Data Type
Default Value



Add customized HTTP request header to implement specific HTTP requests. 





The field name of the customized HTTP request header.N/AIf-Match


StringThe field value of the customized HTTP request header. N/AW/"'82F636DC08F14D22260CE67E505C231D0D2ACD95'"


ObjectSpecify the input data parameters for the selected entities.N/AN/A

Using Customized Headers

See Using Customized Headers (in SAP S/4HANA Read Snap).


Create New Customer Material Data in SAP S/4HANA Instance

This Pipeline example demonstrates using a SAP S/4HANA Create Snap to create new material data at the SAP S/4HANA On-Premise instance.

The example assumes that you have configured and authorized a valid SAP S/4HANA Account (see Configuring SAP S/4HANA Accounts).

Download this Pipeline.

 SAP S/4HANA Create Snap

The following settings are defined for the SAP S/4HANA Create Snap to add customer material data from the SAP S/4HANA On-Premise instance it accesses.

  • API objectZSD_F2499_CUSTOMER_MATERIAL_SRV_0001 (Customer Material) 
  • EntityC_CustomerMaterial_F2499

A successful validation or execution of the Snap gives the following output preview, showing the query results.

 JSON Formatter Snap

A JSON Formatter Snap is connected to the SAP S/4HANA Create Snap to read and format its output data into standard JSON format.

 File Writer Snap

A File Writer Snap is connected to the JSON Formatter Snap to save / write the JSON-formatted data into a file.


To view the output JSON file, you must SSH to the target directory and open the newly-created JSON file. The preview of the output JSON file can be seen below:


Important Steps to Successfully Reuse Pipelines

  1. Download and import the Pipeline into SnapLogic.
  2. Configure Snap accounts as applicable.
  3. Provide Pipeline parameters as applicable.

  File Modified


Aug 04, 2020 by Anand Vedam

Snap Pack History

 Click here to expand...
Release Snap Pack VersionDateType  Updates
August 2022main111 StableUpgraded with the latest SnapLogic Platform release.
4.29main108 StableUpgraded with the latest SnapLogic Platform release.
4.28main100 StableUpgraded with the latest SnapLogic Platform release.
4.27 Patchmain95 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.27main93 StableUpgraded with the latest SnapLogic Platform release.
4.26main88 StableUpgraded with the latest SnapLogic Platform release.
StableUpgraded with the latest SnapLogic Platform release.
StableUpgraded with the latest SnapLogic Platform release.

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 Latest

Enhances the SAP S/4HANA Snap Pack with the following additions:

StableUpgraded with the latest SnapLogic Platform release.


StableInitial release.

See Also