tSAPDataSourceOutput Standard properties - 7.0

SAP

EnrichVersion
7.0
EnrichProdName
Talend Big Data
Talend Big Data Platform
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Open Studio for Big Data
Talend Open Studio for Data Integration
Talend Open Studio for ESB
Talend Open Studio for MDM
Talend Real-Time Big Data Platform
EnrichPlatform
Talend SAP RFC Server
Talend Studio
task
Data Governance > Third-party systems > Business applications > SAP components
Data Quality and Preparation > Third-party systems > Business applications > SAP components
Design and Development > Third-party systems > Business applications > SAP components

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

The Standard tSAPDataSourceOutput component belongs to the Business family.

The component in this framework is available in all subscription-based Talend products.

Basic settings

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.

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

 

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.

Name

Enter the name of the Data Source object into which the data will be written.

Data source type

Select the type of the Data Source system from the drop-down list.

Id

Enter the ID of the Data Source object.

Package size

Enter the package size which specifies the number of data records within a package delivered to SAP.

Source system name

Specify the name of the Data Source system.

Selection date

Specify the date used for selection in a query.

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.

Advanced settings

SAP Properties

If you need to use custom configuration for the SAP system being used, complete this table with the property or properties to be customized. For example,

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

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 is usually used as an end component of a Job or Subjob and it always needs an input link.

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.