tSAPTableInput Standard properties

Property Type

Either Built-In or Repository.

• Built-In: No property data stored centrally.

• Repository: Select the repository file where the properties are stored.

Use an existing connection

Select this check box and from the list displayed select the relevant connection component to reuse the connection details you have already defined.

When a Job contains a parent Job and a child Job, the list displayed presents only the connection components in the same Job level.

Server Type

Select the type of the SAP server to be connected, either Application Server or Message Server.

Client

The SAP system client ID.

UserId and Password

The user connection ID and password.

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.

Language

The language of the SAP system.

Host name

The name or IP address of the host on which the SAP server is running.

System number

The SAP system number.

This property is available only when Application Server is selected from the Server Type drop-down list.

System ID

The SAP system ID.

This property is available only when Message Server is selected from the Server Type drop-down list.

Group Name

The SAP group name.

This property is available only when Message Server is selected from the Server Type drop-down list.

Schema and Edit Schema

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

Click Edit schema 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 window.

Enter your RFC server details in the field provided.

The Studio uses the RFC server as the streaming proxy to support high volume of data extraction without the need to store information on a third-party transfer protocol such as FTP or SFTP.

This field becomes visible when you select Use the RFC server in the Advanced settings view.

Specify the number of records for each package. By default, the value displays 10000.

In case you have a value higher than 10000, for example, 12000, the Studio creates two packages - one package that contains 10000 records and another package that contains 2000 records.

This field becomes visible when you select Use the RFC server in the Advanced settings view.

Connection id

Enter the ID of the connection established by the SAP RFC server, that is, the name of the SAP connection configuration file (the extension not included).

An SAP RFC server can establish multiple SAP connections based on the SAP connection configuration files. By default, the SAP connection configuration files are stored in $TSAPS_HOME/conf/named-connectiond, where $TSAPS_HOME is the directory where the Talend SAP RFC Server has been installed. If you cannot find the desired SAP connection configuration file in the default directory, check the directory specified by the named.connections parameter in the tsap-rfc-server.properties file.

This field is available when Use the RFC server is checked in Advanced settings view.

Number of threads to extract the data from SAP

Set the number of threads for data extraction. The default is 2.

This option is available when you select the Use the RFC server option in the Advanced settings view.

Kafka topic partition count

Set the Kafka topic partition count. The default is 2.

This option is available when you select the Use the RFC server option in the Advanced settings view.

Max time to wait for more data

Set the maximum time period (in seconds) for the client to wait for more data of a Kafka topic when an error occurs. If no data is received when the period expires, the stream will be cancelled. The default is 60.

This option is available when you select the Use the RFC server option in the Advanced settings view.

Table

Enter the name of the table from which the data will be retrieved.

Filter

Enter the filter condition between double quotes. The component will read data based on this condition.

Note that the column value must be surrounded by single quotes and there must be a blank space before and after the equals sign (=) in the filter expression. For example, "MANDT = '800' AND WAERK = 'EUR' OR (FKART = 'F2' AND VBELN = '0090038989')".

Start row number

Specify the sequence number of the row from which data retrieval starts. The sequence number of the row in an SAP table starts from 0.

The default value for this field is -1, which means to read all rows in the specified table.

Max row number

Specify the maximum number of rows to retrieve data from.

The default value for this field is -1, which means to retrieve all rows that meet the filter condition.

Specify a shared destination

Select this check box and specify the shared destination in the Shared destination name field displayed. The shared destination allows the SAP components to use the shared destination on the Talend Runtime when they are executed as part of an ESB Route or ESB Data Service within the Talend Runtime container OSGi Environment.

Besides specifying the shared destination name in the component, you also need to setup the SAP DataSource for the Talend Runtime. What you need to do to define the SAP DataSource and how to configure it are described in the readme.txt provided in the Talend ESB package within the /add-ons/datasource/sap folder.

Note that if you use the component's own connection configuration, your SAP connection will be closed at the end of the component. To prevent this from happening, use a shared destination with its name specified.

Read NUMC data as String in the dynamic column

Select this option to treat data that is of NUMC type in the dynamic column as strings.

If this option is not checked, data that is of NUMC type in the dynamic column is treated as integers.

Enter your Kafka information in the fields provided.

Set max length for variable length type when api.use_z_talend_read_table parameter is true

When the length of any string and string type field is set to 0 in SAP data dictionary, you need to select this check box and in the Max length field displayed specify the maximum length of the data to be retrieved for the string and string type fields. Note that:

• This check box works only when the value of the SAP connection property api.use_z_talend_read_table is set to true.

• This maximum length will be applied to all fields of string and string type. To avoid loss of data, you need to be very careful when determining its value.

SAP Properties

This property is not visible when the Use an existing connection check box is selected.

tStatCatcher Statistics

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

Global Variables

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 + Space 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 usually used as a start component in a Job and it always needs an output link.

Support

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

Connections

Outgoing links (from this component to another):

Row: Main, Iterate

Trigger: On Subjob Ok, On Subjob Error, Run if, On Component Ok, On Component Error

Incoming links (from one component to this one):

Trigger: On Subjob Ok, On Subjob Error, Run if, On Component Ok, On Component Error

For further information about connections, see Talend Studio User Guide.

Limitation/ Prerequisites