Skip to main content Skip to complementary content

tSAPHanaBulkExec Standard Properties

These properties are used to configure tSAPHanaBulkExec running in the Standard Job framework.

The Standard tSAPHanaBulkExec component belongs to the Business family.

The component in this framework is available in all Talend products.

Basic settings


Select a type of database from the list and click Apply.

Property type Select either of the following:
  • Built-in: No property stored centrally
  • Repository: Select the repository file in which the properties are stored. The fields that follow are completed automatically using the data retrieved
Use an existing connection

Select this check box and in the Component List drop-down list, select the desired connection component to reuse the connection details you already defined.

Information noteNote: When a Job contains the parent Job and the child Job, if you need to share an existing connection between the two levels, for example, to share the connection created by the parent Job with the child Job, you have to:
  1. In the parent level, register the database connection to be shared in the Basic settings view of the connection component which creates that very database connection.

  2. In the child level, use a dedicated connection component to read that registered database connection.

For an example about how to share a database connection across Job levels, see Talend Studio User Guide.


Add the database server IP address.


Add the listening port number of DB server.


Add the table name of the database.

Username and Password

Enter the database user authentication data.

To enter the password, click the [...] button next to the password field, and then in the pop-up dialog box enter the password between double quotes and click OK to save the settings.


Enter the name of the table to be written. Note that only one table can be written at a time and that the table must exist for the insert operation to succeed.

Action on table
On the table defined, you can perform one of the following operations:
  • None: No operation is carried out.
  • Drop and create table
  • Create table: The table does not exist and gets created.
  • Create table if not exists: The table is created if it does not exist.
  • Drop table if exists and create: The table is removed if it already exists and created again.
  • Clear table: The table content is deleted. You have the possibility to rollback the operation.
  • Truncate table: The table content is deleted. You do not have the possibility to rollback the operation.

Type of table storage

This option is only available if you create (with or without drop) the database table. This option allows you to define the way the data is stored in the table. The following types of table storage organization are available:

  • Row: Data is stored in rows. It is preferable to use this table type if the majority of table access involves selecting a few records, with all attributes selected.: The table is removed and created again.

  • Column: Data is stored in columns. It is preferable to use this table type if the majority of table access will be through a large number of tuples, with only a few selected attributes.

  • History column: Creates a table with a particular transaction session type called HISTORY. Tables with session type HISTORY: The table is support time travel queries. For more information on HISTORY and time travel queries, see

A schema is a row description, it defines the number of fields to be processed and passed on to the next component. The schema is either Built-in or stored remotely in the Repository.
  • Built-In: You create and store the schema locally for this component only.

  • Repository: You have already created the schema and stored it in the Repository. You can reuse it in various projects and Job designs.

Edit Schema
Click Edit schema to make changes to the schema.
Information noteNote: If you make changes, the schema automatically becomes built-in.
  • View schema: choose this option to view the schema only.

  • Change to built-in property: choose this option to change the schema to Built-in for local changes.

  • Update repository connection: choose this option to change the schema stored in the repository and decide whether to propagate the changes to all the Jobs upon completion. If you just want to propagate the changes to the current Job, you can select No upon completion and choose this schema metadata again in the Repository Content window.

CSV file on the SAP HANA host

Specify the name of the CSV file on the SAP HANA host.

Lines terminated by

Specify the character or sequence of characters used to separate lines.

Fields terminated by

Specify the character, string or regular expression to separate fields.

Advanced settings

Additional JDBC Parameters

Specify additional JDBC parameters for the database connection created.

Error log file name

Enter the file path of the log file.

Number of rows to skip Define the specific number of rows in the import file to skip.
Date format Enter the format of the date strings that are encoded in the import data. You can enter the following values:
  • Y: year
  • MM: month
  • MON: name of the month
  • DD: day
Time format Enter the format of the timestamp strings that are encoded in the import data.
Thread size Specify the number of threads used for concurrent import.
Batch size

Define the number of records to be inserted in a commit.

tStatCatcher Statistics

Select this check box to gather the Job processing metadata at the Job level as well as at each component level.


Usage rule

Use this component to increase the performance of loading data to an SAP HANA database.


tSAPHanaBulkExec should be used to interact with the ERP part of SAP, including S4/HANA.

Dynamic settings

Click the [+] button to add a row in the table and fill the Code field with a context variable to choose your database connection dynamically from multiple connections planned in your Job. This feature is useful when you need to access database tables having the same data structure but in different databases, especially when you are working in an environment where you cannot change your Job settings, for example, when your Job has to be deployed and executed independent of Talend Studio.

The Dynamic settings table is available only when the Use an existing connection check box is selected in the Basic settings view. Once a dynamic parameter is defined, the Component List box in the Basic settings view becomes unusable.

For examples on using dynamic parameters, see Reading data from databases through context-based dynamic connections and Reading data from different MySQL databases using dynamically loaded connection parameters. For more information on Dynamic settings and context variables, see Talend Studio User Guide.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!