Skip to main content Skip to complementary content

tSAPBWInput Standard properties

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

The Standard tSAPBWInput component belongs to the Business family.

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

Basic settings

Property type

Either Built-in or Repository .

 

Built-in: No property data stored centrally.

 

Repository: Select the repository file where Properties are stored. The fields that come after are pre-filled in using the fetched data.

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.

JDBC URL

Enter the JDBC URL of the database you want to connect to. For example, enter: jdbc:jdbc4olap://server_address/database_name to connect to an SAP BW database.

Username

Enter the username for DB access authentication.

Password

Enter the password for DB access authentication.

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.

Table Name

Type in the name of the DB table.

Query Type

Either Built-in or Repository.

 

Built-in: No property data stored centrally.

 

Repository: Select the repository file where Properties are stored. The fields that come after are pre-filled in using the fetched data.

Guess Query

Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition.

Advanced settings

Trim all the String/Char columns

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

Trim column

Remove leading and trailing whitespace from defined columns.

Information noteNote:

Clear Trim all the String/Char columns to enable Trim columns in this field.

tStatCatcher Statistics

Select this check box to collect log data at the component level.

Global Variables

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

Usage rule

This component supports SQL queries for SAP BW database using a JDBC connection.

Limitation

Specific jar and dll files provided by SAP must be added to your Studio and the workstation hosting your Studio. The exact procedure varies among platforms such as 32-bit or 64-bit Windows or Linux.
  • For more information, see How to install the SAP Java Connector and the "Centralizing SAP metadata" section in Talend Studio User Guide.

  • You can find an example of how to install SAP Java connectors in Talend Help Center (https://help.talend.com) and the "Centralizing SAP metadata" section in 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 – please let us know!