July 30, 2023

tSAPHanaInput – Docs for ESB 7.x


Executes a database query with a defined command which must correspond to the
schema definition.

tSAPHanaInput reads a database and extracts fields based
on a query. Then it passes on rows to the next component via a Main row link.

tSAPHanaInput Standard properties

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

The Standard
tSAPHanaInput component belongs to the Databases family.

The component in this framework is available in all Talend products with Big Data
and in Talend Data Fabric.

Note: This component is a specific version of a dynamic database
connector. The properties related to database settings vary depending on your database
type selection. For more information about dynamic database connectors, see Dynamic database components.

Basic settings


Select a type of database from the list and click

Use an existing connection

Select this check box and in the Component List click the relevant connection component to
reuse the connection details you already defined.

Note: 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
    view of the connection component which creates that very database

  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


Database server IP address.


Listening port number of database server.


Name of the database schema.

Username and Password

Database 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.

Schema and Edit

A schema is a row description. It defines the number of fields
(columns) to be processed and passed on to the next component. When you create a Spark
Job, avoid the reserved word line when naming the


Built-in: The schema is created
and stored locally for this component only. For more information,
Talend Studio User


Repository: The schema already
exists and is stored in the Repository, hence can be reused. For
more information, see
Talend Studio User Guide


Click Edit
to make changes to the schema. If the current schema is of the Repository type, three options are available:

  • 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

Table Name

Name of the table to be written. Note that only one table can be
written at a time.

Query Type

Either Built-in or Repository


Built-in: Fill in manually the
query statement or build it graphically using SQLBuilder.


Repository: Select the relevant
query stored in the Repository. The Query field gets accordingly
filled in.

Guess Query

Click the Guess Query button to
generate the query which corresponds to your table schema in the
Query field.

Guess schema

Click the Guess schema button to
retrieve the table schema.


Enter your database query paying particularly attention to
properly sequence the fields in order to match the schema

Advanced settings

Additional JDBC Parameters

Specify additional connection properties in the database
connection you are creating. This option is not available if you
have selected Use an existing
check box in the Basic settings.

Trim all the String/Char columns

Select this check box to remove leading and trailing whitespaces
from all the String/Char columns.

Trim column

Remove leading and trailing whitespaces from defined columns.


Clear Trim all the String/Char
check box to enable this

tStatCatcher Statistics

Select this check box to collect log data at the component

Global Variables

Global Variables

NB_LINE: the number of rows processed. This is an After
variable and it returns an integer.

QUERY: the query statement being processed. This is a Flow
variable and it returns a string.

ERROR_MESSAGE: the error message generated by the
component when an error occurs. This is an After variable and it returns a string. This
variable functions only if the Die on error check box is
cleared, if the component has this check box.

A Flow variable functions during the execution of a component while an After variable
functions after the execution of the component.

To fill up a field or expression with a variable, press Ctrl +
to access the variable list and choose the variable to use from it.

For further information about variables, see
Talend Studio

User Guide.


Usage rule

This component is standalone as it includes the SAP HANA
engine. This is a startable component that can initiate a data flow processing.


tSAPHanaInput 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
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
and context variables, see Talend Studio
User Guide.

Related scenarios

No scenario is available for the Standard version of this component yet.

Document get from Talend https://help.talend.com
Thank you for watching.
Notify of
Inline Feedbacks
View all comments
Would love your thoughts, please comment.x